This template is part of the catalog-to-order-correction records guide, which explains how the three systems connect. Use the packet once you know the company has the chain and want to describe it in a form SourceX can review.
The eight packet fields and how to fill each one
Each field answers a "what, how much, how long, which system, who owns it" question. None needs a login, an export or a screenshot.
| Field | What to write | Ask this person | Never collect |
|---|---|---|---|
| 1. PIM and years | Product, edition if known, first year in use, what came before | PIM or product data manager | Product records or attribute values |
| 2. Version history | Whether attribute changes are versioned, and whether history was ever purged | PIM administrator | The history itself |
| 3. Storefront and years | Platform, first year, any replatforming dates | Ecommerce manager | Catalog exports |
| 4. Publication log | Where sync or import runs are logged and how long logs are kept | Integration developer or agency | Log files |
| 5. ERP and correction records | ERP name and which correction objects exist (credit memo, return authorization, replacement order) | Finance or operations lead | Credit memos or order lines |
| 6. Link back to the original | How a correction points at the order it fixes | Operations lead | Example order numbers |
| 7. Volume ranges | Products, orders per year and corrected orders per year, as ranges | Customer service manager | Exact counts from a report |
| 8. Rights and limits | Supplier content terms, customer contract terms, privacy notices that may restrict reuse | General counsel | Contracts themselves |
An Illustrative completed packet
Illustrative. A 340-person food-service equipment distributor, fictional, described by its operations director and PIM manager in one call.
| Field | Answer | Status |
|---|---|---|
| 1. PIM and years | Akeneo since 2019; supplier spreadsheets from 2014 to 2019 | Stated by company |
| 2. Version history | Product versions kept since go-live; administrator unsure whether a purge ran in 2022 | Unknown: needs PIM admin check |
| 3. Storefront and years | Adobe Commerce since 2017; earlier storefront retired | Stated by company |
| 4. Publication log | Agency-run sync logs kept 30 days | Stated; older runs not recoverable |
| 5. ERP and correction records | NetSuite; credit memos, return authorizations and replacement orders | Stated by company |
| 6. Link back to the original | Most credit memos raised from the invoice; replacement orders cite the original in a memo field | Stated, not verified |
| 7. Volume ranges | 18,000 to 22,000 active products; 60,000 to 80,000 orders a year; 1,500 to 2,500 corrected orders a year | Range only |
| 8. Rights and limits | Two suppliers' content agreements may restrict reuse of their descriptions | Unknown until review |
Read the status column first. This packet says the history of product edits may be strong but needs one admin answer, the record of when edits went live is thin before the last month, and most fixes point back to the order they fix. That is a useful, honest description. A packet with every row marked "stated by company" and no unknowns usually means nobody checked.
For the ERP row in more depth, the metadata-only NetSuite inventory template lists per-record-type fields.
Status codes for every answer
Every row carries one of four codes. They keep the partner from filling gaps with assumptions.
- Stated by company. A named owner gave the answer from knowledge of the system.
- Stated, not verified. The owner believes it but has not looked, for example how consistently staff fill a memo field.
- Range only. A volume given as a band, which is all the packet should hold.
- Unknown. Nobody knows yet, or the answer depends on SourceX's review (rights, de-identification, buyer interest).
Never upgrade a code yourself. If the PIM manager says "probably never purged", the row says "Stated, not verified". The completeness checklist turns these codes into pass, partial or fail scores when the company wants to test the chain further.
Two fields that fail quietly
Two fields deserve a second look because vendor documentation shows where they can quietly fail. On field 2, Akeneo creates a new product version whenever attribute values, status, family, associations or categories change, recording who or what made the change, when, and the old and new values. Its help pages also note that after an administrator purges entities, users may see only a product's first and last versions. So "we use Akeneo" does not answer field 2; "versions kept since go-live, never purged" does.
On field 6, the ERP side varies by how corrections are raised. A NetSuite credit memo can be initialized from a customer, an invoice or a return authorization. One raised from the invoice or return authorization points back to it; one raised directly from the customer record may not point to any order at all. Ask which route the team normally uses.
Field 3, by contrast, rarely fails: Adobe Commerce product import and export files carry one row per product and one column per attribute, with sku the only required value, so a partner can confirm that a product identifier exists without seeing any file.
What stays outside the packet
The packet describes containers, never contents. It holds no product descriptions, no attribute values, no customer names, no order lines, no credit memo amounts and no supplier contract text. If a client offers to "just send an export so you can see", decline and note the offer in the packet as "export available on request". Partners never ask for or handle raw client records; discovery stays at metadata level, and how any records would move is decided only after SourceX's review and a signed agreement with the company. Naming Akeneo, Adobe Commerce or NetSuite here does not imply SourceX has a connector for them.
The general method behind this page is covered in how to prepare a metadata-only inventory of business systems, and the difference between describing records and cataloging them is set out in data catalog vs data inventory.
Who signs off before the packet is shared
The PIM manager, ecommerce manager and operations lead can answer the fields, but the packet should go to SourceX only with the knowledge of the CEO, who can authorize a licensing discussion and is the introduction's sponsor.
Check the company against the program tests before you send anything: 50+ full-time employees at peak (contractors excluded), documented operating history, the rights to license its 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.
Unknown until SourceX reviews it with the company: whether supplier or customer terms restrict any records, how customer details on orders would be excluded or de-identified, which export fields exist in practice, and whether the history covers enough years to be useful. Partners sign the Channel Partner Agreement before submitting introductions. More record locations are mapped on the systems hub.
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 distributor you advise can fill in all eight fields with honest status codes, register as a partner, confirm the company against who qualifies, and read the program terms before you introduce its sponsor with the packet attached.