Delimiter

A delimiter is the character that separates one field from the next in a data file. In a CSV that character is a comma. Swap it for a semicolon or a tab and the file still works, provided the reader is told. So a delimiter is really a contract between whoever wrote the file and whoever reads it.

---

Key Takeaways

• It is only a separator: The delimiter carries no meaning of its own. Consequently any agreed character will do the job.
• A comma inside a field breaks the row: Quoting exists to solve exactly that problem.
• Your locale changes the default: Still, a spreadsheet saved in some regions writes semicolons instead.
• Most import failures are the file: Delimiters and encoding cause the bulk of them, not the importer.

---

How Does A Delimiter Work?

A delimiter works by telling a reader where one value ends and the next begins. First the reader splits each line on that character. Then it matches the resulting values against the header row.

The common delimiters

Four characters cover almost every file you will meet. Each one exists for a reason.

• Comma: The default, and what CSV is actually named after.
• Semicolon: Common where the comma is used as the decimal separator.
• Tab: Useful when your own data is full of commas.
• Pipe: Rare between fields, common inside one field for lists.

So a file’s extension tells you nothing about its delimiter. In practice a .csv file full of semicolons is completely normal.

Why quoting exists

A field containing a comma would otherwise split into two fields. Quoting is the fix, and it is part of the specification rather than a workaround.

The CSV specification says a field containing line breaks, double quotes or commas should be enclosed in double quotes. Visser Labs applies the same rule in its WooCommerce import CSV guide.

Therefore a product named Bolt, 10mm survives the round trip intact. Without the quotes it arrives as two values and pushes every later column along by one.

A double quote inside a quoted field gets escaped by doubling it. Consequently a value that already contains quotes looks strange in the raw file and is still perfectly valid.

Where the delimiter meets the encoding

Still, these two get confused constantly, and they fail in different ways. A wrong delimiter scrambles your columns, while a wrong encoding scrambles your characters.

Visser’s guide is blunt about the second one. Files saved from older Excel versions default to Windows-1252, and every non-ASCII character turns to garbled bytes on import.

So a product name reading cafe with an accent arrives with two junk characters in the middle. Meanwhile the columns line up perfectly, which is exactly why nobody suspects the file.

What breaks in practice

Four failures account for most rejected imports. None of their error messages mention the delimiter.

• An unquoted comma: One row gains a column, so the import rejects it.
• A stray quote mark: Everything after it reads as one enormous field.
• A regional save: Semicolons arrive where the importer expects commas.
• A line break inside a field: One product becomes two broken rows, and the SKU lands in the wrong column.

Therefore open the file in a plain text editor before blaming the tool. The error message rarely points at the row that caused it.

How to find out what a file uses

Checking a file takes under a minute. Two methods answer the question completely.

• Open it in a text editor: The separators are visible, and so are the quote marks.
• Count the first data row: Compare its separators against the number in the header.

So a mismatch between those two counts locates the broken row immediately. In practice a spreadsheet app is the wrong tool for this. It parses the file and hides the very thing you need to see.

What Do The Numbers Say About Delimiters?

Encoding is now near-universal, which makes a mismatch a legacy problem rather than a common one. W3Techs measures UTF-8 at 99.0% of websites whose character encoding is known.

The file format has been standardized for two decades. RFC 4180 described the comma-separated format in 2005, including the quoting rules everything still follows.

Also, export tooling is well used on WooCommerce. Store Exporter, our own order export plugin, reports 6,000+ active installations.

Still, no figure tells you which delimiter your own spreadsheet just saved. In practice that answer comes from opening the file, never from a benchmark.

---

What Does A Delimiter Problem Look Like In Practice?

Here’s a hypothetical example. So picture a homewares store running a spreadsheet product import of 600 items from a supplier file.

The import that half worked

The file opens perfectly well in a spreadsheet app. First they run the import, and 540 products land correctly.

Sixty rows fail with a column-count error. Consequently they assume the importer is buggy. Meanwhile the real cause sits in 60 product names containing a comma.

After opening it as text

So they open the same file in a plain text editor. Then the problem is obvious, because those 60 rows carry one comma too many and no quotes.

Re-saving from the spreadsheet app adds the quoting automatically. Instead of fighting the importer, they fixed the file. In short, the tool was right and the data was wrong.

What the fix did not cover

Also, the supplier sends a fresh file every month. So the same 60 products break again unless the supplier changes their own export.

Therefore they wrote the requirement into the supplier’s brief. Even so, two of the next three files still arrived unquoted. Some problems are somebody else’s spreadsheet.

So they added a five-minute check to the monthly routine instead. Reading the file first turned out cheaper than re-running a failed import.

---

What’s The Difference Between A Delimiter And An Encoding?

What you’re comparing	Delimiter	Encoding
What it defines	Where a field ends	How characters are stored
Typical values	Comma, semicolon, tab	UTF-8, Windows-1252
Symptom when wrong	Columns shift or rows reject	Text turns into junk characters
Where you set it	Export or import options	When you save the file
Does the file still open	Yes, badly	Yes, and it looks fine

In practice both settings live in the same save dialog, which is why they get muddled. Still, the tell is different. Broken columns point at the delimiter, while broken accents point at the encoding.

Also, a file can carry both problems at once. So fix the encoding first, because a garbled quote mark breaks the delimiting as well.

Both matter more during a store migration than in day-to-day work. That is when one bad file becomes your entire catalog.

Therefore check both before a migration, not after it. A bad delimiter rejects rows loudly, while a bad encoding imports quietly and wrong.

---

What Are The Pros And Cons Of Changing The Delimiter?

The pros

• Fewer quoting problems: A tab almost never appears inside product data.
• It survives regional spreadsheets: Semicolons match the default in some locales.
• Easier to eyeball: Tab-separated columns line up in a text editor.

The cons

• Not every importer accepts it: Many expect a comma and offer no setting at all.
• The extension still says .csv: Consequently the next person to open it is misled.
• It hides rather than fixes: Your data still needs proper quoting eventually.

---

Frequently Asked Questions

What delimiter does a CSV file use?

A comma, which is what the name means. Plenty of tools still write semicolons or tabs into a .csv file, so the extension is no guarantee. Open the file in a text editor whenever an import fails unexpectedly.

Why did my import shift into the wrong columns?

Almost always an unquoted delimiter inside a field. A product name containing a comma splits into two values, pushing everything after it along by one. Wrapping that field in double quotes fixes it.

Can I just use a tab instead of a comma?

Often yes, if your importer offers the option. Tabs rarely appear inside product data, so quoting problems mostly disappear. Check that the tool genuinely accepts tab-separated files before committing to it.

---

Why Do Delimiters Matter?

Delimiters matter because a broken import wastes an afternoon and looks like a software fault. The file is usually the culprit, and the delimiter is usually the reason.

So knowing where to look turns a mystery into a two-minute fix. Meanwhile your supplier files stop being a monthly gamble. That matters most when the same file feeds your catalog every month.