Reordering Rules: Decide When Software Suggests a Purchase and When It May Act

A low-stock warning and an authorised purchase are different outcomes. Before adding automatic replenishment to a stock tool, decide which outcome you want, which forecast it uses and who may commit the business to an order. Begin with reviewable suggestions unless you have clear rules for unattended purchasing.

This is a planning recommendation, not a claim that automation is unsuitable for small businesses. The important question is what the software is allowed to do when stock is expected to run short.

Specify the forecast, not just a shelf quantity

An item can still be on the shelf while already promised to customers. Conversely, an incoming order may cover an expected shortage, provided it arrives in time. Ask the developer to show the quantities and dates behind each suggested purchase, including how overdue incoming deliveries are treated.

The official Odoo reordering-rule guide describes product and location rules with minimum and maximum quantities, using forecast stock to trigger replenishment. That is a particular product's approach. Your brief must still define the forecast horizon, included demand and acceptable incoming supply.

Avoid a rule that adds every draft supplier quotation to available supply. Agree which purchasing state counts, and what happens when the expected arrival changes. A forecast should not hide a late supply problem by including goods without their timing.

Minimum, target and buying increment do different jobs

The minimum is a trigger, while the target describes the level to restore. A purchasing increment determines the quantities the supplier will accept. They are not three names for the same setting.

Odoo documents a Multiple field that rounds a replenishment quantity upwards to a suitable multiple. It notes that this can exceed the maximum. Therefore, if your business treats a maximum as a hard storage or spending limit, say so explicitly. Require either a review exception or a different permitted quantity when pack sizes conflict with that limit. Do not call a target a hard cap while allowing silent overshoot.

Also state the unit for each value. A stock threshold in individual items and a supplier order in cases need an agreed conversion; this article concerns the decision to replenish, not the underlying unit-conversion design.

Choose the point of human commitment

Odoo distinguishes automatic triggers from a manual replenishment dashboard where users review needs before clicking Order. Its Buy-route description identifies a generated request for quotation. A request for quotation must not be described as proof that a supplier accepted an order or promised delivery.

For a commissioned tool, specify each allowed step: propose quantity, prepare supplier request, approve purchase, transmit it and record supplier acknowledgement. Some steps may be automated while others remain manual. Identify what happens if no supplier is configured, a price is missing or approval is unavailable.

Require one durable link between the shortage being addressed and its resulting procurement operation. Repeated scheduler runs or uncertain transmission responses should not unknowingly buy the same requirement twice. Preserve unresolved attempts and reconcile the external outcome rather than blindly sending another order. These are proposed reliability controls, not claims about the documented product's implementation.

Demonstrate a changing shortage

Use fictional stock and suppliers for the acceptance exercise:

• Expected demand changes while a suggestion awaits review.
• An incoming delivery is delayed beyond the required date.
• A supplier pack would exceed the agreed limit.
• Two runs encounter the same shortage.
• A purchase transmission has an unknown outcome.
• The supplier or price is missing.
• A user can trace a suggestion to the forecast and procurement state that explain it.

Discuss the smallest useful automation boundary when planning a stock and purchasing application. A trustworthy recommendation with a clear next action can be more useful than a purchase button operating on unexplained numbers.

Source scope

The Odoo 19 guide supports forecast-based minimum/maximum rules, purchasing multiples and manual versus automatic triggering. Forecast policy, hard-cap exceptions, approval design and uncertain-operation reconciliation here are requirements to define, not vendor guarantees or promises that stockouts will disappear.