Skip to main content
Search

Why rows in a file were skipped

Last updated

After an import, the page lists the rows and cells it could not use, each with why. Download skipped rows gives the same list as a file, with the columns Row, Column, In the file, Why it was skipped.

The whole file was refused

A banner names the file and the reason, and nothing starts:

  • "This file is not saved as UTF-8." Save it as CSV UTF-8 (comma delimited) and add it again: a plain "CSV" from Excel may not be.
  • "This file is a spreadsheet workbook, not a CSV file." An .xlsx was added. Save as CSV.
  • "This file is larger than 25 MB." Delete the rows you did not change.
  • A products file on the Variants page, or the other way round.

A row was skipped

  • "The variant ID could not be read. Copy it again from an exported file." The ID column was edited or emptied.
  • "No variant in your store has this ID." The variant was deleted since the export. For orders: "No order from the last 60 days has this ID."
  • "Limit: 25 changes. Apply them." One row takes 25 changes at a time. Apply those, then import the rest.

A cell was skipped

The rest of the row is used; the cell is not.

  • "Enter true or false." for a true or false field.
  • "Enter a country's name or its two-letter code." for a country.
  • "Choose a unit: cm, mm, in or ft." for a dimension, weight or volume whose unit column holds something else.
  • A value Shopify refused, with Shopify's own reason.

Too many skipped

An import stops when too many rows are skipped, rather than stage a file that is mostly wrong. Fix the file and add it again.

Was this article helpful?