Bundle Products

A bundle product is a catalog item that resolves to two or more component SKUs at fulfillment time. You configure the bundle once in DropStream; when an order arrives that contains the bundle SKU on a store where the product is listed, DropStream replaces the single bundle line with its component lines before sending the order to the warehouse — and uses the components when calculating channel inventory.

This is the right tool when your storefront sells a kit, gift set, or pre-pack under one SKU, but your warehouse picks, packs, and counts the parts individually.

How a bundle behaves

Consider a catalog product E-BIKE-BUNDLE with two components: E-BIKE × 1 and E-BIKE-BATTERY × 2. The bundle is listed on SFTP Store with the channel SKU BIKE-SET.

On the way in (orders). When SFTP Store sends an order with a line item for BIKE-SET, DropStream:

1. Looks up the storefront SKU BIKE-SET and finds it’s a listing for the catalog product E-BIKE-BUNDLE.
2. Sees that E-BIKE-BUNDLE has components configured.
3. Sends the order to the warehouse with two line items — E-BIKE × 1 and E-BIKE-BATTERY × 2 — instead of the bundle SKU.

The warehouse picks the parts; the customer-facing order on the storefront still shows the bundle.

On the way out (inventory). When the warehouse reports stock, DropStream computes how many bundles you could ship from the components on hand (limited by whichever component runs out first) and pushes that figure back to the channel as the available quantity for BIKE-SET.

Where the mapping lives

The bundle definition has two parts. Both are visible on the catalog product’s detail page:

• Bundle Components — the list of component SKUs and quantities. Defined on the master product.
• Channel Listings — the storefront SKU each channel uses to refer to the bundle. Each row is a separate per-store listing, so different channels can sell the same bundle under different SKUs (BIKE-SET on one channel, EBIKE-KIT on another).

The components and the per-channel SKUs are independent. You set the components once; you create a listing for every store you sell the bundle on.

Set up a bundle

1. Make sure each component SKU already exists in the catalog as its own product. DropStream needs each component as a master record so the warehouse can pick it and so inventory math works.
2. Create the bundle product itself — click Add Item and give it the bundle’s master SKU (the warehouse SKU you want orders to expand to, if any). Save.
3. Open the bundle product and click Actions → Edit.
4. Switch to the Components tab.
5. Add a row for each component SKU and the quantity per bundle. Click Save Changes.

1. Switch to the Listings tab. Enable the toggle for each store the bundle is sold on, and set the per-store SKU to the SKU the storefront sends in orders (for example BIKE-SET). Save.

The bundle is live the next time DropStream imports an order for that channel SKU.

Behavior to know

• The expansion only applies on stores where the bundle is listed. If a warehouse-side process or a non-listed channel sends the bundle’s master SKU directly, DropStream doesn’t unpack it.
• Components must be normal (non-bundle) products. Don’t nest a bundle inside another bundle.
• The bundle product itself does not need its own warehouse stock. Inventory is computed from the components.
• Changing components affects future orders only. Orders already imported keep the line items they were imported with.

Single-SKU to multi-SKU is the only direction

Bundles always go from one storefront SKU to multiple warehouse SKUs. There is no built-in way to combine multiple storefront SKUs into a single warehouse SKU; for that kind of mapping, use a listing so each storefront SKU resolves to the same master SKU.