Shopify product CSV import fields and common errors

What this guide explains

Learn which Shopify product CSV fields commonly fail before running an import preflight workflow.

• Required headers and stable product handles should be checked before variant-level cleanup.
• Duplicate SKUs, invalid prices, unsupported statuses, and risky image URLs can turn one bad CSV into a messy import.
• Supplier or marketplace exports often need header mapping before they should be treated as Shopify-shaped files.

Review products as groups of variant rows

Shopify product CSVs often use repeated handles to group several variant rows. Sorting or editing one row in isolation can detach variant information from the intended product. Review each handle group together, confirm that option names and values are consistent, and make sure product-level fields appear where the import format expects them.

• Do not treat every repeated handle as an accidental duplicate.
• Check duplicate SKUs separately from legitimate multi-row products.
• Preserve blank continuation cells when the template uses them intentionally.

Use a staged import for high-impact changes

A local preflight catches deterministic file problems but cannot predict every Shopify setting, app, or existing-catalog interaction. Back up the current product export and test a small representative set when the file changes handles, variants, inventory behavior, or image associations.

• Include a simple product and a multi-variant product in the test set.
• Review Shopify's import result before sending the full file.
• Run the exact final CSV again after spreadsheet edits or re-export.

Sources and further reading

• Shopify Help Center: importing products with CSV — Official preparation, backup, product field, image, and import troubleshooting guidance.