Fix CSV encoding and delimiter problems before a Shopify import
Shopify’s CSV reference asks for comma-separated UTF-8 text with LF line feeds. Spreadsheet exports do not always produce that. Depending on regional settings, a file may use semicolons, an older text encoding or a hidden byte-order mark.
By FeedNeat · Reviewed October 27, 2026
Check the delimiter
In some regions, spreadsheet apps save CSV files with semicolons between columns, and Shopify’s reference notes that Excel exports may use other delimiters. FeedNeat tries to detect the delimiter when it reads a file and always writes comma-separated output. If every value still lands in one wide column, re-export the file with commas and check the quoting.
Confirm the text is UTF-8
Product names with accents or non-Latin scripts should look correct in a plain-text editor. FeedNeat reads files as UTF-8. If names already appear as odd symbols such as Crème, the file was saved in another encoding or damaged upstream. Ask for a UTF-8 export instead of replacing characters by guesswork.
Hidden byte-order marks
Some Windows tools add an invisible byte-order mark at the start of a UTF-8 file, which can make the first header fail to match. FeedNeat removes a leading mark when reading, so the first column name is compared as you see it.
Quotes and broken rows
A value containing a comma, quote or line break must be wrapped in double quotes. One stray quote can shift every following cell. Instead of guessing, FeedNeat stops and names the record whose cell count does not match the header. Fix that record in the source and reload.
Line endings in the export
FeedNeat writes its draft export as UTF-8 text with LF line feeds, matching Shopify’s published guidance. Opening and re-saving the export in a spreadsheet can change the delimiter, encoding or identifiers again, so import the downloaded file directly where possible.
Worked example
Name;Code;Price → semicolon file; FeedNeat detects it and exports commas "Linen apron, natural" → quoted because the value contains a comma Crème → encoding already damaged; ask the supplier for UTF-8
Related guidance
- Complete pre-import checklist
- Keep leading zeros in CSV SKUs and barcodes
- Fix ambiguous prices in a supplier CSV
- Understand repeated handles in a Shopify CSV
- Map supplier CSV columns to Shopify product fields
- Draft or active? Status and publishing in a Shopify CSV
- Common Shopify CSV import errors and how to avoid them
For the destination format and field dependencies, consult the official Shopify CSV reference. FeedNeat is independent software and supports a limited subset.