01
Save the baseline before editing
Run and keep a persisted StoreCheck report from the Shopify product CSV you are actually using as the cleanup baseline. The verification flow links back to this saved report.
Shopify cleanup verification
Verify a Shopify catalog cleanup with before-and-after finding evidence.
A higher score is useful, but it is not enough. StoreCheck can link a corrected Shopify CSV to the exact saved baseline and show which findings resolved, stayed, changed but still fail, or appeared after the edit.
Current verification mode compares a corrected Shopify product CSV with its persisted StoreCheck baseline. It does not silently write the corrected data to Shopify.
What the comparison shows
Eight signals — not one reassuring score.
Health score
Compare overall score before and after, but never use the score alone as proof that every intended fix worked.
Active issues
See the count of non-ignored findings before and after the corrected CSV.
Resolved
A finding identity that existed in the baseline and no longer exists in the corrected scan.
Still present
The same rule/product/SKU/field identity remains after the edit.
Changed, still failing
The underlying field changed, but the same StoreCheck rule still fails. This is intentionally surfaced as a warning instead of being counted as resolved.
New findings
A finding identity appears in the corrected scan that was not present in the baseline.
Product count
Any before/after product-count change is highlighted so accidental additions/removals are not hidden by a better score.
Category movement
StoreCheck compares all seven category scores and highlights the categories whose score changed.
Stable finding identity
StoreCheck compares the underlying finding, not a generated row ID.
Finding identity is normalized from four stable dimensions. The current value is intentionally not part of the key, so an edit can be recognized as the same finding and surfaced as “changed, still failing.”
RuleThe StoreCheck rule that raised the finding.
ProductProduct handle first, with product ID/title fallbacks for stable product identity.
SKUVariant SKU where the finding is variant-specific.
FieldThe catalog field associated with the finding.
Six-step verification workflow
Keep the cleanup measurable from baseline to import decision.
02
Make bounded corrections
Change only the fields you intend to change. Keep a clean source copy and avoid mixing unrelated catalog restructuring into the same verification step when you want a clear before/after result.
03
Choose “Verify corrected CSV” from the report
StoreCheck opens comparison mode from the saved baseline. The corrected upload is linked server-side to that source report and kept on the same store.
04
Upload the corrected Shopify CSV
Comparison mode currently verifies a corrected Shopify product CSV. Generic spreadsheets are rejected, and connected-store live scan is intentionally not offered inside this CSV verification flow.
05
Read finding movement before importing
Review resolved, still-present, changed-still-failing, and new findings, plus score, issue, product-count, and category movement. Investigate warnings instead of treating a higher score as blanket approval.
06
Only then continue with your Shopify import workflow
If the corrected file is ready for import, follow Shopify's current import preview and overwrite guidance. StoreCheck's verification is catalog-quality evidence, not a replacement for Shopify's import validation.
CSV comparison mode
The verification page accepts the corrected Shopify CSV, keeps the baseline filename/score/issues visible, and rejects generic non-Shopify spreadsheet assumptions.
Same-store server binding
The API uses the source scan's store for the verification result instead of trusting a client-submitted store ID to move the comparison elsewhere.
Baseline availability matters
Current history retention is 7 days on Free and 90 days on Pro. Run verification while the saved source report is still available.
“Changed” is not the same as “fixed.”
If a field value changes but the same rule still fails, StoreCheck keeps it persistent and shows the before/after values. The comparison UI explicitly warns that a higher score does not make those edits safe. Product-count movement is also flagged before you treat a corrected CSV as ready to import.
Cleanup verification questions
Know exactly what a before/after result proves.
Does StoreCheck compare generated issue IDs?
No. Generated issue IDs can change between scans. StoreCheck compares active findings as a multiset using stable rule + product + SKU + field identity. Message text and current value are deliberately excluded from identity so an edited field can remain the same underlying finding.
What does “changed, still failing” mean?
The corrected scan found the same stable finding identity but the current field value changed. StoreCheck surfaces the before and after values so an attempted edit that still violates the rule is not mistaken for a resolved finding.
Can I run the verification comparison with a live Shopify scan?
Not in the current Verify corrected CSV workflow. Comparison mode accepts a corrected Shopify product CSV and hides the connected-store live-scan option. Normal connected-store scans remain available outside comparison mode.
Is verification available on Free?
Yes. Verification comparisons are enabled on Free and Pro. The baseline still has to be available: current Free history retention is 7 days and Pro retention is 90 days.
Do verification scans consume the normal Free monthly scan allowance?
StoreCheck's current monthly usage counter excludes saved scans that have a sourceScanId, because those verification scans complete an existing cleanup workflow rather than representing a new original catalog upload.
Does a better health score mean the corrected CSV is safe to import?
No. Review changed-still-failing findings, new findings, product-count movement, and the intended Shopify import behavior. StoreCheck provides catalog-quality comparison evidence; Shopify remains responsible for validating and executing the import.
Baseline before cleanup