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

What Is Odoo Field Service?

Odoo Field Service is the dedicated Odoo app for planning, delivering, and tracking on-site services. It bundles task management, a drag-and-drop Gantt scheduler, timesheets, a mobile intervention app, and sales/invoicing into one module so a service business can run a job from request to payment without leaving Odoo. The official Odoo features page lists task management, scheduling (Gantt), timesheets, mobile, and sales/invoicing as the core capabilities.

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

As of Odoo 19.2, the standalone Field Service app was discontinued and its core features were merged into the Odoo Planning app. The Odoo 19.2 release notes state plainly: 'Field Service merged into Planning. The Field Service app has been discontinued. Its features are now integrated into the Planning app.' The same on-site tools — worksheets, time tracking, and resource allocation — now live in Planning. For most of this guide we describe the module as it shipped in Odoo 14 through 19, which is what the majority of installed SMEs run today.

How an Odoo Field Service Job Flows

Field Service is built on Odoo's Project app: every on-site job lives as a task on a field-service project. That makes it straightforward to automate the start of a job, because a task can be created automatically from an email alias, a web form, a sales order, or a helpdesk ticket.

A typical intervention moves through four stages:

1. Intake — a task is generated automatically from a Sales order line (a service product flagged to create tasks), a Helpdesk ticket, an email alias, or a web form.

2. Planning — a coordinator opens the Gantt, calendar, kanban, or map view and drags the task onto a technician and a time slot, sets dependencies, and avoids double booking. The Gantt view lets coordinators drag and drop tasks to plan dates, change assignees, and set dependencies.

3. Execution — the technician receives the task in the mobile app, starts the integrated timer to log a timesheet, attaches photos or a worksheet, scans or selects spare parts (which deduct from a per-technician default warehouse), and captures the customer signature.

4. Billing — on completion, a draft invoice is created from the task form. Tracked working time and sold products are captured automatically, and quotations can be created and sent from the job using predefined products, price lists, and quotation templates.

Odoo Field Service Scheduling and Dispatch

The planning surface of Odoo Field Service is its Gantt view, supplemented by calendar, kanban, and map views. The Gantt lets a coordinator drag a task to change its dates, drop it onto a different technician to reassign, and define dependencies between jobs — all while the view prevents double-booking a technician.

An integrated timer lets technicians track working time directly from the task, and those time logs appear in the task chatter through Timesheets integration. That means the same record that the dispatcher plans is the record the technician works against and the record finance bills from — there is no separate work-order object to reconcile.

For multi-stop days, the map view groups interventions geographically so a technician's route can be sequenced. Odoo Field Service does not, however, ship an automated, constraint-based dispatcher: planning is manual drag-and-drop plus rules-based auto-assignment. We contrast this with Microsoft's Resource Scheduling Optimization below.

The Mobile App and On-Site Worksheets

The Odoo Field Service mobile app is designed for the technician at the customer site. According to the official product page, it lets technicians schedule customer meetings, update inventory from work sheets, track time per intervention, capture employee and customer signatures, and keep records of spare parts used on site.

Worksheets — the customizable intervention report a technician fills out on site — have historically required Odoo Studio to add fields. Official Odoo documentation for Field Service covers creating tasks, product management, planning an itinerary, and worksheets across versions. From v19.2 onward, worksheets use standard 'Planning By Worksheet Template' functionality inside Planning rather than Studio customization.

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

How Field Service Connects to Inventory, Accounting, and Sales

Field Service's value comes from being native to the Odoo suite. It shares one record across operations and finance, so an intervention does not need a second system to bill.

Inventory — a default warehouse can be set per team member, and tracked products can be added by lot or serial number, which keeps stock up to date as the technician consumes spare parts on site.

Accounting and Invoicing — field service tasks generate draft invoices automatically from tracked time and sold materials, so the back office reviews and posts rather than re-keying.

Sales — confirmed sales orders create linked service jobs, and quotations can be created and sent from the task while the technician is still on site.

For Community-edition users who cannot access the Enterprise Field Service app, the OCA's Open FSM modules provide an open-source alternative for field service management in Odoo.

Odoo Field Service vs. Microsoft Dynamics 365 Field Service

Odoo Field Service 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 very different stacks and optimize for different buyers.

Stack and ecosystem. D365 Field Service runs on the Microsoft/Dataverse stack with deep Power Platform and Copilot integration. Odoo Field Service is natively integrated with Odoo's own CRM, Sales, Inventory, and Accounting apps. If your finance team already lives in Dynamics 365, D365 keeps everything in one Microsoft tenant; if you run Odoo as your ERP, 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 Field Service relies on manual drag-and-drop Gantt planning plus rules-based auto-assignment and does not ship native IoT/predictive or an RSO-equivalent optimizer. For SME trades businesses without a dedicated dispatcher, 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. 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.

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

Note: this Odoo module guide is distinct from our Dynamics 365 coverage. If you are evaluating the Microsoft side, see our D365 Field Service guide, 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 — HVAC, plumbing, electrical, appliance repair, and IT/AV installers — that want a single system covering dispatch, on-site execution, and billing without a separate FSM tool.

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

Edition matters too. If your organization standardizes on Odoo Community, the Enterprise-only Field Service app is not available, and the OCA's Open FSM modules are the community-supported path.