A practical catalog change handoff checklist
A concise checklist for agencies delivering a bulk catalog change to a client.
Before the work
Agree the catalog scope, identity key, target fields and exclusions. Export a baseline. Record which system and export method produced it in your own project records. CatalogWitness does not independently attest these facts.
During the work
Keep the approved target sheet separate from platform-specific import instructions. Preserve the original identity strings. For selected target fields, decide explicitly whether blank means a desired empty value. Split batches where blank semantics differ.
After the work
Export the same scope. Check missing and duplicate identities, intended additions, target mismatches and unexpected drift. Inspect partially applied products at field level. Re-export and rerun after correcting discrepancies.
The handoff package
Include the readable report, complete findings, machine-readable settings and file hashes. State all limitations: fields not checked, image-only records, inherited fields, live inventory changes, and unsupported platform behavior. Store original exports according to your client agreement.
Acceptance is a client decision
Do not label a clean comparison as certification of the entire store. Explain what the inputs establish and what remains outside scope. A good handoff gives the reviewer enough information to make that decision.
Source reviewed September 5, 2026: Shopify official documentation. Platform behavior can change; check current guidance before importing.
Try the worked example
The sample uses fictional catalog data. Review every finding free and download the sample evidence package.
Open CatalogWitness →