# Approvals All in One with a Purchase Gate

> The Purchase's own button waits for the approval rule that names it - installed by itself alongside Approval Workflow and Purchase.

- **What it is:** The Purchase's own button waits for the approval rule that names it - installed by itself alongside Approval Workflow and Purchase.
- **For:** Human Resources/Approvals
- **Odoo versions:** 16.0, 17.0, 18.0, 19.0, 20.0 - Community and Enterprise
- **Runs on:** Odoo.sh or Odoo you host yourself - not Odoo Online, which accepts no third-party apps
- **Price:** 138 EUR, one-time, on the Odoo Apps Store
- **Technical name:** bambooforge_approvals_purchase
- **Not for:** Hold anything without a rule. The rule says which purchase orders wait, with a condition written like a filter, and which ladder they climb.; Add a screen. It changes what the button does.
- **Manual:** https://docs.bambooforge.dev/bambooforge_approvals_purchase/
- **Live demo:** https://demo20.bambooforge.dev/odoo/action-bambooforge_approvals.action_bf_approval_rule
- **Store page:** https://apps.odoo.com/apps/modules/20.0/bambooforge_approvals_purchase
- **Manual last updated:** 2026-11-11

---
# Approvals All in One with a Purchase Gate

With Approval Workflow and Purchase installed on Odoo 20, the purchase order's own **Confirm Order**
button waits for the approval an approval rule asks for: the first press raises the request, the
button refuses while it waits, and goes through once it is approved. This small module installs by
itself when both apps are there.

This page is the complete manual of that gate.

## Overview

**For whom.** A company that runs Approval Workflow and Purchase on Odoo 20 and wants some purchase
orders to wait for an approval before **Confirm Order** goes through: an order above 10,000, an
order from a supplier you have not used before. Approval Workflow holds the ladder of people who
approve; this module puts the check in front of the button.

### What it does

- **Stands in front of Confirm Order.** An approval rule on *Purchase Order* whose *Blocks* is
  `button_confirm` stops the button for the purchase orders its condition matches. The first press
  raises the request, on the rule's approval type, with the purchase order's amount and contact, and
  stops with its name and the step it went to.
- **Refuses while it waits, passes once approved.** Pressed again while the request waits, the
  button stops and names the step. Once the request is approved, it goes through.
- **Names an earlier refusal.** After a refusal, the next press raises a new request and says the
  earlier one was refused.
- **Keeps the request.** It is written in a transaction of its own before the button stops, so the
  stop does not roll it back.
- **Works with Odoo's own approval.** With *Purchase > Settings > Order Approval* on, an order that
  passes the gate goes to *To Approve* as Odoo decides, and **Approve Order** goes through.
- **The rules of the purchase order's company.** With several companies ticked, a purchase order
  meets the rules of its own company.
- **An approval covers its amount.** A purchase order that grew past the amount it was approved for
  raises a new request.
- **Installs by itself** when Approval Workflow and Purchase are both installed.

### What it does not do

- **Hold anything without a rule.** The rule says which purchase orders wait, with a condition
  written like a filter, and which ladder they climb.
- **Add a screen.** It changes what the button does.

### What it needs

- **Approval Workflow** (`bambooforge_approvals`) and Odoo's **Purchase** (`purchase`) on Odoo
  20, Community or Enterprise.
- An approval rule on *Purchase Order* with *Blocks* set to `button_confirm`.

## Concepts

**Approval rule.** On Approval Workflow: which purchase orders wait, on which ladder, and which button they
stand in front of (*Blocks*).

**Gate.** The check in front of **Confirm Order**: raise the request, refuse while it waits, pass once
approved.

**Request.** One approval of one purchase order, raised by the gate, decided by the ladder.

## Install and first run

1. Install Approval Workflow and Purchase: this module installs by itself.
   
   Expected: nothing new on the screens.
2. Open *Approvals > Configuration > Approval Rules* and press **New**. Applies To: *Purchase
   Order*; a Condition, such as Total is above 10,000; an Approval Type; Amount Field: Total;
   Blocks: `button_confirm`.
   
   Expected: the rule is saved, and the purchase orders' Action menu offers **Request approval**.
3. Press **Confirm Order** on a purchase order the condition matches.
   
   Expected: the message "... needs approval first: sent as ... to '...'", and the purchase order
   stays as it was.

### Uninstalling

Uninstalling gives **Confirm Order** back to Odoo. The requests raised so far stay in Approval
Workflow, with their trail.

## Flows

What the person at the button sees.

### What the person at the button sees

1. Press **Confirm Order** on a purchase order the rule matches: the request is raised and the
   button stops, naming the request and its step.
2. The approvers find it under *Approvals > Waiting on Me*, and by mail when the type says so.
3. Press **Confirm Order** again while it waits: the message names the step it waits on.
4. Once it is approved, **Confirm Order** goes through.

## How it works

### When the gate stands

Each press of **Confirm Order** (`button_confirm`) asks Approval Workflow, for each purchase
order:

- the active rules on *Purchase Order* whose *Blocks* is `button_confirm`, of no company or of the
  company of the purchase order;
- for each rule whose condition matches the purchase order: an approved request for at least its
  amount now lets it through; a waiting one stops it; none raises one and stops it.

Odoo's **Approve Order** passes the same check: called on a draft through the programming interface
it raises the request instead of confirming.

The demo data's seed runner is the only code that passes the gate without a request: it carries an
object no request can produce. No context key opens it.

### Who reads and writes what

- The request is raised in the name of whoever pressed **%(button)s**. The ladder is built without
  them, so they never approve it themselves.
- Who may see and decide on the request is Approval Workflow's.

### How we make sure it works

Before every release, **1 automated checks** run against this app on Odoo 16, 17, 18, 19 and 20.
Among them:

The complete list is in the source you receive.

## For managers

This gate has no analysis of its own: its requests show under *Approvals > Reporting*, by type and
outcome, with the days each approver takes.

## Reference

The complete reference of this app is generated from the code on every release and published with
this manual at https://docs.bambooforge.dev/bambooforge_approvals_purchase/ under *Reference*.

## Troubleshooting and FAQ

****"<purchase order> needs approval first: sent as <request> to '<step>'."****

The first press on a purchase order the rule matches. The request waits on that step.

****"<purchase order> is waiting for approval: <request> is at '<step>'."****

Pressed again while it waits. Ask the people on that step, or open the request.

****"... (an earlier request was refused: <request>)"****

A new request was raised after a refusal. Read the refusal's reason on the earlier request.

****The request is not raised and the message is about access.****

The person who pressed Confirm Order may not create a request: give them Approvals' *User* right
(every internal user has it).

### Questions people ask

****Do I have to install it?****

It installs by itself when Approval Workflow and Purchase are both there.

****Does it stop every purchase order?****

Only those an active rule with *Blocks* `button_confirm` matches.

****What about Odoo's own Order Approval setting?****

It still applies after the gate: an order the gate let through can go to *To Approve*. It is off
in a new database (*Confirm purchase orders in one step*).

****Can somebody skip it?****

No context key opens the gate.

### Support

Write to [support@bambooforge.dev](mailto:support@bambooforge.dev) with your Odoo series, the rule and what the screen said.

## Changelog

### 20.0.1.0.2

- This manual.


## Reference

Generated from the module's own code (version 20.0.1.0.2, series 20.0) on 2026-11-12; every menu, field, setting, scheduled action, group, rule, report and endpoint below is read from the files, not written by hand.

### Models

#### purchase.order (extends Odoo's purchase.order)

Adds no fields.
