CSV import errors (coming soon)

CSV import/export is coming soon and is not yet generally available. This page documents the planned CSV error-handling behavior for early testers and internal teams.

Resolve common CSV validation and import issues.

Symptom

• Import fails with header, encoding, or data type errors.

Likely causes

• Incorrect headers or missing ID columns.
• Non-UTF-8 encoding or special characters.
• Type mismatches (strings in number fields, invalid metafield types).

Steps to fix

1. Export a fresh sample CSV to compare headers.
2. Save as UTF-8 (no BOM). Avoid smart quotes and hidden characters.
3. Ensure ID/handle columns are unchanged and unique.
4. Validate numeric columns (price, compare-at) contain only digits/decimal points.
5. For metafields, confirm namespace.key and value types.
6. Re-upload and re-run Preview to verify sample rows.

Prevention

• Keep canonical headers; don’t rename columns.
• Use consistent formats for numbers and dates.

What to send support

• A redacted sample of your CSV (first 10 rows), error message, and your shop URL.

Next steps

• Review CSV basics → Map CSV columns to confirm headers/actions.
• Use Job history & rollback to see which rows failed and re-run only those rows.
• Contact support using the Support & contact checklist so your message includes the shop URL, job ID, screenshots, and CSV snippet.

Was this helpful?

Need more help? Visit the Support & contact checklist for what to include (shop URL, job ID, screenshots, CSV snippet), then email support@xyppy.com or open an issue at GitHub Issues.