The Friction
Dispatch gets messy when routes live outside the work.
Several people juggle stops, jobs, customer locations, traffic, timing, and schedule changes by hand. The route is separate from the work record.
Field routing software for the dispatch scramble.
Routing is available with limited beta access for selected users while improvements continue. It helps teams plan route scenarios with dispatch context, scheduled work, customer and job records, stops, and field notes.
The Clean State
Route planning starts from the jobs already in OdinCore.
Routing keeps route scenarios, stop context, scheduled work, customer records, and field details closer together for selected beta users.
Dispatch Context
See what is scheduled, where the work is, and which customer or job it belongs to.
Route Scenarios
Build and review route scenarios before the field day gets reshuffled.
Traffic and Weather Context
Traffic-aware or weather-aware checks may count as additional routing runs when used.
Field Records
Keep notes, status, customer details, and follow-up tied to the work.
Route Planning Guide
Field routing works best when it starts from real job records.
Routing is not just a map. For field service work, it should help the team understand which jobs are scheduled, which stops belong together, and when the day is being recalculated too often.
Limited Access During Beta
Selected beta users can use Routing while we continue improving field routing, dispatch context, and usage controls.
Predictable Usage Language
A routing run means one route scenario or action. Traffic-aware checks, weather-aware checks, larger stop counts, and repeated recalculations may count as more runs.
No False Optimization Promise
OdinCore uses route-planning and dispatch-support language until automated optimization is ready enough to describe honestly.
Routing Guides
Learn where field routing fits.
Use Routing when schedules, crews, stops, and customer details need to live closer together.
Estimated Usage Pricing
Straight pricing by routing run.
One routing run means one route scenario or action. Traffic-aware checks, weather-aware checks, large stop counts, or repeated recalculations may count as additional routing runs. Final Routing pricing may adjust before full release as usage costs and real customer patterns are confirmed.
| Usage | Estimated Price | Notes |
|---|---|---|
| Routing Access | Estimated $10/mo | Required when Routing is active. |
| 1-1,000 Runs | Estimated $0.06/run | Good for smaller teams testing route planning. |
| 1,001-5,000 Runs | Estimated $0.05/run | Lower unit cost as routing volume grows. |
| 5,001+ Runs | Estimated $0.04/run | High-volume pricing for larger teams. |
Limited Access
Routing is live for selected beta users.
Follow updates as Routing improves around field routing, dispatch context, route scenarios, and usage controls.