Every morning looks roughly the same when you run an Odoo field service operation. You have a full board of crews, open jobs, parts staged in the shop, certifications to verify before anyone rolls out, and a dispatch window that does not wait. When that coordination holds together, customers see a professional outfit that shows up on time with the right people and equipment. When it breaks down, jobs slip, customers call to complain, and someone in the back office spends the afternoon chasing down paperwork that should have closed two days ago.
If your operation runs on Odoo, there is a significant change you need to understand heading into the back half of 2026. As of the Odoo 19.2 release, the standalone Field Service app has been discontinued. The features did not disappear; they moved into the Planning app, which is now Odoo’s single scheduling engine for field operations. At Novobi, we have guided field service companies through Odoo deployments for over 12 years, and the clearest thing we can tell you right now is this: what happened in 19.2 is an upgrade in disguise, not a loss. Here is what actually changed and why your crews come out ahead.
What actually changed with Odoo field service in 19.2
The standalone app is retired, not deleted
Across the Odoo 19.1 and 19.2 release cycle, Odoo consolidated Field Service’s core capabilities into Planning to create a more consistent and flexible scheduling experience. The work-order logic, resource assignment, parts tracking, and customer-facing workflows all moved. Nothing operationally critical was cut. The front door changed, but the rooms behind it are still there, and most of them are larger than before.
“Field Service” is now a way of working, not an app to install
In Odoo 19.2 and later, “Field Service” refers to a configuration and operating mode within Planning rather than a separate app you install from the app list. If you are on an older version and still see the standalone Field Service app in your menu, you are running a legacy release. This distinction matters if you are comparing Odoo Field Service documentation across versions, searching for setup guides, or scoping an upgrade path. Any guide that references the standalone app as the starting point is describing a workflow from an earlier release.
Why Planning is the stronger home for Odoo field service teams
Dispatch without the morning scheduling puzzle
The Auto Plan feature is the most immediate operational win. Planning can assign shifts and sales orders automatically rather than forcing a dispatcher to manually drag and drop across a board all morning. The system checks which employees carry the required role, confirms they have no overlapping shifts, accounts for approved time off and holidays, and respects configured working hours before making any assignment. A dispatcher looking at the schedule can filter the view by Resource, Role, Project, or Sales Order depending on what question they need answered right now. One thing Auto Plan does not solve for is geography. It does not calculate drive time or weigh how far apart two jobs sit; client location is listed as a future input on Odoo’s v20 roadmap. Auto Plan answers the question of who is qualified and available, not who is closest. That call still belongs to your dispatcher.
The Kanban, Gantt, and Map views each match a different mental model your dispatcher already uses. “Who is available?” lives in the resource-filtered Gantt. Route gaps and unassigned jobs surface in the Map and Kanban views, respectively, replacing reactive scrambling with a structured, repeatable dispatch process that does not rely on a single person holding all the context in their head.
Putting the right credentials on every shift
Roles in Planning include custom property fields, and those fields automatically surface on every shift tied to that role. For Odoo field service operations, this means that certifications, required work location types, language requirements, and equipment qualifications can be attached directly to the role definition rather than checked manually by a dispatcher who, hopefully, remembers. When a new shift is created for that role, the relevant fields are already there.
For regulated service work, specifically HVAC, electrical, medical equipment servicing, and any compliance-driven trade work, this eliminates the manual cross-check that previously lived on a spreadsheet or inside one experienced dispatcher’s memory. The certification requirement is visible at the scheduling stage, not discovered after the crew is already on site. That shift from reactive to proactive delivers more value than any single feature on the list. It’s worth being precise about what this is. The requirement surfaces on the shift, and technician skills can be filtered on in the Gantt view, so the dispatcher sees the credential before assigning anyone. It is a strong prompt at the right moment, not a hard validation rule that refuses an unqualified assignment.
Scheduling equipment alongside the people who use it
Planning treats heavy equipment, specialist tools, and vehicles as assignable resources alongside technicians. A crane, a diagnostic unit, or a specialty service vehicle can be added directly to a shift, and multiple resources, both technicians and tools, can share the same time window. Each resource is tracked separately, so the system will flag a conflict if the same piece of equipment is being double-booked across two jobs on the same day. For operations where the bottleneck is equipment rather than headcount, this capability makes Planning genuinely useful, not just visually organized.
Technicians also gain more visibility into their own schedules. The new My Planning view gives each person a clean calendar of their own shifts, and publishing a shift sends an ICS file so it drops straight into Google Calendar or Outlook. Small changes, but together they remove a meaningful share of the “what am I on tomorrow?” calls that eat up a dispatcher’s morning.
The back-office connection that keeps billing and inventory clean
The integrated ecosystem emerged from the merger intact. Parts used on a job still automatically draw down inventory. Completed jobs still generate time-and-materials invoices against the linked sales order. Service history stays attached to the customer record in CRM.
This is the point that separates Odoo from point-solution field service management (FSM) tools: the scheduling and financial layers are the same system, not two platforms exchanging data through an integration that breaks on a bad day.
When a job closes in Planning, the downstream effects in Inventory and Accounting happen because they all share the same database. There is no sync delay, no mapping error, no end-of-month reconciliation project. The service work and the business record arrive at the same time.
Two moments make this concrete on site: Pressing Complete opens the customer-facing report containing time, materials, worksheet, and photos on the technician’s tablet; the customer signs on the spot, and the PDF sends automatically. And the under-warranty checkbox suppresses billing while still relieving inventory, so covered parts land on the sales order as delivered at zero price rather than quietly walking off the van.
Where Odoo field service is heading next (Planning roadmap)
MapBox integration and smart routing on the Odoo 20 roadmap
Based on Odoo’s published 20 roadmap, MapBox integration is slated to surface estimated travel times directly in the Gantt view, alongside smart route optimization in the Map view for dispatchers managing multiple stops in a day. These are capabilities that purpose-built FSM platforms have marketed heavily for years as reasons to choose a vertical tool over a general ERP.
Planning as Odoo’s central resource layer going forward
The architectural intent behind the 19.2 consolidation is clear: Odoo is building Planning into the unified layer through which all resource scheduling flows, whether for manufacturing, field service, or project work. The investment Odoo is making in Planning’s routing, resource model, and automation engine is not a one-time reorganization; it is a sustained strategic direction. Investing in Planning now means investing in the part of the platform Odoo is actively prioritizing, not a sidecar app that gets minimal attention in each release cycle.
What this shift means for your operation
If you’re evaluating Odoo for field service now
New customers coming in on 19.2 get the full scheduling engine, access to the Odoo mobile app for technicians, resource management, and back-office integration out of the box in a single app. There is no separate Field Service app to deploy, configure, or maintain alongside Planning. That simplicity reduces implementation scope and shortens the path to go-live in a meaningful way. For field service companies evaluating Odoo for the first time, the current release offers the most unified entry point the platform has provided, because the scheduling and financial layers are fully integrated rather than merely connected.
If you’re already running the Field Service app
Your features are in Planning now, and most of them offer more capability than they did in the standalone app. Odoo has flagged specific configuration impacts from the merge, including changes to the duration format for allocated hours and field visibility adjustments in the planning form when Field Service integration is enabled. A documented list of regressions was also addressed in subsequent fixes, covering SOL generation, button visibility, multi-company behavior, worksheet recomputation, and inventory-access filtering, among others. This upgrade rewards careful planning over a rushed cutover, so map your current configuration before touching anything in production.
This is exactly the kind of transition Novobi handles for clients. We map what you have running today to what Planning supports, identify gaps before go-live, and contain disruption so your crews can keep working while the system moves beneath them. Our team has managed enough of these transitions to know where the edge cases hide, and we build that institutional knowledge into the upgrade plan before the first configuration change is made.
How the new Planning engine fits manufacturers and aftermarket service teams
Certification tracking for regulated equipment and compliance-driven work
Industrial field work operates under a simple rule: if a technician is not certified to service that equipment, they cannot be on that job. The Planning role-level property field capability makes this trackable and enforceable at the scheduling stage. You define the certification requirement on the role, and it appears on every shift that uses that role. A dispatcher assigning a crew to a medical device installation or a regulated HVAC system can see the credential requirement on the shift record without leaving the scheduling view.
Scheduling specialized tools and recurring maintenance against open sales orders
Consider a manufacturer running quarterly maintenance visits against an aftermarket service contract. Planning can schedule the right technician for that visit and assign the required specialty tool as a material resource on the same shift. It then links the entire entry to the sales order that drives the invoice. When the job closes, the sales order, inventory record, and customer history all update together within the same ERP, without reconciling with a separate FSM platform at month-end. For industrial operations running contracted aftermarket service programs, that workflow is significantly cleaner than managing two systems that never quite agree.
The mechanism behind that is worth seeing. A subscription product configured to plan services against a project template generates the project, the task, and a recurring shift series in one action; Odoo’s own 19.2 demo builds a monthly maintenance contract and publishes twelve months of visits across three technicians without anyone opening a calendar. For an OEM, the other half of the story is traceability: serial and lot records tie the part fitted on that visit back to the order you originally built, so a service call can answer what you shipped and what has been done to it since.
The path forward for field service on Odoo
The Odoo field service story in 2026 is about consolidation delivering real capability. The scheduling engine is more powerful, the resource model handles both people and equipment, and the back-office connection that makes service work financially visible is fully intact.
For field service companies evaluating a modern ERP, the Planning-first model means less system complexity from day one. For teams already running on Odoo, the path forward is clear even if the upgrade requires a steady hand to navigate the documented configuration impacts.
The implementation choices made early in this kind of transition determine how smoothly your crews operate on the other side. Whether you are mapping your operation to Odoo field service for the first time or moving an existing Field Service deployment into Planning, the gap between a clean go-live and a painful one usually comes down to how well the upgrade was planned before anything was touched.
Novobi’s team has run these transitions for field service companies across manufacturing, distribution, and services industries. If you want to walk through what the move looks like for your specific setup, we are ready to have that conversation.
Contact us here, and we will show you exactly where your current workflows fall within Planning and what, if anything, needs attention before you flip the switch.
DISCLAIMER: The information in this article reflects the views and opinions of Novobi, based on publicly available information, and is intended for informational purposes only. It is not legal or financial advice. All trademarks are the property of their respective owners.
