Developer disclosure: CatalogDelta is my app, published under Ethan Carter. This is an AI-assisted developer introduction, not a customer review.
If you import supplier CSVs or make bulk product edits, the import can finish while the resulting catalog still needs checking. A useful manual spot-check is to open a few changed variants and check their SKU/barcode, price versus compare-at price, description, and images. Decide first whether blank barcodes or zero prices are intentional for your products.
CatalogDelta provides a repeatable, read-only check of the active Online Store catalog after those edits. It flags missing content/identifiers, duplicate SKUs or barcodes, and unusual sale-price states. You choose the relevant policy checks. It does not upload/import your CSV, edit products, roll back changes, or certify feed/legal compliance.
- Free: up to 50 products and 100 variants, with 7 days of finding history.
- Pro: $6.99 USD/month, up to 500 products and 2,000 variants, with 30 days of history.
- Scans are started by the merchant; scheduled scans and email alerts are not included. Failed scans do not clear previous findings.
CatalogDelta on the Shopify App Store
If this matches a post-import problem you have, which check matters most to you? Please keep examples non-sensitive and do not post store credentials or customer data.
Free post-import handover checklist — copy and use without installing an app
This is for the person checking a supplier import or bulk edit after the job finishes, especially when someone else ran it. Keep the record in your own workspace; there is no need to send a catalog or credentials to me.
1. Define what should have happened
- Record the batch time, responsible person, intended products/variants and fields that were meant to change.
- Keep the dated pre-change export and original import file. An export is a reference, not a guarantee of a complete store rollback.
- List deliberate exceptions first: for example, products that legitimately have no manufacturer barcode or an intentional zero price.
2. Check the result, not only the success message
- Are the intended products and variant combinations still present? Don’t treat a matching SKU alone as proof of identity.
- Compare the intended price changes and any compare-at values on the affected variants.
- Check images, descriptions and identifiers that were supposed to stay unchanged.
- Inspect a customer-facing example where relevant; an admin/import preview is not the same as a storefront check.
- Keep skipped, failed and unverified items separate from verified items. A partial check should not be reported as a clean batch.
3. Leave an exception register the next person can act on
Copy this header into your notes or sheet:
Batch | Item/variant reference | Check | Expected result | Observed result | Owner | Next action | Rechecked at
For repeated checks, add a state:
- NEW: first detected within the comparison history.
- RECURRENT: detected, absent on a completed check, then detected again. Inspect the upstream process as well as the individual field.
- RESOLVED: no longer detected on the completed check. Confirm the scope and policy didn’t simply change.
Keep unresolved findings even when the latest comparison says “nothing new.” No new changes is not the same as no remaining issues.
Shopify’s CSV documentation explains dependent variant columns and why removing a column is not always a harmless edit.
Developer disclosure: I build CatalogDelta. This is an AI-assisted, tool-independent checklist, not a customer result, a full backup procedure or a promise to catch every catalog problem. It is free to copy; no signup or review is required.