Operations console
Load, clean, solve, review, dispatch, and learn — every step stays explicit enough for operators to trust and practical enough for drivers to run.
What CoeRoute does today
Most routing tools stop at the optimized sequence. CoeRoute keeps going: it helps you clean up customer data, compare the plan against your current routes, dispatch to drivers, and use the actual day to improve tomorrow's assumptions.
Upload CSVs with addresses, coordinates, demand, service time, and truck preferences. The app validates columns, geocodes missing coordinates, caches results, and lets operators correct bad addresses before they poison a route.
CoeRoute builds road-network distance and duration matrices, then uses OR-Tools to assign stops across the fleet under capacity, depot, and service assumptions. That means routes reflect roads, not straight-line guesses.
Dispatchers can review maps, truck loads, stop order, and projected mileage impacts before locking a route. Manual moves are staged first so the operator sees consequences before committing.
Upload current route assignments and see before/after miles, time, and workload balance. CoeRoute is built to answer the practical buyer question: “Is this route better enough to change how we work?”
Locked routes become driver views reachable at drive.coeroute.com, with SMS/email dispatch hooks where configured and copy/paste links when messaging is not connected yet.
Customers, fleet, drivers, route history, usage, and tenant boundaries live in the product. CoeRoute is more than a solver script; it is an operations console for maintaining routes over time.
The operator workflow
Bring in customer addresses, coordinates, demand, service-time assumptions, current assignments, and fleet limits.
Resolve geocoding misses, review address-confidence flags, and cache known-good locations for future solves.
Generate routes with real road distances, configurable vehicles, depot assumptions, capacity limits, and cost-function choices.
Explore the map, route tree, mileage totals, workload balance, and insertion/move costs before committing the plan.
Send drivers secure route links. Drivers tap arrived/complete today; passive GPS dwell and day-bracket capture are next on the roadmap.
Post-mortems reveal variance, reordered stops, service-time drift, and concrete updates to apply before the next route cycle.
The moat
Generic solvers know the map. CoeRoute learns the operation: which customer docks take longer, where drivers reverse the order, which stops need a practical time window, and where OSRM's estimate misses the real world.
Why it matters
Repeatable CSV import, cached distance matrices, and route history reduce the spreadsheet grind.
Road-network distances, workload balance, and before/after comparison make the tradeoffs visible.
Driver capture turns field reality into service-time updates, post-mortems, and better next-week assumptions.
Each route adds operational evidence instead of disappearing into memory and dispatch folklore.
Pilot with your routes
CoeRoute is best evaluated against real customer stops, real fleet limits, and the routes your team already runs.