Standard-first delivery
Implementation by phases
Verified business data
MAXCODE connects purchasing with inventory, sales, manufacturing, projects and accounting according to the company's actual scope. Automated replenishment can be useful, but only after products, vendors, lead times and responsibilities are sufficiently reliable.
When do you need purchasing software?
Purchasing software becomes important when several departments order from the same vendors, prices and dates depend on quantity, or an incorrect order can stop delivery or manufacturing. A spreadsheet can track an order list, but it is difficult to connect requests, approvals, purchase orders, receipts and bills without manual reconciliation.
Typical signs that the purchasing process needs attention include:
If you have few vendors, infrequent orders and one person can reliably control the entire process, a separate purchasing system may not be necessary. Connected ERP provides more value when purchasing depends directly on inventory, sales or manufacturing.
What does the purchasing process look like in Odoo?
The process can start with manual demand, a sales plan, manufacturing demand or an inventory replenishment rule. Purchasing prepares a request for quotation, checks the vendor, price and date, and confirms the purchase order. When Inventory is connected, order confirmation creates an expected receipt. The vendor bill can then be checked against agreed and received data according to configured controls.
A typical flow looks like this:
1. Demand for a product or service is identified.
2. Current and forecast stock and open orders are checked.
3. Purchasing sends a request for quotation to one or more vendors.
4. Price, date, quantity and other terms are compared.
5. An authorised person confirms the purchase order.
6. Inventory records full or partial receipt and any differences.
7. The vendor bill enters review, posting and payment.
Not every business request is a standard Odoo purchase order. Internal purchase requests, tenders or multi-level approvals may require additional configuration and verification of the Odoo edition.
How should vendors, prices and lead times be maintained?
Vendor data is more than a name and tax identifier. Useful automation requires knowledge of which vendor supplies each product, at which minimum quantity, price, currency and expected lead time. An obsolete price or unrealistic lead time can automatically create the wrong order.
Before importing data, verify:
If a product has several vendors, the choice should not always be reduced to the lowest price. Lead time, reliability, quality and minimum quantity may matter more. Odoo stores operational data, but a responsible person must define the business rule.
How does purchasing connect to inventory and replenishment?
Reordering rules can suggest or trigger a request for quotation when forecast stock falls below a configured minimum. This can reduce manual monitoring, but only when stock levels and vendor lead times are reliable. Incorrect opening stock produces incorrect purchasing suggestions.
Before automating, review several periods of real consumption and exceptions. Seasonal products, project purchasing, long lead times and products ordered only for a specific customer do not necessarily need the same rule.
For the wider inventory context, see Odoo Inventory. The connected customer-to-delivery flow is described on the Odoo Sales page, while the overall approach is covered in Odoo implementation in Croatia.
How can approvals be configured without slowing work?
Approval should be connected to real risk. If every small order waits for a director, the system becomes an electronic version of a poor process. More useful criteria may include value, cost type, department, a difference from the contracted price or selection of a new vendor.
For each threshold, define:
The exact implementation depends on the Odoo edition, installed applications and required rules. The process should first be proven on several real cases.
When is the purchasing application not enough?
The purchasing application cannot determine what the company should buy when the sales plan, manufacturing bills of materials or project demand are not maintained. It cannot confirm delivery quality or decide whether a substitute product is acceptable. Those decisions require responsible people and connected processes.
Integrations with EDI, a vendor portal, an external warehouse or a specialised approval system may be separate projects. Errors should also be tested, including partial receipt, price changes, rejected deliveries and bills without purchase orders.
What does an Odoo Purchase implementation look like?
Implementation starts with several representative orders, not the full catalogue. One case should be normal, while another should include a real exception such as partial delivery or a price change.
Common steps include:
The time and cost depend on data quality, number of vendors, approval rules and integrations. Wider factors are explained on the Odoo pricing page.
What should you prepare for an initial assessment?
Prepare a typical purchase order, a vendor price list, a receipt example and a vendor bill. Add a case where the quantity, price or delivery date differed from the agreement. Record who made the decision and where it was documented.
A useful step without purchasing software is to select the ten most frequently purchased products and record the vendor, price, minimum quantity, lead time and person who approves changes. If that data is not reliable, maintain it first and automate ordering later.
Start with one real process
A representative document reveals the real scope faster than a generic feature list.