# Catalog-to-order correction completeness scorecard | SourceX

Canonical: https://refer.sourcex.si/resources/catalog-to-order-correction-completeness-checklist
Last updated: 2026-11-04

A catalog-to-order-correction trail breaks when a corrected order can no longer be pinned to the product version that caused it. Seven checks show whether that has happened: coverage, product versions, publication timing, order capture, correction linkage, correction reason and the shared-identifier test. Each can be scored pass, partial or fail from a conversation with the system owners, without opening a product, order or credit memo. Three or more passes, with no fail on versions or linkage, is usually enough to discuss, even if one other check has a known gap.

This scorecard is part of the [catalog-to-order-correction records guide](/guides/chain-catalog-to-order-correction). Fill in the [metadata packet](/resources/catalog-to-order-correction-metadata-packet) first; this page scores what the packet describes.

## The seven checks, scored

Ask each question of the named owner and score the answer. "Not sure" is a partial, not a pass.

| Check | Question to ask | Pass | Partial | Fail |
|---|---|---|---|---|
| 1. Coverage | Which years does each system cover, and do they overlap? | PIM, storefront and ERP overlap for 3+ years | Overlap under 3 years, or one system replaced mid-period | No period where all three exist |
| 2. Product versions | Is every attribute change versioned, and was history ever purged? | Versioned since go-live, never purged | Versioned, purge status unknown | Values overwritten in place, or history deleted |
| 3. Publication timing | Is each sync or import run logged with a completion time, and for how long? | Per-product publish time kept for the full period | Run-level logs, or kept only recently | Not logged |
| 4. Order capture | Does the order line keep the SKU and the attributes shown at checkout? | SKU plus key attributes stored on the line | SKU only, with order timestamp and time zone | Kit or bundle SKU hides the component |
| 5. Correction linkage | Does each credit or replacement point at the original order? | System link from correction to invoice or order | Link by memo field or staff habit | No link |
| 6. Correction reason | Is the reason recorded in a field or comment that names the product data? | Reason code or comment on most corrections | Free-text reason, used inconsistently | Resolved by phone, no note |
| 7. Shared identifier | When a product changes materially, does it keep its SKU? | New SKU for material changes, or versions tied to dates | Same SKU kept, but dates allow matching | Same SKU kept, and no dated versions or logs |

## How to read a score

Count the passes, but read the fails by row, because they do not weigh the same.

- **Worth discussing:** three or more passes and no fail on any check. The chain can be rebuilt for at least part of the period.
- **Worth discussing with a known gap:** a fail on check 3 or check 6 only. The archive is strong on decisions and corrections but weak on timing or reasons; SourceX can judge whether that matters.
- **Not yet:** a fail on check 2 or check 5. Without dated product versions, or without corrections tied to orders, there is little to connect. Note the years affected; a later period may still pass.

A score is a description, not a verdict. Whether a given archive is suitable for AI training or evaluation is decided in SourceX's review.

## Check 7 in depth: one part number, two physical products

This check decides more scores than any other, so it is worth hearing what a pass and a fail sound like in practice. The test is simple: when the physical item changes, does the part number change with it?

Illustrative. A fictional fastener distributor sells a box of stainless screws under part number SS-0812. In June its supplier moves from boxes of 100 to boxes of 50, and the price drops. The product team updates the pack quantity, but the part number stays SS-0812. For the next eight days the online catalog still says 100 per box. A buyer who orders 20 boxes for a 2,000-screw job receives 1,000 screws and calls in.

| Answer the owner gives | Score | What a reviewer can later prove about the June orders |
|---|---|---|
| "Pack changes always get a new part number" | Pass | Every order line names the physical item it shipped |
| "Same number, but our item history is dated and we keep the web sync log" | Partial | Which orders fell inside the eight-day gap, by date |
| "Same number, and we only keep the current value" | Fail | Nothing: June orders look identical before and after |

A partial is common and often good enough, because dates can stand in for a new identifier. It only works when checks 2, 3, 4 and 5 hold for the same weeks, which is why check 7 is scored last.

One historical point belongs in the call. Until February 28, 2024, Akeneo offered a Published Products option that froze a released copy of an item beside the working copy. A firm that used it held, by design, two copies under one code in those years. That record of exactly what went live can help, but tying orders to the right copy takes care, so ask whether the option was switched on and when.

## An Illustrative scorecard

Illustrative. A 410-person electrical parts wholesaler, fictional, scored in one call with its PIM manager and finance lead.

| Check | Score | Note |
|---|---|---|
| 1. Coverage | Pass | PIM, storefront and ERP overlap from 2019 |
| 2. Product versions | Pass | Versioned since go-live; administrator confirms no purge |
| 3. Publication timing | Fail | Sync logs kept 14 days |
| 4. Order capture | Pass | SKU, order time and time zone on each line |
| 5. Correction linkage | Pass | Credit memos raised from the invoice |
| 6. Correction reason | Partial | Reason comment on roughly half of credit memos, per finance lead |
| 7. Shared identifier | Pass | New SKU for material changes since 2021 |

Result: worth discussing with a known gap. Without publish times, an order placed inside a sync gap can be dated only roughly for most of those years. The wholesaler's [human review and correction workflow](/guides/how-to-assess-human-review-records-and-correction-workflows) is the stronger story, and that is what the introduction should lead with. To see what a storefront-only export would miss in the same case, read [what a storefront-only export of a corrected order leaves out](/guides/catalog-to-order-correction-missing-context).

## Why each answer can come from a conversation

Each check maps to a feature the vendors document, so the owner can answer from memory of the setup rather than by pulling files. On the product side, Akeneo's help describes a version saved on each attribute, status, family, association or category edit, and separately warns that an administrator purge can leave users seeing only an item's first and latest versions: hence the purge question in check 2. On the finance side, NetSuite system notes keep a read-only log of who changed which field and when, and Adobe Commerce lets staff type a comment while raising a credit memo, which is where a reason for check 6 usually sits if anyone wrote one.

## Who owns each answer, and who authorizes the next step

Checks 1, 2 and 7 belong to the PIM manager or administrator; check 3 to the integration developer or agency; check 4 to the ecommerce manager; checks 5 and 6 to finance or customer service. None of them can authorize a licensing discussion. The CEO can, sometimes with general counsel where supplier content terms may restrict reuse, and is the introduction's sponsor.

Before introducing the sponsor, confirm the company meets the program tests: 50+ full-time employees at peak (contractors excluded), 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.

Unknown until SourceX reviews it: supplier and customer contract limits, how customer details on orders would be excluded or de-identified, which export fields actually exist, and whether the passing years are enough for a buyer. Partners never ask for or handle raw order, product or credit memo files, and this page does not imply SourceX connects to Akeneo, Adobe Commerce or [NetSuite](/systems/netsuite). Partners sign the Channel Partner Agreement before submitting introductions. Support-ticket records around the same corrections are covered in [licensing customer support data for AI](/resources/license-customer-support-data-for-ai).

## 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 wholesaler or distributor you work with scores in the worth-discussing band, [register as a partner](/register), check it against [who qualifies](/who-qualifies), and read the [program terms](/terms) before introducing its sponsor with the scorecard.

## 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/serenity-restore-a-previous-product-version
- 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/stores-sales/order-management/credit-memos/credit-memo-create
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/chapter_158644279544.html
- https://refer.sourcex.si/terms
