How child/component SKU prices resolve across sales channels

Follow the inheritance ladder that decides which price a child or component SKU takes in your context.

1. When a SKU from another catalogue needs a price in your context — typically a component inside a parent SKU, or a subscribed publisher's SKU — it resolves down a fixed ladder, stopping at the first match.

2. (1) an explicit inheritance mapping defined for the parent SKU on the sales channel being used: the child's price is read from the mapped child sales channel, with all its price types.

3. (4) the child SKU existing in the publisher's business unit: the publisher's default price is used.

4. (5) otherwise, the default price from the child's owning organisation.

5. The answer changes whenever mappings are added or removed, or the child is added to or removed from the publisher's channel, which is why component prices can appear to change without anyone editing them directly.