Fewer empty miles, less chasing for payment.
Backhaul demand, hours-aware planning and portal-based paperwork for carriers — built for better utilisation and less admin.
- Fleet & route baseline
- Portal, telematics & driver pilot
- Backhaul & planning live
- Invoicing & disputes
- Whole fleet, measured
A carrier’s margin is made in two places: the return leg and the back office.
Trucks run home empty because the demand that would fill them sits in a shipper’s spreadsheet the dispatcher never sees. Invoices wait for a proof of delivery that is in the cab until Friday, then wait again while the shipper’s freight audit gets round to it. Utilisation and cash are both lower than the fleet deserves.
Order & Supply Management for carriers puts network demand on the dispatcher’s board along the routes the fleet already runs, so an empty return leg becomes a tender the dispatcher can accept. Plans are built within driver hours and equipment limits. Proof of delivery, documents, invoices and disputes go through the app and the portal, so the evidence the shipper needs arrives the moment it exists — and payment follows.
Built around the numbers a carrier actually feels: empty miles, days from invoice to payment, loads a week per truck, and a driver app that needs three taps. Your existing shipper relationships run on the platform under your terms; the network adds demand, not disintermediation. See the platform overview for the shared layer.
What it does, in detail.
The return leg, filled from the network.
When a driver delivers in İzmir and the truck is due back in Gebze, the dispatcher’s board already shows the tenders whose pickup lies within a configurable radius of that delivery and whose window fits the driver’s remaining hours. Each is ranked by margin per loaded kilometre, with the deadhead shown. Accepting one is a tap; the shipper sees the acceptance immediately and the load joins the plan.
- Matches on pickup proximity, window fit and remaining hours
- Margin per loaded kilometre and deadhead shown per match
- Contracted shippers first; open network demand where you allow it
- Acceptance rate and backhaul fill tracked per vehicle and route
Checked before it is offered, so the plan holds.
A plan that requires a driver to run past their hours is a plan the dispatcher will change by hand at 15:00, and every hand change teaches the team to ignore the system. Assignment on Order & Supply Management checks remaining driving and duty time, rest requirements, the equipment the load needs and the dock windows at both ends before a load can be offered. Re-planning on disruption keeps the same rules, and shows the reason for every change.
- Remaining hours and rest requirements checked at assignment
- Equipment compatibility — reefer, tail-lift, ADR — enforced
- Dock windows at pickup and delivery inside the check
- Re-plan on disruption, with reasons shown
Evidence at the dock, invoice straight from the load.
The proof of delivery is captured on the driver’s phone as a photo and a signature the moment the load is delivered. The platform attaches it to the rated load and generates the invoice, which the shipper’s freight audit matches automatically to the rate agreed at award. Where nothing differs, it is approved without anyone reading it. Where an accessorial is due — waiting time, a second delivery attempt — the evidence is already on the load, so the dispute, if there is one, starts from it.
- POD and documents captured at the dock, attached automatically
- Invoice generated from the rated load; matches what the shipper expects
- Accessorial claims with stamps and photos, not phone calls
- Days from POD to payment tracked per shipper
The fleet’s economics, per vehicle.
Utilisation is usually a fleet-level guess. On the platform it is a per-vehicle fact: loaded versus empty kilometres, revenue per kilometre and per working day, idle time at docks and yards, and backhaul fill on each route. The figures come from the same execution record the shipper reads, so a conversation about a lane’s economics starts from shared numbers.
- Loaded-mile share and revenue per km per vehicle
- Idle time at docks and yards, by shipper site
- Backhaul fill per route and per driver
- Exported to your own BI through the event ledger
Three seats on the carrier side.
Network demand on the board.
Tenders arrive in the portal. Backhaul matches appear along planned routes. Assignments are checked against hours and equipment before a driver sees them.
- Backhaul matches ranked by margin per loaded km
- Assignment blocked when hours or equipment do not fit
- Re-plan with reasons when the day changes
Three taps, and it works in the yard.
Check in, loaded, delivered — one tap each, with large targets. POD is a photo and a signature at the dock. No signal means the update queues and syncs later, with nothing to re-enter.
- Offline-first, piloted with real crews before rollout
- POD and documents captured at the dock
- Status the shipper sees without a call
Invoices that go out and get paid.
Invoices are generated from rated loads with the POD attached, so they match what the shipper expects and leave less to query. Disputes carry evidence and a deadline. Payment follows with less chasing.
- Invoice generated from the rated load
- Accessorials claimed with evidence already on the load
- Dispute ageing and days-to-payment per shipper
How the carrier side connects.
What ships for carriers.
Pilot routes first, then the fleet.
Fleet & route baseline
Vehicles, drivers, equipment and last quarter’s routes and invoices. A measured empty-kilometre and days-to-payment baseline per route.
Portal, telematics & driver pilot
Dispatchers on the portal, telematics connected, and the driver app piloted with real crews on pilot routes until three taps is what actually happens in the yard.
Backhaul & planning live
Network demand switched on along pilot routes; hours-aware assignment tuned to how your fleet really runs. First backhaul fills measured.
Invoicing & disputes
Invoices generated from rated loads with POD attached; disputes and accessorial claims in the portal. Days to payment tracked per shipper.
Whole fleet, measured
Rollout by route and depot. Regular reports against the baseline, at a rhythm agreed with you: empty kilometres, backhaul fill, days to payment, loaded-mile share per vehicle.
Frequently asked questions
See it on your own data.
A guided demo with an engineer who operates the platform — walked through on your routes and your fleet, not a canned deck.