What do the warnings and errors after a supply shipment import mean, and how do I fix them?

Some messages stop the whole import before anything is saved, and others mean a shipment was saved but one step did not finish. Each shows in the import notification; open “Raw metadata” to see the reason, how many rows it affects, and up to three shipment numbers.

Endless checks the whole file first. Any error found then fails the import and saves nothing. Fix the file and upload all of it again.

“Item SKU … is not on PO Number …” means the purchase order exists but does not have a line with that SKU. Check the SKU and Item PO Number. If the product belongs on that purchase order, add the line to the purchase order first. If the line should not be linked to a purchase order, leave Item PO Number blank.

“is already at … and cannot be moved to …” means the Status column names a status behind the shipment’s current one. The import only moves a shipment forward, so it cannot take a Received shipment back to In Transit or move a Closed or Canceled shipment. Clear the Status cell or set a later status. To move a shipment back, use the shipment page.

After the file passes, Endless saves each shipment, then its costs, then its note, then its status.

“Shipment saved but its costs were not updated” means the shipment and its lines were saved but the cost columns, such as Origin Costs or Duties, were refused. The reason follows the message, often that you do not have permission to edit shipment costs. Enter the costs on the shipment, or ask an admin.

“Shipment saved but its status stopped short” means the shipment moved forward until a step was refused, and it stays at the last status it reached. Usually the shipment has no items, or it has no destination building or destination name, which In Receiving, Received, and Closed need. Fix the shipment, then move it on from the shipment page or another import.