Odoo 20 Field Service Change: Impact on Dispatch and Service Operations

Your dispatcher opens Odoo 20 and the Field Service app is gone. Jobs are now shifts, custom code points at models that no longer exist, and a technician who adds a part can become a full paid user. Our Odoo upgrade services map these changes before they hit your schedule.

This guide explains the Odoo 20 field service change in plain words: what moved, what your dispatchers and technicians will see, what it means for billing, licences and custom code, and how to plan the switch.

What happened to the Field Service app in Odoo 20?

Odoo discontinued the Field Service app and moved its features into the Planning app. The official release note says so in one line, and our Odoo 20 Field Service release notes explain it with screenshots.

In Odoo 20, an intervention is a Planning shift with a customer and an address. The new Odoo field service module, planning_field_service, adds maps, worksheets, reports and stock to Planning. The old industry_fsm modules do not exist any more.

This is why so many users are confused. On the Odoo forum, a thread titled "Where is the Field Services App?" asks why the app shows as installed but never appears. The answer from Odoo: it was discontinued and merged into Planning.

Watch out for old guides. Many tutorials, videos and even AI assistants still tell you to "open the Field Service app." One forum user said adding products was so unclear that he created a sales order and worked backwards. Use this table instead.

When does the Odoo 20 field service change reach your business?

It depends on where Odoo runs: Odoo Online already has it, while Odoo.sh and on-premise databases get it when they upgrade to Odoo 20. That timing decides how urgent this is for you.

Can you upgrade to Odoo 20 today? Not yet for most existing databases. As of early October 2026, the highest target on Odoo's upgrade platform is 19.0. That gives you time to test and plan before the switch.

What happens to your existing tasks, worksheets and job history?

Your tasks are meant to become shifts during the official upgrade, but you should test this on a copy, because worksheets and custom fields need extra work. No one can see the real Odoo 20 upgrade output until the platform opens.

Three things need checking on a test copy:

• Job history: confirm every past intervention, with its customer, technician, times and report, appears as a shift.

• Worksheets: in Odoo 20, worksheet templates use property fields instead of Studio models. Studio-based templates must be moved over.

• Custom fields: fields you added to Field Service tasks will not appear on shifts on their own.

Test on a copy, never on production. Restore a copy of your database, run the upgrade, then ask a dispatcher and a technician to run a normal day on it. They find gaps faster than any checklist.

What does the field service flow look like in Odoo 20, from request to invoice?

In Odoo 20, a field service job starts as a request, becomes a shift, is completed on the technician's phone and ends as an invoice. Here is the full flow in order.

1. Request: the customer fills in the new /service-requests form on your website, or a Helpdesk ticket comes in.

2. Quote: your team sends a quotation, or creates one later from the shift.

3. Shift: the request becomes an unscheduled shift that the dispatcher drags onto a technician.

4. Notice: the technician gets the schedule by email or WhatsApp, and the customer can get a confirmation email.

5. Work: the technician signs in, fills the worksheet, adds parts and gets the customer's signature.

6. Report: clicking Complete creates the customer report and updates the time spent.

7. Invoice: time, parts and travel fees go to the invoice through Sales.

Most businesses can keep their current steps. What changes is where each step lives, so map your current flow onto this one before you upgrade.

What changes for dispatchers in Odoo 20 Planning?

Odoo dispatch now happens in the Odoo Planning schedule, which gains a side panel, priority-based Auto Plan, maps and team shifts. Our Odoo 20 Planning release notes list all 20 Planning changes.

The changes dispatchers will notice most:

• Side panel: unscheduled shifts, such as web requests, sit in a panel and are dragged onto a technician and time.

• Priority shifts: shifts carry a priority from Low to Urgent, and Auto Plan schedules the higher ones first.

• Location-aware Auto Plan: Auto Plan uses the customer's location, so addresses need correct coordinates.

• Team shifts: one shift can hold several technicians, instead of one copy per person.

• Vans and kits: materials such as a van can be assigned to a technician and follow them onto every shift.

• Maps and travel times: a map timeline, routes and travel times in the Gantt, all powered by Mapbox.

What about jobs that do not finish on day one? Multi-visit jobs are common in installation and repair. Leave the remaining work as a new or open shift, link it to the same task, and plan it from the side panel.

Can Odoo schedule recurring maintenance visits? Yes. A shift can repeat at a set interval, and the repeats copy the technician, role and project from the first shift. Forum users who built recurring tasks by hand will find this simpler.

Can a technician decline a shift? If you allow it, a technician can click "I am unavailable" on a published shift, and it goes back to the open shifts for the dispatcher to reassign.

What changes for technicians using the Odoo field service mobile app?

Technicians now work from My Planning and My Map, where they sign in to each job, fill worksheets, add parts and collect signatures. The Odoo field service mobile app is the same Odoo app, and field work now lives in Planning.

According to Odoo's field service documentation, a job works like this:

• Before the job: the shift must be published and have a customer before the technician can sign in.

• During the job: the technician fills the worksheet, scans product barcodes and adds parts.

• At the end: clicking Complete creates the customer report, which the customer can sign, with an option to hide prices.

• Location: Odoo records the technician's location at sign-in and completion, and logs it on the shift.

• Navigation: My Map shows the day's jobs and opens each address in Google Maps.

Technicians who keep using WhatsApp, paper and Google Maps are a real risk. Field service teams fall back to these tools when the app feels slow. Give technicians a short, job-focused view and train them on their own phones.

Can technicians use Odoo field service offline?

Only for short gaps in signal: Odoo 20's offline mode is not built for working a whole day without internet. This is the top complaint we found from field teams working in basements, plant rooms and new builds.

Odoo's offline mode documentation sets clear limits:

• Open it first: you can only reopen records and views you opened while online.

• No photo uploads: attachments and images can be viewed offline but not uploaded.

• Changes wait in a queue: offline edits sync automatically when the connection returns.

• Storage cap: Odoo keeps up to 2 GB of offline data and removes the oldest first.

• Hard refresh wipes it: a hard refresh deletes all locally stored data.

The practical fix: ask technicians to open the day's shifts and worksheets before leaving signal, and to upload photos once back online. If your teams work offline for hours, plan a custom solution before you commit.

How does Odoo field service billing work in Odoo 20?

Billing runs through Sales, and you can invoice time, parts and travel from the shift. Turning on billing installs the Sales app.

The main options:

• Time-based billing: needs the Project and Timesheets apps and a billable project, and is based on the time recorded on the shift.

• Parts and products: added from the shift and invoiced through the linked sales order.

• Under warranty: ticking this sets the price of the job to zero.

• Travel fees: a fixed travel-time fee, or a fee per distance, which needs Mapbox to measure the distance.

• Quotes on site: a technician can create a quotation from the shift for extra work.

Set your billing rules in a test database first. Billing errors were among the most-viewed Field Service questions on the Odoo forum in earlier versions.

Do field technicians count as paid users in Odoo 20?

A technician who only does field work can be a cheaper Light User, but one who adds products to a job becomes a full User. This is the licence trap most businesses miss.

Field Services is on Odoo's Light User list. But Odoo's documentation says adding products from a shift needs the Sales access right "User: All Documents," which is outside the Light list. One right outside the list makes the person a full, billed User.

What about subcontractors? People you schedule in Planning are set up as employees. Without a login they see shifts on a Planning portal page, but the employee record still counts as a Light User. Our Odoo 20 Light User guide explains the rules.

What breaks in payroll and project reporting?

Odoo 20 removes work entries from Payroll, and replaces the profitability report on the Project dashboard. Both matter to service businesses that pay or price by time.

If your technicians' pay depended on planned shifts flowing into work entries, that flow needs rebuilding. Check overtime, night and weekend premiums, and travel time, which often sit outside project time.

Keep project time and working time apart. Project time tells you what a job cost. Working time covers attendance, breaks and labour rules. Field teams need both, and Odoo 20 is a good moment to separate them cleanly.

What breaks in custom code and integrations?

Any custom code built on Field Service tasks must be rewritten for Planning shifts. This is usually the largest single cost in a field service upgrade.

The main breaking points:

• Tasks to shifts: code that extends project.task for field service must move to planning.slot.

• One technician to many: the shift's resource_id field became resource_ids, so custom code, reports and filters on it break.

• Worksheets: custom code reading the old x_ worksheet models breaks, because those models are gone.

• Map views: custom map views must use the new routing values, ordered or optimized.

• Unscheduled shifts: code that assumes every shift has dates must handle shifts with no dates yet.

• Integrations: Odoo 20 removes XML-RPC and JSON-RPC, so connectors to other systems need updating.

For a step-by-step method, read our guide to the Odoo 20 upgrade and custom modules. For connectors, see our guide to Odoo API integration.

What do you need to set up before going live on Odoo 20 field service?

Several Odoo 20 field service features need outside accounts or clean data before they work. Set these up before go-live, not after.

• A Mapbox account and token: needed for routes, Gantt travel times and distance-based travel fees.

• Correct customer addresses: Auto Plan and maps need addresses with coordinates.

• Location sharing: the live map needs technicians' check-ins and location.

• A WhatsApp Business account: needed to send schedules by WhatsApp, with approved message templates.

• Helpdesk flow: confirm your tickets still create interventions as expected.

• Calendar sync check: Odoo's Google and Outlook sync covers the Calendar app, so test how technicians will see shifts on their phones.

What changes for your customers?

Customers get more ways to ask for service and more updates about it. These are new in Odoo 20 Planning.

• Website request form: customers book service at /service-requests and leave their address.

• Confirmation email: an optional email confirms the visit.

• Ratings: a report shows how customers rated your interventions.

• Equipment history: you can see every past visit for a serial number, flag equipment as maintained through Subscriptions, and open its manuals from Documents.

Is Odoo field service Community or Enterprise?

Odoo field service is Enterprise only, in Odoo 20 as before. All 20 Planning changes in Odoo 20 are Enterprise only too.

Community users have two routes. The Odoo Community Association offers its own Field Service modules, and paid field service apps are sold on the Odoo App Store. Both are separate from Odoo's own app, so check who maintains them before you build on them.

What about Odoo field service pricing? Field service needs an Enterprise subscription. Technicians who only do field work can be Light Users, and planners and office staff need full Users. Mapbox and WhatsApp Business are separate accounts with their own costs.

Where does Odoo field service still fall short?

Odoo field service handles scheduling, mobile work and billing well, but complex jobs and strict labour rules need extra work. Know these limits before you choose.

• Complex multi-trade jobs: Odoo does not shift follow-on work automatically when one step runs late.

• Team-wide route planning: maps order each technician's route, but Odoo does not offer a fleet-wide route optimiser.

• Skills and labour rules: Planning assigns by role and availability, so certifications, rest rules and overtime limits need setup or custom rules.

• Long offline work: offline mode covers short gaps only.

Is Odoo the best field service software? For businesses that want field service, stock, sales and accounting in one system, Odoo is a strong fit. Dedicated tools such as Jobber or ServiceTitan suit trade businesses that want field service alone.

What are the field service pain points by industry?

Every field service industry feels the Odoo 20 change in a different place, from van stock to compliance records. The table sums up the pain, the Odoo 20 solution and how we help.

Construction and installation firms feel the multi-visit problem most. We help them split each project into phases that dispatchers can move without losing the overall plan. See our Odoo ERP for construction.

Medical device and healthcare service firms need every inspection on record and easy to find. We design worksheets and access rules that keep audits simple. See our Odoo ERP for healthcare.

HVAC, solar and equipment service firms gain most from priorities, van stock and travel fees, as long as Mapbox and clean addresses are in place first.

How should you plan the switch to Odoo 20 field service?

Plan the switch around your quiet season, test it with real users and train dispatchers before technicians. A rushed switch in peak season costs far more than the upgrade.

1. Check your current setup: version, apps and custom modules.

2. Map today's flow, from request to invoice, onto the Odoo 20 flow.

3. List custom code, Studio worksheets and integrations that touch Field Service.

4. Set up Mapbox, addresses, WhatsApp and billing rules on a test copy.

5. Run a full day on the test copy with a dispatcher and two technicians.

6. Train dispatchers first, then technicians on their own phones.

7. Go live in your quiet season, with support on hand for the first two weeks.

Not sure what your system holds today? Our free Odoo Health Check shows your version, apps and modules, and the Odoo migration cost calculator gives a cost and timeline range.

How iVentureTeam helps with the Odoo 20 field service change

iVentureTeam moves your field service operation to Odoo 20 Planning with your data, worksheets and custom code working on day one. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists over 13+ years.

• Upgrade and testing: we run the move on a copy, check every job, worksheet and report, then switch production.

• Custom code rewrite: we move task-based code to shifts and update reports, filters and integrations, through our Odoo customization services.

• Dispatch setup: priorities, Auto Plan, Mapbox, travel fees, van stock and WhatsApp schedules.

• Licence review: we map each technician to the right licence before your renewal.

• Training: short, role-based sessions for dispatchers and technicians.

Looking for an Odoo partner for field service businesses? We work with installation, maintenance and inspection firms that need dispatch, stock and billing in one system.

Odoo field service case study: Stigah BV

A Dutch medical device safety firm shows what field teams need from Odoo: one record per device, mobile access and clear roles. Stigah BV has made healthcare aids safer across the Netherlands since 2005.

Stigah's device records, inspection schedules and protocol permissions sat in separate places. Field staff needed access from tablets and phones, and inspection history had to be kept for 7 years.

In 10 weeks, we built an Odoo portal with three user roles, inspection protocols with per-protocol permissions, and automation rules that drive inspection statuses. It works on desktops, tablets and phones, and keeps 7 years of inspection data.

"Our dealers and technicians now work from the same portal, and every device record is traceable," says Stigah's Managing Director. Read the Odoo healthcare case study for Stigah BV.

Stigah's project used Odoo Portal and automation rules, not the Field Service app. The lessons carry over to Odoo 20: make the device the core record, design worksheets around inspections, and give each role only the access it needs.

The bottom line on Odoo 20 field service

Odoo 20 field service is a stronger dispatch tool than before, but it is a real change for your people, your code and your licences. Odoo Online users already have it, and everyone else gets it at the upgrade.

Test the move on a copy, rewrite task-based custom code, set up Mapbox and clean addresses, check which technicians become full users, and train your dispatchers first. Then go live in your quiet season.

Ready to move your field service to Odoo 20?

Find out what the change means for your dispatch, technicians and custom code before you upgrade. Book a free Odoo field service review, call +91-90235-15208, or email business@iventureteam.com.