+91 98414 81435Free diagnosis
OdooBots
Loading
Module · Purchase

Odoo Purchase

Purchasing is where money leaves the business, and in most companies it leaves through WhatsApp. An order is agreed on a call, the goods arrive, the bill follows weeks later, and nobody can say whether the price matched what was agreed or whether the full quantity arrived.

Odoo Purchase is worth implementing for one control above all the others: a bill cannot be paid until the purchase order and the goods receipt agree with it.

Arun KumarOdoo Functional Consultant, 8+ years| Reviewed by Karthik Raj| Updated 20 October 2026| Covers Odoo 16–19, Community & Enterprise
Book a free Odoo diagnosis +91 98414 81435
0Odoo projects delivered
0Consultants & developers
Three-wayPO, receipt and bill agreeing
ChennaiAmbattur, Tamil Nadu
Odoo Purchase — requests for quotation, purchase orders and vendor bills matched in Odoo
630
630+ projectsdelivered on Odoo

Businesses running Odoo with OdooBots

Dhanalakshmi Industries logo Sanjeev Autoparts logo Electro Flux Equipments logo Anchor Marine Equipment Company logo NEXG logo PV Constructions logo SESS logo
Definition

What is Odoo Purchase?

Odoo Purchase runs buying from request to bill, with the bill matched against the order and the receipt before anyone pays it. Requests for quotation go to several vendors with their own prices and lead times, approval thresholds hold anything above a value, reordering rules raise suggestions from actual stock levels, blanket orders cover agreed annual rates, and receipt and bill are matched against the order automatically.

Three-way matching is the whole point. Without it, an ERP records purchasing rather than controlling it, and the difference shows up as overpaid invoices nobody ever finds.

RFQ
A request for quotation to one or more vendors. Becomes a purchase order when confirmed.
Three-way match
Purchase order, goods receipt and vendor bill agreeing on quantity and price before payment.
Reordering rule
A minimum and maximum per product per location that raises a replenishment suggestion.
Blanket order
An agreed rate and quantity over a period, called off as needed.
Capabilities

What Odoo Purchase does

Six parts make up the purchasing application, and its value comes from what it checks rather than what it records.

Requests for quotation

RFQs to several vendors with their own prices, lead times and minimum quantities, compared side by side before an order is placed.

Multi-vendorLead timeCompare

Purchase orders

Orders with agreed prices, delivery dates and terms, confirmed to the vendor and visible to the warehouse expecting the goods.

TermsDatesVisible

Approvals

Threshold-based approval so anything above a value needs a second pair of eyes, applied by configuration rather than by memory.

ThresholdsSecond eyesAudit trail

Replenishment

Reordering rules per product and location raising suggestions from real stock and incoming quantities, with the buyer still approving.

Min/maxPer locationSuggestions

Agreements

Blanket orders and purchase agreements holding an agreed rate over a period, called off as required rather than renegotiated each time.

BlanketCall-offRates

Bills and matching

Vendor bills matched against the purchase order and the goods receipt, with differences held for review instead of paid quietly.

MatchingDifferencesHeld
Connected

How Odoo Purchase works with the rest of Odoo

A reordering rule or a sales order raises a need. An RFQ goes out, prices are compared, and a purchase order is approved if it is above the threshold. The warehouse receives against that order, so quantity differences surface at the gate. The vendor bill is then matched against both, and anything that does not agree is held rather than paid.

Each of those steps is a control, and together they are the difference between knowing what you spent and deciding what you spend.

  • Needs raised from real stock levels and confirmed demand, not a guess
  • Vendor prices, lead times and minimum quantities held per vendor
  • Approval applied by value, automatically, with a trail
  • Receipt recorded against the order so shortfalls appear immediately
  • Bills matched before payment, with differences held for review
Odoo Purchase connected to the other Odoo applications in one database
One database — how purchase shares records with the rest of Odoo instead of exporting to it.
Expertise · how we work

What we settle in week one of an Odoo purchase implementation

These are the configuration decisions that are cheap to make now and structural to change once transactions exist. We walk through each one before a single record is migrated.

  1. Approval thresholds

    Which values need approval and by whom. Set too low it becomes a bottleneck; absent entirely it is not a control at all.

  2. Reordering rule scope

    Which products get min and max levels, per which location, and who reviews the suggestions rather than approving them blindly.

  3. Vendor pricelists

    Agreed prices, minimum quantities and lead times held per vendor, so an RFQ starts from the real rate rather than a phone call.

  4. Receipt steps

    One, two or three-step receiving. More steps give you an inspection gate and cost handling time; fewer are faster and see less.

  5. Bill matching tolerance

    How much price or quantity difference passes automatically and what is held. Zero tolerance stalls; wide tolerance is not a control.

  6. Landed costs

    Whether freight, duty and clearing are added to product cost. If they are not, your margin figures are wrong by exactly that amount.

  7. Who may create a vendor

    Vendor master control, because uncontrolled vendor creation is where both duplicate payments and fraud begin.

Community or Enterprise

What Odoo Purchase includes, and what needs Enterprise

Odoo moves features between Community and Enterprise from one version to the next, so the list below is what holds today and is confirmed against your own version during the diagnosis rather than taken as permanent.

Community covers the purchasing cycle: RFQs, vendor pricelists, purchase orders, reordering rules, blanket orders, receipts and bill matching. The control that matters most is in the free edition.

Enterprise adds approval and document handling around the edges, which is worth pricing against how many purchase orders you actually raise.

  • Approvals app — a general approval workflow beyond the purchase threshold. Enterprise.
  • Invoice digitisation (OCR) — reading vendor bills into drafts. Enterprise, charged by credit.
  • Documents — a workspace for supplier paperwork tied to records. Enterprise.
  • Quality — inspection control points on receipts. Enterprise.
  • Studio — extra fields and screens without code. Enterprise.
  • Community is enough where approval by value and three-way matching are the controls you need.
Odoo Purchase reporting view used to compare Community and Enterprise features
Editions — the features that decide whether Enterprise is worth its per-user charge.
Trust · honest advice

Where Odoo Purchase needs work

We would rather say this before you buy licences than after. These are the areas where we scope real development, recommend a bolt-on, or tell you another tool is the better answer.

Vendor portals

Suppliers responding to RFQs in a portal of their own is beyond the standard flow and is scoped as development.

Complex sourcing

Weighted scoring across price, lead time and quality to pick a vendor automatically needs custom logic.

Import documentation

Bills of entry, customs paperwork and clearing agent workflows usually need a custom module alongside landed costs.

Rate contracts with slabs

Tiered annual rate contracts with retrospective adjustment are common in India and not standard Odoo.

Supplier scorecards

Formal vendor rating on delivery, quality and price over time is a reporting build on top of the data.

Procurement planning

Planning purchases against a demand forecast needs the forecast to exist, and thin history does not produce one.

Our services

Our Odoo purchase implementation process

Implementing Odoo Purchase needs more than installing the application. It should reflect how your business already works, and change only what is worth changing.

  1. What you do today

    Understand what you buy, how orders are approved today, whether vendor rates are agreed in advance, and how bills are checked before payment.

  2. Configuration decisions

    Settle approval thresholds, reordering scope, receipt steps and bill matching tolerance before anything is configured.

  3. Configure, not customise

    Set Odoo Purchase up around how you work rather than installing it at its defaults, and build only what configuration genuinely cannot reach. See Odoo customization.

  4. Data migration

    Masters, open items and opening balances prepared and loaded. Data cleaning is scoped explicitly, because it is usually the largest single task. See Odoo migration.

  5. Testing with your own records

    Your team runs real transactions in a test database before go-live, including the awkward cases that never appear in a demonstration.

  6. Training and go-live

    Role-based training for the people who key transactions daily, then cutover, hypercare and ongoing support and AMC.

Trust · what it costs

What an Odoo Purchase implementation costs

We do not publish one price, because the same application costs very differently depending on the factors below. We do publish what moves the number, and the price is fixed in writing before work starts.

  • Vendor and item countLarge vendor pricelists need preparation before they are useful.
  • Approval complexityMulti-level approval by value and category adds configuration.
  • Receipt stepsInspection gates add warehouse configuration and training.
  • Landed cost handlingFreight and duty allocation is configuration plus discipline.
  • Import operationsCustoms documentation usually needs a custom module.
  • Purchase volumeHigh order counts need the flow simplified, not just modelled.
Why us

Why choose OdooBots to implement Odoo Purchase

We configure three-way matching with a tolerance your team can live with on day one. Zero tolerance stalls payments and gets switched off within a fortnight, which leaves you with no control at all — the usual outcome when it is set by someone who does not have to clear the queue.

Based inAmbattur, ChennaiTamil Nadu 600053, India
Phone+91 98414 81435Mon–Sat, business hours IST
Delivered630+ Odoo projects30+ consultants and developers
Versions supportedOdoo 16 – 19Community and Enterprise
FAQ

Odoo Purchase: frequently asked questions

What is Odoo Purchase?
The application that runs buying from request to bill: RFQs to several vendors with their own prices and lead times, approval thresholds by value, reordering rules raising suggestions from real stock, blanket orders for agreed rates, and vendor bills matched against the order and receipt before payment.
What is three-way matching and why does it matter?
The purchase order, the goods receipt and the vendor bill all agreeing on quantity and price before anyone pays. Without it an ERP records purchasing rather than controlling it, and overpaid invoices are never found because nothing was ever compared.
Can Odoo reorder stock automatically?
Yes, through reordering rules with a minimum and maximum per product and location, raising a replenishment suggestion from real on-hand and incoming quantities. The buyer still approves the suggestion — what disappears is the weekly spreadsheet that decided what to approve.
Can purchase approval be required above a value?
Yes, through threshold-based approval applied automatically with an audit trail. The threshold is worth setting with the people who clear the queue: too low and it becomes a bottleneck that gets switched off, absent entirely and it is not a control.
Does Odoo handle blanket orders or rate contracts?
Blanket orders and purchase agreements hold an agreed rate and quantity over a period, called off as needed. Tiered annual rate contracts with retrospective adjustment, which are common in Indian distribution, are not standard and are scoped as development.
How are freight and duty handled?
Through landed costs, which add freight, duty and clearing to the product cost rather than booking them as separate expense. If they are not added, your margin figures are understated by exactly that amount, which is why it is settled in week one.
Do we need Enterprise for purchasing?
Usually not. RFQs, vendor pricelists, orders, reordering, blanket orders, receipts and three-way matching are all in Community. Enterprise adds the Approvals app, invoice OCR, Documents and Quality control points, which repay high purchase volumes.
What happens when a bill does not match?
It is held for review rather than paid, with the difference visible against the order and the receipt. The tolerance for small price or quantity differences is configured deliberately, because zero tolerance stalls the payment run and wide tolerance defeats the purpose.
References

Sources and official documentation

Product capabilities stated on this page are documented by Odoo. The configuration advice, edition notes and limitations come from our own implementations.

Ready to put Odoo Purchase to work?

Tell us how purchase approval works today and whether bills are checked against receipts. Those two answers shape the configuration, and the diagnosis call is free.

Book a free Odoo diagnosis Talk to us +91 98414 81435