CATALOGPROOF · WORKED SAMPLE · 3 OCTOBER 2026

What changed after a catalog update?

This synthetic two-row Shopify export illustrates an independent evidence handoff. The results below were computed by the current CatalogProof comparison engine. They are not observations about a real merchant or a payment test.

1 exact SKU matched · 4 review differences · 1 SKU absent after · 1 new SKU

SKUFindingBeforeAfterSource lineInterpretation
SH-01price_changed29.000.292 → 2Compare only exports with the same base currency. A difference may be intentional.
SH-01identifier_blank00122 → 2Review this identifier change against the intended catalog.
SH-01option_changedSmallMedium2 → 2Option values changed. Shopify documents that option edits can recreate variant IDs; verify dependent apps.
SH-02not_found_aftershirt3 → No exact SKU match in the after file. Verify export scope and SKU renames before treating this as a deletion.
SH-03new_skushirt → 3SKU exists only in the after export. This may be a new product or a renamed SKU.

What the reviewer does next

  1. Check whether $29.00 → $0.29 is the intended price for SH-01.
  2. Confirm whether the barcode change from 0012 to blank and the Small → Medium option change were intended.
  3. Check whether SH-02 was renamed SH-03 or was omitted by the second export's scope.
  4. Record each decision and re-export the files after any corrections.

What this demonstrates

The evidence packet preserves exact values, source rows and uncertainty. It does not verify live checkout, variant internal IDs, orders, redirects or actual image reachability. Those stay in the merchant's release process.

Inputs: before.csv / after.csv. Machine-readable output: findings.json / findings.csv.

Compare a pair of authorized exports in CatalogProof. Product contents stay local.