Why did my purchase order import fail, and how do I fix it?

Endless checks the whole purchase order file before it saves anything, so one error stops the entire import and no purchase orders are created or updated. You get an “Import failed” notification with the number of errors. Open “Raw metadata” on that notification to see each reason, how many rows it affects, and up to three PO numbers. Fix the file and upload all of it again.

Dates can be YYYY-MM-DD or month first, such as 04/03/2026, 4-3-2026, or 04/03/26. Endless always reads a date with slashes or dashes as month, day, year, so 04/03/2026 is April 3, and 13/02/2026 is rejected as “not a valid date.” Use YYYY-MM-DD.

“PO Number is archived” means that number belongs to an archived purchase order. The import cannot update an archived purchase order or reuse its number. Restore the purchase order first, or use a different number.

“has conflicting values for PO Number” means rows for the same purchase order disagree on a purchase order field, such as two different supplier names, statuses, or dates. Put purchase order fields on its first row and leave them blank on its other rows, or repeat the same value. Rows with a blank PO Number belong to the purchase order above them.

“Duplicate Item SKU found for PO Number” means one SKU appears on two rows of the same purchase order. A product can be on only one line, so combine the rows into one with the total quantity.

“Active supplier not found for Supplier Name” means the name does not exactly match an active supplier, including capitalization and spacing. Archived suppliers do not match. Correct the name, or use the Supplier Handle column, which takes priority over the name.

Other common errors are “Product not found for SKU,” a column that “has been renamed” (use the new heading it names), and a value that “looks like a number a spreadsheet rewrote,” which means a value was turned into scientific notation. Format that column as text and export again.