How do I prepare ordered and shipped history CSV files for ECHO?
Prepare separate files for ordered and shipped history, with one row per date, SKU, and sales channel in each file.
| Column | Meaning |
|---|---|
| date | Required; YYYY-MM-DD. Use the order date for ordered history and shipment date for shipped history. |
| sku | Required; preserve exact spelling and capitalization. |
| sales_channel | Required; use the Endless channel handle where one exists. |
| quantity_ordered or quantity_shipped | Required; positive whole number. |
| order_count or shipment_count | Optional; distinct orders or shipments in that row, zero or more. |
| revenue | Optional product revenue after item discounts, without tax or shipping charges. Use numbers without currency symbols. |
| note | Optional context about the source. |
For ordered history, exclude canceled orders and removed lines, then group by order date, SKU, and channel. Sum units and discounted product revenue, and count distinct orders within each group.
date,sku,sales_channel,quantity_ordered,order_count,revenue,note
2026-01-05,TEE-BLACK-M,shopify-dtc,14,5,420.00,Previous system
For shipped history, group shipped lines by shipment date, SKU, and channel. Sum units that shipped and their discounted product revenue, and count distinct shipments.
date,sku,sales_channel,quantity_shipped,shipment_count,revenue,note
2026-01-07,TEE-BLACK-M,shopify-dtc,10,4,300.00,Previous warehouse
An order containing three SKUs contributes to three daily SKU counts. Adding those counts across SKUs does not give a distinct order total. Leave counts and revenue blank when unknown; they contribute zero to those metrics.
Choose a cutoff before Endless’s automatic history begins. Import and reconcile a short period first. See history import matching and overlapping sources.