FICTIONAL SAMPLE · REVIEW HANDOVER
A missing exact match needs an explanation.
This sample shows the deliverable for an export-based catalogue review: a queue of findings, each tied to its source records, with decisions left open where the files do not settle them.
Every product, SKU and image address here is fictional. These are test cases, not customer results. No store was connected or changed.
What is in the sample
29 Amazon offer records contain 26 active records and 24 distinct active seller SKUs. Two inactive records are retained separately; one unrecognized status needs review. Among active records, 12 have a published counterpart in the supplied Shopify export. The full review queue contains 24 offer records, including hints and unknown checks. The source files contain 14 issues.
These counts describe different units. A published counterpart can still have a condition conflict or another finding. The review queue also includes the unrecognized-status record.
Five decisions to work through
| Seller SKU | Evidence and finding | Proposed next action |
|---|---|---|
RF-1011 | The inventory master says refurbished; the matched Shopify variant says new. Amazon record 16 · master record 13 · Shopify record 15 | Confirm the physical item and approved condition wording, then scope a correction before the next content update. |
RF-1014 | An exact Shopify SKU exists, but an approved link points to a different Shopify SKU. | Hold the mapping. Ask the catalogue owner which variant and inventory identity are correct; do not choose automatically. |
RF-1001-FBA | A declared approved Amazon → inventory → Shopify route reaches an existing published product. | Inspect and confirm the declared route, including the additional unrecognized channel row retained for review. Do not count this row as a new product page solely because the seller SKU differs. |
RF-1002 | The matching product exists as a draft in the Shopify export. | Review its content and publication intent before creating a page or publishing it. |
0711 | The file contains Shopify SKU 711. The leading zero differs, so the values were not joined. | Ask for the intended identity. Keep the original SKU values intact until an explicit correction or mapping is approved. |
Files you can inspect
The CSV review queue is suitable for a spreadsheet. Potential formula-leading values are prefixed with an apostrophe; the JSON report preserves exact source values, file hashes, mappings and record anchors.
Acceptance for a paid audit
Agree the export versions, SKU scope and field meanings first. The handover includes the exception report, review of the agreed priority findings and one revision. A finding is accepted when it can be traced to the supplied records and its proposed next step is clear. Unknowns remain explicit.
Live publication, image quality, stock propagation and fulfilment-location behaviour require a separate check. Store edits follow a separately agreed scope.