Every morning, someone in your operation decides who is going where. Maybe it is you. Maybe it is a dispatcher. Maybe the drivers divide a stack of work orders over coffee. However it happens, the job is the same: group stops, choose an order, assign the work, and communicate changes.
That manual approach can become harder to maintain as routes, service types, and access restrictions change. Route optimization gives dispatchers a road-aware sequence to compare with the order they would otherwise build by hand.
Where Manual Planning Gets Difficult
A dispatcher can recognize neighborhoods and obvious detours, but it is difficult to compare every possible stop order against road travel estimates. The problem becomes richer when a route also has customer access windows, different service durations, driver shift boundaries, or breaks.
Optimization does not guarantee a particular reduction in mileage, planning time, fuel, or labor. Those outcomes depend on geography, the quality of the starting route, traffic conditions, service mix, and the constraints supplied to the optimizer. The useful question is whether the returned sequence improves the routes in your operation.
Measure that with your own baseline:
- Compare planned and actual route distance.
- Compare estimated and actual route duration.
- Track how often dispatchers manually reorder an optimized route.
- Review late arrivals and constraint conflicts.
- Ask drivers whether the sequence is practical on the road.
How Route Optimization Works
Route optimization is more than sorting pins by straight-line distance. A routing provider compares travel estimates over the road network and returns a stop order for the submitted problem.
DropHaul offers two optimization qualities:
- Standard sequences geocoded jobs using provider travel estimates. It is intended for everyday route ordering.
- Premium can also apply configured stop access windows, service durations, driver shift boundaries, and break durations. Premium results include schedule-aware per-stop arrival estimates.
Configured constraints are inputs, not a promise that every requested schedule is feasible. If the submitted jobs and constraints cannot form a valid solution, the run can fail instead of inventing a route that ignores them.
Routes can begin and end at the configured yard. Current optimization does not enable live or historical traffic inputs, so a driver's navigation app may still adapt differently once the route is underway.
What DropHaul Applies
DropHaul's optimization workflow is built into dispatch:
- Build the route. Add geocoded jobs to a driver's route for the day.
- Choose Standard or Premium. Standard focuses on stop order. Choose Premium when supported scheduling constraints need to be part of the problem.
- Run optimization. DropHaul sends the eligible route inputs to the selected optimization service.
- Apply the result. When the run succeeds, DropHaul writes the returned stop sequence directly to the route and syncs it to the driver app.
There is no fixed completion-time promise. Standard runs through 11 geocoded jobs use the fast path; larger Standard runs continue through the asynchronous optimizer. Premium and fleet-wide runs are asynchronous as well.
Enforced Run Limits
Single-route optimization requires at least 2 geocoded jobs and supports up to 200 total jobs. Fleet-wide optimization supports up to 100 routes and 500 total jobs in one run, with no smaller per-route cap inside that aggregate limit.
Fleet-wide optimization operates only on the eligible routes and jobs submitted for that run. It does not automatically include every active vehicle, and it does not promise equal workloads.
Credits and Re-optimization
Self-serve paid plans include a UTC calendar-month pool of optimization credits:
- Starter includes 3 credits.
- Pro includes 6 credits.
- Fleet includes 12 credits.
- Enterprise includes unlimited optimization credits.
A Standard run uses 1 credit and a Premium run uses 3. Monthly credits reset on the first day of each UTC month and do not roll over. Purchased credit packs do not expire.
When priorities change, you can run optimization again while credits are available. A successful result replaces the route's stop sequence and syncs the update to the driver app.
Evaluating the Fit
Route optimization is a planning tool, not a guaranteed savings calculator. Start with routes whose stop order is difficult to reason about, compare the returned sequence with your current process, and measure the operational results that matter to you.
The strongest signal is not an industry-wide percentage. It is a repeatable improvement in your own route data, dispatcher workflow, and driver feedback.