This module allows to add a substate to purchase request. For each purchase request state you can define a substate. We this module you can define substate which allow you to extend purchase request workflow. For example, you can add substate "To Verify" if the order can not be approved without document checked and verified
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Adds sub-states to purchase requests, letting you track extra steps like 'To Verify' or 'Checked' inside the normal approval states and send an email when a request is verified.
This module extends purchase requests with sub-states, which are smaller steps that sit inside the standard request states. On the purchase request form a new status bar appears in the header showing the sub-state, and you can click it to move the request between the sub-states that belong to its current state.
A configuration record is created for the purchase request model, with two target states: 'To be approved' and 'Approved'. Demo data shows example sub-states for the 'To be approved' state: 'To Verify', 'Checked' and 'Verified', each with its own order.
- The 'Verified' sub-state is linked to an email template named 'Verified'. When a request reaches that sub-state, the requester receives an email saying their purchase request has been verified by the procurement team.
- The sub-state choices shown on a request are filtered so only those matching the request's current state are available.
The module touches the purchase request screen and the sub-state configuration model, and it adds 'Purchase Request' as a possible model when setting up sub-state types. No other business rules, checks or scheduled actions are defined in the code.
Depends on
Required by other modules
Models and fields (2)
- purchase.request · new model
- base.substate.type · extends an existing modelmodel
Text generated by AI (DeepSeek) from reading the Odoo 18.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 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/purchase-workflow.
terminal Installation and usage
OCA documentation · Odoo 18.0Usage
Source · Odoo 18.0- Go to Settings \> Technical \> Database Structure and Add "Base substate". If necessery you can add "target State values" (ex define a substate for "cancel" state). Substate sequence is very important.
- Create a purchae request and check if the substate are displayed on the header of form view. Check if you can't set substate defined for purchase request if sate is a To be approved.
No verified information in OCA: Installation, Configuration.
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.