Blog
Custom Approval Workflows in Odoo: Purchases, Expenses, Discounts
How to set up approvals in Odoo for purchases, expenses and discounts: what works out of the box, what Studio adds, and when custom code is the right call.
- bottom
- odoo
Most growing companies hit the same wall. Someone buys something they should not have, an expense report sails through without a second look, or a salesperson gives a 30% discount nobody signed off on. The fix is an approval workflow, and Odoo can do this in several different ways.
The short answer: use the built-in settings first (they cover simple purchase and expense approvals), add Odoo Studio approval rules for amount-based or multi-step routing, and write custom code only when the rule depends on data or logic that Studio conditions cannot express. Discount approval is the area where you are most likely to need Studio or custom work.
Start with what Odoo already does
Before building anything, check the native options. They are cheaper to run and survive upgrades with no effort.
Purchase orders
Odoo’s Purchase app has an order approval setting. In the Odoo 13.0 documentation, you enable Order Approval in Purchase settings and set a minimum amount. Above that amount, an order confirmed by a regular user moves to a “To Approve” status until a purchase manager approves it. The page is old, so confirm the exact labels in your own version. The behavior has stayed broadly the same in later releases.
Two practical notes:
- It is a single threshold and a single approver tier. There is no “under $5K goes to the team lead, over $5K goes to finance” in this setting.
- The approval status applies to orders made by non-manager users, so test with a regular purchase user, not your admin account.
Expense reports
In the Odoo 18 Expenses app, approval is part of the standard flow. Only users with at least Team Approver rights for the Expenses app can approve a report, and only reports in Submitted status can be approved. For many small teams, this is enough.
What it does not give you out of the box is amount-based escalation. A $40 taxi and a $9,000 conference trip go through the same single approval step.
The Approvals app
Odoo also has a dedicated Approvals app. Its approval types let you list approvers, mark some as required, and send requests to the right people. Odoo’s own Approvals basics training touches on adding approvers and requiring the employee’s manager as an approver. It suits general requests (a laptop, a trip, a contract sign-off). It is not wired into every transaction, so a purchase order does not automatically wait on it unless you build that link.
Level two: Studio approval rules
When the native option is too blunt, the next step is Odoo Studio approval rules. The idea is simple: you attach an approval step to a button, such as Confirm on a purchase order or Submit on an expense report.
According to the Odoo 19 documentation, you can:
- Name specific approvers, an approver group, or both.
- Add conditions that decide when a step applies, using the filter next to the Approvers field.
- Chain several steps in order.
- Mark a step as exclusive, so the same person cannot approve more than one step on a record.
A user who is not authorized and clicks the button gets an error, and an activity is created for the approvers. Decisions are logged in the chatter, which helps with audits.
A common pattern, described in an Odoo community thread on multi-level purchase approvals, is to put rules on the Confirm Order button with conditions on the order total and a different approver group for each band. That is a reasonable model for many companies.
Things to know before you commit:
- Studio is an Enterprise-side tool, so it affects licensing. Check current pricing on Odoo’s pricing page rather than assuming.
- Approval features and field names can differ between versions. If you upgrade, retest every rule.
- Rules live in your database as customizations. Document them, or the next admin will not know why a button refuses to work.
Discounts: the tricky one
Purchases and expenses have a natural native home. Discount approval does not, at least not in a way we could verify in Odoo’s official documentation. Searching the documentation turned up no built-in discount threshold approval in Sales, only quotation-level confirmation options.
You have three realistic routes:
- Studio rule on the Confirm button of the sales order. Add a condition for the order total or margin. This works if your rule is about the order as a whole.
- Studio rule with a discount condition. If your condition can be expressed as a filter on the record, for example “any line has a discount above 15%”, Studio can cover it. Test carefully, because line-level conditions are where filters get awkward.
- A custom module. A small module can compute the maximum discount per order, compare it with a rule table (by salesperson role, customer tier or product category), and block confirmation or send it to a manager.
Third-party apps exist as well, such as sales order approval modules on the Odoo Apps store. They are typically built around an order-amount threshold and a “To Approve” state. Check that the module covers discounts, not just totals, and that it is maintained for your version.
When to go custom
Studio handles a lot, but custom code earns its place when:
- Approvers depend on data outside the record, such as a budget remaining in another model, a customer credit limit, or cost-center ownership.
- You need approval limits per person (approver A up to $10K, approver B up to $50K) that are stored in a table users can maintain.
- You need delegation, out-of-office handling or automatic escalation after a number of days.
- You must integrate with an external system, for example a spend-management tool or an e-signature service.
- You have dozens of rules and the Studio interface has become difficult to review.
Custom does not have to mean heavy. A well-scoped approval module is often a few models, a couple of views and some access rules. The cost is in maintenance: every Odoo upgrade needs a test pass.
Another option is a community or paid add-on, like the expense approval route app listed for Odoo 18 with multi-stage approvals based on criteria like amount. Treat any add-on like any third-party code. Read what it changes, check the maintenance record and test it in a copy of your database first.
A comparison
| Need | Native | Studio rules | Custom code |
|---|---|---|---|
| Single PO threshold, one approver | Yes | Yes | Overkill |
| Expense manager sign-off | Yes | Yes | Overkill |
| Amount bands, different approvers | No | Yes | Yes |
| Discount limits by role or customer tier | No | Partly | Yes |
| Per-person limits kept in a table | No | No | Yes |
| Escalation and delegation rules | Limited | Limited | Yes |
| Upgrade effort | Lowest | Low to medium | Medium to high |
Design the policy first
Most approval projects stall because nobody wrote down the policy. Before touching Odoo, answer these:
- What triggers approval: amount, category, supplier, margin, discount?
- Who approves each level, and who covers when they are away?
- What should happen on rejection: back to draft, or a comment and resubmit?
- What must be logged for your auditors?
- Which users must not approve their own requests?
Keep it short. Two or three levels cover most small and mid-size businesses. Every extra level adds waiting time, and people will start working around the process.
Rolling it out
- Turn on the native settings and run them for a week or two.
- Add Studio rules only where the native option leaves a real gap.
- Test in a copy of your database, with a regular user and each approver role.
- Train approvers on where their approvals show up (activities and the chatter).
- Review after a month. If approvals take too long, relax the thresholds rather than adding exceptions.
Sources: Odoo 13.0 purchase order approval docs; Odoo 18.0 approve expenses docs; Odoo 19.0 Studio approval rules docs; Odoo Approvals Basics; Odoo community thread on multi-level purchase approvals; Odoo Apps: sale_order_approval; Odoo Apps: expense approval route; Odoo pricing. Odoo menus, labels and licensing change between versions and editions, so verify details against the official documentation for your version before you build.
If you are weighing native settings, Studio or a custom module for your approval rules, we are happy to talk it through. Teknologia Solutions offers a no-charge conversation, with no obligation, to look at your process and tell you honestly which route fits.