# Approvals All in One with an Inventory Gate

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

- **What it is:** The Inventory's own button waits for the approval rule that names it - installed by itself alongside Approval Workflow and Inventory.
- **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_stock
- **Not for:** Hold anything without a rule. The rule says which transfers wait, with a condition written like a filter, and which ladder they climb.; Hold what the Point of Sale delivers. A sale at the till makes its transfer done by itself.; Add a screen. It changes what the button does.
- **Manual:** https://docs.bambooforge.dev/bambooforge_approvals_stock/
- **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_stock
- **Manual last updated:** 2026-11-11

---
# Approvals All in One with an Inventory Gate

With Approval Workflow and Inventory installed on Odoo 20, the transfer's own **Validate** 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 Inventory on Odoo 20 and wants some
transfers to wait for an approval before **Validate** goes through: a return to a supplier, a
transfer to a third-party warehouse. 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 Validate.** An approval rule on *Transfer* whose *Blocks* is
  `button_validate` stops the button for the transfers its condition matches. The first press
  raises the request, on the rule's approval type, with the transfer'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.
- **Backorders and returns are transfers of their own.** Odoo's backorder and immediate transfer
  dialogs press Validate again and meet the gate; a backorder or a return the rule matches waits for
  its own approval.
- **The rules of the transfer's company.** With several companies ticked, a transfer meets the rules
  of its own company.
- **An approval covers its amount.** A transfer that grew past the amount it was approved for raises
  a new request.
- **Installs by itself** when Approval Workflow and Inventory are both installed.

### What it does not do

- **Hold anything without a rule.** The rule says which transfers wait, with a condition written
  like a filter, and which ladder they climb.
- **Hold what the Point of Sale delivers.** A sale at the till makes its transfer done by itself.
- **Add a screen.** It changes what the button does.

### What it needs

- **Approval Workflow** (`bambooforge_approvals`) and Odoo's **Inventory** (`stock`) on Odoo 20,
  Community or Enterprise.
- An approval rule on *Transfer* with *Blocks* set to `button_validate`.

## Concepts

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

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

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

## Install and first run

1. Install Approval Workflow and Inventory: this module installs by itself.
   
   Expected: nothing new on the screens.
2. Open *Approvals > Configuration > Approval Rules* and press **New**. Applies To: *Transfer*; a
   Condition, such as Type of Operation is Delivery and the destination is a vendor location; an
   Approval Type; Amount Field: none (a transfer has no amount; leave it empty); Blocks:
   `button_validate`.
   
   Expected: the rule is saved, and the transfers' Action menu offers **Request approval**.
3. Press **Validate** on a transfer the condition matches.
   
   Expected: the message "... needs approval first: sent as ... to '...'", and the transfer stays as
   it was.

### Uninstalling

Uninstalling gives **Validate** 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 **Validate** on a transfer 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 **Validate** again while it waits: the message names the step it waits on.
4. Once it is approved, **Validate** goes through.

## How it works

### When the gate stands

Each press of **Validate** (`button_validate`) asks Approval Workflow, for each transfer:

- the active rules on *Transfer* whose *Blocks* is `button_validate`, of no company or of the
  company of the transfer;
- for each rule whose condition matches the transfer: 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 backorder and immediate transfer dialogs press Validate again; the Point of Sale makes its
transfers done by itself, past the gate.

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

This gate has no automated check of its own yet. The gate it calls is checked by Approval
Workflow's own: the request raised on the first press, the button refused while it waits and
passed once approved, an earlier refusal named, and no context key that opens it.

## 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_stock/ under *Reference*.

## Troubleshooting and FAQ

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

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

****"<transfer> 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 Validate 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 Inventory are both there.

****Does it stop every transfer?****

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

****Does a backorder need approving again?****

Yes, when the rule matches it: it is a new transfer.

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

No context key opens the gate. Odoo's dialogs press Validate again and meet it; only the Point
of Sale's own transfers pass by.

### 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

#### stock.picking (extends Odoo's stock.picking)

Adds no fields.
