Fix import errors

Understand why import rows fail and how to correct and re-upload them.

Updated June 21, 20261 min read

When an import runs, Fiddle validates every row and reports the ones it couldn’t accept by row number and reason. Valid rows still import — only the flagged rows need attention.

Read the error report

Each failed row lists its row number and the reason it failed. Open your source file, jump to those rows, and correct the values in place.

Common errors and fixes

Error Cause Fix
Duplicate SKU Same SKU appears twice Remove the duplicate or merge the rows
Unknown unit Unit isn’t in your account Use an existing measurement unit
Record not found References an item/customer not yet imported Import the referenced record first
Missing required field A required column is blank Fill the flagged column
Invalid number/date Symbols or wrong format in the cell Use plain numbers and a consistent date format

Most “record not found” errors come from importing out of order. Import locations and items, then suppliers and customers, then pricing and sales orders.

Re-upload safely

  1. Fix only the flagged rows in your file.
  2. Re-upload the same file.
  3. Confirm the preview shows the previously failed rows as valid.

Re-running an import matches on the unique key (SKU or name), so already-imported rows are updated, not duplicated. You can safely re-upload the whole corrected file.

Next steps

For formatting that prevents errors in the first place, see Prepare your import file.

Was this article helpful?

Related articles

Still need help?

Ask Filo, our built-in AI assistant, for an instant answer — or get in touch with our team and we'll take it from there.