Compare a current Shopify export with the CSV you plan to import
A planned update file can look plausible while leaving out a variant combination that exists in the store today. Review that difference before uploading, especially when the change touches variants, options, prices, or inventory.
What this comparison catches
For each product handle, compare the current and planned Option1 Value, Option2 Value, and Option3 Value combinations. A combination present in the fresh export but absent from the proposed file deserves a deliberate decision before import. It may be an intentional removal; it may also be a row that disappeared during editing.
A practical two-file review
- Export the relevant products from Shopify immediately before preparing the update. Keep that original export unchanged.
- Use the fresh export as the baseline and the proposed update as the planned file.
- For every reported missing option combination, decide whether it is an intended removal or a missing row.
- Run a small test import on one affected product and inspect its variant count before the full update.
Run the comparison locally
Open the free Catalog Preflight checker. Choose the planned import as the main file and the current export as the optional baseline. It runs in the browser and does not upload the files, connect to Shopify, or modify a store.
The paid implementation kit includes the offline checker, an annotated sample, an import-review worksheet, and a decision guide.
Limits
This is a structural comparison, not an import simulator or recovery tool. It cannot determine whether an omission is intended, inspect a live store, restore deleted variants, or guarantee an import result. Work from copies and follow Shopify's current CSV documentation.