Shopify CSV Error Line Number Doesn’t Match Excel Row? How to Locate It
Shopify might report an import issue at “Line 53” while spreadsheet row 53 looks completely normal. That mismatch does not automatically mean the error is elsewhere: a CSV is a text file with records, and one spreadsheet cell can contain a newline. Your editor, a text viewer, and an importer may therefore present different numbers for the same logical row.
First identify what is being counted
| Term | What it means | Why it differs |
|---|---|---|
| Physical file line | Text between newline characters in the raw CSV | A quoted description can contain embedded newline characters |
| CSV record | One parsed product row, potentially spanning several physical lines | Correct parsing treats quoted newlines as part of one field |
| Spreadsheet row | One visible row after import into Excel or Sheets | Spreadsheet software may interpret or repair malformed data when loading |
| Shopify import message | A diagnostic tied to the file processed by Shopify | Use the exact diagnostic and preserve the exact file bytes when investigating |
Reproduce this difference with a four-column CSV
Consider this small example. The description for the first product contains a newline inside a quoted field. It is still one CSV record.
Title,URL handle,Description,SKU
Blue T-shirt,blue-tee,"First line of description
Second line of description",TEE-1
Canvas tote,canvas-tote,"A simple bag",TOTE-1The text occupies four physical lines but represents one header and two data records. A raw text editor may show the Canvas tote on line 4, while a spreadsheet correctly presents it as row 3. If you count only spreadsheet rows, you can chase the wrong product.
Try the free downloadable example file and compare a plain-text editor with a spreadsheet import preview. This is synthetic demonstration data, not a Shopify-approved catalog.
Procedure: isolate the true failing record
- Keep the exact CSV submitted to Shopify. Do not re-export it first: spreadsheet applications may silently alter encoding, quotes or line endings.
- Write down the full error, including its line number, referenced handle and whether it says ignored, illegal quoting or validation failed.
- Open the raw CSV in an editor that can show physical line numbers and invisible characters. Look around that number, not only at one line.
- Check whether preceding Description or other fields contain an opening double quote, embedded newline and correct closing quote. Two consecutive double quotes are how CSV represents a literal quote inside a quoted field.
- Identify the row's
URL handle, title and optional SKU; match that combination to the intended product. Do not rely solely on its position. - If Shopify says a line was ignored because it contained no product data, examine the Title and handle columns for that record. See ignored lines and handle collisions.
- Correct a copy, then re-run the CSV checker. Retest a small import; never overwrite your complete live catalog just to debug a few rows.
When line numbers are accurate but the data looks fine
The issue may be a semantic requirement rather than broken parsing. For example, two rows may parse correctly but carry the same option combination, or a product handle may conflict with an existing product. See variant dependencies. A parser's “no errors” result does not imply Shopify will accept every value.
The CSV checker reports source-row findings for the subset of product fields it understands. It does not reproduce every Shopify error or tell you which line Shopify's internal parser refers to when a malformed quoted cell spans multiple lines. Keep an original export, and verify against the official product CSV instructions.
Related resources
Repair stray quotes · Check CSV delimiters · Download safe practice files.
Primary source
Use the Shopify Help Center documentation for current platform requirements. SellerFile Studio does not represent Shopify and cannot guarantee your particular store's import outcome.