Field Service Management in Odoo: Scheduling Technicians and On-Site Jobs
Short answer: Field service management in Odoo schedules technicians against open jobs, gives them the task details, worksheet and parts list on a phone, and turns a completed visit into an invoice without re-entering anything in the office. Each visit is a task with a customer, an address, a time slot and a technician; parts used come out of stock, time is logged, the customer signs on site, and the job is invoiced from the same record. It fits maintenance, installation and repair businesses that send people to a customer's site rather than a shop.
In most service companies we visit, the field team is coordinated from a WhatsApp group and a whiteboard. It works with three technicians. With fifteen, jobs are double-booked, parts disappear from stock without a trace, and invoices go out weeks after the work, if they go out at all. This guide covers what a field service system should solve, how to set it up in Odoo step by step, and the mistakes that keep teams on WhatsApp even after the system goes live.
What should it solve?
- Which technician is free, and how far they are from the next job.
- What parts a job needs, and whether they are in the van or the warehouse.
- Proof the work was done: signature, photos, time on site.
- Turning a finished job into an invoice the same day, not weeks later.
- A history per customer and per piece of equipment, so the next visit starts informed.
How does the flow work?
A service request becomes a task with a location, a time window and a technician. The technician sees it on a phone, with the customer's equipment history and any notes from the last visit. Parts used are logged against the job, pulling from stock automatically. Once marked done, the job can be invoiced, including both labour and parts, straight from the same record.
How do you set up Odoo Field Service step by step?
Odoo Field Service is part of Odoo Enterprise and runs on top of Project, Timesheets and, if you use parts, Inventory and Sales. On Odoo Community, a similar flow is built on Project with dedicated modules. Menu names follow recent Odoo versions.
1. Define your service types as projects
In Field Service → Configuration → Projects, create a field service project per type of work you invoice differently, for example Preventive maintenance contracts, Breakdown repairs or Installations. Each project has its own stages, team and invoicing rules.
2. Set up technicians and working hours
Make sure every technician is a user with the right access, and has working hours set. If technicians carry stock in their vans, set up each van as its own stock location so parts used are deducted from the right place, not from the main warehouse.
3. Enable the features you need
In Field Service → Configuration → Settings, enable worksheets if technicians must fill in a checklist or report on site, and products if they use parts or materials that must be invoiced and taken out of stock. Timesheets are part of the flow, so time on site is recorded by default.
4. Design your worksheet templates
In Field Service → Configuration → Worksheet Templates, create a template per job type: the checks to perform, readings to record, photos to attach and the customer's comments. Keep them short; a worksheet that takes longer than the job will be skipped.
5. Plan the day
Create tasks from a phone call, a helpdesk ticket or a sales order, then plan them in the Gantt view by technician and the map view to see the day's route. Drag and drop to reassign when someone is off sick or a job overruns.
6. Run the visit on the mobile app
On site, the technician opens the task in the Odoo mobile app, starts the timer, adds the parts used from the product catalogue, fills in the worksheet, takes photos and collects the customer's signature. The signed report can be emailed to the customer before the technician leaves.
7. Invoice the same day
When the task is marked done, time and parts are already on the linked sales order. The office reviews and creates the invoice from the same record, without asking the technician what happened.
| Step | WhatsApp and whiteboard | Odoo Field Service |
|---|---|---|
| Scheduling | Double-bookings and missed jobs | Gantt and map views by technician |
| Job details | Sent in a message, lost in the chat | Task with address, history and worksheet on the phone |
| Parts used | Not recorded; stock drifts | Added on the task and deducted from stock |
| Proof of work | A phone call afterwards | Timesheet, photos and customer signature |
| Invoicing | Weeks later, from memory | From the same record, the same day |
What usually goes wrong without a system?
- Jobs are scheduled on a WhatsApp group or a whiteboard, and double-bookings happen.
- Parts used on site are not recorded, so stock counts drift and nobody notices until a count.
- Invoicing waits for someone to remember what happened on a job from a week ago.
- There is no history of what was done at a customer's site last time.
What does an implementation look like?
Here is how this typically unfolds, in an anonymised, illustrative example: an air-conditioning maintenance company in Jeddah with technicians coordinated on WhatsApp and preventive maintenance contracts tracked in a spreadsheet. The work starts by separating contract visits from breakdown calls into two field service projects, each with its own invoicing rule. Vans are set up as stock locations and loaded with an opening count. One short worksheet per job type replaces the paper forms. During the first weeks, the coordinator keeps the WhatsApp group only for urgent messages, while every job is created and closed in Odoo. Once technicians see that a signed report closes the job on the spot, the paper forms disappear.
Which numbers should you track?
Once jobs run through the system, a few numbers tell you how the field operation is doing:
- Jobs completed per technician per day, by type of job.
- First-time fix rate: the share of jobs closed on the first visit, without a return trip for parts.
- Time from job done to invoice: the clearest measure of how much cash the old process was holding back.
- Van stock differences: what each van's count shows against what the system expects.
- Repeat visits per customer or equipment: a signal of recurring faults worth fixing at the source.
What are the common pitfalls?
- Long worksheets: technicians skip them. Ask only for what the customer or your warranty process needs.
- Van stock not set up: parts are deducted from the main warehouse, and van counts never match.
- Jobs still created outside the system: if the coordinator sends jobs on WhatsApp, the planning view is wrong. Create every job as a task.
- No connectivity plan: test the mobile app in your real coverage areas before go-live.
- Invoicing rules left vague: decide which jobs are billed by time, by fixed price or under a contract before the first visit.
Frequently asked questions
Does this work offline, if a site has no signal?
The mobile app can work with limited connectivity and sync once a signal returns, though this depends on configuration and should be tested for your coverage areas.
Can customers see when a technician is on the way?
Yes, this can be set up through notifications tied to the job status, if your process needs it.
Is this only for maintenance companies?
No. Installation teams, delivery and assembly services, and any business sending people to a customer's location can use the same structure.
Can a helpdesk ticket create a field service job?
Yes. When a support ticket needs someone on site, the helpdesk team can plan a field service intervention from the ticket, and the visit stays linked to the original request.
How are preventive maintenance contracts handled?
Recurring visits can be planned as recurring tasks or generated from the contract, and invoiced under the contract terms rather than per visit.
Is Odoo Field Service available in Odoo Community?
Odoo Field Service is part of Odoo Enterprise. On Odoo Community, a similar flow is built on the Project app with dedicated modules for scheduling, parts and invoicing.
Give your field team a system, not a WhatsApp group
ExtraMile builds field service workflows on Odoo for maintenance, installation and repair businesses, from van stock to worksheets and same-day invoicing.
Ask about field service on Odoo or message us on WhatsApp: Egypt · Gulf
This article was drafted with AI assistance for ExtraMile Business Solutions.
