After repeated Shopify imports: a 3-scan example for returning catalog issues

Ask & Offer
1

Developer disclosure: I’m Ethan Carter, the developer of CatalogDelta. This is an AI-assisted workflow example using invented data, not a customer result. You can use the same approach in a spreadsheet without installing an app.

A supplier import can bring back a problem you already fixed. Treating every warning as a brand-new task hides that pattern. Here is a small example using the same variant, the same SKU requirement, and complete checks throughout:

Check What the check sees Classification Useful next action
Monday SKU is blank for the first time in the retained history NEW Confirm that a SKU is required, then correct the source/value
Tuesday, after the correction The same issue is absent RESOLVED Verify the intended fix, not just disappearance from the report
Friday, after another supplier import That same SKU issue is detected again RECURRENT Inspect the input file or mapping that may be reintroducing it

Three safeguards matter more than the labels:

  1. Keep the product/variant identity, scan scope and checking policy consistent. A disabled check, excluded product, or recreated variant can make a comparison misleading. Record those changes separately.
  2. Keep the current unresolved list alongside the changes. If an issue is present on both checks, “nothing new” does not mean “nothing wrong.”
  3. A failed or incomplete check is not proof that old issues are resolved. Wait for a complete result before closing a task.

A recurrence does not prove which app or person changed the field. It is a reason to investigate the process with your team or supplier. Nor does a clean check verify every possible import field or business requirement.

For the next real import: keep a dated reference export, complete a baseline check, make the planned change, and check again. In your handover, record a non-sensitive item reference, the issue, the intended rule/value, an owner and the next verification step. No customer records or passwords belong in that sheet.

In CatalogDelta this is a manual, read-only workflow, not automatic monitoring or repair. Free covers up to 50 products AND 100 variants with 7-day history. PRO is USD 6.99 per 30 days for up to 500 products AND 2,000 variants with 30-day history; both catalog caps apply. The example describes comparisons within retained history.

The useful test is whether your next real catalog change leads to a useful decision—not how many times you can click Scan in one sitting.

2

Hi @CheneyCHAN Welcome To Shopify Community So The NEW/RESOLVED/RECURRENT framing is a clean way to separate “is this happening” from “did we actually fix the root cause,” most merchants (and honestly most tools) collapse those into one binary status, which is exactly how the same import bug quietly comes back three months later disguised as a fresh issue.

The safeguard about scan scope/identity consistency is the one that’s easy to overlook, a product that got recreated or excluded mid-comparison can absolutely produce a false “nothing new” read, and that’s the kind of silent false negative that erodes trust in any check over time once someone eventually notices the gap.

The reference-export-before-each-import habit is solid practice even completely outside your tool, treating a supplier import like a deployment (baseline snapshot, change, verify) rather than a one-off action is the mental model that actually prevents this class of problem, the tool just makes that discipline easier to sustain consistently.