Odoo Field Service: Dispatch, Worksheets, and On-Site Parts

Introduction

Odoo Field Service supports businesses that sell expertise and outcomes: projects, timesheets, field visits, and helpdesk tickets should tell one story about customer commitment and margin.

When delivery and support run on separate tools, utilization drops, SLAs are missed, and invoicing happens weeks after work is done.

Field Service links tasks, time, parts, and customer communication so account managers see delivery health without chasing status emails.

Agency owners, professional services partners, and customer support leads can map these use cases to how they already run engagements.

Field Service is part of Odoo's modular ERP. Teams adopt it when they want clear responsibilities, repeatable workflows, and searchable history instead of isolated messages and offline spreadsheets. Odoo Field Service: Dispatch, Worksheets, and On-Site Parts states the storyline for stakeholders approving.

This article is a ranked Top 10 from Level 1 (easy) to Level 10 (expert). Every level includes numbered steps: what you would actually click in Odoo Field Service.

Start where you are comfortable, not at level 10 because it sounds impressive.

Read the challenge section next, then open the level that matches your team today.

In this guide, you will see:

• What Odoo Field Service is responsible for in a typical company stack
• Where teams feel the most friction today (and why)
• Ten ranked use cases from beginner discipline to advanced strategy
• When automation or integrations justify bringing in an Odoo partner

The Challenge

A client calls angry about a delayed project. Support, delivery, and account management each have a different version of truth. Time was billed late, so margin looked fine until someone ran the numbers.

Project and support businesses sell time and outcomes, but utilization and SLAs are tracked late. Margin erodes when billing, delivery, and ticket history are not on one timeline.

Sound familiar? Teams usually hit these walls:

• Projects started late because sales context is missing
• Support tickets without link to contracts or invoices
• Time captured after the fact, hurting billable margin

The good news: you do not need a big-bang project to fix everything. Pick one use case below, run it for 30 days in Odoo Field Service, and measure what changes.

Top 10 Field Service Use Cases

10 use cases for Odoo Field Service, ranked from Level 1 (easy, do it this afternoon) to Level 10 (expert). Each one answers: what would we build, and what are the clicks in Odoo?

Level 1 is the easy daily win. The last level is intentionally over the top so you see how far the same app can scale when architecture and data stay clean.

Pick your level, follow the numbered steps in a test database, then move up when the previous level feels boring.

1. Dispatch your first on-site visit from one task Level 1 — Easy

Level 1 is the simplest Field Service action: one dispatcher creates one task and assigns it to one technician. No planning grid, no worksheet, no invoicing yet, just a paperless work order.

Here's how you'd do it in Odoo:

1. Install the Field Service app, open Field Service, Tasks, New, and set Customer, Site Address, and Scheduled Date.
2. Pick one Technician in the Assigned To field, write a short Description of the issue, and save the task.
3. Attach any prior photo or invoice from the chatter so the technician arrives on site already in context.
4. The technician opens the Odoo mobile app, taps the task, follows the address link, and reads the brief en route.
5. On return, the technician marks the task Done; the customer receives an automatic completion email with the report.

What you get: Paper work orders disappear, the dispatcher and the technician read the same task, and nothing is lost between the office and the van.

2. Equip technicians with the mobile field service app Level 2 — Easy

Level 2 turns the phone into the technician's main tool. The Odoo mobile app, with map navigation and offline mode, removes the round-trip to the office for every job.

Here's how you'd do it in Odoo:

1. Ask each technician to install the Odoo mobile app and log in with their Field Service user; create the user if needed in Settings, Users.
2. From Field Service, My Tasks, the technician sees only their assigned visits of the day, sorted by scheduled time.
3. Tap the Address link to open the route in the phone's native maps app for turn-by-turn navigation to the customer site.
4. Use the Start and Stop timer buttons on the task to log time on site; the duration is captured even without a connection.
5. At the end of the day, the phone syncs and the office sees every completed visit, every photo, and every note already in Odoo.

What you get: Technicians spend their day on customer sites instead of in the office, and the dispatcher gets real-time status on every visit.

3. Build a worksheet template for repeatable visit reports Level 3 — Easy

Level 3 introduces Worksheets, the first pillar of the blog title. A short structured form replaces free-text notes so every visit of the same type produces the same data.

Here's how you'd do it in Odoo:

1. Install Worksheet, go to Field Service, Configuration, Worksheet Templates, New, and name it Annual Maintenance Check.
2. Use Studio to drop the fields the technician must fill: equipment serial, condition Pass or Fail, measurements, parts replaced, notes.
3. On the task type Annual Maintenance, link this Worksheet Template so it appears automatically inside every related task.
4. On the mobile app, the technician fills the worksheet on site, and the customer signs the same screen before leaving.
5. Open the closed task to find a PDF with the worksheet, the signature, and the chatter; share it with the customer in one click.

What you get: Visit reports stop being random paragraphs and become structured data the team can filter, compare, and act on.

4. Track parts used on site so stock and invoice match reality Level 4 — Medium

Level 4 covers the second pillar of the blog title: on-site parts. The Products tab links Field Service to Inventory so the van stock decrements automatically and nothing is billed twice or forgotten.

Here's how you'd do it in Odoo:

1. In Inventory, Configuration, Warehouses, create one virtual location per technician van so its stock is tracked separately from the main warehouse.
2. On each Field Service task, open the Products tab and add the parts the technician expects to use, with a quantity.
3. On the mobile app, the technician confirms parts as Used at the end of the visit, or adds extra parts that were not planned.
4. On task validation, Odoo posts a stock move that decrements the van location; the invoice line picks up the same products and prices.
5. Schedule an Internal Transfer every Monday morning to refill the van from the main warehouse based on the previous week's consumption.
6. Inventory, Reporting, Stock per Location, to confirm each van carries the right parts for the upcoming week of visits.

What you get: Month-end surprises disappear: every part used on site is on the invoice, in the stock report, and in the customer's history.

5. Auto-invoice labor and parts from the technician's timesheet Level 5 — Medium

Level 5 closes the cash loop. The Timesheets integration on each task captures real labor time, so the invoice combines hours and parts without any rekeying in Sales.

Here's how you'd do it in Odoo:

1. On the task, set Sales Order or create one with a Service product invoiced on Timesheets and a Product Hourly Rate matching the contract.
2. On the mobile app, the technician starts the timer on arrival and stops it before leaving; the timesheet line is attached to the task automatically.
3. Confirm the parts used in the Products tab; both labor hours and parts are pushed to the related Sales Order in real time.
4. From the task, click Create Invoice; Odoo generates a draft invoice with the breakdown (hours, parts, travel) ready for review.
5. Send the invoice by email with the worksheet PDF attached, so the customer sees what was done and what is billed in one document.
6. Reporting, Time and Material per Task, to confirm billable utilization per technician and per customer every week.

What you get: Invoicing time per visit drops from days to minutes, and finance closes the month with no parked or partial work orders left open.

6. Capture signature, photos and GPS as audit-grade proof of visit Level 6 — Medium

Level 6 uses the mobile capture features unique to Field Service. Signature, before-after photos and GPS coordinates turn every visit into an audit-grade record that survives any customer dispute.

Here's how you'd do it in Odoo:

1. On the task, the technician taps Add Photo at arrival to capture the equipment state before any intervention starts.
2. At the end of the work, the technician adds an After photo and a short note; both are attached to the chatter with a timestamp.
3. Enable Geolocation on the task type so the GPS coordinates of the device are logged at the start and at the end of the visit.
4. The customer signs the worksheet on the technician's screen; the signature is embedded in the PDF report and stored on the task.
5. On the task type, mark Signature and Photo as Required to Close so technicians cannot finish a task without the proof.

What you get: Service disputes become 30-second conversations because the photo, the signature, and the GPS trace already live on the task.

7. Plan and route multi-tech teams across many sites with the map view Level 7 — Hard

Level 7 connects Field Service to Planning. The map view assigns the right technician to the right job based on skill, location, and availability, and sends the customer an ETA window automatically.

Here's how you'd do it in Odoo:

1. Install Planning, then Field Service, Configuration, Technicians, and set each tech's base location, working hours, and Skills.
2. Open the Planning Gantt and the Map view to see all open tasks and where every technician is for the week.
3. Drag a task on the map to the nearest available technician with the right Skill; Odoo updates the Scheduled Date and notifies the technician.
4. Enable an ETA SMS template so the customer receives a window the morning of the visit, with the technician's name and phone number.
5. When a job runs long, drag the next visit to a later slot or reassign it to a colleague; the customer gets a new ETA in one click.

What you get: More billable hours per technician per week, less drive time, and fewer 'where is the tech?' calls from frustrated customers.

8. Sell recurring maintenance plans with auto-generated yearly visits Level 8 — Hard

Level 8 plugs Field Service into Subscriptions. Recurring contracts produce their own scheduled visits, so planners stop firefighting quarterly maintenance and start running it on rails.

Here's how you'd do it in Odoo:

1. In Subscriptions, create a Maintenance Plan template with the number of visits per year, the invoicing rule, and the renewal term.
2. In Sales, build a quotation that includes the Maintenance Plan product; on confirmation, the subscription and first invoice are created.
3. Use Studio Automation: when a subscription is Active, generate Field Service tasks for each scheduled visit of the year in one batch.
4. On each task, the planner assigns the right technician; the customer receives a confirmation email seven days before the visit.
5. On the subscription, the smart button Visits shows all past and upcoming tasks with their status, signed worksheets, and invoices.
6. Sixty days before renewal, an Activity reminds the account manager to call the customer; renewal is signed via the Sign app.

What you get: Recurring service revenue runs with operational discipline; planners spend their week on exceptions instead of recreating the same calendar.

9. Run SLA contracts with a customer portal and real-time visit status Level 9 — Hard

Level 9 makes Field Service customer-facing. SLA rules drive priority and escalation, while the portal lets the customer open tickets, follow status, and download reports without calling the dispatcher.

Here's how you'd do it in Odoo:

1. Install Helpdesk, configure SLA Policies (response under 2 hours, resolution under 8 hours for Priority Critical), and link them to a Service Team.
2. Enable Portal Access on each customer contact so they reach a dedicated page listing their open tickets, scheduled visits, and signed reports.
3. On any SLA breach, Studio Automation escalates the related Field Service task to a senior technician and pings the account manager in chatter.
4. From the portal, the customer opens a ticket; Helpdesk creates the matching Field Service task with the right priority and team automatically.
5. The customer follows the visit in real time on the portal: assigned technician, ETA window, on-site status, signed worksheet, invoice.

What you get: Customers feel served, SLAs become measurable, and account managers walk into renewals with data instead of promises.

Wiring SLA policies, the customer portal, the Helpdesk-to-Field-Service handoff, and the breach escalations is the kind of cross-app setup Dasolo runs as a partner-led engagement.

10. Run an IoT-driven AI dispatcher across the full Field Service stack Level 10 — Expert

Level 10 is the full operating system: IoT sensors trigger interventions, an AI dispatcher picks the right technician and the right parts, and a live dashboard shows the whole field operation in one view.

Here's how you'd do it in Odoo:

1. Install the Odoo IoT box on customer equipment, or use a vendor MQTT or REST feed, to push sensor data to Odoo every minute.
2. With Studio, when a sensor crosses a threshold for 60 seconds, auto-create a Field Service task with Priority Urgent and the matching task type.
3. Train an AI dispatcher on past tasks to pick the nearest available technician with the right Skill and the parts already in the van.
4. If the part is missing in the van, an Internal Transfer is scheduled the same day from the warehouse; the customer is notified before failure.
5. Marketing Automation sends a tailored email after each visit (NPS, renewal hint, upsell) based on equipment age and contract type.
6. Build a Spreadsheet Field Live dashboard: open tickets, ETA risk, billable hours, predictive vs reactive ratio, and SLA breaches, refreshed in real time.

What you get: Equipment uptime climbs, reactive interventions drop by 30 to 60 percent over a year, and field service becomes a growth engine instead of a cost center.

Designing the IoT pipeline, the AI dispatch rules, the Subscriptions and Inventory wiring, and the live operations dashboard is the architecture Dasolo assembles as a partner-led engagement, so teams skip the multi-quarter trial-and-error phase.

When Expert Help Makes Sense

If levels 1 to 6 fit your world, you can often succeed with standard Odoo Field Service, a patient internal owner, and a sandbox where people are allowed to break things safely.

From level 7 upward, the stakes rise: automated workflows that email the wrong customer, Studio fields that block upgrades, APIs that silently stop syncing stock at 2 a.m.

That is not a failure of your team. It is a signal that architecture, testing, and governance matter.

Bring in a partner when you need multi-app design, country-specific compliance, complex integrations, or a go-live date the board already put in the calendar.

Work With Dasolo

Dasolo helps companies implement Odoo the way they actually work: custom apps, clean integrations, and training people will remember after the consultants leave.

If your roadmap for Field Service includes the advanced use cases in this guide, we can map a phased plan: quick wins first, then automation and integrations with clear owners and test scripts.

You keep control of scope and budget. We bring the Odoo depth so your team does not learn expensive lessons in production.

Book a free consultation:

Schedule your demo