An optimiser that ignores your constraints produces a nice plan and a bad day. Travia starts from the constraints, builds rounds that dispatch can actually send out, then measures what they delivered.
Detours, empty runs, stop order fixed by hand: every day carries kilometres that serve no customer.
The engine orders the stops and allocates vehicles at the level of the whole day, with as little distance and empty running as possible.
A truck is half empty one day and overloaded the next, because there is no overall view of capacities and quantities.
Volume, weight and compartments are matched against real vehicle capacities before any order is assigned.
One to two hours a day to put the rounds together, and as much again to rebuild them when an order arrives late.
Orders and constraints go in together; the plan is computed, then adjusted by hand wherever dispatch decides.
Time windows, access, qualifications, customer priorities: whatever is not in the calculation is fixed by hand or paid for on the road.
Time windows, access, qualifications and priorities are calculation parameters. An order that cannot be placed is reported, not forced.
Travia gives no general figure: the gain depends on your network, your constraints and the quality of today’s plan. That is why we suggest rebuilding one of your real days and comparing, before any commitment.
Yes. The computed plan is a starting point: dispatch can move a stop, change a vehicle or lock a round. Changes in the field then flow into tracking.
The Travia driver app delivers the round and reports status, proof and incidents. Its roll-out is part of training; testing a real day asks nothing of the drivers.
Send us your current rounds. We reproduce your constraints and compare the results with your current organisation.
No software change required first