A bundle can look in stock while one of its components is nearly gone. That is how a gift set stays available after the last mug sells separately—or how a manual adjustment fixes the mug but leaves the bundle quantity untouched.

Our view at Studio Eucalipto is simple: the bundle quantity should come from the component that can make the fewest complete sets. If your catalogue uses a parent bundle SKU plus component SKUs, LedgerLeaf Pro turns that relationship into an explicit bundle rule instead of leaving your team to repeat the calculation and update every listing by hand.

Leafy’s Quick Answer

Give the bundle and every component a clear SKU, confirm that Shopify tracks the component inventory, then create a LedgerLeaf Pro bundle rule connecting the parent SKU to its component SKUs. Check the calculated quantity with a small stock example, activate the rule, and test a component sale, a bundle sale, and a restock before relying on it.

Find the component that limits the bundle

Shopify’s bundle inventory guidance uses a limiting-component calculation: divide each component’s available inventory by the quantity needed for one bundle, round down, and use the lowest result.

Imagine a gift set containing one tea tin and one mug:

  • 12 tea tins can make 12 sets;
  • 5 mugs can make 5 sets;
  • the sellable bundle quantity is 5, because the mug runs out first.

The numbers are not added together. The bundle is only complete while every required component is available. If a set needs two tea tins instead, 12 tins can make 6 sets, and the 5 mugs still limit the bundle to 5.

Why bundle quantities drift

The formula is easy; keeping every stock path aligned is the harder part. Drift usually begins when:

  • a component is sold on its own but the parent bundle SKU is not recalculated;
  • a return, stocktake, or purchase delivery adjusts one component only;
  • the bundle and components are edited independently;
  • inventory tracking is off, or a component is allowed to continue selling when out of stock.

That last setting matters. Shopify notes that an untracked component—or one configured to continue selling when unavailable—is ignored in its standard bundle availability calculation. Review those settings before diagnosing the sync rule.

Shopify’s standard bundle structure already calculates availability from its components. The LedgerLeaf workflow is for the operational relationship around your parent and component SKUs: bundles, kits, or linked listings where shared stock needs an explicit rule that your team can see and review.

Build the relationship in LedgerLeaf Pro

Start with one real bundle, not the whole catalogue. Give the parent a distinct SKU such as GIFT-TEA-01, and keep the component SKUs unique, such as TEA-EARL-100 and MUG-GRN-01. A duplicated SKU is a label collision, not a bundle definition.

Then open the Inventory workspace in LedgerLeaf Pro and create a bundle rule that connects the parent SKU with the component SKUs. For a conventional bundle, the useful behaviour is the minimum: the lowest component stock controls the parent quantity. LedgerLeaf’s current product page describes bundle rules for parent and component SKUs, plus minimum, maximum, and exact sync logic for different stock relationships.

Name the rule after the actual set so another person can understand it later. Review the selected SKUs before activation; a clean rule is easier to audit than a clever naming workaround.

Test the rule before trusting it

Use deliberately uneven stock so the expected result is obvious:

  1. Set the tea to 12 and the mug to 5; confirm the bundle becomes 5.
  2. Reduce the tea by one; the bundle should remain 5 because mugs still limit it.
  3. Reduce the mug by one; the bundle should become 4.
  4. Restock the mug and confirm the parent quantity responds as expected.
  5. Repeat the check after a real test order and the return workflow your team uses.

Leafy’s Watch-Out

Do not activate a broad SKU pattern until one small rule behaves correctly. Check missing SKUs, inventory tracking, out-of-stock settings, and every component selected in the rule first.

This is the memorable division of work: SKUs identify the items; a LedgerLeaf bundle rule keeps their stock relationship operational. Once that relationship is explicit, the bundle quantity can follow the components instead of becoming another number someone must remember to fix.