Software · What you see

Reporting

What shipped, what came back, what it cost. Reporting built from the work itself rather than assembled afterwards from exports.

01
Built from the floor's own records
02
Cut by SKU, channel, date, reason
03
Turnaround is actual, not target
04
Read it live or export it
What it produces

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.

Returns by SKU ยท last 90 daysCSV
SKUSoldBackRate
RKM-SND-L42013833%
RKM-SND-M5129719%
CTE-WHT-S388318%
SWM-BLK-10210147%
One size running at 33% โ€” a sizing problem, not a returns problem
How it runs

Three steps, in order.

  1. Built from the floor's own recordsEvery report is drawn from the scans, grades and charges captured as the work happened.
  2. Cut the way you need itBy SKU, by channel, by date, by reason. The useful question is rarely the total.
  3. Exported or read liveRead it in the dashboard or take it out as a file for your own analysis.
What that includes

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
What we need from you
  • Which cuts you actually use โ€” most reporting goes unread
  • Your rate card, so volumes can be costed
What you get back
  • 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
The honest bit

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.

Talk to someone who runs the floor

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.