Publish SKUs to a sales channel
Add SKUs to a channel and understand which ones get mapped, skipped or removed.
When SKUs are added to a sales channel, the platform filters the list silently instead of erroring. For a store-level channel, only SKUs that are already part of the org's inventory are mapped; for a business-unit channel, only SKUs already in that BU's inventory. Any SKU not in the corresponding inventory is dropped without a warning, and SKUs already published to the channel are skipped too (no duplicates). The call still returns success, so a client saying 'I published 50 SKUs but only 30 appear on the channel' has most likely selected SKUs that aren't in the org/BU inventory yet — they need to add those SKUs to their inventory (or to the BU) first, then publish again. Adding a whole SKU group publishes each SKU in the group under the same silent-filter rules. Removing SKUs behaves differently: if NONE of the requested SKUs are actually on the channel, the call errors with 'no SKUs removed' instead of silently succeeding; removal also deletes any channel-specific prices set for those SKUs, so re-publishing later starts with fresh pricing. Removing SKUs no longer affects serviceability for business units that had subscribed them from this channel — those business units keep their serviceability, and re-publishing the SKUs to the channel does not change it. The channel must belong to the client's own org — you cannot add or remove SKUs on a channel you merely subscribe to.
Channel availability is managed per SKU, so a SKU can be published to one sales channel even when it is not available in another, and a catalogue can be built up channel by channel over time.
Sales-channel assignment can be used to keep catalogue categories separate between locations or channels: a designer assigned only to one channel's sales channel does not see categories whose SKUs are published only in another channel.