Approval Exposure
See what your purchase orders actually had to clear before being confirmed
The video below shows Approval Exposure running on a real Odoo 19 database. Want it driven against your own data, or a question answered first? Ask and we will set up a session.
Odoo Community has exactly one purchase approval control: a single amount threshold, above which anyone in the Purchase Manager group can confirm. There is no second tier, and no record of who approved what beyond generic chatter. Most organisations assume tighter control than that.
This report says what the control actually is, and what has passed through it.
Five orders worth $103,100 cleared a single check - and four people could approve any of them.
What it does
Careful when the check is off entirely
When a second approval is switched off, every order cleared a single check regardless of value. Reporting "0 orders above the threshold" there would be true and completely misleading - so the report says what actually happened instead.
Reports, never approves
This app adds no tier, blocks no confirmation and writes no audit record. It does not extend purchase.order at all - a test asserts the module contains no approval-behaviour path.
And then what
If the picture this gives you is thinner than expected, adding real tiers is a change to how the system behaves and belongs with the app that also has to enforce it.
What it does not do
Stated up front so nothing about the scope is a surprise after you install it.
Screenshots
Requirements
- Odoo 19.0, Community or Enterprise.
- Odoo.sh or On-Premise only. Third-party apps cannot be installed on Odoo Online (SaaS) databases — check your hosting before buying.
- Module
mh_purchase_approval_exposure, version 19.0.1.0.10, licensed OPL-1.