# Bundle inventory exception, worked case | SourceX

Canonical: https://refer.sourcex.si/guides/bundle-inventory-reconciliation-exception-examples
Last updated: 2026-11-04

The records that explain a bundle inventory exception are the ones that let someone recompute the variance from the bundle definitions that were live at the time, then follow who traced it, who approved the correction and whether the next count held. In the Illustrative case below, a gift set changed on the store but not in the ERP, a cycle count found 300 extra cleansers, and eight dated records turn an unexplained write-up into a complete, checkable decision.

This worked case belongs to the [bundle inventory reconciliation guide](/guides/workflow-bundle-inventory-reconciliation). It walks through one hard case in order, names the person and the record at each step, and ends with how a commerce ERP integrator can spot the same pattern at a client without opening any records.

## The setup: one cleanser, four ways to sell it

Illustrative. A fictional 210-person personal-care brand sells a 50 ml travel cleanser on its own and inside three bundles: a starter kit with one cleanser, a travel trio with one, and a gift set. The store runs on a commerce platform; stock and costs sit in an ERP.

Neither system holds stock on the bundle itself. Shopify's documentation says bundle inventory is determined by the inventory of each component, with the lowest-stocked one setting how many bundles can be sold. NetSuite tracks kit inventory on the individual component members, and the kit record cannot show an available quantity. So the only thing connecting a gift set order to the cleansers it used is the bundle definition that was live when it shipped. That is why this case is hard: one component, four selling paths, and two systems that each keep their own recipe.

## Step by step: what went wrong and who decided what

On February 24, merchandising decided to cut the gift set from two cleansers to one from March 1 to hit a new price point. The ecommerce manager updated the bundle on the store. Nobody updated the kit definition in the ERP.

March sales, and the cleansers each system deducted:

| March sales path | Units sold | Cleansers per unit, store | Store depletion | Cleansers per unit, ERP kit | ERP depletion |
|---|---|---|---|---|---|
| Cleanser on its own | 900 | 1 | 900 | 1 | 900 |
| Starter kit | 400 | 1 | 400 | 1 | 400 |
| Travel trio | 250 | 1 | 250 | 1 | 250 |
| Gift set | 300 | 1 | 300 | 2 | 600 |
| Total | 1,850 | Not applicable | 1,850 | Not applicable | 2,150 |

The March 31 cycle count found 300 more cleansers on the shelf than the ERP expected. That equals the gift set difference exactly: the ERP deducted 600 against 300 actually shipped.

The decisions that followed, each with its owner and record:

| Step | Date | Decision or event | Who | Record it left |
|---|---|---|---|---|
| 1 | Feb 24 | Gift set cut to one cleanser from March 1 | Merchandising lead | Planning ticket |
| 2 | Mar 1 | Store bundle saved as version 2 | Ecommerce manager | Bundle definition with effective date |
| 3 | Mar 1 to 31 | Two systems deduct different quantities | No one; automatic | Order lines and component movements |
| 4 | Mar 31 | Count shows plus 300 against the ERP | Warehouse manager | Count sheet by location |
| 5 | Apr 1 | Gap traced to the gift set kit, arithmetic attached | Inventory analyst | Investigation note |
| 6 | Apr 2 | Plus 300 correction approved, reason "Correction" | Inventory director | ERP stock adjustment with approver |
| 7 | Apr 2 | ERP kit updated, March 1 effective date noted | ERP administrator | Kit change log |
| 8 | Apr 30 | April count matches within tolerance | Warehouse manager | Count records |

## Why this sequence is useful evidence

Take away steps 1, 2 and 5 and the case becomes a 300-unit write-up with no reason. Keep them and it shows a full loop: a problem, the reasoning that found its cause, an authorized action and a checked result. That loop is what makes documented exceptions interesting for AI training and evaluation, as [exception handling data for AI agents](/guides/exception-handling-ai-agents-data) explains, and it mirrors the approval pattern in [procurement approvals and exception workflows](/guides/how-to-assess-procurement-approvals-and-exception-workflows).

Three details carry most of the value:

- **Two versions of one definition, both dated.** Without version 1 and its end date, nobody can recompute what the ERP should have deducted.
- **A correction with a named approver and a reason.** An adjustment posted with no reason looks like shrinkage reversed.
- **A later count.** Step 8 is the evidence that the diagnosis was right, not just plausible.

Reason codes can also age out of easy view. Shopify's per-product adjustment history shows the last 180 days, with older adjustments in a separate report that can be filtered by SKU, location, staff, app and reason. Whether the company still has step 6 in readable form depends on which view it relies on.

## How to recognize similar cases at a client

You do not need to see a single order to know whether a client has cases like this. Ask the inventory director, and listen for these signs:

| Ask | A promising answer | A weak answer |
|---|---|---|
| Does any component sell alone and in several bundles? | "Yes, our hero products are in most kits" | "Each bundle has its own SKUs" |
| Where are bundle definitions kept, and are old versions saved? | "In both systems, with change logs" | "We overwrite them" |
| When counts and the ERP disagree, who investigates? | "An analyst writes a note, the director approves" | "We just adjust to the count" |
| Do corrections carry reason codes? | "Yes, and a memo" | "Sometimes" |
| Is a bundle change, app switch or pricing rollout planned? | A named date | None known |

A client with mostly promising answers likely holds complete cases. The [records across systems map](/guides/bundle-inventory-reconciliation-records-across-systems) shows how each step is joined, and the [who-can-say-yes tree](/questions/who-can-license-bundle-inventory-reconciliation-records) shows whom to introduce. Partners keep discovery at metadata level: which records, how many years, which systems, who owns them.

For SourceX, an introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Whether buyers want this record set, the rights result and any offer stay unknown until SourceX reviews it. Related records are on [inventory and fulfillment](/data-types/inventory-and-fulfillment) and the [ecommerce industry page](/industries/ecommerce).

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a client's inventory director can describe cases like the gift set, with dated definitions, approved corrections and later counts, [register as a partner](/register), check the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce the decision-maker.

## Sources

- https://help.shopify.com/en/manual/products/bundles/shopify-bundles
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N2225190.html
- https://help.shopify.com/en/manual/products/inventory/adjusting-inventory/adjustment-history
- https://refer.sourcex.si/terms
