Shopify Product CSV Preflight Checklist: A Safer Import Workflow
The safest product CSV import begins before you upload. A file may be syntactically correct while still overwriting variants, changing prices, detaching images or misidentifying the intended product. This checklist separates structural validation, semantic review, and post-import verification so an entire catalog is not used as a test.
1. Identify the operation and use the right file type
Write down whether this is a brand-new catalog import, an update of existing products, or a location-level inventory quantity update. Product CSV and inventory CSV formats serve different purposes. Shopify's product-import documentation describes Title as the primary required column for a new simple product, while product updates require both URL handle and Title. Adding variants introduces additional dependencies. For warehouse quantities, follow the separate inventory CSV documentation instead.
2. Preserve a true backup
Export the current product catalog and store the untouched file separately. Do not keep only a copy resaved through Excel: changing column formats or sort order during editing can cause differences that are hard to reverse. Record import date, target store and the exact source system. For a supplier export, document which input fields were approved as retail prices rather than assuming its “Price” column is ready for storefront display.
3. Review the preflight matrix
| Check | Example danger | What you should verify |
|---|---|---|
| Header names | Legacy Handle and current URL handle both present | One intended meaning per column; no accidental collisions |
| Encoding / quoting | Curly quote or embedded comma shifts columns | UTF-8 text and correctly escaped quotes |
| Product handles | Different products share one handle | Groups represent one product with correct variants |
| Variant options | SKU updates omit Option1 values | Complete identifying option combinations |
| Prices | Wholesale cost mapped as retail price | Intended merchant selling amount and format |
| SKU / barcode | Leading zeros deleted by spreadsheet software | Identifiers preserved as text |
| Image URLs | Login-only supplier image or changed row order | Stable permitted public images associated with intended product |
| Product status | Unreviewed products published as active | Deliberate draft/active states and sales channels |
| Taxonomy and references | Unrecognized category, missing referenced product | Official category IDs and existing reference targets |
4. Run a local diagnostic without modifying the store
Use our free Shopify CSV checker on a copy of the intended product file. Review the warnings and export the findings. The tool supports a constrained set of columns and cannot validate Shopify's live taxonomy, product existence, image accessibility, warehouse inventory or every metafield format. Treat it as a first pass, not a platform certification.
For suppliers whose columns differ from Shopify's, use the supplier CSV converter, then verify all mapped prices and handles. A small synthetic practice kit is available if you want to learn how the checker behaves before opening a real merchant file.
5. Test a representative small batch
Do not choose only your simplest product. A meaningful test set should include a simple product, a product with variants and the most complicated product/image relationship represented in the actual catalog. Review the import preview, overwrite options and Shopify's warnings. After import, compare the expected and actual title, variant identifiers, price, status, media and inventory assignments. Record any errors verbatim for diagnosis.
6. Batch intelligently, then reconcile
If a large import is needed, divide by complete product handles, preserving all variants and image rows for each product. Do not split randomly at every N CSV text lines. After each import, check the final product and variant count. A successful upload confirmation is not a substitute for checking what actually changed in the store.
7. Know when to stop
Stop and investigate if you see unintended variant recreation, detached images, unexpected price movement, missing reference targets, or stock quantities changed in another location. Do not run repeated overwrites over the same failing data in the hope that the platform will “fix” the file.
SellerFile Studio is an independent browser-based tool suite. We do not claim to have tested every workflow in a merchant's live store. This checklist is a risk-reduction framework informed by published Shopify CSV specifications, not a guarantee of import success.
One-minute sign-off before importing
- I preserved the original catalog export separately from the working CSV.
- I selected the correct product-import workflow rather than an inventory quantity workflow.
- I reviewed all source headers, required columns and UTF-8 quoting.
- I confirmed that every product handle and variant option combination identifies the intended object.
- I verified selling prices, SKUs and image URLs against source-of-truth information.
- I understand what the import will overwrite and which product statuses will be published.
- I tested a representative small subset and examined the actual resulting products.
- I can restore or manually reverse unwanted changes if the larger import produces unexpected results.
Reference and related reading
See the line-number debugging guide, image import troubleshooting, daily variant limit explanation, and the official Shopify product CSV documentation.
Primary source
Use the Shopify Help Center documentation for current platform requirements. SellerFile Studio does not represent Shopify and cannot guarantee your particular store's import outcome.