Import errors

Rows that failed to import — the usual causes and how to re-import just the failures.

4 min read · Troubleshooting

Sign-in required — we'll send you straight to the right screen.

An import that finishes with errors didn't fail — it imported the good rows and flagged the bad ones. Fix the flagged rows and re-import just those.

The usual causes

Barcode column lost leading zeros

Excel treats 00123 as the number 123. The barcode imports short, then scans don't match.

  • Fix: format the barcode column as Text in Excel before pasting values, then re-import.

Missing required fields

A row without a name (or whatever the template marks required) is skipped.

  • Fix: fill the blanks on the failed rows.

Duplicate SKU or barcode

The row collides with a product that already exists.

  • Fix: check whether that product is already in the catalog — it may have imported on an earlier run. Give the new row its own SKU.

Unrecognized category / variant format

Category names and variant option syntax must match the template's format.

  • Fix: compare the failing cell to the template's example rows exactly.

Re-import only the failures

  1. In the result, note which rows errored and why.
  2. Open the file, fix just those rows.
  3. Re-import the file — the importer skips rows for products that now exist, so you're not creating duplicates.

Tip: Do the first import on a copy of the file. Once the good rows are in, trimming the file down to just the failed rows makes the second pass tiny and easy to verify.

Sign-in required — we'll send you straight to the right screen.

Related guides

Didn't find what you needed? Press Ctrl K to search all guides, or ask your admin to open the ? menu in the app.