A negotiated price loses its value when each buyer retypes it or places orders against an outdated agreement. For teams deploying Odoo in Belgium and France, blanket orders provide a starting point for organising recurring purchases. This Odoo Enterprise guide explains their role, then sets out Underside’s approach to acceptance testing, purchase commitments and migration.
What a blanket order covers
In Odoo 19, a blanket order connects recurring purchases with a supplier and agreed prices. Enable the feature through the purchase agreement settings. Line prices need to be entered; existing product prices are not filled in automatically. Requests for quotation created from the agreement remain linked to it, and the Ordered field tracks ordered quantities. The documentation also describes the connection with supplier data used for replenishment.
Agree what quantities mean before configuring the system
We recommend bringing purchasing, logistics and finance together around a real agreement. An annual quantity might represent a forecast, a negotiation target or a firm commitment. The team needs to specify that meaning in its procedure and contractual documents. Do not assume an entered quantity acts as a hard purchasing limit: test the behaviour of your version and installed modules.
Assign an owner to each agreement. That person should be able to explain its period of use, product scope, units, delivery terms and renewal process. Keep an explicit reference to the approved commercial agreement so two buyers do not work from different conditions.
An acceptance scenario with expected outcomes
Fictional Underside example: a supplier offers 1,000 units at €4.80 each for a quarter. The team prepares successive orders for 200 and 150 units. Its checks should distinguish the 350 units ordered from quantities actually received and invoiced. A remaining balance of 650 units is meaningful only if the original 1,000 units are the agreed baseline for that calculation.
- Compare each order’s price and unit with the approved agreement.
- Test a partial delivery, a cancellation and a quantity change.
- Try an order above the planned volume and document who must decide.
- Try an order after the agreed period and check the expected handling.
- Check that a price change does not silently alter previously approved commitments.
These are acceptance requirements to adapt to your process, rather than automatic restrictions guaranteed by Odoo. If a control is missing, start with an explicit procedure before deciding on an extension.
Connect agreements with replenishment without duplicate orders
We recommend testing one product purchased both manually and automatically during the pilot. Define who handles demand when a buyer has already prepared an order. Compare proposed documents before confirmation and examine competing or outdated supplier prices. Use our Odoo replenishment guide to prepare these tests.
If a supplier portal or another system sends orders, define a unique reference for each request and a recovery rule for interrupted processing. Resending a request must not create a second commitment. This is an integration design requirement to test with the technical owner.
Prepare for migration in Belgium or France
For an Odoo project in Belgium or France, list active agreements, amendments and outstanding purchase orders. We recommend reconciling volumes already used with the purchasing team before deciding what to migrate. Importing the initial quantity without its history can give a misleading view of the remaining balance.
Within a group, identify the purchasing company and receiving site for each case. Ask the relevant owners to approve common rules and local exceptions. Support this work with a controlled Odoo data migration.
Underside’s analysis: track time-consuming exceptions
We recommend limiting the pilot to one supplier and a few products. Measure orders without an agreement reference, price discrepancies and the time needed to explain a balance. Less retyping is not enough if buyers still have to rebuild the history in a spreadsheet. Extend the scope when these exceptions have an owner and a resolution process.
Official source
Functional reference: blanket orders in the Odoo 19 documentation, in French. The numerical example, control checks and deployment recommendations are Underside’s analysis.
Start with a real supplier agreement to plan recurring purchases in Odoo with Underside.