Understand what a price type is and how the Default one works

See how price types act as named price lists scoped to an organization and where the Default list comes from.

1. Price types are named price lists scoped to one organization. Every org gets a price type literally named 'Default' (created during store signup with default=true); it is mapped as the master admin's preferred list at both org level and default business-unit level. Additional price types (e.g. Dealer, Retail, MRP) are created from the admin portal, and the backend only allows org-level catalog managers to create or rename them. A price type does nothing by itself: it must be (a) attached to one or more sales channels — the sales-channel + price-type pair is what actually holds per-SKU prices — and (b) mapped to individual users so they can see it. The Default price type can never be deleted (the API returns CANNOT_DELETE_DEFAULT_PRICE_TYPES). When a client asks 'what is a price type / price list', explain it as a parallel set of price, tax, margin and discount values for the same catalog, switchable per user and per sales channel: the same SKU can quote differently under Retail vs Dealer without duplicating the catalog.

2. A price type is not a price by itself — it only holds per-SKU prices once it is attached to a sales channel, so the same SKU can quote differently under different channel + price-type combinations, and users must be mapped to the price type to see it.

3. A setup can begin with just the single Default price type and its sales channel.

4. Additional sales channels and price types can be created later from the admin portal when the business expands.