How Listings Resolve SKUs

Storefronts and warehouses don’t always agree on what to call a SKU. A listing is how you tell DropStream that the same item goes by different names in different systems — and what to do about it. This article walks through what DropStream does on order import for each case.

The lookup

When an order arrives from a channel, DropStream takes each line item’s SKU and looks for a listing on that store with the same channel SKU. There are three possible outcomes:

1. No listing matches the SKU

DropStream sends the order line to the warehouse with the SKU exactly as the channel reported it. Nothing is translated. This is fine for any SKU where the channel and warehouse already agree.

2. The SKU matches a listing whose master is a normal product

DropStream replaces the channel SKU with the master product’s SKU on the outbound order line. The warehouse receives the master SKU regardless of what the storefront called it.

Per-channel overrides (name, weight, price, image URL, description) on the listing are used for that channel’s records; the master values are used as the default for any field the listing leaves blank.

3. The SKU matches a listing whose master is a bundle

DropStream replaces the channel SKU with the bundle’s component lines. A single line for BIKE-SET × 1 becomes E-BIKE × 1 plus E-BIKE-BATTERY × 2 on the outbound order. Quantities multiply: BIKE-SET × 3 becomes E-BIKE × 3 and E-BIKE-BATTERY × 6.

See Bundle products for the full bundle flow.

Inventory uses the same mapping

When DropStream pushes inventory back to a channel, it pushes the level for the listing’s channel SKU — not the master SKU. For bundles, the channel level is computed from the components on hand, so the number on the storefront reflects how many complete bundles you could ship.

If a SKU isn’t listed on the channel, the inventory update is pushed using the SKU as the warehouse reported it.

What this means in practice

• Channel and warehouse agree on the SKU: you don’t need a listing. The SKU passes through.
• Channel and warehouse use different SKUs for the same item: create a listing so DropStream substitutes the master SKU on outbound orders and pushes inventory under the channel SKU.
• One channel SKU should fulfill as multiple warehouse SKUs (a kit): create a bundle master product, list it on the channel under the storefront’s SKU. See Bundle products.
• The same item is sold under different SKUs on different stores: list the same master product on each store with that store’s channel SKU. The master is shared; the listings are independent.