Odoo replenishment: reduce shortages without inflating stock

A confirmed customer order, a missing component and an urgent purchase: the problem often starts long before the warehouse. For an SME using Odoo in Belgium or France, reliable replenishment means connecting stock forecasts to purchasing decisions. This guide proposes a preparation method for an Odoo Enterprise project, based on the mechanisms documented in Odoo 19.

Understand what a rule triggers

A reordering rule compares forecast stock with a minimum and targets a maximum. The Buy route generates a request for quotation; the Manufacture route generates a manufacturing order. With a manual trigger, the requirement appears on the replenishment dashboard for a user to process. Order multiples can cause the maximum to be exceeded. These behaviours are described in the official reordering rules documentation.

Creating a document does not replace your purchasing approval policy. Before automating, decide who checks quantities, prices and commitments to the supplier.

Choose a strategy for each product family

Odoo documentation distinguishes reordering rules, replenishment on order and the master production schedule. The choice depends on the business process, as explained in its overview of replenishment strategies.

Our recommendation is to separate regular consumables, critical parts, seasonal products and items sold only occasionally. Applying one policy to every product can hide trade-offs between availability, storage costs and cash flow. Have purchasing and operational managers agree on these families before entering thresholds.

Avoid combining the master production schedule and reordering rules for the same products: Odoo documentation advises against this combination because it can duplicate replenishment needs. Validate the selected strategy in your version and configuration before rollout.

Prepare the data before setting thresholds

Start with a limited selection of products. Check purchase and stock units, selected suppliers, locations, outstanding orders and observed lead times. A receipt recorded late can distort the interpretation of demand as much as an incorrect threshold.

• Assign an owner for product records and supplier data.
• Compare quoted lead times with recent receipts.
• Identify old orders that will no longer be delivered.
• Check inter-warehouse movements before placing another purchase.

For a business operating in Belgium and France, prepare separate scenarios for each site: a shared supplier does not mean an identical lead time. Document delivery routes and receiving practices explicitly.

Test with a numerical example

Illustrative example: your team plans a minimum of 20 units and a target of 60. If forecast stock is 15 units, the gap to the target is 45. Use this calculation as a checkpoint in a test database, then add real constraints: packaging, incoming orders and scheduling. The aim is to understand each proposal before letting it drive the buyers’ daily work.

Also test a customer cancellation, a partial receipt and a supplier delay. For each case, record the expected document, expected quantity and person responsible for intervening. This checklist becomes your reference when configuration changes.

Underside analysis: manage exceptions and measure results

We recommend starting with a daily human review of the pilot scope. Record corrected proposals and their reasons: incorrect data, an exceptional sales event or an unsuitable threshold. Move towards more automation only once corrections are understood and controlled.

Track shortages among pilot products, stock value and the share of urgent purchases. Compare periods with similar demand; fewer shortages achieved through a large increase in stock deserve analysis before being treated as a success.

Prepare your Odoo Enterprise project

This work complements the organisation of purchasing in Odoo and reliable inventory and logistics. An Odoo audit in Belgium or France can help select the pilot scope and identify data gaps.