Delivery diagnostics for logistics teams
Every delivery, on the best route.
Root Route traces every late delivery to its root cause, from a missing address to a lane that fails on Fridays, and hands each fix to the team that owns it.
Order desk, warehouse, carriers and customer support in one workspace.
Platform
Every order checked before the truck moves.
- Check 01 / 04
Addresses complete before they ship
AI reads each emailed order, flags a missing street, suite or ZIP, and drafts the reply asking the client for it. An operator approves before the order reaches the WMS.
On-time points at stake0.0 pts - Check 02 / 04
Promises that respect the cut-off
Orders that arrive after the dispatch cut-off get a date the warehouse can actually keep, not a same-day promise that is late at checkout.
On-time points at stake0.0 pts - Check 03 / 04
Shipped from the nearest stock
Flags orders sent from a farther warehouse when the nearest one had stock, and suggests weekly stock moves so it does next time.
On-time points at stake0.0 pts - Check 04 / 04
Carriers judged on fair data
Scores every carrier lane only on deliveries with no upstream cause, so a bad address never counts against a driver. Weak lanes and capacity days stand out.
On-time points at stake0.0 pts
Delivery on the wayNext stop: your door.
Network
One timeline for every delivery.
Orders, warehouse picks, carrier scans and complaints are joined into one journey per delivery. Every late one is attributed to the cause that made it late, across every warehouse, carrier and lane.
How it works
From inbox to root cause in three steps.
- 01Step 01 / 03
Connect
Bring orders by email, API or EDI, plus warehouse, carrier, tracking and complaint data. Email is read by AI and always checked by a person.
Data sources joined0 - 02Step 02 / 03
Diagnose
Five cause checks run on every delivery: address, cut-off, warehouse, carrier lane and route. Each flag shows the rule and the data behind it.
Late deliveries with a cause found0% - 03Step 03 / 03
Replay
Replay past deliveries with each fix switched on to see what it would have changed, before anyone changes a process.
On-time, replayed with every fix71.0%
Results
What it found in 48,340 deliveries.
- of late deliveries had a cause before pickup
- 67%
- of late deliveries traced to one of five causes
- 100%
- late deliveries avoided in replay
- 8,447
- on-time gained in replay, 71.0% → 88.5%
- 17.5 pts
Reference run on six months of one network’s data: 5 warehouses, 6 carriers, 280 clients.
Six roles with least-privilege access · Every approval and override recorded · No order reaches the WMS without a person’s approval
Features
One workspace, a screen for every team.
- 01
Overview
On-time rate, the five causes ranked by points lost, and what each fix is worth.
Everyone - 02
Order emails
AI-read orders with flagged gaps, drafted client replies and one-click approval to the WMS.
Order desk - 03
Warehouses
Cut-off misses, orders sent from the wrong site, unpaid penalties and weekly stock moves.
Warehouse - 04
Carriers
Lane scorecards on fair data, capacity days and a recommended carrier you can override.
Carriers - 05
Complaints
Every complaint linked to its delivery and triaged by the cause behind it.
Support - 06
Order journey
One delivery from email to doorstep: each stage, who acted and where it slipped.
Everyone - 07
Replay
Past deliveries replayed with each fix on, by segment, before you change anything.
Leadership
Built for people
People decide. Root Route shows why.
- 01
A reason on every flag
Each cause shows the rule and the data that tripped it, in plain language.
- 02
AI drafts, people approve
AI reads order emails and drafts replies. Nothing reaches the WMS or a client without a person.
- 03
Overrides with a reason
A carrier manager can overrule any recommendation; the reason is kept with the order.
- 04
A view for each role
Six roles, from order desk to leadership, each see their own screens and actions.
Order journey · D000213
- AddressCompleteChecked at intake
- Cut-offMissedReceived after the 8am cut-off
- WarehouseNearest with stockPlacement rule passed
- Carrier laneFair-data score OKNo lane issue this day
Root cause: cut-off · fix owned by the order desk