| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Approvals (approvals)
• Discuss (mail) • Employees (hr) |
| Lines of code | 235 |
| Technical Name |
approvals_routing |
| License | OPL-1 |
| Website | https://www.orado.cn |
Approval Routing — Dynamic Approver Resolution with Conditional Branching
Extend the standard Odoo Approvals module with rule-based dynamic routing. Resolve approvers from source documents, branch approval chains by amount thresholds or product categories, and configure everything through the familiar approver list UI — no coding required.
Key Features
🔄 Dynamic Approver Resolution
Resolve approvers at runtime from linked document fields. For example, automatically assign the buyer from a purchase order or the salesperson from a sale order as the first approver.
🔀 Conditional Branching
Route requests to different approvers based on domain conditions. Amount-based branching (e.g. ≤5000 → Manager, >5000 → Director) and product-category routing are fully supported.
📄 Generic Source Document
A Reference field on approval requests links to any source document
(purchase orders, sale orders, contracts, etc.). Downstream modules
simply register their models via _selection_source_document().
⚙ Native Domain Builder
Conditions use Odoo’s built-in domain widget — the same visual filter builder used in automation rules. No custom condition models, no code, just point-and-click configuration.
👥 Zero New Models
Extends the existing approval.category.approver model directly.
No new database tables, no data migration — just three new fields
on the approver configuration you already know.
🔃 Full Backward Compatibility
Categories without routing rules behave exactly as before. Existing approval workflows continue to work unchanged after installation.
Approver Source Types
| Source | Description | Example |
|---|---|---|
| Fixed User | A specific user configured on the category approver line (standard behavior). | General Manager, CFO, Accounting Supervisor |
| Document Field | Resolved at runtime by following a dot-separated field path from the approval request. | source_document.user_id (buyer from PO) |
| Request Owner | The user who created the approval request. | Self-review step, initial submission confirmation |
How It Works
- Open an Approval Category and go to the Approvers tab.
- For each approver line, choose the Approver Source: Fixed User, Document Field, or Request Owner.
- Optionally add a Condition (domain filter) — the approver line only activates when the condition matches.
- When a request is created, the system evaluates each line in sequence: checks the condition, resolves the user, deduplicates, and builds the approval chain.
- Use the Refresh Approvers button on draft requests to re-evaluate after changing key fields.
Configuration Examples
Payment Approval (amount-based branching):
| Seq | Name | Source | Condition |
|---|---|---|---|
| 10 | Buyer Review | Document Field: source_document.user_id | — |
| 20 | Manager Review (≤5000) | Fixed User: Manager | payment_amount ≤ 5000 |
| 20 | Director Review (>5000) | Fixed User: Director | payment_amount > 5000 |
| 30 | Finance Check | Fixed User: CFO | — |
Seq 20 lines are mutually exclusive — only one matches based on the payment amount.
Compatibility
Odoo 19 Enterprise
- Requires the
approvalsmodule (Odoo Enterprise) - Does not modify enterprise source code — pure inheritance
- Compatible with existing approval categories and requests
Support
If you have any questions or issues, please contact us at feihu.zhang@orado.cn.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module