# Bundle reconciliation system map and linking keys | SourceX

Canonical: https://refer.sourcex.si/guides/bundle-inventory-reconciliation-records-across-systems
Last updated: 2026-11-04

Reconstructing a bundle inventory reconciliation takes five joins: the order line to the bundle definition version live on the order date, that version to its component SKUs and quantities, the component movements in the commerce platform to those in the ERP (usually through a SKU-to-item lookup), the cycle count to the variance it produced, and the variance to the approved correction. The first join is the one most often missing, because a storefront usually keeps only today's recipe and seldom stores earlier ones with their dates.

This system map is part of the [bundle inventory reconciliation guide](/guides/workflow-bundle-inventory-reconciliation). It shows which system holds each record, the identifier that links it to the next, who owns it, and what one Illustrative case looks like when you follow it through every key, including the join that only partly holds.

## The systems that hold one bundle's history

A mid-size brand usually spreads bundle history across four or five places, and none of them holds the whole story.

- **Commerce platform.** Orders, bundle products and their component lists. On Shopify, bundle availability is calculated from component inventory, with untracked components left out of the calculation.
- **Middleware or add-on.** Some brands keep a lookup that translates storefront items into ERP item numbers, either in an add-on or in integration middleware. It is easy to forget because nobody opens it day to day.
- **ERP.** Kit or assembly records, item fulfillments, inventory transactions and adjustments. In NetSuite, kit inventory is tracked on the individual component members, and the kit record itself cannot show an available quantity.
- **Warehouse system or 3PL portal.** Cycle counts and on-hand by location.
- **Ticket queue or email.** The investigation notes and approvals that explain why a correction was posted.

Because the kit has no balance of its own anywhere, the reconciliation lives in the links between these places.

## Linking keys, system by system

| System | Record | Linking key | Owner |
|---|---|---|---|
| Commerce platform | Order line | Order number plus bundle SKU and order date | Ecommerce manager |
| Commerce platform or add-on | Recipe version | Bundle SKU plus effective date | Ecommerce manager |
| Commerce platform | Component list for that version | Component SKU and quantity | Ecommerce manager |
| ERP | Kit member list | Component item ID mapped to component SKU | ERP administrator |
| ERP | Item fulfillment and inventory transaction | Order number, component item ID | Inventory director |
| Warehouse system | Cycle count | Count ID, item, location, count date | Warehouse manager |
| ERP | Inventory adjustment | Adjustment ID, reason code, approver | Inventory director, controller |
| Ticket queue | Investigation note and approval | Ticket number citing the adjustment ID | Inventory analyst |

Rows 3 and 4 need a lookup whenever the storefront and the ERP use different identifiers for the same item. If that lookup lived in an add-on, it disappears when the subscription ends.

## One order followed through every join (Illustrative)

Illustrative. A fictional 240-person home-fragrance retailer sells a winter trio: three candles in one box. In October, one candle's supplier changed and the candle got a new SKU. Shopify's documentation says that when a component's SKU changes, the bundle must be deleted and recreated, so the store's winter trio was rebuilt from scratch under the same SKU, while the ERP kit simply had one member swapped.

Follow one November order through every key:

| Join | Key value in this case | Found in | Holds? |
|---|---|---|---|
| Order to bundle version | Order 48213, winter trio, Nov 12 | Commerce platform | Partly: only the rebuilt recipe exists |
| Version to components | Candle A, candle B, new candle C SKU, one each | Commerce platform | Yes, for the new version |
| Store components to ERP items | Candle C SKU mapped to ERP item 7710 | Add-on lookup | Yes, until the app is retired |
| Movements across systems | Order 48213, items 7701, 7705, 7710 | ERP fulfillment | Yes |
| Count to variance | Count 2291, item 7709 (old candle C), plus 46 units, Nov 30 | Warehouse system | Yes |
| Variance to correction | Adjustment 5530, reason "Kit mapping", approved by inventory director | ERP and ticket 1184 | Yes |

The variance on the old candle SKU only makes sense once you know the store rebuilt the recipe in October and a few early orders still pointed at the retired lookup entry. That fact lives in the rebuilt recipe's creation date and the lookup's change history, two records that are easy to lose.

## Where the chain usually breaks

| Weak point | What happens | Ask |
|---|---|---|
| Bundle recreated instead of versioned | Past orders point to a definition that no longer exists | Are old bundle definitions or their creation dates kept anywhere? |
| Mapping held in an app | Store-to-ERP item mapping disappears with the subscription | Who owns the mapping table, and is it archived? |
| Kits posted as one line | The integration sends the bundle, not its components, to the ERP | Does the ERP see component movements per order? |
| Location not tracked on bundles | Shopify bundles do not track inventory by location | Are counts compared by location or only in total? |
| Corrections with no reason | Adjustments cannot be linked to a cause | Are reason codes and approvers required? |
| Adjustment history aging out | Shopify's per-product view shows 180 days; older items are in a separate report | Which report or ERP register goes back furthest? |

None of these questions requires opening a record. An integrator can answer most of them from the integration design alone, which is why [ERP consultants](/for/erp-consultants) are often first to see whether a client's history is joinable.

## Questions to settle before an introduction

Keep discovery at metadata level: which systems, which keys, how many years, who owns each. Then confirm the basics. 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. What stays unknown until SourceX reviews it: buyer interest, the rights result, which joins survive and any offer.

The [worked gift set case](/guides/bundle-inventory-reconciliation-exception-examples) shows the same joins in a single exception, and the [referral brief template](/resources/bundle-inventory-reconciliation-referral-brief-template) has a field for the weakest join. For neighboring work, see [general ledger reconciliation](/resources/mcp/mcp-general-ledger-reconciliation), [how to identify ecommerce operating workflows](/guides/how-to-identify-ecommerce-operating-workflows) and [reconciliation exceptions](/data-types/reconciliation-exceptions-ai-agent-training-data).

## 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 can trace an order to its bundle version, its component movements and the approved correction across its systems, [register as a partner](/register), check the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce the inventory director's executive.

## Sources

- https://help.shopify.com/en/manual/products/bundles/eligibility-and-considerations
- 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
