Why manual csv to json converter fails on real files

A supplier CSV has a product title like "Hoodie, black". Split on commas and the title becomes two columns, every price after it shifts one position to the right, and nobody notices until the import fails.

You see this most often in supplier catalogues, exported analytics tables, address lists with commas inside fields. Naive splitting treats every comma as a delimiter, including the ones inside quoted fields.

What actually goes wrong

Manual handling fails in a specific way: it does not produce obviously broken output, it produces output that is almost right. Naive splitting treats every comma as a delimiter, including the ones inside quoted fields. The mistake survives review because nothing looks wrong until an importer rejects the file or a report is quietly incorrect.

A cheaper habit

Check the file before it leaves your machine. That is the entire purpose of CSV to JSON Converter — it reads the data you paste, applies the same rules an importer would, and shows the row that will break, rather than a summary of how many rows broke.

The row and column count in the summary is the cheapest sanity check there is: if a 4-column file reports 7 columns, the delimiter is wrong.

For the full picture — imports, feeds, variants, identifiers — see the pillar guide: Shopify product data management.

Try it on your own file

Open CSV to JSON Converter and paste a sample. It is free, it does not store anything, and you do not need an account. If the file is sensitive, save the page locally and run it offline.

Questions people ask

Are quoted commas handled?

Yes — RFC 4180 quoting is parsed properly, so "Hoodie, black" stays one field.

Does it keep leading zeros?

Yes, values are treated as text, so SKU 00127 stays 00127.