Switch a SKU's pricing source and see it propagate to channels

Change the pricing-source switch on the default price and understand how the costing fields overwrite every sales-channel price.

1. In the admin portal the pricing-source switch is presented as two options on the SKU's default price — 'Price as Completely built unit' and 'Priced from constituent elements'.

   ✓ Am 16. Oktober 2026 im Produkt geprüft

2. Changing the pricing-source switch applies to the default price and propagates to every sales-channel price row of that SKU.

   ✓ Am 16. Oktober 2026 im Produkt geprüft

3. Four fields on a price control how a modular SKU's amount is computed rather than what the rate is: pricing_from (constituents vs design vs design_and_constituents - i.e. price built up from raw materials/components or taken from the design-level rate), cbu, exclusion_list, and override_margin. These can only be edited on the org/BU DEFAULT price - the sales-channel-level update path explicitly does not accept them. When any of them is changed on the default price, the backend finds every sales-channel price row for that SKU within the org/BU and bulk-overwrites those four fields there too, including on channel prices that are in custom mode with their own rates. So a client changing 'price from raw materials' on the master price silently flips the costing method on every dealer/channel price of that SKU, even ones they thought were independent. The rate fields (price/tax/margin/discount) are NOT touched by this propagation - only the costing behavior. If a client reports a channel quotation suddenly computing from constituents (or ignoring component costs), ask whether anyone recently edited the default price's costing settings; per-channel costing overrides are not supported.

4. SKU prices inherit in two layers. (1) Each sales-channel x price-type price starts linked to the SKU's org- or BU-level default price: until someone customizes it, no explicit price row exists and the system shows the default price (reported with actual:false). Saving custom values creates a price row whose referred_price_id points at the default price with use_referred_price=false (unlinked). Re-linking ('use default') only flips use_referred_price back to true — the custom values stay stored and reappear if unlinked again. Saving in linked mode when no row exists creates nothing. (2) For SKUs sourced from another catalog, the default price itself can be linked to the source SKU's price ('Link price to source sku' / 'Unlink price from source sku' in Manage Pricing); price resolution follows the referral chain to its end. Support translations: 'I changed the default price but one sales channel still shows the old price' means that channel/price-type combination was unlinked (custom). 'The price changed by itself' usually means the row is linked and the default — or the source SKU's price — changed upstream.

   ✓ Am 19. Oktober 2026 im Produkt geprüft