Bundle inventory reconciliation history: what to inventory before a bundle pricing rollout

Short answer

Before a bundle pricing rollout changes bundle definitions, inventory the records that explain each bundle reconciliation: every version of each bundle definition with its effective dates, the component movements recorded by the commerce platform and the ERP, the cycle counts that exposed variances, and the approved stock corrections with their reasons. Note the span, system and owner of each, and the date old definitions or tools will be replaced. Partners collect that metadata only and introduce the person who can authorize a licensing discussion.

Visual briefFull-size diagram
A split panel: on the left a bundle edited in place keeps versions 1, 2 and 3 in one chain so past orders still point to the definition that shipped; on the right a bundle deleted and recreated at the rollout leaves past orders pointing to a definition that no longer exists.
Illustrative. How the rollout changes a bundle decides whether past stock corrections can still be explained.

Bundle history is fragile in a specific way. Inventory is not held on the bundle itself but on its components, so the only thing that connects a past order to the units it consumed is the bundle definition that was live when it shipped. A pricing rollout that rewrites those definitions can cut that link without deleting a single order. This guide explains why, gives the inventory questions for a commerce ERP integrator to ask, and shows an Illustrative inventory sheet.

Why does a bundle pricing rollout put reconciliation history at risk?

Because bundles are recipes, and a rollout often replaces the recipe rather than editing it. When the recipe goes, past orders lose the record of which components, in what quantities, they drew down.

Platform documentation shows how this happens. Shopify says bundle inventory is determined by the inventory of each product in the bundle, with the lowest-stocked component setting how many bundles can be sold, and that if a component's SKU changes the bundle must be deleted and recreated. NetSuite tracks kit/package inventory on the individual component members, and the kit record cannot display an available quantity. In both cases the stock lives on components and the bundle definition is the only bridge. A rollout that introduces new SKUs, new bundle records or a new bundling app can leave every historical order pointing at a definition that no longer exists, which is the contrast the graphic draws.

There is a second clock. Shopify's per-product adjustment history shows the last 180 days; older adjustments are analyzed in a separate report, filterable by SKU, location, staff, app and adjustment reason. Knowing which view the team relies on tells you how far back corrections can be read today.

What should be inventoried before a bundle pricing rollout affects bundle inventory reconciliation history?

The record classes, their coverage, the system and owner of each, and the date the rollout replaces definitions or tools. It helps to think in three moments.

Before the rollout. List every bundle definition that has ever been live, with component quantities and effective dates, in both systems. Note whether the commerce platform keeps prior versions or only the current one, and whether the ERP kit records carry change history. Record the years of cycle counts and adjustment registers, and the reason codes in use.

At the rollout. Ask how bundles will change: edited in place, deleted and recreated, or moved to a new bundling app. Ask which SKUs will change. Each choice decides whether past orders still point to the definition that was live when they shipped.

After the rollout. Ask what the integrator will archive from the old configuration, and who signs off on decommissioning any app or mapping table.

An Illustrative inventory sheet

Illustrative, for a fictional 180-person skincare brand selling on its own store with an ERP behind it. The sheet holds metadata only.

Record classSystemCoverageWhat the rollout does to it
Bundle definitions and versionsCommerce platformCurrent definitions only; no version historyOverwritten or recreated at the rollout
Kit records with component quantitiesERPSince 2019, with change logEdited for the new pricing
Bundling app configuration and mapping tableThird-party appSince 2022Subscription ends after the rollout
Inventory adjustments with reason codesCommerce platform and ERP180-day view in the store; full register in the ERPUnaffected, but loses its link to old definitions
Cycle counts and variance reportsERPMonthly since 2019Unaffected
Correction approvalsEmail and a ticket queueSince 2021Mailbox retention applies

The last column is the one the decision-maker needs. It turns "we are changing our bundles" into a list of what can still be explained afterwards.

What a partner should not do

Do not recommend retaining data beyond the company's retention policy, or delaying a rollout, because the history might be licensable. Raise the deadline with the owner and leave the decision to the company. Do not run reports in the client's systems for the referral. The distinction between an email archive and a backup is a useful parallel: a configuration backup restores today's setup, while an archive keeps what was true on a past date. The NetSuite inventory template shows the same metadata-only approach for an ERP.

What stays unknown until SourceX reviews it?

The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, 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.

The inventory or operations director usually knows coverage and can answer the metadata questions above. Rights to the records sit with the company, subject to any terms in its commerce platform, app and marketplace agreements that its counsel reviews. The person who can authorize a licensing discussion is the CEO, or the owner in an owner-run company.

Beyond that, a partner cannot know in advance whether buyers want this record set, what the rights review concludes, which records are selected, the offer, or any reward. The inventory and fulfillment page, the e-commerce page and the industries hub cover neighboring records.

Go deeper on bundle inventory reconciliation

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 bundle pricing rollout will overwrite years of bundle definitions and corrections, register as a partner, check the company against who qualifies, and read the program terms before you introduce the executive who can authorize the discussion.

  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 does a pricing change put inventory history at risk?

Bundle pricing rollouts often come with new bundle definitions, new SKUs or a new bundling app. If old bundles are deleted and recreated rather than edited, the link between past orders and the definition that was live at the time can disappear. That link is what explains past stock corrections.

Does every bundle variance count as an exception worth noting?

No. Routine count differences happen in every warehouse. The cases worth listing are the ones with a documented cause, an approved correction and a later check, because those show how the company reasoned about the variance.

Can a partner run a quick report in the client's ERP to size the history?

Only if that is already part of a paid engagement the client authorized for its own purposes, and even then the partner shares counts and date ranges, not the report. For the referral itself, ask the inventory director for estimates.

Sources

  1. help.shopify.com/en/manual/products/bundles/shopify-bundles
  2. help.shopify.com/en/manual/products/bundles/eligibility-and-c…
  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