Reporting
What shipped, what came back, what it cost. Reporting built from the work itself rather than assembled afterwards from exports.
Built from the floor's own records
Cut by SKU, channel, date, reason
Turnaround is actual, not target
Read it live or export it
Reporting, as you see it.
Reporting built from the floor's own scans rather than assembled from exports. The useful cut is rarely the total.
Three steps, in order.
- Built from the floor's own recordsEvery report is drawn from the scans, grades and charges captured as the work happened.
- Cut the way you need itBy SKU, by channel, by date, by reason. The useful question is rarely the total.
- Exported or read liveRead it in the dashboard or take it out as a file for your own analysis.
What that includes.
- Despatch volumes and turnaround
- Return rate by SKU, size and reason
- Cost per order and per return
- Stock movement and ageing
- Exportable for your own reporting
- Which cuts you actually use โ most reporting goes unread
- Your rate card, so volumes can be costed
- Despatch volumes and turnaround
- Return rate by SKU, size and reason
- Cost per order and per return
- Stock movement and ageing
- Exports for your own reporting
We report what we measured, including the figures that do not flatter us. Turnaround times are actual, not targets, and if a week went badly the report will show it.
All software →
Live dashboard
Stock, orders and returns as they move.
Charges as they happen
Every billable action is itemised by the system at the moment it occurs.
Evidence links
Send the proof straight to your customer.
Talk to the floor
Messages reach the people actually handling your stock, with the order, product or SKU attached by search, so there is nothing to explain.
Want to see it on your own orders?
Run a four-week trial. No contract, no minimum — long enough that the returns from week one come back inside it.