Routing support for field work is coming to OdinCore.
Routing is planned for teams that need dispatch context, scheduled work visibility, route-planning support, customer/job connection, and field records without separating the day from the rest of the business.
Dispatch context for teams managing crews, visits, routes, and scheduled field work.
Scheduled work visibility tied to jobs, customers, and the records already inside Core.
Route-planning support without promising automated optimization before the module is ready.
Field notes, customer context, and work status designed to stay connected to the wider workspace.
What Routing is for
A cleaner operating layer for work that moves.
Routing is being shaped around practical visibility: who is going where, what work is scheduled, which customer record is involved, and what the field team needs to know before the next stop.
Dispatch and schedule context
Give the day a clearer plan without forcing dispatch, jobs, and customer details into separate places.
Route-planning support
Plan around location-based work and route visibility while the deeper product behavior is validated in beta.
Records that carry forward
Keep field notes, job status, customer context, and follow-up connected to the same workspace.
Pricing guidance
Routing roadmap pricing and fit.
Routing is planned as a paid add-on after Core. Pricing is being published early so teams can compare the future path clearly while the module is still under construction.
- Monthly
- Planned $29/mo
- Annual
- Planned $290/year
- Core
- Core Workspace will be required when Routing launches because customer, job, document, and reporting records need the shared foundation.
- Presale
- Presale reservations can hold first-year savings before launch access opens. There is no charge today.
Follow the build
Watch Routing move through the roadmap.
Routing is not being sold as a finished module yet. Follow product updates as dispatch, scheduling, and route-planning support mature through beta feedback.