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.
| Field | What goes in it | Mark as estimate? |
|---|---|---|
| Company | Sector, full-time headcount at peak, country, years operating | Headcount if unsure |
| Business task | The reconciliation in one sentence | No |
| Record classes | Bundle definitions with effective dates, order lines, component movements, counts, corrections with reasons, investigation notes | No |
| Systems | Commerce platform, storefront add-on, ERP, warehouse system, ticket queue, by type | No |
| Coverage | First year held in each system | Yes, unless from a system report |
| Volume | Live bundles, shared components, corrections a month | Yes |
| Weakest join | The link you are least sure survives, usually order line to bundle version | No; state it as a question |
| Access event | A documented app end, migration or rollout date and its source | No |
| Owner and signer | Who holds the records; who can approve a discussion | No |
| Not shared | The list of what the brief leaves out | No |
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.
| Field | Entry |
|---|---|
| Company | Outdoor-gear retailer, about 310 full-time staff at peak, Canada, 15 years operating |
| Business task | Reconciling component stock when one item sells alone and inside several bundles and kits |
| Record classes | Bundle definitions with effective dates, order lines, component movements, monthly counts, corrections with reason codes, investigation tickets |
| Systems | Commerce platform with a storefront add-on; ERP; warehouse system run in-house; ticket queue for stock investigations |
| Coverage | Commerce platform since 2017; ERP since 2014; counts in spreadsheets before 2018 (director's estimate) |
| Volume | About 65 live bundles sharing 180 components; about 25 corrections a month (estimate, not verified) |
| Weakest join | Whether bundle definitions from before the current app can be tied to the orders that used them |
| Access event | Storefront add-on subscription ends when a new app goes live, planned for March 1 |
| Owner and signer | Finance owns the adjustment register; the CEO decides, with the inventory director as sponsor |
| Not shared | No 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.
| Number | Good source | Weak source |
|---|---|---|
| Years of correction history | ERP adjustment register's earliest date, read by the controller | "We've always done it this way" |
| Corrections a month | A count from the adjustment report | A guess from one busy month |
| Live bundles | The commerce platform's bundle list count | The marketing calendar |
| Reason-code coverage | Share of adjustments with a reason, from a report | Assumed |
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.