# Catalog-to-order-correction records | SourceX

Canonical: https://refer.sourcex.si/guides/chain-catalog-to-order-correction
Last updated: 2026-11-04

A company connects catalog-to-order-correction records by matching each order's timestamp against two clocks: when the product attribute changed in the PIM, and when that change reached the storefront. When two catalog versions share one SKU, the order line alone cannot say which version the customer bought. Akeneo version history, Magento order dates and the ERP's correction records together can, and a partner can describe whether those clocks exist without reading any of them.

## The business task: keeping what was sold equal to what was shipped

A distributor changes product data all the time: a supplier revises a spec, a dimension is corrected, a pack size changes. Each change has to reach the storefront before customers rely on it. When it arrives late, someone orders the old description and receives the new product, and the customer service and finance teams have to decide what to do: replace, refund, credit or explain. A corrected order is a small, fully documented decision about a mismatch between a published fact and a delivered one, which is the kind of reasoning rarely found in public text.

## Where the three clocks are kept

Each system holds one part of the story, and each records time differently.

- **PIM (Akeneo).** Akeneo creates a new product version whenever attribute values, status, family, associations or categories change, and records the author or system, the timestamp, and the old and new values. That is the decision clock.
- **Storefront (Adobe Commerce, formerly Magento).** Product import and export files carry one row per product and one column per attribute, with sku as the only required value. The publication time usually lives in the sync job's own logs, not on the product. That is the publication clock, and often the weakest.
- **ERP (NetSuite in this example).** Orders, shipments and credits. NetSuite system notes record the time of a change, the user, the field and the old and new values, and cannot be edited. In the storefront, Adobe Commerce issues refunds through credit memos, which can only be created for invoiced orders, so a refund leaves its own dated record. That is the correction clock.

The product identifier joins the systems. The timestamps decide which version applies.

## How can a company connect catalog-to-order-correction records across systems?

Line up three timestamps for every corrected order: the PIM version change, the storefront publication, and the order itself.

The worked example is an Illustrative 260-person industrial supplies distributor. Product data is enriched in Akeneo, published to an Adobe Commerce storefront, and orders, shipments and credit notes run through NetSuite. On March 3 a product manager changes the wattage of a heater, SKU HX-2040, from 1500 W to 1800 W because the supplier revised the unit. Akeneo saves version 15. The storefront picks up the change on March 5.

| Order | Placed | PIM version at that moment | Storefront showing | Which version applies | Outcome |
|---|---|---|---|---|---|
| A | March 2 | 14 (1500 W) | 14 (1500 W) | 14, no conflict | Shipped as described |
| B | March 4 | 15 (1800 W) | 14 (1500 W) | Ambiguous: customer saw 14, warehouse picked 15 | Customer reports wrong wattage; corrected order |
| C | March 7 | 15 (1800 W) | 15 (1800 W) | 15, no conflict | Shipped as described |

Illustrative. The SKU, dates and versions are fictional.

Order B is the record worth having. It joins a catalog decision, a publication delay, a customer complaint and a correction. To rebuild it, the company needs all three clocks for the same two days: the Akeneo version timestamp, a sync log that shows March 5, and the NetSuite or credit memo trail for the correction.

## What breaks when two catalog versions share one product identifier

The SKU stays HX-2040 throughout, so any join on SKU alone matches order B to both versions. Only time separates them, and time is the clock most likely to be missing.

Akeneo used to offer a partial safeguard. Its Published Products feature kept a frozen published version beside an editable working copy of one product; Akeneo removed it on February 28, 2024. A company that relied on it before that date may hold a record of exactly what was published, and after it, only version history and sync logs. That date is worth noting in any description of the chain.

Three questions make the gap concrete, and none needs a record:

1. Are storefront sync jobs logged with a completion time per product, and for how long are those logs kept?
2. When a supplier revision changes a product materially, does the team create a new SKU, or keep the old one?
3. Are corrected orders tagged with a reason that names the product data, so they can be counted?

## Who should sponsor the introduction?

The CEO can authorize exploring a license of the company's own records, often with the COO or CFO as sponsor. The PIM manager and the ecommerce manager are the people who can describe the chain, and an outside PIM or commerce agency often knows the sync setup best, but none of them can authorize a license on their own.

The distributor must meet the program's tests: 50+ full-time employees at peak (contractors excluded), documented operating history, the 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.

Unknown until SourceX reviews it with the company: whether supplier content agreements restrict any product attributes, how customer details on orders are excluded or de-identified, which export fields exist in practice, and whether version history and publication logs cover enough of the period to match orders reliably. Partners never ask for or handle raw order or product files. This page does not imply that SourceX connects to Akeneo, Adobe Commerce or NetSuite. For the wider map of where records like these sit, see the [systems hub](/systems), the [NetSuite systems page](/systems/netsuite) and [what data provenance means](/proof/what-is-data-provenance). Partners sign the Channel Partner Agreement before submitting introductions.

## Go deeper on catalog-to-order-correction records

- [What a storefront-only export of a corrected order leaves out](/guides/catalog-to-order-correction-missing-context): the same Illustrative order read before and after its PIM and ERP context is added.
- [Catalog-to-order-correction metadata packet](/resources/catalog-to-order-correction-metadata-packet): the counts, date ranges, systems and owners a partner can share, with a filled Illustrative packet.
- [Catalog-to-order-correction completeness checklist](/resources/catalog-to-order-correction-completeness-checklist): a pass, partial or fail scorecard for judging whether the records are complete enough to discuss.

## 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 or manufacturer you work with keeps dated product versions and can tie corrected orders back to them, [register as a partner](/register), check the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before introducing its sponsor.

## Sources

- https://help.akeneo.com/serenity-take-the-power-over-your-products/serenity-enrich-your-product
- https://help.akeneo.com/serenity-take-the-power-over-your-products/important-update-deprecation-of-the-published-products-feature-from-akeneo-pim
- https://experienceleague.adobe.com/en/docs/commerce-admin/systems/data-transfer/data-attributes-product
- https://experienceleague.adobe.com/en/docs/commerce/payment-services/payments-checkout/manage/refunds
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/chapter_158644279544.html
- https://refer.sourcex.si/terms
