This decision tree is part of the bundle inventory reconciliation guide. It is written for commerce ERP integrators who meet these companies through implementation work and want to route an introduction correctly. It is general information, not legal advice.
Why the inventory director is the sponsor, not the signer
The inventory director sees every part of the reconciliation: the cycle counts, the variances, the investigation notes and the corrections they approved. They can tell you how many years of counts exist and whether old bundle definitions were kept. That knowledge makes them the best sponsor.
Authority is a different question. Inventory corrections change the books, so the adjustment register is a finance record. Bundle definitions are commercial decisions owned by merchandising or ecommerce. And the records sit in systems on both sides of an integration: NetSuite, for example, tracks kit inventory on the individual component members rather than on the kit, so the ERP holds the stock history while the store holds the recipe. A licensing discussion touches all of that, which is why it needs the CEO, who can speak for company data as a whole.
Five questions that find the signer
Work through these with the inventory director. Each answer either names the signer or adds a reviewer.
| Question | If yes | If no or not sure |
|---|---|---|
| 1. Is the brand part of a group, portfolio or holding company? | Ask whether data agreements need group approval; note that approver alongside the CEO | The brand's CEO is the signer |
| 2. Does finance own the adjustment register and its retention? | The controller or CFO confirms years and rules | Ask who does; note it as unknown |
| 3. Do counts or stock sit with a 3PL? | The 3PL services contract needs reading | Counts are the brand's own records |
| 4. Did a storefront add-on or middleware hold definitions or mappings? | Check its terms and what was exported | Definitions sit in the brand's own systems |
| 5. Will the CEO take a short call? | Introduce them, with the director as sponsor | Do not submit yet; ask the director to raise it with the CEO |
The integrator's own role appears nowhere in the "yes" column. Its value is in answering question 4 and describing systems, as covered on the ERP consultants page.
Owners of each record class
| Record class | Typical owner | Their part in the decision |
|---|---|---|
| Bundle definitions and version history | Ecommerce or merchandising lead | Explains changes; does not sign |
| Kit records and component mappings | ERP administrator or integrator | Describes what exists and exports; no authority |
| Cycle counts and location quantities | Warehouse manager or 3PL | Confirms coverage; 3PL contract may limit sharing |
| Inventory adjustments with reasons and approvers | Controller or CFO | Owns the register and its retention |
| Investigation notes and approvals | Inventory director | Sponsor; knows the cases |
| Company data as a whole | CEO | Authorizes a licensing discussion |
Several of these owners can describe the same record from different angles. That helps a reviewer understand coverage, but none of it changes who may license the records.
Contracts to read before anyone says yes
Three outside agreements most often affect bundle inventory records. Each is for the company and its counsel to read, not the partner.
- 3PL services agreement. If a third-party warehouse runs the counts, the contract decides what count and location data the brand holds and may share.
- Supplier agreements. Component costs and supplier identities can be confidential. Unit movements are usually less sensitive than costs, but counsel decides.
- Storefront add-on or marketplace terms. If definitions lived in an app, check what the brand exported before cancellation. Shopify notes that a component SKU change forces a bundle to be deleted and recreated, so the store may not keep older versions; an app export or the brand's own files may be the only record of them.
Why data rights matter sets out why these questions are settled before any buyer conversation, and the comparison of AI partnerships and data licensing explains what kind of agreement is being discussed.
Left open until SourceX's rights review
The tree identifies the signer. It does not settle:
- whether the company holds the right to license each record class
- whether supplier, 3PL or app terms exclude any records
- which cost fields must be removed
- whether buyers want this record set, and on what terms
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 before submitting introductions. The metadata-only NetSuite inventory template shows how to record system facts without touching records, and the worked gift set case shows what a complete exception looks like.
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.
Once the inventory director has agreed to bring in the CEO, who can speak for the company's records, and any 3PL or app contracts are on the list for counsel, register as a partner, check the company against who qualifies and read the program terms before you make the introduction.