Odoo Field Service: Planning, Mobile & Invoicing for On-Site Work

What Is Odoo Field Service?

Odoo Field Service is the dedicated Odoo stack for planning, delivering, and tracking on-site interventions. It bundles task management, drag-and-drop Gantt scheduling, timesheets, a mobile intervention app, spare-parts consumption, customer signatures, and sales/invoicing so a service business can run a job from request to payment without leaving Odoo. The official product page still markets this as field service management: Kanban, Gantt, and map views for planning; a mobile app for worksheets, stock, time, and signatures; and automatic tasks from sales orders.

The Field Service capability is exclusive to Odoo Enterprise — it is not available in Community, and Odoo’s comparison material places Gantt dispatch, on-site worksheets, and mobile intervention on the Enterprise side of the ledger. Odoo SA shipped the original Field Service app with Enterprise V13 in 2019, after the Odoo Community Association (OCA) released its open-source Open FSM modules in 2018.

As of Odoo 19.2 (March 2026 release notes), the standalone Field Service app was discontinued and its core features were merged into the Odoo Planning app. The official wording is direct: “Field Service merged into Planning. The Field Service app has been discontinued. Its features are now integrated into the Planning app.” Product marketing still uses the field-service label (trial links target `planning_field_service`), but operators on 19.2+ live in Planning for on-site work. Most of this guide describes the shared capability set that spans Odoo 14–19 and the post-merge Planning surface, because the majority of SME installs still run pre-merge versions while SaaS and early adopters already work inside Planning.

Odoo 19.2: Field Service Merged Into Planning

The 19.2 merge is the single biggest product change field-service buyers must understand in 2026. Odoo did not delete on-site features; it folded them into Planning so scheduling (shifts, resources, Gantt) and field execution (worksheets, geolocation, signatures, multi-tech teams) share one app surface instead of two.

Partner write-ups of the 19.2 notes and the official webinar series spell out what operators feel day to day: worksheets no longer need Studio for basic custom fields; Sign In / Complete capture geolocation and open a client signature portal; multiple technicians and materials can sit on one shift with time multiplied by team size; an “under warranty” toggle can move stock without charging the customer; shifts link to project tasks and recurring subscription work; and a location button computes map directions to the site.

If you are still on Odoo 19.1 or earlier, you keep the standalone Field Service app and should plan a process review before upgrading past 19.2: role names, menu paths, and worksheet customization change even when the business outcome (plan → execute → bill) stays the same.

How an Odoo Field Service Job Flows

Field service work in Odoo is built on Project tasks: every on-site job is a task on a field-service project (or, post-merge, a Planning shift tied to that task). That design is what makes automation natural — a task can be created from an email alias, a web form, a confirmed sales order line, an appointment, or a Helpdesk ticket without a separate work-order system.

A typical intervention moves through four stages that stay on one record from intake to cash:

1. Intake — a task is generated automatically from a Sales order line (service product configured to create tasks or projects), a Helpdesk ticket escalated to a field visit, an email alias, a confirmed appointment, or a web form. Odoo 19 also supports task templates and project templates with roles so recurring job types stay consistent.

2. Planning — a coordinator opens Gantt, calendar, kanban, or map view and assigns a technician and time slot, sets dependencies, and avoids double booking. Map view clusters jobs by area so multi-stop days can be sequenced; Gantt drag-and-drop remains the primary manual dispatcher.

3. Execution — the technician receives the job on mobile, signs in (geolocation when enabled), runs the timer for travel and on-site time, completes the worksheet, attaches photos, consumes spare parts from a per-technician warehouse or van stock, and captures the customer signature on complete.

4. Billing — on completion the job moves toward invoicing: draft invoices pull tracked time and sold materials; quotations can still be created on site with predefined products, price lists, and templates. Warranty-flagged parts can update stock without a customer charge when that flow is enabled.

Because there is no second work-order object to reconcile, the same record the dispatcher plans is the record the technician works and finance bills. That single-record design is the main operational advantage of native Odoo field service over a bolt-on FSM that only syncs summaries.

Odoo Field Service Scheduling and Dispatch

The planning surface is Gantt first, with calendar, kanban, and map as alternate lenses. Gantt lets a coordinator drag a task to change dates, drop it onto another technician to reassign, and define dependencies — while the view prevents double-booking a resource. Odoo 19 refinements include hiding weekends by default for cleaner weekday boards, an undo affordance after drag-and-drop moves, and portal Gantt access when external stakeholders follow a project timeline.

Kanban cards surface priority (including a 3-star priority model on Odoo 19), quick assign, and subtasks so coordinators can triage urgency without leaving the board. Map view groups interventions geographically; itinerary tools help reorder stops, but Odoo does not ship a full constraint-based optimizer comparable to Microsoft’s Resource Scheduling Optimization (RSO).

An integrated timer lets technicians track working time from the task, and those logs appear in task chatter through Timesheets. When geolocation is enabled in project or Planning settings, start/stop of the timer can log GPS coordinates in the chatter so timesheet accuracy is auditable. Planning is still primarily manual drag-and-drop plus rules-based assignment — strong for SME trades teams without a full-time optimizer, weaker for large fleets that need automated SLA routing.

The Mobile App, Worksheets, and Offline Work

The mobile experience is designed for the technician at the customer site. According to the official product page, technicians manage appointments end to end: fill worksheets, keep spare-parts stock up to date, record time per appointment, and collect employee and client signatures. Partner coverage of Odoo 19 adds travel-vs-work time, before-and-after photos, and open-in-maps navigation from the assigned task.

Worksheets are the intervention report filled on site — instructions, checklists, measurements, photos, and sign-off. Official documentation still describes worksheets under Field Service for version 19.0. Historically, rich worksheet customization often required Odoo Studio. From the 19.2 Planning merge onward, worksheets use standard property fields so many SME templates no longer need Studio just to add a few fields, and photos can attach directly to the final PDF report.

Offline capability matters for basements, remote sites, and weak-signal construction zones. Odoo 19 expanded offline-first mobile behavior so field workers can create, edit, archive, and delete records without a connection and sync when connectivity returns; general offline search improvements landed in the 19.x line as well. Always test real van routes and dead zones before go-live — offline is only as good as the cache and the training that teaches techs when to force a sync.

Because the mobile client writes back to the same task or shift record, anything captured on site (photos, signatures, parts, time, geolocation) is immediately visible to the coordinator in Gantt and to accounting at billing time.

How Field Service Connects to Inventory, Sales, Helpdesk, and Accounting

Field service’s value comes from being native to the Odoo suite. One record spans operations and finance, so an intervention does not need a second system to bill or to deplete stock.

Inventory — a default warehouse can be set per team member (including van stock patterns), and tracked products can be added by lot or serial number so spare parts used on site reduce stock in real time. Warranty flows can move stock without a customer charge when configured.

Sales — confirmed sales orders create linked service jobs when service products are set to create tasks (or full projects with tasks). Quotations can be created and sent from the job while the technician is still on site, using predefined products, price lists, and templates.

Helpdesk and CRM — tickets escalate to field visits without re-keying the customer or site; CRM history retains service visits and upcoming work so account teams see what the field team already knows.

Projects and Timesheets — tasks feed project timelines and progress; timesheets feed payroll analysis and job cost. Appointments can generate field-service tasks with assignee and schedule carried over when products are configured that way.

Accounting and Invoicing — tasks generate draft invoices from tracked time and sold materials so the back office reviews and posts rather than re-keying. That is the difference between “we finished the job” and “we got paid for the job.”

Enterprise Field Service / Planning vs OCA Open FSM

If your organization standardizes on Odoo Community, the Enterprise Field Service / Planning field-service surface is not available. The Odoo Community Association maintains the OCA/field-service repository (often called Open FSM) under open-source licenses, with modules covering territories, branches, districts, workers, orders, maintenance bridges, portal access, digitized signatures, and related extensions.

Open FSM is the right conversation when you need Community licensing, multi-location fleet structure, vehicle-centric inventory patterns, or advanced territory models that partners have built in the OCA stack. Enterprise Planning field service is the right conversation when you want vendor-supported Gantt/map dispatch, native mobile worksheets, and tight Sales → task → invoice automation inside a standard Odoo Enterprise rollout.

Do not treat them as drop-in equivalents. Open FSM is a module suite with its own data model and upgrade path; Enterprise Planning is Odoo SA’s product surface with the 19.2 merge semantics above. Evaluate against your edition, partner support model, and how much custom fleet structure you actually need on day one.

Odoo Field Service vs Microsoft Dynamics 365 Field Service

Odoo Field Service (now the Planning field-service surface) is the Odoo-side analog of Microsoft Dynamics 365 Field Service. Both manage work orders or tasks, scheduling and dispatch, mobile execution, timesheets, and invoicing for on-site interventions — but they sit on different stacks and optimize for different buyers.

Stack and ecosystem. D365 Field Service runs on the Microsoft/Dataverse stack with Power Platform and Copilot integration. Odoo field service is natively integrated with Odoo CRM, Sales, Inventory, Projects, Helpdesk, and Accounting. If finance already lives in Dynamics 365, D365 keeps everything in one Microsoft tenant; if you run Odoo as your ERP, Planning field service is the natural extension.

Scheduling depth. D365 Field Service emphasizes IoT-driven predictive maintenance and the Resource Scheduling Optimization (RSO) add-in for automated, constraint-based dispatch. Microsoft’s own documentation describes RSO as the add-in that “automatically schedules jobs to the resources best equipped to complete them.” Odoo relies on manual drag-and-drop Gantt planning plus rules-based assignment and map itinerary helpers — not a native RSO equivalent. For SME trades without a dedicated optimization team, Odoo’s Gantt is usually enough; for larger service operations that need automated routing and SLA optimization, D365 with RSO is the stronger fit.

Edition and cost. Odoo field service is Enterprise-only (not in Community) and is generally lower total cost of ownership for SME trades and services businesses that already chose Odoo. D365 Field Service is a per-user Microsoft subscription aimed at mid-market and enterprise service operations, and RSO is an additional per-optimized-resource license. This page does not invent list prices — quote current Microsoft and Odoo price lists for your region and user mix.

Roadmap note. As of Odoo 19.2 the standalone Odoo Field Service app was merged into Odoo Planning, so the equivalent surface is Planning with field-service task and shift patterns. D365 Field Service remains a standalone Microsoft business application.

This Odoo module guide is distinct from our Dynamics 365 coverage. If you are evaluating the Microsoft side, see our D365 Field Service overview, our D365 field service mobile guide, and our D365 field service pricing page.

When Odoo Field Service Fits an SME

Odoo field service tends to fit SME trades and services businesses that want one system covering dispatch, on-site execution, parts, and billing without a separate FSM product. Strong industry patterns include HVAC and mechanical trades, plumbing and electrical, facilities and building services, telecom and network install, appliance and equipment repair, IT/AV installation, light manufacturing field service (install + warranty), and safety or compliance inspections that mix scheduled and reactive work.

It is a strong choice when you already run (or are adopting) Odoo for CRM, Sales, Inventory, Helpdesk, or Accounting, because the field record flows straight into those apps. It is weaker when you need automated, constraint-based route optimization at scale (look to D365 Field Service with RSO), deep IoT-based predictive maintenance, Mixed Reality remote assistance, or a pure Community edition without an OCA specialist.

Edition and version still matter. Community shops should budget Open FSM or an upgrade to Enterprise. Shops on 19.2+ should train on Planning menus, property-field worksheets, multi-tech shifts, and warranty stock behavior rather than hunting for a separate Field Service app icon. Before you buy, map three real jobs end to end: a sold installation, a helpdesk-escalated repair, and a warranty revisit — if those three flow cleanly through Planning, Sales, Inventory, and Invoicing, Odoo is usually the right call.

Frequently asked questions