Bundle inventory reconciliation referral brief: a blank template and a completed retailer example

Short answer

A company introduction about bundle inventory reconciliation is a one-page brief the inventory director has checked. It gives the company's size and location, the systems that hold bundle definitions, component movements and stock corrections, the years each covers, rough counts of bundles, components and corrections, the unresolved question about a component that sells alone and in several bundles, any access deadline, the records owner and the executive who can approve a discussion. It includes no orders, count sheets or exports.

Visual briefFull-size diagram
Eight blank tiles of a referral brief fill in one by one with Illustrative values for a fictional 310-person outdoor-gear retailer: headcount, systems, years of history, bundle and component counts, corrections per month, the app end date, the CEO as signer and a note that no records are shared.
Illustrative. Values describe a fictional retailer and are estimates marked as such.

This template is part of the bundle inventory reconciliation guide. Fill it after a first conversation with the inventory director. It is written for commerce ERP integrators, who usually know the systems side already and need a tidy way to hand the rest to a decision-maker.

The blank brief, field by field

Copy the fields as they are. Every entry should be short enough to read aloud and specific enough to check.

FieldWhat goes in itMark as estimate?
CompanySector, full-time headcount at peak, country, years operatingHeadcount if unsure
Business taskThe reconciliation in one sentenceNo
Record classesBundle definitions with effective dates, order lines, component movements, counts, corrections with reasons, investigation notesNo
SystemsCommerce platform, storefront add-on, ERP, warehouse system, ticket queue, by typeNo
CoverageFirst year held in each systemYes, unless from a system report
VolumeLive bundles, shared components, corrections a monthYes
Weakest joinThe link you are least sure survives, usually order line to bundle versionNo; state it as a question
Access eventA documented app end, migration or rollout date and its sourceNo
Owner and signerWho holds the records; who can approve a discussionNo
Not sharedThe list of what the brief leaves outNo

The volume field matters because stock does not live on the bundle. Shopify calculates bundle availability from the inventory of each component, and NetSuite tracks kit inventory on the component members. So "40 bundles sharing 120 components" says more about the reconciliation's difficulty than any total order count could.

The same brief, completed (Illustrative)

The values below describe a fictional retailer. They are Illustrative, not a real company, case or deal.

FieldEntry
CompanyOutdoor-gear retailer, about 310 full-time staff at peak, Canada, 15 years operating
Business taskReconciling component stock when one item sells alone and inside several bundles and kits
Record classesBundle definitions with effective dates, order lines, component movements, monthly counts, corrections with reason codes, investigation tickets
SystemsCommerce platform with a storefront add-on; ERP; warehouse system run in-house; ticket queue for stock investigations
CoverageCommerce platform since 2017; ERP since 2014; counts in spreadsheets before 2018 (director's estimate)
VolumeAbout 65 live bundles sharing 180 components; about 25 corrections a month (estimate, not verified)
Weakest joinWhether bundle definitions from before the current app can be tied to the orders that used them
Access eventStorefront add-on subscription ends when a new app goes live, planned for March 1
Owner and signerFinance owns the adjustment register; the CEO decides, with the inventory director as sponsor
Not sharedNo orders, count sheets, adjustment registers, exports, supplier names or logins

Two things make this a good example. Every number that came from memory says so. And the weakest-join field asks a question instead of claiming the history is complete.

Estimates versus verified counts

A first brief will contain estimates, and that is fine as long as each one is labeled. What matters is where a number came from, because SourceX's review will check it later.

NumberGood sourceWeak source
Years of correction historyERP adjustment register's earliest date, read by the controller"We've always done it this way"
Corrections a monthA count from the adjustment reportA guess from one busy month
Live bundlesThe commerce platform's bundle list countThe marketing calendar
Reason-code coverageShare of adjustments with a reason, from a reportAssumed

One trap: Shopify's per-product adjustment history shows only the last 180 days, while older adjustments sit in a separate report filterable by SKU, location, staff, app and reason. If someone sized correction history from the per-product view, the coverage will look shorter than it is. Ask which view the number came from.

Edits the inventory director makes before forwarding

Before the brief goes to the CEO, the inventory director should read it once and make these edits:

  • Remove names. Suppliers, the 3PL, staff and customers become counts or roles.
  • Remove costs. Unit costs and write-off values stay out; the record class is enough.
  • Confirm the signer. The CEO decides; the who-can-say-yes tree shows who else to involve.
  • Date the access event. A planned app end date with its source is real urgency; an assumed one is not.

The system map explains the joins behind the weakest-join field. For screening the company first, use the ecommerce screening worksheet or the client opportunity brief generator, and for the covering note, the warm introduction brief.

Check eligibility before sending. 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. Partners sign the Channel Partner Agreement first, and the first valid introduction within the 90-day window is credited when the company submits a verified application. Rights, buyer interest and any offer stay unknown until SourceX reviews it. More sector context is on the ecommerce industry page.

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.

When the inventory director has checked every field and marked each estimate, register as a partner, confirm the company on who qualifies and read the program terms before you send the brief to the CEO.

  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

Who should check the brief before it is sent?

The inventory director. They know whether the years, volumes and systems are right, and they can mark which numbers are estimates. The brief should be something they are comfortable forwarding to their CEO unchanged.

Can the brief mention the brand's suppliers or 3PL by name?

Leave names out. Say that counts are run by an outside warehouse or that components come from several suppliers. Names add nothing to a first review and can touch confidentiality terms.

Sources

  1. help.shopify.com/en/manual/products/bundles/shopify-bundles
  2. docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/sectio…
  3. help.shopify.com/en/manual/products/inventory/adjusting-inven…
  4. 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