Why is my imported history missing, skipped, or on the wrong date in ECHO, and how do I start over?

Rows are skipped when ECHO cannot read them. Imported data can also seem missing because of filters or how rows combine, and most channels’ orders are dated by when Endless received them.

The import notification gives the number of rows skipped and the most common reasons:

• “Invalid date”: the date is blank or unreadable. Use YYYY-MM-DD. A date such as 03/04/2024 is read month first, as March 4.
• “Missing SKU” or “Missing sales channel.”
• “Invalid quantity”: the quantity is blank, not a number, or below 1. Inventory imports accept 0.
• “… looks like a number a spreadsheet rewrote”: a value such as 1.2E+11. Format the column as text and export again.

If the import completed but you do not see the data:

• Check the Dates, SKU, Sales Channel, and Source filters.
• Order history appears under Units Ordered, shipment history under Units Shipped, and inventory under Inventory.
• A row with the same date, SKU, and sales channel as an earlier import replaces it.
• If 0 records were written, every row was skipped.

“Delete Echo data” is in ECHO’s Actions menu. Choose the data to delete, Order history, Shipment history, or Inventory snapshots, and the filters, then “Review deletion…”, type the confirmation text, and choose “Permanently delete.” It deletes Manual and Adjustment records only. Automatic records and inventory changes are protected, and records added or changed after you confirm are kept. It cannot be undone. To restore the data, import your file again. Only an Admin can delete ECHO data.

Units Ordered uses the date each order was created in Endless. Shopify and Amazon orders keep the date they were placed. Orders from other channels and EDI take the date Endless received them, so a backlog brought in at once lands on that day. Units Shipped uses each shipment’s ship date. Contact Endless support for help moving a backlog to its original order dates.