Purchasing and procurement

What you ordered, and what actually arrived

Buying goes wrong in the gap between the three documents: the order, the goods and the bill. Keeping them on one record means the difference shows up at the door rather than in the ledger a month later.

An Odoo requests-for-quotation list with late and unacknowledged counts.

Suppliers

One record per supplier, with the history on it

Terms, contacts, lead times and what they have actually delivered before, on the record the next order is raised from rather than in somebody's inbox.

An Odoo vendor list with contacts and activity.

Arrival

Counted at the door, not at month end

The receipt names the order it belongs to, so a short delivery is a discrepancy on the day rather than a mystery when the stock count disagrees.

An Odoo receipts list with source documents and status.

The bill

Checked against the order and the receipt

Three documents that have to agree before money moves. Where they do not, the difference is on screen instead of in an argument after payment.

An Odoo vendor bill list with references and amounts due.

Spend

What you buy, from whom, and at what price

Purchase volume and value over time, by vendor and by product — the figures a negotiation needs, read off the orders rather than assembled for the meeting.

Screenshots show the Odoo interface, captured from Odoo's public demo database or published by Odoo S.A. at odoo.com — not Rkieh Productions client systems. Odoo is a trademark of Odoo S.A. Rkieh Productions is an Odoo partner and implements and configures Odoo for its clients; what any given system does depends on edition, enabled modules, hardware and the agreed solution design.

In scope

What the module covers

This describes the scope Rkieh Productions can implement or configure using Odoo and related integrations. Final availability depends on edition, enabled modules, hardware and the agreed solution design.

Suppliers

Vendor records with terms, lead times, contacts and the pricing that applies to them.

RFQs

Requests sent to the vendors that can supply, and compared on price and date rather than on memory.

Purchase orders

The agreement: what, how many, at what price and by when, confirmed and now measurable against.

Approvals

Who may commit the business to what, decided by role and by value rather than by who is in the room.

Receipts

What arrived, counted on arrival against what was ordered, moving stock as it lands.

Vendor bills

Matched to order and receipt before release, and posted to the same accounts every other cost posts to.

One document

One order, two jobs promise and yardstick

ERP and business operations

It says what was promised, at what price, arriving when. Everything after it — the receipt, the bill, the stock valuation — is measured against it, which is what makes a late or short delivery a fact rather than an impression.

An Odoo purchase order with its lines, taxes and receipt status.

Connected

What buying is wired to

A purchase order that reaches nothing else is a PDF. These are the joins that make it an operation.

Inventory

A receipt moves stock at the location it actually landed.

Accounting

The bill posts to the accounts and taxes configured, against the cost the goods carried in.

Products

One catalogue, with vendor pricing and lead times held against the product itself.

Replenishment

Reordering rules raise the request; buying decides what to do with it.

Manufacturing

Components arrive against the orders that need them, at the dates production planned for.

Reporting

Spend, lead time and on-time delivery per vendor, from the orders themselves.

What changes

Four things buying stops doing

Chasing by email

The order carries its own status and its own deadline.

Approving after the fact

Commitment happens at the point it is authorised.

Paying then checking

Order, receipt and bill agree before the money moves.

Negotiating on memory

Price and lead-time history comes off the orders.