Catalog-to-order-correction metadata packet: a fill-in template for PIM, storefront and ERP records

Short answer

A referral partner can record the outline of a catalog-to-order-correction archive without opening a single record: which PIM, storefront and ERP hold the chain, since which year, which object types exist, rough volumes as ranges, who owns each system, and what nobody has checked yet. This page is the packet itself: eight fields, how to fill each one, a status code for every answer, and an Illustrative completed copy. Raw products, orders and credit memos stay locked with the company.

Visual briefFull-size diagram
A metadata packet card filling in six headings that group its eight fields (systems, years, object types, volume ranges, owners and unknowns) beside a locked stack of raw product, order and credit memo records that the packet never opens.
Illustrative packet, with the eight fields grouped under six headings. The fields describe the records; the records themselves stay locked with the company.

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.

FieldWhat to writeAsk this personNever collect
1. PIM and yearsProduct, edition if known, first year in use, what came beforePIM or product data managerProduct records or attribute values
2. Version historyWhether attribute changes are versioned, and whether history was ever purgedPIM administratorThe history itself
3. Storefront and yearsPlatform, first year, any replatforming datesEcommerce managerCatalog exports
4. Publication logWhere sync or import runs are logged and how long logs are keptIntegration developer or agencyLog files
5. ERP and correction recordsERP name and which correction objects exist (credit memo, return authorization, replacement order)Finance or operations leadCredit memos or order lines
6. Link back to the originalHow a correction points at the order it fixesOperations leadExample order numbers
7. Volume rangesProducts, orders per year and corrected orders per year, as rangesCustomer service managerExact counts from a report
8. Rights and limitsSupplier content terms, customer contract terms, privacy notices that may restrict reuseGeneral counselContracts 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.

FieldAnswerStatus
1. PIM and yearsAkeneo since 2019; supplier spreadsheets from 2014 to 2019Stated by company
2. Version historyProduct versions kept since go-live; administrator unsure whether a purge ran in 2022Unknown: needs PIM admin check
3. Storefront and yearsAdobe Commerce since 2017; earlier storefront retiredStated by company
4. Publication logAgency-run sync logs kept 30 daysStated; older runs not recoverable
5. ERP and correction recordsNetSuite; credit memos, return authorizations and replacement ordersStated by company
6. Link back to the originalMost credit memos raised from the invoice; replacement orders cite the original in a memo fieldStated, not verified
7. Volume ranges18,000 to 22,000 active products; 60,000 to 80,000 orders a year; 1,500 to 2,500 corrected orders a yearRange only
8. Rights and limitsTwo suppliers' content agreements may restrict reuse of their descriptionsUnknown 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.

  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

Can I fill in the packet myself from what I know of the client's stack?

You can draft it, but every answer should be confirmed by the person who owns that system and marked with its status. A packet full of guesses is worse than a short one that says unknown.

Should the packet include example SKUs or order numbers?

No. Identifiers of real products, customers or orders are record content. The packet describes the kind of identifier used and whether it links systems, never specific values.

Who receives the packet?

The partner shares it with SourceX when introducing the company's decision-maker, under the Channel Partner Agreement. The company can review it first, and should.

Sources

  1. help.akeneo.com/serenity-take-the-power-over-your-products/s…
  2. help.akeneo.com/serenity-take-the-power-over-your-products/s…
  3. experienceleague.adobe.com/en/docs/commerce-admin/systems/data-transfer…
  4. docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/sectio…
  5. 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