WHAT WE SEE IN THE FIELD
The technician knows where to go but the company does not know what happened there.
- A customer calls with an issue.
- Someone creates a calendar event.
- The technician receives the address by email or WhatsApp.
- They go on site.
They use two spare parts from the van, and spend two and a half hours fixing the problem.
The customer signs a piece of paper.
Three days later, Finance asks: What should we invoice?
Inventory asks: Which parts were used?
The service manager asks: How long did the intervention take?
And someone starts collecting information.
The field intervention happened but the business process around it did not.
A good Field Service system should connect what happens before, during and after the technician arrives.
ODOO FIELD SERVICE IN PRACTICE
The intervention should start from the business event that created it
A Field Service task does not always need to be created manually.
In Odoo, field service tasks can be created from Sales Orders and also from Helpdesk tickets. A service sold through a quotation can create the corresponding field task automatically when the Sales Order is confirmed. A support request can also be escalated into an on-site intervention.
That connection matters.
Imagine this process:
Customer reports problem → Helpdesk ticket created → Remote diagnosis attempted → On-site intervention required → Field Service task created
The technician does not start with a blank task since the service request already has context.
And after the intervention, the Field Service task remains connected to the original support case.
That is considerably more useful than creating a separate calendar appointment.
SALES CAN CREATE FIELD WORK DIRECTLY
Some interventions start with a sale, not a support ticket
Consider an installation company. The customer buys:
- Installation service
- Equipment
- Configuration
The quotation is confirmed.
If the service product is configured accordingly, Odoo can create the Field Service task directly from that Sales Order.
This avoids a common operational gap.
Sales does not need to send an email saying:
“Can someone schedule this installation?”
The confirmed sale already becomes operational work because the Sales Order remains connected to the task.
This is an important Odoo principle: a transaction should create the next operational step whenever possible.
Not another internal message.
HOW WE WOULD CONFIGURE IT
Start by defining what creates an intervention
Before designing screens or stages, we would normally identify the main entry points.
Example:
New installation: Triggered by a Sales Order.
Corrective maintenance: Triggered by a Helpdesk ticket.
Preventive maintenance: Created according to an agreed service schedule.
Inspection: Created as a planned field task.
Commercial intervention: Possibly linked to an existing customer or Sales Order.
Different intervention types may require different information and different workflows.
- An installation may require equipment information and a commissioning checklist.
- A repair may require fault description, serial number and parts consumed.
- An inspection may require a structured report.
The task should therefore reflect the type of work being performed.
PLANNING THE TECHNICIAN
Assignment is more than putting a name on a calendar
Once the task exists, someone still needs to decide:
- Who should go?
- When?
- Where?
- How long should the intervention take?
Odoo Field Service tasks can carry assignees, dates and allocated time, and the broader Odoo planning environment can be used to organise resources and workload. Field Service also provides a map view of scheduled interventions.
This means dispatching becomes part of the same operational system.
The planner can work from the actual tasks rather than reconstructing the schedule in a separate calendar.
LOCATION MATTERS
Field Service is partly a logistics problem
A technician may have five interventions in one day and becaususe of thate, the order matters.
Travelling from: Lisbon → Sintra → Almada → Cascais → Loures would not be a particularly efficient schedule.
Odoo Field Service includes a map view showing task locations, and tasks can be organised into an itinerary according to their planned dates. With the relevant mapping integration, technicians can also open routes in Google Maps.
This does not replace a full route-optimisation platform for highly complex dispatch operations.
But for many field service businesses, simply having customer locations and daily interventions visible together already improves planning considerably.
WHAT HAPPENS ON SITE?
The technician should work from the same task the office sees
Once on site, the Field Service task becomes the operational record of the intervention, and depending on the process, the technician may need to record:
- Work performed
- Time spent
- Products or spare parts used
- Customer observations
- Photos or attachments
- Worksheet information
- Completion status
The objective is simple: when the technician leaves, the company should not need another phone call to understand what happened.
The task should contain the result.
TIMESHEETS
Time spent should not need to be reconstructed later
Odoo Timesheets can be used to log time directly against projects and tasks, including through a timer. Timesheets can also support customer invoicing where services are billed on a time-and-material basis.
Considerind an intervention scheduled for two hours, if the technician actually spends three hours and fifteen minutes, that information may affect:
- Customer invoicing
- Project profitability
- Technician utilisation
- Future planning assumptions
- Warranty analysis
The important point is not simply knowing when the technician arrived, but rater knowing how much effort the intervention actually consumed.
PRODUCTS AND SPARE PARTS
The two parts taken from the van should not disappear from stock
This is where Field Service becomes particularly interesting from an ERP perspective.
Odoo allows technicians to add products used during an intervention through the Field Service product catalogue.
Those products can update inventory and can also be added to the customer invoice.
Imagine a repair requiring:
- 1 replacement pump
- 2 seals
- 1 filter
The technician records those items while completing the intervention and now the same information can serve three purposes:
- Operations knows what was used
- Inventory knows what left stock
- Finance knows what may need to be invoiced
There is no need to type the same consumption again later.
TECHNICIAN VAN STOCK
A van can effectively behave like a warehouse
Field technicians often carry stock with them.
Odoo allows users to have a default warehouse, which can be useful when a technician regularly draws materials from a specific warehouse or carries inventory associated with their field operations. When materials are used through Field Service, stock movements can be reflected against the relevant warehouse.
This is a small configuration choice with large operational consequences.
Without stock visibility, the business may know:
“We have 14 units.”
But not know that:
- 8 are in the main warehouse
- 3 are in Technician A's van
- 2 are in Technician B's van
- 1 has already been consumed but not recorded
Field Service processes only become reliable when physical material movement is also reliable.
TIME AND MATERIAL INVOICING
The invoice should follow what actually happened
Some field services are sold at a fixed price, others are billed according to:
- Time spent
- Materials used
or both.
Odoo Field Service supports time-and-material invoicing flows where products consumed during the intervention are added to the relevant sales flow, while billable timesheets can provide the basis for invoicing labour.
This means Finance does not need an email saying:
“Please invoice 3 hours, one pump and two seals.”
The operational data already exists, and so, the invoice can be based on what the technician actually recorded.
That reduces both administrative effort and billing leakage.
BILLING LEAKAGE
Unrecorded field work is often unbilled field work
This is an underestimated issue.
A technician uses a €75 component, if nobody records it, the customer never gets billed.
Or the technician spends an extra 90 minutes on site and the service report says only:
“Issue solved.”
If finance invoices the standard two hours.
- The work happened.
- The cost happened.
- The revenue did not.
When time and materials are recorded inside the same operational task, these omissions become much easier to prevent.
Field Service configuration therefore affects profitability, not only scheduling.
WORKSHEETS
Some interventions require more than free text
Certain field processes need structured information. For example, a maintenance intervention might require:
- Equipment condition
- Meter reading
- Safety checks
- Components replaced
- Measurements
- Customer observations
- Recommended next action
Odoo Field Service supports worksheets that can be used to structure the information technicians capture during an intervention. Worksheets can also be associated with Field Service tasks created from Helpdesk.
This is useful when the organisation needs consistent service documentation. But the same rule applies here as elsewhere in Odoo:
- Do not create twenty fields because they are possible.
- Capture the information that someone will actually use.
CUSTOMER SIGNATURE
Completion should be confirmed where it happens
For many businesses, the technician finishing the work is not enough - the customer needs to confirm that the intervention took place.
Field Service worksheets can be signed by the customer after the work has been completed, providing confirmation of the intervention.
This can replace processes where technicians return to the office with paper documents that later need to be:
- scanned,
- matched to the customer,
- attached to the job,
- and stored somewhere else.
The evidence stays connected to the task.
FROM HELPDESK TO FIELD SERVICE
Remote support and on-site support should not become two disconnected processes
This integration is particularly valuable. Imagine:
- A customer reports that a machine has stopped working.
- Support creates a Helpdesk ticket.
- The support team tries remote troubleshooting.
- They identify that an engineer must visit the site.
From the Helpdesk ticket, an on-site Field Service intervention can be planned and the resulting field task remains linked to the original ticket.
Now the engineer can see why they are going and after the intervention, Support can see what happened.
That creates continuity across Customer request → Diagnosis → Intervention → Resolution instead of two teams keeping two separate histories.
THE MOST COMMON MISTAKE
Using Field Service as a digital calendar
Imagine an implementation where each task contains:
- Customer.
- Address.
- Date.
- Technician.
- Nothing else.
The company now has a better calendar, but it still does not know:
- what happened,
- how long it took,
- which materials were used,
- whether the customer confirmed completion,
- what should be invoiced,
- or whether the original support issue was solved.
Field Service creates value when the intervention is connected to the wider ERP, not simply when the appointment appears on a screen.
ANOTHER COMMON MISTAKE
Making technicians perform administration for the office
The opposite mistake is equally common.
- A technician finishes a 45-minute intervention.
- Then spends 20 minutes filling in Odoo.
- Ten fields.
- Five mandatory notes.
- Three classifications.
- Photos.
- Checklist.
- Timesheet.
- Stock.
- Signature.
- Internal report.
The system may contain excellent data but the field team will hate using it.
Every piece of information requested from the technician should therefore answer a question: Who uses this information and for what?
If the answer is unclear, we would challenge whether it needs to be captured.
Good Field Service design protects data quality without turning technicians into data-entry clerks.
FIELD SERVICE IS AN END-TO-END PROCESS
The task is only the middle
The real process may look like this:
Quotation → Sales Order → Field Service Task → Planning → Technician Intervention → Timesheet + Materials → Customer Signature → Invoice
Or:
Helpdesk Ticket→ Remote Diagnosis → Field Intervention → Resolution
Different companies will have different flows. The important point is that Odoo can connect the steps.
A strong implementation decides where those connections should exist.
OXALYO'S TAKE
Field Service should close the gap between the office and the field
The hardest part of field operations is often not performing the intervention but keeping everyone else aligned with what happened.
- Sales needs to know what was sold.
- Planning needs to know who is going.
- The technician needs the right information.
- Inventory needs to know what was consumed.
- Finance needs to know what should be billed.
- Customer Service needs to know whether the issue was resolved.
- Management needs to understand time, cost and performance.
When these teams operate through separate calendars, messages and spreadsheets, every intervention creates administrative work.
A well-configured Odoo Field Service process connects that information around the same operational record.
The technician does the work once - the business should not need to reconstruct it afterwards.
FAQ: ODOO FIELD SERVICE
What is Odoo Field Service?
Odoo Field Service is used to manage work performed at customer locations, including field tasks, technician assignment, planning, time recording, materials and related service processes.
Can Odoo create a Field Service task from a Sales Order?
Yes. A service product can be configured so that confirming a Sales Order automatically creates the corresponding Field Service task.
Can Odoo create an on-site intervention from a Helpdesk ticket?
Yes. Odoo Helpdesk can create a Field Service task for an on-site intervention while maintaining the relationship with the original support ticket.
Can technicians record time in Odoo Field Service?
Yes. Odoo Timesheets can be used to record time against tasks, including through timers, and those timesheets can support invoicing in billable service scenarios.
Can technicians record spare parts used during an intervention?
Yes. Field Service includes product management functionality that allows products used on site to be recorded. This can update inventory and add the products to the relevant invoicing flow.
Can Odoo manage stock carried by field technicians?
Odoo can associate users with default warehouses, which is useful in field service scenarios where technicians carry stock or regularly use materials from a specific warehouse.
Does Odoo Field Service support customer signatures?
Yes. Field Service worksheets can be used to document completed work and can be signed by customers to confirm the intervention.
Can Odoo show field interventions on a map?
Yes. Odoo Field Service provides a map view for tasks with customer addresses and can display itineraries based on scheduled interventions.
Can Odoo invoice field service based on time and materials?
Yes. Odoo can combine billable timesheets with products consumed during the intervention to support time-and-material service invoicing.