What a web-shop export of a refunded order cannot explain: catalog context read before and after

Short answer

A web-shop export loses the reasons behind a correction. Adobe's product import and export format needs only one value, the product code, with one row per item, so the file describes each item as it reads today. A refund issued after a supplier revision then looks unprovoked: the description matches what shipped, and nothing records that a buyer saw an older description first. The explanation lives elsewhere: in the product information system's change history, the publishing job's logs and the ERP's refund trail.

Visual briefFull-size diagram
A two-column table compares a standalone Magento export with the connected history for order B; the connected cells start blank and fill one by one with the version window, the two-day publication gap, the linked correction and the supplier revision reason.
Illustrative order. The export shows the catalog as it is now; the connected history shows it as the customer saw it.

This before-and-after reading belongs to the catalog-to-order-correction records guide, and borrows its fictional 260-person industrial supplies distributor. One purchase, order B for a heater, is read twice: once from the web-shop files only, once with everything around it.

Before: the refund as the web-shop files show it

Illustrative. A reviewer gets the current product file and the shop's sales history. Nothing else.

Item in the filesWhat it saysHow a newcomer reads it
Product rowHeater, rated 1800 WIt was always sold as an 1800 W unit
Order BOne line for that heaterAn ordinary purchase
Credit memo on order BRaised after a complaintDelivery damage, or a change of mind
Second orderSame item, sent freeA goodwill replacement
ReasonBlankUnknown

Adobe Commerce raises a credit memo from an invoiced order to refund all or part of it, so the money side is dated and real. What the files cannot say is why. The product row was overwritten when the rating changed, so the description this buyer actually read is gone from them.

After: the same purchase with its surrounding history

Add the three neighboring records for the same week.

  • Product information system (Akeneo here). Version 14 rated the heater at 1500 W; version 15, saved two days before order B reached the shop, rated it 1800 W, with the editor's name and both values. Akeneo creates a new version whenever values, status, family, associations or categories change, and records who or what made it.
  • Publishing logs. The new rating went live two days after it was saved, and order B was placed inside that window.
  • ERP (NetSuite here). The shipment of the newer unit, the complaint, the credit and the replacement, each change stamped by system notes that record time, user, field and old and new values, and cannot be edited.
  • Change comment. Supplier revision.

Now the purchase has a cause (the supplier changed the unit), a lag (publishing ran behind the edit), a mismatch (the buyer read 1500 W and received 1800 W) and a remedy (credit plus replacement).

What is lost and where that context lives

Missing from the web-shop filesWhere it survivesHow it can vanish
The rating the buyer read when orderingVersion 14 in the product historyHistory purged or never kept
When the edit was made, and by whomVersion 15 with its editorSame as above
When the edit went livePublishing job logsLogs rotated after weeks
That order B fell inside the lagOnly the joined datesLost if either date is missing
Why the credit was raisedERP complaint and credit trailERP replaced without history
The business reasonChange comment: supplier revisionComment left blank

Illustrative. Rows describe the example, not a tested export.

Why one product code cannot hold two descriptions

The product code stays HX-2040 across both versions. A join on that code alone matches order B to either one, and the shop file holds only the newer. Dates are the only thing that separates them, and three different records hold those dates: the version history, the publishing log and the order itself. A web-shop export carries only the last.

This is also why a product catalog is not the same thing as a data inventory: the catalog describes products now, while the inventory describes what records exist and for how long. See data catalog vs data inventory, and for why origin and change history matter to a buyer, what data provenance is. Records that explain a correction, rather than just show it, are among those missing from most AI training data.

Checking for context without opening a file

Ask the ecommerce or product data manager three questions:

  1. How far back does product version history go, and is a change reason usually typed?
  2. Are publishing jobs logged per product, and for how long are the logs kept?
  3. Can a corrected order in the ERP be tied to the product change that caused it, by tag or reason code?

The pass, partial or fail version of these questions is the catalog-to-order-correction completeness checklist.

The CEO can authorize exploring a license of the company's own records, often with the COO or CFO as sponsor; the product data and ecommerce managers can describe the chain but cannot authorize it. The company needs 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 content restrictions, how customer details on orders are excluded or de-identified, which export fields exist and any offer. Partners never ask for or handle raw order or product files, and this page does not imply SourceX connects to Akeneo, Adobe Commerce or NetSuite. More: the NetSuite systems page, the ecommerce industry page and 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 keeps PIM version history and sync logs alongside its storefront and can tie corrections back to product changes, register as a partner, check it against who qualifies, and read the program terms before introducing its sponsor.

  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

Would a full Magento database backup solve this?

Only partly. A backup from the right day freezes the catalog at that moment, but it still would not hold the PIM's change reason or the ERP's correction trail. Ask whether dated backups exist, and for which years, as one more piece of context.

Do customer details need to be part of this history?

No. The useful part is the product version, the timing and the correction. How customer details on orders are excluded or de-identified is settled in SourceX's review, not by the partner.

Sources

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