Know who can edit prices and manage price types

Compare org-level and BU-level catalog manager rights to see who can change which prices and price types.

1. Price editing runs through a dedicated authorization check. An org-level catalog_manager can edit any price. A BU-level catalog_manager can edit (a) the BU default price when a business_unit_id is passed without a sales channel, and (b) sales-channel prices only for channels owned by a BU where they hold catalog_manager. Everything else returns UNAUTHORIZED_PRICE_UPDATE — including a BU catalog manager trying to edit org-level sales channels or the org default price. Managing price types is split: creating or renaming a price type requires the org-level catalog_manager role (BU catalog managers cannot create price types), while deleting accepts org- or BU-level catalog managers. Listing price types (get_all_of_store / get_all_of_user) has no role gate — any logged-in user of the org can read them. Price updates pass through audit logging ('price_update'), so there is a trail of who changed which price and when. If a client reports 'user gets unauthorized when saving a price', compare the user's role scope (org vs BU) with the ownership of the sales channel or default price being edited — mismatched scope is almost always the cause.

2. Sales channels can be set up so that each branch or region has its own price list, letting the same item be priced differently in each location.