ApproveFlow — Purchase
by Zerixo Technologies Ltd. https://zerixo.xyz/products/approveflow/purchase$ 159.46
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Purchase (purchase)
• Discuss (mail) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4700 |
| Technical Name |
approveflow_purchase |
| License | OPL-1 |
| Website | https://zerixo.xyz/products/approveflow/purchase |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Purchase (purchase)
• Discuss (mail) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4700 |
| Technical Name |
approveflow_purchase |
| License | OPL-1 |
| Website | https://zerixo.xyz/products/approveflow/purchase |
Purchase Control Pack — ApproveFlow for Odoo 19
Multi-Level Purchase Order Approvals, Tiered by Spend
Stop uncontrolled purchasing. Enforce tiered approval authority before any purchase order is confirmed — automatically, inside Odoo.
Pricing
Simple one-time pricing
Add just the Purchase Control Pack for €59 — no bundle required.
How It Works
The full approval lifecycle on a purchase order
No developer needed. Every step happens inside Odoo — from submission to confirmation.
PO meets spend threshold — Request Approval button appears
When a PO exceeds the configured spend threshold, the Request Approval button appears in the header. PO confirmation is blocked immediately until the workflow completes.
PO enters Waiting for Approval
The PO shows a yellow banner with the current approver's name. Approve, Reject, Cancel Approval, Force Approve, and Force Reject buttons are visible. The chatter logs every state change.
Approver receives notification & reviews the request
An automatic email is sent the moment an approver's turn arrives. The Approval Request shows which rule triggered it, total PO amount, and Approval History per level.
PO approved — confirmation unlocked
Once all approval levels pass, the PO shows a green Approved banner. The Confirm Order button is now active. Full audit trail recorded in the chatter permanently.
Or rejected — with reason and resubmit path
Rejection reason stored on the request and the PO. A rejection email is sent automatically. The Request Approval button reappears — the agent can revise and resubmit without admin intervention.
Approval Request
Approvers act with full context — no email chains
Every approval request opens as a structured form with the rule, total PO amount, SLA status, and multi-level history — so approvers decide immediately.
- ✅One-click approvalApprove or reject directly from the request form
- ⚠️Force Approve / Force RejectAdmins can override any level — reason mandatory and logged permanently
- 📜Approval History tableEvery level's status, approver, and timestamp in one place
- 📧Auto email with review linkApprover notified the moment their turn arrives
Configuration
Set up spend-tier rules in minutes — no code required
Configure which POs trigger approval, the spend thresholds, and who approves at each level — all through a standard Odoo form.
- 📊Spend-tier routingDifferent approval chains trigger automatically at configurable spend amounts
- 🔀Sequential & Parallel modesAll must approve, any one can approve, or minimum threshold
- ⏱️Per-level SLA hoursSet different deadlines for each approval level independently
- 🔍Approval status filtersFilter POs by Pending / Approved / Rejected workflow state in the list
Key Capabilities
What Purchase Control adds to ApproveFlow
- 🚫PO confirmation gatePurchase orders cannot be confirmed until all required approvers sign off
- 📊Spend-tier routingDifferent approval chains trigger automatically at configurable spend thresholds
- 🔄Re-approval on changesSignificant order line edits while pending automatically restart the workflow
- 📧Automatic notificationsApprovers receive instant emails with approve/reject links
- 🛡️Audit-ready activity historyEvery approval decision logged with user, timestamp, and reason
- 🔍Approval status filtersFilter POs by Pending / Approved / Rejected workflow state instantly
Operational Impact
What changes after deployment
Procurement teams maintain spend discipline without adding friction — approvals happen automatically in Odoo, not over email.
- ✓Eliminate unbudgeted purchases — every PO above threshold requires sign-off before confirmation
- ✓Enforce spend authority — different approval chains based on order value and supplier
- ✓Reduce procurement cycle friction — automatic routing replaces manual chasing
⚙️ Requires ApproveFlow Platform Engine
This control pack runs on the ApproveFlow Core Engine — the approval rule engine, SLA system, inbox management, and audit trail. Install the Core Engine first, then install this extension. The Core Engine is available from €79 launch price on the Odoo App Store.
Compatibility
Installation
Fast to install, nothing to build
Install ApproveFlow Core Engine
Go to Apps → search ApproveFlow → install ApproveFlow — Core.
Install this Purchase Control Pack
Search ApproveFlow Purchase in Apps → install ApproveFlow — Purchase.
Create an Approval Rule for Purchase Orders
Go to Approvals → Configuration → Approval Rules → New. Set document type to Purchase Order, add spend thresholds and approvers per level.
Done — POs are now gated
Qualifying purchase orders will show the Request Approval button. Confirmation is blocked until the workflow completes.
Frequently Asked Questions
Common questions
Can I set different approval chains for different spend amounts?
Yes. Configure multiple spend tiers — for example, ≥€1,000 requires Manager approval, ≥€10,000 requires Director, ≥€50,000 requires CFO.
Does it block PO confirmation completely?
Yes. The Confirm Order button is disabled and the PO is locked at 'Waiting Approval' until the workflow completes.
Can I route specific suppliers through dedicated approvers?
Yes. Rules can target specific vendor categories or individual vendors, regardless of order amount.
What happens if an approver is on leave?
The SLA timer triggers automatic escalation after the configured deadline. Users can also pre-configure delegation periods via the Delegations menu.
Also Available
Extend approval control across your business
| Module | What It Controls | Launch Price |
|---|---|---|
| ApproveFlow Core Engine | Approval framework — required for all control packs | €79 |
| Accounting Control Pack | Vendor Bill posting gate — block until finance approves | €69 |
| HR Control Pack | Expense claims and Leave Request approval workflows | €49 |
Enforce Procurement Control in Odoo Today
Stop unbudgeted purchases before they happen — automatically.
Get Purchase Control Contact Support✓ 24h support response · ✓ Free updates · ✓ OPL-1 License
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