Odoo and the Field Service App do not provide a way to track what is required and/or missing at the different stages of the FSM order process. Some organizations needs a way to track documentation, materials, signature and various activities.
This module allows you to have a list of sub-statuses and set them as default or potential sub-statuses on each FSM stage. The stage configuration will drive:
- the sub-status set when entering a stage
- the list of potential sub-statuses available depending on the stage
auto_awesome What this module does
AI-generated from the code · Odoo 15.0Adds a Sub-Status field to Field Service orders so teams can track what is required or missing at each stage. Sub-statuses are configured per stage and automatically applied when an order enters that stage.
This module extends the Field Service app with a second level of status tracking for orders. A new configuration menu called Sub-Status appears under the Field Service order configuration, where managers can create a simple list of sub-statuses (each one is just a name).
On each Field Service stage, you can now set a Default Sub-Status and a list of Potential Sub-Statuses. These fields only show for order-type stages. When an order is moved into a stage, the default sub-status of that stage is automatically written on the order, and the order's sub-status field only offers the default and potential sub-statuses of the current stage.
The order form shows the Sub-Status field next to the tags, and it is required, so every order always has one. Changing the sub-status is tracked in the chatter with a dedicated 'Substatus Changed' notification subtype.
Out of the box, a 'Default' sub-status is created and assigned to the New, Completed and Cancelled stages. Field Service users can read sub-statuses, while managers can create, edit and delete them.
Depends on
Menus it adds
Models and fields (3)
- fsm.order · extends an existing modelsub_stage_id (Sub-Status)
- fsm.stage · extends an existing modelsub_stage_id (Default Sub-Status), sub_stage_ids (Potential Sub-Statuses)
- fsm.stage.status · new modelname
Text generated by AI (DeepSeek) from reading the Odoo 15.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 3 confirmed, 6 with no information of 9 versions.
Sources · Odoo 12.0
Confirmed on 2026-11-03 in branch 12.0 of OCA/field-service.
terminal Installation and usage
OCA documentation · Odoo 15.0Installation
Source · Odoo 15.0To install Field Service and have the mapping features, you need to install GeoEngine.
Please refer to the installation instructions available at: https://github.com/OCA/geospatial/tree/11.0/base_geoengine
Configuration
Source · Odoo 15.0To configure this module, you need to:
- Go to Field Service > Configuration > Orders > Sub-Statuses
- Create your list of sub-statuses
- Go to Field Service > Configuration > Orders > Stages
- Select a stage and set the default sub-statuses as well as the potential sub-statuses
Usage
Source · Odoo 15.0To use this module, you need to:
- Go to Field Service > Operations > Orders
- Create a new service order.
- The sub-status is set to the default sub-status of the New stage.
- The list of sub-statuses is filtered based on the potential sub-statuses of the New stage.
- Move the service order in the process. The sub-status is set and filtered according to the stage.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.