Odoo Purchase: Supplier Enquiries to Receipts

A purchase order should preserve what the supplier agreed to provide.

The order needs the correct product, supplier reference, quantity, unit, currency, terms and expected timing. If buyers rely on abbreviated descriptions or unmaintained vendor codes, the rest of the process can faithfully record the wrong item. Clean procurement data is therefore a prerequisite to useful automation.

Requests for quotation allow the business to record supplier offers before confirming procurement. Decide how technical clarifications, alternatives and commercial changes are approved and communicated. The supplier response should update the customer or production commitment where the purchase exists to satisfy that demand.

Choose how demand should lead to purchasing.

Different products may need different supply rules. The correct design should express the commercial and stock policy already agreed by the business.

Maintain the supplier information that buyers actually use.

Supplier codes, purchase units, price information and lead times should be reviewed by a named owner. A supplier’s catalogue may use a different reference from your internal stock code. Maintain the relationship rather than creating duplicate products whenever a new supplier is added.

External supplier feeds, catalogues or portals require a defined source of truth, field mapping and update process. Data access and failure handling must be verified. The existence of a supplier field in Odoo does not establish a ready-made connection to every supplier system.

An order, a receipt and a vendor bill answer different questions.

The purchase order records the agreement. Inventory records what actually arrived. The vendor bill records the supplier’s financial claim. A partial delivery, rejected item or changed charge can make those records differ legitimately or reveal an error. Assign responsibility for investigating the difference and the evidence needed to resolve it.

Agree the relevant billing and control policies with finance, including permissions and the exact point at which an approval is enforced. Recording all three documents is not the same as proving every mismatch is blocked automatically. Use an actual exception to demonstrate the required behavior.

Requirements that may extend the purchasing foundation.

Bring sample documents and the desired decision flow to discovery so the scope can be tested rather than inferred.

• Multi-level or conditional approvals based on value, margin, category, project or budget.
• Formal tender evaluation, bid comparison, contract registers or specialized procurement governance.
• Letters of credit, customs files and import-document preparation or approval.
• Supplier portals, EDI, marketplace connections or automated catalogue updates.
• Advanced landed-cost allocation and any specialized finance or statutory reporting requirements.

Test currencies and open procurement before cutover.

An Iraq business may buy in foreign currencies while keeping its company accounts in an agreed base currency. Finance should approve active currencies, rate maintenance, valuation and reconciliation. Additional acquisition costs require the relevant landed-cost setup and accounting treatment; they should not be confused with every import-management requirement.

Prepare suppliers, product mappings, units and open purchase orders with an agreed cutover status. Test a changed supplier offer, partial receipt, rejected quantity and bill difference. Reconcile the resulting stock and balances, then train buyers, receivers and finance on their shared exception process.