Manage Field Service Locations, Workers and Orders
Field Service
This module is the base of the Field Service application in Odoo.
Table of contents
Configuration
The base Field Service module can be used with minimal initial configuration. It also allows for many advanced features, which require a more in-depth configuration.
Order Stages
The stage of an order is used to monitor its progress. Stages can be configured based on your company’s specific business needs. A basic set of order stages comes pre-configured for use.
- Go to Field Service > Configuration > Stages
- Create or edit a stage
- Set the name for the stage.
- Set the sequence order for the stage.
- Select Order type to apply this stage to your orders.
- Additonally, you can set a color for the stage.
Field Service Areas
You can manage designated areas or locales for your field service workers, salesmen, and other resources. For example, salesmen may serve a particular Territory. There may be multiple Territories served by a single Branch office location. Multiple Branches are managed within a District and these Districts are managed under an encompassing Region.
Setup a Territory
- Go to Settings > Users & Companies > Territories*
- Create or select a territory
- Set the territory Name and description
- Select or create a branch which this territory serves
- Choose a type of zip, country whichs defines the boundary used
- Input a list of zip codes, countries based on your desired configuration
Setup Branches, Districts, and Regions
If your business requires, define your Branches, Districts, and Regions. These are found under Field Service > Configuration > Locations
Advanced Configurations
Additional features, automations, and GeoEngine features can be enabled in the General Settings panel for Field Service.
- Go to Field Service > Configuration > Settings
- Enable additional options
- Configure new options
Manage Teams
Teams can be used to organize the processing of field service orders into groups. Different teams may have different workflows that a field service order needs to follow.
- Go to Field Service > Configuration > Workers > Teams
- Create or select a team
- Set the team name, description, and sequence
You can now define custom stages for each team processing orders.
- Go to Field Service > Configuration > Stages
- Create or edit a stage
- Select the teams for which this stage should be used
Manage Categories
Categories are used to group workers and the type of orders a worker can do.
- Go to Field Service > Configuration > Workers > Categories
- Create or select a category
- Set the name and description of category
- Additionally, you can select a parent category if required
Manage Tags
Tags can be used to filter and report on field service orders
- Go to Field Service > Configuration > Orders > Tags
- Create or select a tag
- Set the tag name
- Set a color index for the tag
Manage Order Templates
Order templates allow you to create standard templates for your orders.
- Go to Field Service > Master Data > Templates
- Create or select a template
- Set the name
- Set the standard order instructions
Usage
To use this module, you need to:
Add Field Service Locations
Locations are the specific places where a field service order is performed.
- Go to Field Service > Master Data > Locations
- Create a location
You can also convert an existing contact:
- Open the contact form
- Go to the Field Service tab
- Click Convert to FS Location
Or create a child contact with type Location under a customer; a related Field Service location is created automatically.
Add Field Service Workers
Workers are the people responsible for performing a field service order. These workers may be subcontractors or a company’s own employees.
- Go to Field Service > Master Data > Workers
- Create a worker
You can also convert an existing contact:
- Open the contact form
- Go to the Field Service tab
- Click Convert to FS Worker
Process Orders
Once you have established your data, you can begin processing field service orders.
- Go to Field Service > Dashboard > Orders
- Create or select an order
- Enter relevant details for the order
- Process order through each stage as defined by your business requirements
Known issues / Roadmap
The roadmap of the Field Service application is documented on Github.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Authors
- Gray Matter Logic
Contributors
- Gray Matter Logic:
- Maxime Chambreuil <maxime.chambreuil@graymatterlogic.com>
- Wolfgang Hall <whall@graymatterlogic.com>
- Maxime Chambreuil <maxime.chambreuil@graymatterlogic.com>
- Steve Campbell <scampbell@graymatterlogic.com>
- Bhavesh Odedra <bodedra@graymatterlogic.com>
- Michael Allen <mallen@graymatterlogic.com>
- Sandip Mangukiya <smangukiya@graymatterlogic.com>
- Serpent Consulting Services Pvt. Ltd. <support@serpentcs.com>
- Brian McMaster <brian@mcmpest.com>
- Raphaël Reverdy <raphael.reverdy@akretion.com>
- Ammar Officewala <ammar.o.serpentcs@gmail.com>
- Yves Goldberg <yves@ygol.com>
- Freni Patel <fpatel@graymatterlogic.com>
- Tecnativa:
- Víctor Martínez
- Nils Coenen <nils.coenen@nico-solutions.de>
- Alex Comba <alex.comba@agilebg.com>
- APSL-Nagarro:
- Bernat Obrador <bobrador@apsl.net>
- Antoni Marroig <amarroig@apsl.net>
- Komit Consulting:
- Truong Thi Kim Hoa <hoa-ttk@komit-consulting.com>
Other credits
The development of this module has been financially supported by:
- Gray Matter Logic <https://www.graymatterlogic.com>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainers:
This module is part of the OCA/field-service project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
What this app does not do
- The roadmap of the Field Service application is documented on Github .
Store apps required
None.
Odoo Community modules used
base_geolocalizecontactsresource
Apps that complement it
| Series | Version | Status | Published on |
|---|---|---|---|
| 19.0 | 19.0.1.2.3 | In development | 25/09/2026 |
Listing generated from julien2364/omnifloo-oca-field-service (branch 19.0, commit 21946f6a27bb).
Automatic store check (separate from the publisher's), applied to all apps. Conforme.
| Check | Result | Effect if absent |
|---|---|---|
| Manifeste lisible sans exécution | conforme | bloquant |
| Licence reconnue (AGPL-3) | conforme | bloquant |
| Aucune dépendance vers Odoo Enterprise | conforme | bloquant |
| Aucun import de code Enterprise | conforme | bloquant |
| Aucun en-tête de licence Enterprise | conforme | bloquant |
| Icône static/description/icon.png | conforme | déclasse |
| Description (static/description/index.html ou README) | conforme | déclasse |
| Tests automatisés (tests/test_*.py) | conforme | déclasse |
| Traduction française (i18n/fr.po) | conforme | info |
| Section « Ce que le module ne fait pas » | conforme | info |
| Titre de 70 caractères au plus (13 actuellement) | conforme | info |
| Résumé en français | absent | info |
Reviews from signed-in customers. One rated review per customer; the publisher can reply. Sign in to leave a review.
- Publisher
- Odoo Community Association (OCA)
- Report a problem
- https://github.com/OCA/field-service
- Omnifloo customers
- Support included with your plan: help centre.