Wrong delimiter in a product import? How to fix it

Your product file looks fine, but the import puts every value in one column, splits descriptions into extra fields, or puts prices under the wrong heading. The problem may be the delimiter, the character that separates one column from another.

Check what separates the columns before changing the file. The CSV Editor can help you inspect how your CSV is arranged, then you can choose a matching option in the product import screen.

Check the delimiter before importing

1. Open the product CSV in the CSV Editor. Look at the header row and a few product rows. Check whether the values appear in separate columns or all in one.
2. Open the same file in a plain-text editor. Look between the values in the header row. Common delimiters are a comma, a semicolon, a tab, or sometimes a vertical bar. For example, SKU,Name,Price uses commas.
3. In the product importer, find its delimiter or separator choice. Select the character you saw between the fields in the file, then check the preview before continuing.
4. Compare the preview with the original file. Check a product with a long description, a price with a decimal point, and an ID that starts with zero. Confirm each value appears under the correct heading.

If the product importer does not offer a delimiter choice, use the system or application that created the file to export a version with the separator the importer expects. Keep the original unchanged until you have confirmed the new file imports correctly.

What the import preview means

Every row appears in one column

The importer probably expects a different separator from the one in the file. A comma-separated file may be interpreted as a semicolon-separated file, or the other way around. Check the first row in a plain-text editor and select the matching delimiter in the import screen.

Descriptions or names spill into extra columns

A comma or semicolon inside a product description may be getting treated as a column break. In a correctly formatted CSV, a field containing the delimiter is usually enclosed in double quotes. For example, SKU42,"Blue, small",12.99 has three fields, not four. If the quotes are missing or unmatched, ask for a fresh export or fix the quoting before import. See how quoted commas affect CSV fields.

Columns line up, but values are under the wrong headings

The delimiter may be correct, but the importer may have mapped a field to the wrong product attribute. Check its column-mapping preview. Make sure fields such as SKU, product name, description, price, and inventory quantity match the corresponding destination fields.

Commas in the file look unusual

Some files use semicolons between columns, often because commas are used for decimal values in the source region. Do not assume that every CSV uses commas. A tab-separated file may also be described as TSV. For more on this case, see what to check when a CSV uses tabs instead of commas.

Fix the delimiter problem

1. Choose the separator shown in the file. Use the import screen's preview or; if available. Check that the header and product rows split into the same number of columns.
2. Check quotes around fields that contain separators. Product names and descriptions may contain commas, semicolons, or line breaks. Those characters should not split a field when the CSV quotes are correct. If a row has an opening quote but no closing quote, the rest of the row may shift into the wrong columns.
3. Export a new copy with the expected separator. If the importer only accepts one format, export another copy from the source system using that format. Avoid replacing every comma in a text editor: some commas are part of product descriptions or prices, not column breaks.
4. Check regional list; s only if automatic detection is wrong. On Windows 11, open Control Panel › Clock and Region › Region › Additional; s and inspect List separator. On macOS, check System Settings › General › Language & Region, but note that a region change can affect date and number formats and may not change every app's CSV import behavior. Prefer selecting the delimiter in the importer rather than changing system settings.
5. Run a small test import. If the system allows it, try one or two products first. Check the saved product records, including prices, stock counts, IDs, and descriptions, before importing the full catalog.

When importing IDs such as 001284, check that the importer treats them as text if the leading zeros are important. A delimiter fix does not prevent an importer from converting IDs, dates, or prices to a different data type.

Keep the original file for comparison

Save any corrected export as a separate copy and compare it with the original before uploading it. The CSV Editor runs in your browser, and your file stays on your device.