Seller guides / Product files
Six common product CSV problems and how to check them
A file can look tidy in a spreadsheet and still import incorrectly. Keep an untouched original, then check these six things in a working copy.
1. Product codes changed
Spreadsheet software may read an identifier as a number or date. A SKU such as 0042 can become 42. Long codes may appear in scientific notation. Either can make a later product match fail.
Import identifier columns as text and compare a few values with the original file. Pay particular attention to leading zeros, long barcodes and codes that resemble dates.
2. Commas split a field
A comma inside a value needs CSV quoting. For example, "Blue mug, large" is one field. Without the quotation marks, the comma can create an extra column and shift the remaining values.
Use a spreadsheet's CSV export rather than assembling rows by hand. Check fields containing descriptions, line breaks or comma-separated tags.
3. A cell looks like a formula
Spreadsheet software can interpret cells beginning with characters such as =, + or @ as formulas. ListWright rejects cells starting with those characters or a tab.
Review the source value and rewrite an affected product label as plain text where appropriate. Adding an escape character can change the value an importer receives, so inspect the exported file before using it.
4. Typographic quotes replaced CSV quotation marks
CSV field boundaries use straight double quotation marks, ". Curly quotation marks are fine inside normal product copy, but they cannot replace the straight marks that enclose a CSV field.
If you edit a raw CSV in a word processor, automatic formatting can change those boundaries. Use a spreadsheet or plain-text editor and keep the original identifiers intact.
5. The encoding does not match
An encoding mismatch can turn Café into unreadable text. Save as CSV UTF-8 and check accented characters after exporting.
Some files include a byte order mark at the beginning. An importer that does not handle it can misread the first header. If that header looks correct but is rejected, check the file's encoding and export settings.
6. The rows have different field counts
A stray comma or an unquoted line break can make a row differ from its header. Open the file with a CSV-aware tool and check the parsed rows. A description can legitimately contain a quoted line break, so the number of physical lines is not always the number of products.
Then confirm the template itself. Correct CSV formatting cannot supply a missing category, price, variant option or other marketplace requirement.
Before your next upload
- Keep an untouched backup and use the current destination template.
- Compare product identifiers and counts with the source.
- Check a row with commas, a row with accented text and a row with variants.
- Test a small batch and read its processing report.
- Inspect the resulting products before using the full file.
For ListWright's input, see the CSV format and samples. For the destination file, read the Shopify import guide or what Etsy supports.