Bundle inventory reconciliation system map: which system holds each record and the keys that join them

Short answer

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.

Visual briefFull-size diagram
Five system nodes, the commerce platform, bundling app, ERP, warehouse system and ticket queue, with linking keys such as order number, bundle SKU plus date, component SKU, count ID and adjustment ID travelling between them to join one Illustrative case, with one join marked broken where the bundle was recreated.
Illustrative map for a fictional home-fragrance retailer. The weakest join is the bundle version, not the order.

This system map is part of the bundle inventory reconciliation guide. 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

SystemRecordLinking keyOwner
Commerce platformOrder lineOrder number plus bundle SKU and order dateEcommerce manager
Commerce platform or add-onRecipe versionBundle SKU plus effective dateEcommerce manager
Commerce platformComponent list for that versionComponent SKU and quantityEcommerce manager
ERPKit member listComponent item ID mapped to component SKUERP administrator
ERPItem fulfillment and inventory transactionOrder number, component item IDInventory director
Warehouse systemCycle countCount ID, item, location, count dateWarehouse manager
ERPInventory adjustmentAdjustment ID, reason code, approverInventory director, controller
Ticket queueInvestigation note and approvalTicket number citing the adjustment IDInventory 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:

JoinKey value in this caseFound inHolds?
Order to bundle versionOrder 48213, winter trio, Nov 12Commerce platformPartly: only the rebuilt recipe exists
Version to componentsCandle A, candle B, new candle C SKU, one eachCommerce platformYes, for the new version
Store components to ERP itemsCandle C SKU mapped to ERP item 7710Add-on lookupYes, until the app is retired
Movements across systemsOrder 48213, items 7701, 7705, 7710ERP fulfillmentYes
Count to varianceCount 2291, item 7709 (old candle C), plus 46 units, Nov 30Warehouse systemYes
Variance to correctionAdjustment 5530, reason "Kit mapping", approved by inventory directorERP and ticket 1184Yes

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 pointWhat happensAsk
Bundle recreated instead of versionedPast orders point to a definition that no longer existsAre old bundle definitions or their creation dates kept anywhere?
Mapping held in an appStore-to-ERP item mapping disappears with the subscriptionWho owns the mapping table, and is it archived?
Kits posted as one lineThe integration sends the bundle, not its components, to the ERPDoes the ERP see component movements per order?
Location not tracked on bundlesShopify bundles do not track inventory by locationAre counts compared by location or only in total?
Corrections with no reasonAdjustments cannot be linked to a causeAre reason codes and approvers required?
Adjustment history aging outShopify's per-product view shows 180 days; older items are in a separate reportWhich 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 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 shows the same joins in a single exception, and the referral brief template has a field for the weakest join. For neighboring work, see general ledger reconciliation, how to identify ecommerce operating workflows and reconciliation exceptions.

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, check the company against who qualifies and read the program terms before you introduce the inventory director's executive.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Why can't the bundle's own stock history answer the question?

Because in both systems the stock lives on the components. Shopify calculates bundle availability from component inventory, and NetSuite tracks kit inventory on component members. The bundle record holds a recipe, not a balance.

Is a 3PL's warehouse system part of the map?

Often, yes. If counts happen in a third-party warehouse, the count records and location quantities sit in its system, and the services contract decides what the brand can access and share. Note it on the map as a separate owner.

Sources

  1. help.shopify.com/en/manual/products/bundles/eligibility-and-c…
  2. help.shopify.com/en/manual/products/bundles/shopify-bundles
  3. docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/sectio…
  4. help.shopify.com/en/manual/products/inventory/adjusting-inven…
  5. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment