Bundles and Kits: Stock and Pricing Setup

A bundle is several products sold under one listing at one price. On the marketplace it is a single item; in your warehouse it often is not. Bundles lift average order value, move slow sellers alongside fast ones and put two products into one shipment — and the trouble starts exactly there: one listing, several stock records. This guide covers how to calculate bundle stock, set up the SKU and barcode, price it without losing margin, and handle fulfilment and returns.

Two kinds of bundles

There are two types, and their stock logic is completely different.

• Pre-packed bundles. The products are combined into a single box with its own shelf location and count, so from a stock point of view it is an ordinary product: you sell as many as you packed. Setup is simple, but the packing labour is spent up front, and breaking a bundle means writing its pieces back into stock.
• Assembled-per-order bundles. The pieces sit separately and are picked together when an order arrives, so the same product can sell on its own and inside several bundles. But its stock is a derived number, and a wrong derivation means selling what you do not have.

Most sellers end up with the second type, and that is where the weight of this guide sits.

Calculating bundle stock

For an assembled bundle there is one rule: divide each component's available stock by the quantity it contributes, then take the smallest result. In a two-piece bundle with 40 units of one item and 7 of the other, bundle stock is 7 — the 40 units are useless to this listing.

Three details make or break this:

• The weakest link is the ceiling. When one component runs out, the bundle runs out. Set low-stock alerts at component level, not on the bundle listing, so the warning comes from the piece that actually constrains you — see low stock alerts and days of stock.
• The same unit appears in several listings. A component listed on its own and inside two bundles is advertised three times. Treat those listings as independent and you will sell stock you do not have — the classic source of overselling, explained in inventory sync and overselling.
• One sale moves several listings. When a bundle sells, stock changes for every listing its components appear in, on every channel. Trigger updates at component level, not per listing.

Bundle stock, in other words, is not something you maintain by hand. Components belong in one shared pool, and the bundle quantity is derived from it.

SKU and barcode setup

A bundle is a catalogue record of its own, and getting it right makes everything after it easier:

1. Give the bundle its own SKU and keep the code readable — base product code, a "BDL" marker, the piece count. A random code means nobody knows what is inside six months from now.
2. Keep the component list in one place: which SKU, how many of each. This is the recipe that both the stock calculation and the pick list read from.
3. Issue the bundle its own barcode. Reusing a component's code puts the wrong item on the scanner at receiving and on returns; the rules are in the GS1 and EAN barcode guide.
4. If the bundle has variants, build the matrix from the start: every size or colour combination is a separate bundle SKU with its own recipe, as in variant management.
5. Verify the mapping channel by channel, using the method in product matching with SKUs and barcodes. If you do not know which code the listing is tied to, stock and price land on the wrong record.

Bundles also carry a content load: piece count in the title, full list in the description, every piece visible in one image. A buyer who cannot tell what is in the box either does not buy or returns it.

Pricing: how deep can the bundle discount go?

A bundle sells because it costs less than the pieces bought separately — but the discount is not open-ended. Rather than pricing by feel, build the bundle its own cost floor.

Start with component costs plus packing labour, then add the channel's deductions; because the bundle's price is higher, the commission is larger in absolute terms too — see how marketplace commissions and fees are calculated. Shipping usually favours the bundle — two items, one parcel — but volumetric weight rises, and with bulky pieces that advantage disappears. Put shipping in as an amount, not a percentage.

Once the floor is set, do not let the system go below it: in campaign periods a bundle caught by the same discount rule as single items can end up double-discounted and sold at a loss. See floor price rules and preventing loss-making sales.

One more check: the bundle should stay cheaper than the current sum of its pieces on the same channel. A discount on single items can quietly leave the bundle looking expensive, so revisit bundles after any price change.

Fulfilment and returns

A bundle order arrives as one line but is picked from several locations. The pick list has to show the recipe, not just the bundle name; otherwise the packer has to remember what goes inside, and a parcel that ships a piece short costs a return and a performance hit.

On returns, separate two cases. A sealed bundle goes back to the shelf after inspection. One that arrives opened or incomplete cannot be sold as a bundle: decide in advance whether you write the pieces back into stock or repack, and run those on a separate lane. The wider flow is in marketplace returns and the return portal.

Step-by-step launch checklist

1. Decide the type: pre-packed, or assembled per order.
2. Write the recipe: which SKU, how many of each.
3. Create the bundle SKU and its own barcode.
4. Derive bundle stock from components, and attach the low-stock alert to the weakest link.
5. Work out the cost, add deductions and shipping, set the floor price.
6. Prepare the content: piece count in the title, full list in the description, everything in one image.
7. Launch on one channel first and follow a few orders end to end.
8. Once verified, open the other channels and add bundles to your price-change checklist.

Do not skip step seven. Bundle setup rarely fails on the first order; it fails on the second listing that shares a component, and catching that on one channel is cheaper than on five.

How this works with Bulutegra

In the Bulutegra Integration Panel component stock sits in a single pool and reaches every channel at once, so whichever listing a component sells through, the current figure goes everywhere. Bundle recipes and component deduction are set up on the ERP side (Nebim V3, Logo, Mikro, SAP); orders are written to the ERP automatically with customer, line items, carrier and payment details, while shipping and invoicing continue in your own system. Low-stock alerts and the days-of-stock report surface the weakest link early, the price matrix puts list, sale and floor price side by side per channel, and the profitability page calculates contribution per channel using VAT, return risk and the commission model.

If you want to run bundles without breaking component stock, take a look at our solutions or request a demo.