A product CSV update can look harmless when it changes one field such as price or unit pricing. The risky part is that the planned file may no longer describe the same variant structure as the current catalog.
A practical safeguard is to compare two files before importing:
- Export the relevant products from Shopify immediately before editing. Keep this current export unchanged.
- Treat that export as the baseline and the proposed upload as the planned file.
- For each Handle, compare the Option1 Value, Option2 Value, and Option3 Value combinations.
- Review any combination present in the baseline but absent from the planned file. It might be an intended removal, or it might be a row that disappeared while the CSV was edited.
- Test one affected product before running the full import.
This check is especially useful when an update touches variants, options, pricing, SKU, or inventory. A total row count is not enough because a single product can occupy several rows.
I made a free browser-local comparison in Catalog Preflight: https://catalog-preflight.pages.dev/shopify-csv-preflight-checker
Choose the planned import as the main file and the fresh Shopify export as the optional baseline. It reports variant option combinations in the baseline that are missing from the planned file. The files stay in the browser; the checker does not sign in to Shopify, upload a CSV, modify a store, restore data, or guarantee an import result.
Shopify's current product CSV documentation should remain the source of truth for the columns and dependencies in your particular import. Work from copies and make a small test import first.
References:
Top comments (0)