| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 2066 |
| Technical Name |
skit_approval_engine |
| License | OPL-1 |
| Website | http://www.srikeshinfotech.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 2066 |
| Technical Name |
skit_approval_engine |
| License | OPL-1 |
| Website | http://www.srikeshinfotech.com |
DYNAMIC APPROVAL MANAGEMENT SYSTEM
Approval workflows for every Odoo screen — no coding required.
When a large purchase needs sign-off, does it get stuck in WhatsApp messages, emails and verbal confirmations with no clear record of who approved what? Odoo's built-in approvals only cover a handful of standard documents. The moment you need approvals on custom screens, conditional triggers or multi-level sign-offs — you're stuck building complex customisations.
The Dynamic Approval Engine changes that. Configure approval workflows on any Odoo screen that supports the chatter — including your own custom modules — without writing a single line of code.
This module is built for you if:
- Your team needs purchase, expense or HR approvals with amount-based conditions
- You have custom Odoo screens that need governance and sign-off controls
- You need a full audit trail showing who approved what and when
- Your organisation has multiple companies with separate approval policies
- You are tired of approval requests disappearing into email chains
How Organisations Use This Module
Manufacturing & Procurement
A manufacturing company sets up a 3-level purchase approval: Team Lead approves first, then Finance Manager, then CFO — but only for orders above ₹2,00,000. Below that threshold, no approval is required and the order flows through immediately.
Human Resources
An HR team configures leave approval for senior staff so that both the line manager and the HR director must sign off before leave is granted. Junior staff follow a simpler single-approver rule.
Custom Modules
A logistics company built a custom "Dispatch Order" screen in Odoo Studio. Using the Approval Engine, they enforce a mandatory approval gate before any dispatch is confirmed — without writing a single line of code.
Multi-Entity Organisations
A holding group with three subsidiaries in Odoo configures completely separate approval rules per company. Finance approvals in Company A have no effect on Company B or C.
Video Tutorial
Watch our detailed video demonstrations and tutorials on YouTube for hands-on learning.
Key Highlights
Chatter-Based Approval Framework
Works on any Odoo screen with a chatter — sales orders, vendor bills, custom modules, HR records. Not just the handful of built-in approval documents Odoo ships with.
Rule-Based Triggering
Set conditions so approvals only fire when they need to — for example, only when a purchase order exceeds ₹5,00,000. Configured in plain Odoo filter language. No coding required.
Sequential & Parallel Approvals
Sequential means approvers are notified one at a time in a fixed order. Parallel means all approvers are notified at once. You can mix both in the same workflow to match your exact org structure.
User & Group Approvers
Assign a specific person, an entire user group or both as approvers for each stage. Configure whether one approval from the group is enough or whether all members must sign off.
Multi-Company Approval Rules
Each company in your Odoo instance has completely separate approval configurations. No cross-contamination between entities — essential for group companies and holding structures.
Central Approval Dashboard
See every pending, approved, rejected and cancelled request in one place. Managers get a full picture of approval workloads without opening individual documents.
Real-Time Approval Banners
A prominent banner appears on the document itself when approval is pending. The requesting user and approvers see the live status — no one needs to go looking for it.
Automatic Escalation Control
Set a deadline in days for each stage. If the approver does not act within that time, the request automatically escalates. No more approvals left waiting indefinitely.
Complete Audit Trail
Every action — who approved, who rejected, when and any comment — is permanently logged in the document's own chatter. Fully traceable for audits, compliance and dispute resolution.
The module introduces a dedicated Approval Engine application with three core menus:
- Dashboard
- Requests
- Configuration
Dashboard
The dashboard provides a real-time overview of approval requests categorized by:
- Pending
- Approved
- Rejected
- Cancelled
See every pending approval at a glance — no more missed sign-offs or chasing colleagues.
Requests
Two smart request views are available:
My Requests
Track every request you've submitted — status, current stage and who is yet to approve.
All Requests
Full organisation-wide view — every approval request, every status, in one screen.
Flexible Configuration with Approval Rules & Stages
Approval Rules
Users can define approval rules by selecting:
- A chatter-enabled target model
- Multiple approval stages
Configure rules in minutes — pick the model, set conditions, assign approvers - Done.
Each rule can be linked to a specific button action (method) and triggered only when configured domain conditions are satisfied.
Approval Stages
Each rule can contain one or multiple approval stages with:
- Company and model control
- Target button method
- Domain conditions (example: amount > 50,000)
- Sequential or parallel approval types
- Approver users and approver groups
- Escalation days per stage
Notify multiple approvers simultaneously — no waiting for one before reaching the next.
This allows businesses to design simple to complex multi-level approval workflows without writing custom code.
Automatic Approval Triggering with Visual Status
When a user performs an action on a configured document:
- The system automatically raises an approval request
- A warning banner appears on the document indicating pending approval
- The requested approvers receive approval notifications
- When the approval type is set to Sequential and multiple approvers are configured:
- The first approver receives an email notification requesting approval
- Once approved, the next approver in the sequence is notified automatically
- This process continues until all required approvals are completed
- When the approval type is set to Sequential and multiple approvers are configured:
- The original action is temporarily restricted until approval is completed
Approval pending status displayed directly on the document — impossible to miss.
Intelligent Approver Handling
If the creator of the record already belongs to the configured approver group:
- The action is allowed immediately
- The approval is automatically recorded in the chatter
This prevents unnecessary blocking and ensures smooth business operations.
Delegation of Pending Approvals
The Approval Engine allows approvers to delegate pending approval requests to other users when required. For approval requests that are in Pending status, a dedicated Delegate button is available in the request view.
By clicking the Delegate button, users can select one or more users to whom the approval responsibility should be transferred.
Once delegated, the system automatically sends email notifications to the selected users, informing them that their approval is required.
This feature ensures business continuity when approvers are unavailable and enables flexible workload distribution across teams.
If an approver or manager rejects a request, the system instantly updates the banner to display the latest approval status.
Advanced Rule Protection & Data Integrity
The module enforces strong validations:
Rules with active requests cannot change the target model
Rules with existing requests cannot be deleted (only archived)
Modifying a rule automatically cancels all related pending requests
Cancelled requests remain visible in the dashboard
This guarantees consistent approval behaviour and protects historical approval data.
Our Features
Heading
Heading
Heading
Latest Releases
24th Jan, 2026
Odoo Studio compatibility: If approval configurations are created via Odoo Studio, the system will prioritise and apply the Studio configuration. The Approval Engine module rules will be ignored for that specific process.
About Us
Built by Srikesh Infotech — an Odoo-certified partner with 18+ years of ERP experience across 23 countries. All purchases include 90 days of free support.
Module Services
Industries We Serve
Our Services
Our Products
Free Support
You will get 90 Days free support in case any bugs or issue
Srikesh Infotech is an India based software company that focuses on highly qualitative, timely delivered and cost-effective offshore software development. We have 18+ years of technical and functional experience in ERP Customization and Implementation.
Please note that You're not allowed to distribute this module after purchase! In case of any question regarding this module feel free to email us on info@srikeshinfotech.com or raise a ticket on support.
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