Odoo Purchase manages the procurement cycle from supplier selection to purchase order confirmation, from goods receipt to the vendor bill. It connects to Inventory (receipts and stock replenishment), Accounting (vendor bills and three-way matching) and Manufacturing (purchase of the components that manufacturing orders require). This article describes what the module covers, how it is configured, which mistakes recur most often and how to decide between standard, configuration, integration and custom development. It refers to Odoo 20 Enterprise.
When an implementation is healthy
A purchasing implementation works when five conditions hold:
- every purchase starts from a need generated by the system (reordering rules, make to order, manufacturing orders) and not from verbal requests or email chains;
- purchase orders are confirmed in Odoo and sent to suppliers from Odoo, with no parallel order documents outside the system;
- three-way matching between order, receipt and vendor bill is enforced: no bill is paid without a confirmed order and a validated receipt;
- vendor pricelists and lead times in Odoo reflect the real commercial agreements;
- purchase reports (spend analysis, vendor performance, on-time delivery) are available in Odoo without exporting to Excel.
The module covers five areas: the request for quotation and order flow (request, confirm, receive), vendor management (pricelists, lead times, agreements), purchase agreements (blanket orders, calls for tenders), three-way matching (order, receipt, bill) and reporting (spend analysis, vendor performance).
Module basics for daily buyers
People in purchasing work mostly in list and form views.
| View | Typical use in purchasing |
|---|---|
| List | All requests for quotation and orders with state, vendor, expected delivery: bulk send and confirm |
| Form | A single request or order: lines, delivery address, payment terms, billing policy |
| Kanban | Optional: requests by state (draft, sent, confirmed) |
| Pivot | Spend by vendor, by product category, by period |
| Graph | Purchase volume trends, on-time delivery rates |
The RFQ dashboard is the buyer's daily view. It has filters for requests sent, late requests (order deadline passed), not acknowledged (the vendor has not responded) and late receipts (expected arrival passed). In a healthy implementation "late requests" and "late receipts" are empty.
A few filters are used every day. On requests and orders: state (request, order, received, billed), vendor, buyer, grouped by vendor or category. In purchase analysis: grouping by vendor, month and product, to see spend concentration. On vendor bills: state (draft, posted, paid) and linked order, to verify the three-way match. Recurring views are saved as favourites: "My orders awaiting receipt", "Late deliveries this week", "Orders to bill this month".
Requests, orders and bills have a chatter with three tools: the internal note for negotiations, exceptions and communication history; the message, which goes from the request straight to the vendor and whose reply is logged on the document; the activity, to chase a late delivery, ask for order confirmation or escalate to a manager. An example: an order's delivery is three days late. The buyer notes "Called the vendor: delayed by customs, new date Friday", schedules a reminder activity for Friday and mentions the warehouse manager.
Demand-driven purchasing, not habit-driven
Every purchase should start from a system signal and not from the buyer's routine. There are four sources of signal:
- the reordering rule (minimum and maximum): the scheduler generates the request for quotation when stock falls below the minimum;
- the make-to-order route on the sales order: confirming the order triggers the request for that product;
- the need of a manufacturing order: confirming it with missing components triggers replenishment;
- the manual request: acceptable for non-catalogue, one-off or strategic purchases.
The scheduler (Inventory, Operations, Replenishment: Run Scheduler) runs daily. Buyers review the generated requests, adjust quantities if needed, confirm and send. They do not create orders from scratch for catalogue items. If buyers create all the orders by hand, from memory or from a spreadsheet of "what we usually order", Odoo's integration with replenishment is not active.
Vendor pricelists: the commercial contract in Odoo
The vendor pricelist encodes the price agreed with each supplier. For each vendor and product pair you record: the name and code the vendor gives the product (they appear on the order instead of the internal ones), the agreed unit price, the minimum quantity (Odoo warns if you order less) and the lead time in days, used by replenishment planning.
The vendor at the top of the pricelist is the default for reordering rules. With several vendors for the same product Odoo chooses by quantity break and price. If prices are entered by hand line by line, there is no price consistency, no automatic vendor selection and no way to analyse spend by comparing agreed and actual price.
Three-way matching and billing control policy
Three-way matching links the vendor bill to the order (what was ordered) and the receipt (what arrived). The path: the order is created with agreed quantity and price; the receipt is validated with the quantity actually received, which may differ from the ordered one; the vendor bill arrives. The billed quantity must match the received one and the unit price the order's, within tolerance. If they match, the bill can be posted and paid. If they do not, the billing control policy decides.
The billing control policy is set by product category and determines when the cost is recognised:
- on ordered quantities: the bill can be posted as soon as the order is confirmed, before receipt. Fine for services, subscriptions, advances, maintenance contracts. The risk is that accruals are needed if the period closes before arrival;
- on received quantities: the bill is posted only after the receipt is validated. It is the choice for physical goods, components, raw materials. The cost is recognised only when goods are in stock, so no accruals.
Using "on ordered quantities" for physical goods makes the cost appear before the goods arrive: stock valuation and the profit and loss are both temporarily wrong. Paying a bill without a validated receipt is a failure of financial control, and the policy by category prevents it automatically.
Blanket orders and tenders
Two types of purchase agreement complete the individual orders.
The blanket order is an agreement with a vendor for a product, at an agreed price, over a period. An example: buy up to 10,000 units of component X from vendor A at 5.00 euros each during the year. The individual orders are created against the blanket order and the remaining quantity updates itself. It avoids renegotiating the price on every order and enforces the volume commitment. If volume commitments with key suppliers exist but are tracked on spreadsheets, the feature is not in use.
The call for tenders sends the same request to several vendors together. The responses are compared in Odoo on price, lead time and terms, the award goes to the best offer and the other requests cancel themselves. It formalises competitive comparison and leaves a verifiable trail.
Configuring vendors, RFQs and orders
Vendor. On the contact form: company type (not individual) for B2B suppliers; payment terms (30 days, 60 days, immediate) applied to every order; currency if buying in foreign currency; fiscal position for EU and non-EU suppliers (intrastat, reverse charge on services). On the product form, Purchase tab, you record several vendor lines: the first, with priority, for the main vendor with price, lead time, minimum quantity and code; the second as an alternative at a different price; the third as an emergency vendor, dearer but faster.
From request to order. The draft request for quotation is sent to the vendor by email or from the portal. When the vendor confirms, the buyer uses Confirm Order and the request becomes a purchase order, with the receipt scheduled. The key fields of the order are the order deadline (by when the vendor must confirm), the receipt date (expected delivery, which drives warehouse planning), the delivery destination (company warehouse or a specific location), the billing control policy (inherited from the product), the agreement (the link to a blanket order, if any) and the vendor reference (the vendor's order number, copied to the receipt's source document).
Receipts, vendor bill and returns
Receipt and backorder. The confirmed order creates the receipt by itself, ready when the date arrives. If the quantity received equals the ordered one you simply validate. If it is lower, on validation Odoo asks whether to create a backorder: with Yes a new receipt is created for the missing quantity, awaiting the next delivery; with No the partial delivery is accepted and the rest cancelled. The validated receipt updates stock and enables matching for the bill.
Vendor bill. When the vendor sends the invoice, from Purchase, Orders you select the order and use Create Bill: the bill is pre-filled from the order lines and the received quantities. The buyer or accountant checks that quantities match the receipt and prices the order, and in case of difference contacts the vendor before posting. With Post the payable enters Accounting and payment is scheduled according to the vendor's terms.
Return to vendor. If the goods received are defective or wrong, from the validated receipt you use Return: the reverse transfer is created that takes the goods back from Stock to the virtual Vendors location. The reason is documented in the chatter, the vendor is notified and the credit note awaited, which in Accounting is registered against the original bill. Handling returns with manual inventory adjustments instead of return transfers is a warning sign.
Automated replenishment. When a reordering rule triggers (stock below minimum), a draft request is created for the default vendor, the one with priority one on the pricelist. Every morning the buyer reviews the batch of requests from Inventory, Operations, Replenishment, adjusts quantities (consolidates orders, rounds to the minimum order) and confirms. The expected receipt date is today plus the vendor's lead time plus the security lead time.
Call for tenders. A need is identified that is non-catalogue, strategic or high-volume; a request is created with products and quantities; you use the send to several vendors option, choosing them from a list; one request per vendor is created together. Vendors reply by email or from the portal, the buyer compares the responses (Purchase, Orders, filtering by agreement), confirms the best offer and the others are cancelled; cancellation is automatic if the agreement type is tender.
What changes with Odoo 20
Odoo 20 Enterprise is the baseline. Before classifying a need as development (Studio or custom), it is worth testing it against these features.
- RFQ dashboard. New filters: requests sent, late requests (deadline passed), not acknowledged (the vendor has not responded) and late receipts (expected arrival passed).
- Vendor reference. The one entered on the order is copied to the receipt's Source Document field.
- Agreement. The order field that links it to a purchase agreement is called Agreement.
- Grouping requests by vendor. A setting on the vendor (Group RFQ: on order, daily, weekly, always) consolidates into one request the replenishment needs generated automatically. Manual requests are never grouped, and needs stay separate across warehouses, currencies and dropshipping.
- Vendor pricelists. They fill requests and orders by themselves (price, quantity, lead time) and can be imported. Confirming an order does not create a pricelist line: without a pricelist, the request falls back to the most recent confirmed order line for that vendor.
- Purchase suggestions. The suggestion (minimum and maximum, bulk purchase) is vendor-specific: each product needs a matching pricelist line.
- Matching from order to bill. From the vendor bill you can auto-complete from the order or use the PO Matching button to match line by line (the detail sits in the Accounting area).
- Quality rate. Per vendor (Quality app), visible on the vendor form and on requests and orders.
For development requests the guidance is this: supplier comparison spreadsheets, manual reports on receipt status, vendor follow-up trackers, workarounds for the vendor portal and custom replenishment suggestions are first tested against the standard and configuration of Odoo 20 Purchase and Inventory.
The rationalisations you hear
| In the company they say | What it really is |
|---|---|
| "We create orders by hand because reordering rules are too complex to set up" | They need four fields: product, location, minimum, maximum. The complexity is in the discipline of setup, not in the feature. |
| "We pay vendor bills without an order because it is faster" | Without an order there is no budget authorisation, no price check and no delivery verification. A bill without an order is uncontrolled spend. |
| "We negotiate the price every time, pricelists keep changing" | Even changing prices are better tracked as pricelist updates than as manual entries. Price history is auditable, memory is not. |
| "We do not use blanket orders because our volumes are unpredictable" | A blanket order works with a maximum quantity, not a committed one: it fixes the agreed price without imposing a volume. |
| "The bill arrives before the goods, we post it at once" | You post after the receipt. If treasury requires early payment, use an advance payment entry, not a bill posted too early. |
| "We send orders from our personal email because Odoo's template is wrong" | The order PDF is customisable. Sending from personal email means the vendor's replies are not logged on the order and delivery confirmations are not tracked. |
| "Three-way matching slows us down" | Matching stops wrong payments. The "slowdown" is the time that used to be lost reconciling disputes with vendors. |
Warning signs
- Orders created by hand for every catalogue product: no integration with reordering rules or manufacturing orders.
- Vendor bills posted without a linked order: uncontrolled spend, no budget authorisation.
- Bills posted before the receipt is validated: the cost is recognised before the goods arrive and three-way matching is bypassed.
- Vendor pricelists not configured: prices entered by hand on every order, no consistency.
- No lead time on the pricelist: replenishment planning uses zero lead time and stock-outs are guaranteed.
- Orders sent from personal email: replies not logged, delivery confirmations not tracked.
- One vendor per product: no alternative configured, a supply disruption has no fallback.
- No billing control policy on the category: Odoo uses "on ordered quantities" for goods too.
- Blanket orders and volume agreements with key suppliers tracked only on spreadsheets.
- Calls for tenders run outside Odoo: offers compared by hand, no verifiable trail.
- Late orders (past the deadline) not monitored: vendor non-performance is invisible.
- Purchase analysis report never consulted: spend concentration and vendor dependency unknown.
- Returns to vendor handled with manual inventory adjustments instead of return transfers.
How to verify a configuration
After configuring or assessing purchasing, verification goes through these checks:
- vendor pricelists are configured for all key suppliers: product, price, lead time, minimum quantity;
- the default vendor (priority one) is set on all regularly purchased products;
- the billing control policy is set by category: on received quantities for physical goods, on ordered quantities for services;
- reordering rules exist for all replenished products, with the vendor chosen automatically by pricelist priority;
- the purchase scheduler has been tested: requests are created automatically when stock falls below the minimum;
- the email template for requests and orders is customised and orders go out from Odoo, not from personal email;
- three-way matching is enforced: for goods, no bill posted before the receipt is validated;
- alternative vendors exist for critical components (at least one fallback per product);
- blanket orders are created for strategic vendors with volume commitments;
- the return flow has been tested, from the return transfer to the vendor's credit note;
- the purchase analysis report has been examined: spend by vendor and category, actual price against pricelist price;
- monitoring of late orders is active: late requests, not acknowledged and late receipts are reviewed daily;
- payment terms are set on vendor records and apply to every order.
Standard, configuration, integration or custom development
To compare the current process with what Odoo covers without customisation, the starting point is knowing what is standard: the request for quotation, order, receipt, vendor bill flow; comparison across several vendors and preferred-vendor rules per product; purchase approval workflows (amount thresholds); requests generated by replenishment with reordering rules; allocation of landed costs to incoming shipments; vendor performance tracking (on-time delivery, quality); blanket orders and call-off scheduling.
Six questions help classify each gap before asking for development:
- How does a purchase request start? Who can request it, through which channel, who approves before the order goes out? Informal requests by email or chat are solved with configuration: Purchase approvals and, if needed, the Approvals module.
- How are vendors chosen for a new order? A single preferred vendor, a request to several vendors, framework agreements? A single vendor is configuration, comparing offers is standard, complex strategic sourcing may need an external tool.
- Are orders tied to warehouse needs? Or created independently of stock? Unlinked orders are a configuration gap solved with reordering rules and the Buy route.
- How are vendor bills matched to orders? Manual check, automatic three-way matching, no check? With no check, Odoo's three-way matching solves it: tolerance configuration is standard.
- What happens when a delivery does not match the order in quantity or quality? Who handles it, through which process? Informal handling is solved with the return and vendor credit note flow.
- Are there contracts or blanket orders with fixed quantities or prices over time? If so, the solution is standard with blanket orders. Complex scheduling with delivery windows may need Studio.
The typical classification of the commonest cases is this:
| Common gap | Typical path | Signals that push towards custom |
|---|---|---|
| Informal purchase requests | Configuration (approvals) | Multi-level approval with dynamic spend limits by cost centre |
| No vendor comparison | Standard (request for quotation) | Strategic sourcing with weighted scoring criteria beyond price and delivery |
| Orders not tied to stock | Configuration (reordering rules) | Complex demand planning with an external forecasting system |
| No three-way matching | Configuration | Tolerance rules tied to complex contract terms per vendor |
| Manual entry of vendor bills | Configuration | EDI or XML invoice format from the vendor needing a custom parser |
This article is an OIAR skill
What you have just read is the content of a skill from the OIAR catalogue, written for people. Knowledge like this, but richer and deeper, written for the agents, drives the interviews, the analysis and the report inside the platform. Skills are used in OIAR: to try this one on a project of yours you need an account.
odoo-purchaseGuide to designing and assessing the Odoo 20 Enterprise Purchase module: requests for quotation and orders, vendor pricelists, three-way matching between order, receipt and bill, blanket orders and tenders, billing control policy, returns to vendor. It includes warning signs, the rationalisations heard in companies and the questions that decide between standard, configuration, integration and custom development. Use it when setting up or checking the purchasing process in Odoo, with or without interviews with buyers and purchasing managers.