How it works
From order to proof, in four steps
The same sequence whether the order comes from the portal, your ERP or the API, and whether it is one rush run or a standing route.
-
1
The order lands
From the portal, your ERP, your storefront or the API. The address, the window and the vehicle class are validated on arrival.
-
2
Dispatch assigns and routes
A screened driver with the right vehicle is matched to the job and the window, with conflicts flagged rather than absorbed.
-
3
Tracking goes out
Your branch and your customer follow the same status and ETA, and get told when something changes.
-
4
Exceptions get resolved
Closed site, nobody to receive, a refused delivery: reassigned or escalated to the contact named on the order.
-
5
Proof closes the loop
Photo, signature, recipient, timestamp and cost, attached to the order and ready for the invoice.
-
6
You see what it cost
Per delivery, per branch and per route, with the exceptions counted rather than quietly dropped from the average.
What travels with every delivery
The record is the product as much as the driving is. Everything below is captured as part of the job, not chased afterwards.
Timing depends on driver availability in your market and on the window you need. We confirm a window when we accept the order instead of promising a number everywhere.
- Order reference and cost centre from your system
- Pickup and delivery timestamps with location
- Item counts and any handling instructions
- Photo and signature or an approved exception
- The reason for any exception, in the driver's own words
- The final cost, itemised