| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Employees (hr) |
| Lines of code | 408 |
| Technical Name |
cm_sa_approval_escalation_engine |
| License | OPL-1 |
| Website | https://cm.sa |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Employees (hr) |
| Lines of code | 408 |
| Technical Name |
cm_sa_approval_escalation_engine |
| License | OPL-1 |
| Website | https://cm.sa |
| Versions | 17.0 18.0 19.0 |
Approval Escalation Engine
Reassign approvals up the management chain when the approver does not act in time.
A purchase order, expense report, or leave request waiting on one approver is one of the most common Odoo pain points: if that person is away or slow, the record sits silently until someone complains. Odoo core has no auto-escalation and no named fallback. This engine watches any model with a state and an owner field, then escalates step by step, a reminder first, then the approver's manager, then a named recipient. Every step lands in email, chatter, and an audit log.
Approval Escalation Engine
Escalate pending approvals, POs, expenses, and leaves up the management chain when approvers sit on them too long.
What it does
Pending records getting stuck on an approver's desk is one of the most common Odoo pain points. If the approver is on leave, sick, or just slow, the record waits silently and nobody notices until somebody complains.
Odoo core has no auto-escalation on purchase orders, expense reports, leaves, or approval requests. Chatter activities can remind the approver, but there is no built-in way to reassign to a manager or a named fallback after N hours.
What this module adds:
- Rule engine per model: pick the target model, state, and owner field.
- After N hours without action, send a reminder activity or email to the approver.
- After another N hours, reassign to the approver's manager.
- After another N hours, escalate to a named recipient (e.g. CFO).
- Out-of-the-box rules for purchase orders, expense reports, time off / leave requests, and approval requests.
- Custom rules can target any model with a state and an owner field.
- Full audit log of every escalation, who was reassigned, when, and why.
Who benefits
Approvers, controllers, finance managers, and operations leads at mid-market and enterprise companies where approval SLAs matter.
How it works
Cron-driven rule evaluation, no core-model inheritance. Every escalation writes to the audit log and posts to chatter. TransactionCase tested on Odoo 17, 18, and 19. Safe to install, safe to uninstall.
What the module looks like
Real screenshots from a live Odoo 19 install. Every view is standard Odoo chrome, no bespoke widgets to learn.
Common questions
Does it inherit or patch core Odoo models?
_register_hook to wrap the target method at registry load, and the wrapper unwinds cleanly at uninstall. No schema changes to core tables, no monkey-patches, no Studio surgery.Does it work on Odoo Community, or only Enterprise?
Can I uninstall it cleanly if it does not fit?
What support do I get after buying?
Can Cube Master customise it for my company?
Beyond this module, Cube Master also builds:
We are a full technology house. The Odoo utility you are reading about is one part of what we ship. If your back office, website, or app team needs more, we have the team for it.
More from the Cube Master catalogue
We ship 33 single-feature utilities at the same price point. If this one solved a pain for you, the others probably will too.
About Cube Master
We blend mastery with creativity - نمزج الإتقان بالإبداع
Cube Master is a Saudi technology house based in Al-Mubarraz. We design, build, and run business systems for customers across the Gulf and beyond: end-to-end Odoo ERP rollouts, custom AI workflows, corporate websites, and mobile apps. Strategic technology partners with Microsoft, AWS, Odoo, and Umbraco.
The Odoo utility you are reading about is one small piece of what we ship. If you need any of the above for your company, talk to us.
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