Bundle Stock Rules and Best Practices

Quick Answer

Bundle stock is calculated automatically using the formula: floor(min(S₁÷Q₁, S₂÷Q₂, …, Sₙ÷Qₙ)) where S = component stock and Q = component quantity. Always receive stock onto components, never the bundle itself.

Rule 1: Bundle Must Have Zero Stock Before Configuration

You cannot configure a bundle on a variation that already has physical stock. The variation must have zero actual quantity before the Configure Bundle option becomes available.

Why? Bundle stock is virtual — it is calculated from component stock. If a bundle had its own physical stock, it would conflict with the calculated value and lead to overselling.

Rule 2: Stock = Minimum of Component Stock ÷ Quantity

The available bundle quantity is the lowest number of complete bundles that can be assembled from all components.

Formula: floor(min(S₁÷Q₁, S₂÷Q₂, …, Sₙ÷Qₙ))

Example 1 — Multi-product bundle:

• Hoodie: 18 in stock, quantity per bundle = 1 → 18 possible
• Jogger: 24 in stock, quantity per bundle = 1 → 24 possible
• Bundle stock = min(18, 24) = 18

Example 2 — Multi-pack:

• Jogger: 24 in stock, quantity per pack = 5 → floor(24÷5) = 4 possible
• Pack stock = 4

Example 3 — Mixed quantities:

• Soap: 50 in stock, quantity per bundle = 2 → floor(50÷2) = 25
• Candle: 30 in stock, quantity per bundle = 1 → 30
• Card: 100 in stock, quantity per bundle = 1 → 100
• Bundle stock = min(25, 30, 100) = 25 (limited by soap)

Rule 3: Receive Stock on Components Only

Never receive stock directly onto the bundle SKU. Always receive stock onto the individual component SKUs. When component stock increases, the bundle stock recalculates automatically.

If you receive stock onto a bundle SKU by mistake, it creates a conflict between physical stock and calculated stock.

Rule 4: Global Search Across All Catalogues

When adding components in the Configure Bundle modal, the search field searches all catalogues simultaneously. You can use any SKU in your account as a component, regardless of which catalogue it belongs to.

Best Practices

• Name bundle SKUs clearly: Use a naming convention like BundleSKU_ProductName to easily identify bundles
• Monitor bottleneck components: The component with the lowest possible bundle count limits your entire bundle stock
• Restock strategically: Check which component is the bottleneck before placing purchase orders
• Keep component stock accurate: Since bundle stock depends entirely on component stock, regular stock checks on components are essential
• Use feeder quantities wisely: You can set feeder quantities on bundle variations for channel-specific stock control