# Inventory bundle history before a pricing rollout

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

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.

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 class | System | Coverage | What the rollout does to it |
|---|---|---|---|
| Bundle definitions and versions | Commerce platform | Current definitions only; no version history | Overwritten or recreated at the rollout |
| Kit records with component quantities | ERP | Since 2019, with change log | Edited for the new pricing |
| Bundling app configuration and mapping table | Third-party app | Since 2022 | Subscription ends after the rollout |
| Inventory adjustments with reason codes | Commerce platform and ERP | 180-day view in the store; full register in the ERP | Unaffected, but loses its link to old definitions |
| Cycle counts and variance reports | ERP | Monthly since 2019 | Unaffected |
| Correction approvals | Email and a ticket queue | Since 2021 | Mailbox 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](/systems/email-archive-vs-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](/resources/a-metadata-only-netsuite-inventory-template-for-company-introductions) 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](/data-types/inventory-and-fulfillment), the [e-commerce page](/industries/ecommerce) and the [industries hub](/industries) cover neighboring records.

## Go deeper on bundle inventory reconciliation

- [Bundle inventory reconciliation referral brief template](/resources/bundle-inventory-reconciliation-referral-brief-template) gives a fill-in introduction note.
- [Bundle inventory reconciliation exception examples](/guides/bundle-inventory-reconciliation-exception-examples) works through stock variances and the corrections that closed them.
- [Bundle inventory reconciliation records across systems](/guides/bundle-inventory-reconciliation-records-across-systems) is a field map of how commerce platform and ERP bundle records join.
- [Who can license bundle inventory reconciliation records](/questions/who-can-license-bundle-inventory-reconciliation-records) answers which decision-maker to introduce.

## 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](/register), check the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before you introduce the executive who can authorize the discussion.

## Sources

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