| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Purchase (purchase) • Invoicing (account) |
| Lines of code | 74 |
| Technical Name |
amadio_purchase_approval_matrix |
| License | OPL-1 |
| Website | https://amadio.io |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Purchase (purchase) • Invoicing (account) |
| Lines of code | 74 |
| Technical Name |
amadio_purchase_approval_matrix |
| License | OPL-1 |
| Website | https://amadio.io |
Purchase Approval Matrix
Configure multi-level PO approval tiers based on order value — route every purchase order to the right approver automatically, with a full audit log.
The Challenge
Why organizations need Purchase Approval Matrix
Without structured approval routing, purchase orders above any threshold can be confirmed by anyone with access — bypassing financial controls entirely.
Operations teams email purchase orders to managers for approval outside of Odoo. There's no audit trail, no tracking, and approvals get lost in inboxes.
Some organizations need VP approval for orders over $50,000 but department manager approval is sufficient for routine purchases. Standard Odoo has no tier structure.
What Purchase Approval Matrix Does
Six capabilities built specifically for this problem
Amount-Based Approval Tiers
Define tiers with minimum and optional maximum amounts. Orders in each range route to the designated approver group automatically.
Multi-Approver Configuration
Each tier supports multiple approvers. Configure require-all (all must approve) or any-one mode depending on your governance requirements.
Full Audit Log
Every approval action — approve, reject, or reset — is logged with the approver's name, timestamp, and optional note. The log is permanent and accessible on the PO.
Confirmation Override
The standard Confirm button is overridden to check the approval tier. POs cannot bypass the approval matrix — the system enforces compliance at the ORM level.
One-Click Approve/Reject
Approvers see a clear action panel on the PO form. They approve or reject with an optional note — no email required, no external system.
Admin-Managed Tiers
The approval matrix is configured in Purchase → Configuration → Approval Tiers. Changes take effect immediately for new POs without code changes.
How It Works
Operational in minutes — not weeks
Configure Your Tiers
Go to Purchase → Configuration → Approval Tiers. Define tiers with amount ranges and assign approver users to each tier.
Submit a Purchase Order
When a buyer confirms a PO, the system evaluates the total amount, identifies the applicable tier, and moves the PO to Pending Approval.
Approvers Act
Designated approvers see pending POs in their queue. They review, approve or reject with a note, and the PO moves to Approved or back to Draft accordingly.
Perfect For
Industries and organizations that rely on Purchase Approval Matrix
Mid-Market Businesses
Organizations with $500K+ annual purchase spend need structured controls. A 3-tier matrix (manager / director / CFO) eliminates unauthorized purchasing.
Healthcare & Public Sector
Procurement compliance in regulated industries requires documented approval at defined thresholds — with an audit trail available for internal and external review.
Multi-Entity Operations
Groups with multiple legal entities can configure separate approval matrices per company — each with its own thresholds and approver hierarchies.
Technical Specifications
Compatibility and deployment details
| Odoo Version | 18.0 |
|---|---|
| Platform | Odoo.sh & On-Premise |
| License | OPL-1 |
| Author | AMADIO |
| Support | info@amadio.io |
| Website | amadio.io |
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