Even the best production plan falls apart if materials don't arrive on time. A manufacturer can have the right routing, a complete Bill of Materials, and a fully optimized MRP run. If procurement is delayed, misrouted, or untracked, the entire production schedule breaks down.
Purchase Orders (POs) are the formal mechanism that closes this gap. They translate procurement decisions into documented, trackable commitments with suppliers, specifying what needs to be bought, in what quantity, by when, and from whom.
In Apache OFBiz, Purchase Orders sit at the intersection of planning and execution. They can be generated automatically from Material Requirements Planning (MRP) recommendations or created manually for ad hoc procurement needs. Either way, every PO is tied back to the Bill of Materials (BOM) to ensure every component purchased has a defined role in the final product.
A Purchase Order is a formal document issued by a buyer to a supplier to authorize the procurement of specific goods or services. It defines what to buy, how much, at what price, and under what delivery terms.
In Apache OFBiz, the PO is more than an administrative record. It acts as the operational link between the procurement plan and supplier execution. Every PO is tracked through a defined lifecycle, from creation and approval to receipt and closure, giving businesses full visibility into outstanding commitments and incoming inventory.
A typical Purchase Order in Apache OFBiz includes:
• Supplier details (who the order is placed with)
• Order items (product descriptions, quantities, and unit prices)
• Delivery dates and destination (when and where materials should arrive)
• Payment and shipment terms (agreed conditions for settlement and logistics)
• Order status tracking progress through stages: Created, Approved, Completed
Purchase Orders serve a purpose beyond just requesting materials. In Apache OFBiz, they:
• Provide legal and financial documentation for every procurement transaction
• Prevent unauthorized or duplicate purchases through structured approval workflows
• Keep inventory forecasts accurate by linking incoming stock to planned requirements
• Support cost accounting by connecting each PO to invoices, receipts, and payments
• Ensure supplier accountability by locking in delivery dates and agreed quantities
Purchase Orders don't exist in isolation. They are a direct output of the MRP process and a direct input to production. Once MRP identifies that certain materials cannot be produced internally and must be sourced externally, those external requirements are converted into Purchase Orders.
Consider the skateboard manufacturing example. After an MRP run, Apache OFBiz identifies that components like stickers (STC1001) and warranty cards (STC1002) are not produced in-house. These appear as external requirements in the system. Once reviewed and approved, they are converted into a Purchase Order addressed to the relevant supplier, with quantities, lead times, and delivery dates automatically populated from the MRP output.
When the supplier ships the materials and they are received at the warehouse, the inventory is updated automatically, and the PO is marked as Closed. This keeps the production schedule on track without manual data entry or reconciliation.
Apache OFBiz’s Purchase Orders work closely with the rest of the manufacturing ecosystem:
• MRP Module: Converts approved external requirements into draft POs automatically
• Inventory Module: Updates stock levels as soon as goods are received against a PO
• Supplier Management: Pulls vendor details, pricing, and terms directly into the PO
• Accounting Module: Links each PO to invoices and payments for a complete financial audit trail
Apache OFBiz supports two methods for creating Purchase Orders, depending on whether the procurement need was identified by MRP or initiated manually.
This is the standard method when MRP has already identified what needs to be purchased. The process involves five steps:
1. Review and approve proposed external requirements in the Requirements module
2. Group approved requirements by supplier to see what each vendor needs to fulfill
3. Generate a draft Purchase Order per supplier with a single click
4. Review item quantities, prices, and delivery dates and adjust if needed
5. Finalize and approve the order, then send it to the supplier
For procurement needs that fall outside the MRP process, such as one-off purchases, emergency stock, or items not in the BOM. A PO can be created manually:
6. Navigate to Order > Order Entry > Purchase Order
7. Select the supplier, internal organization, and destination facility
8. Add order items with product details, quantities, and pricing
9. Define delivery dates, payment terms, and any internal notes
10. Finalize and approve the order
For detailed, step-by-step instructions on both methods, refer to the Creating Purchase Orders from MRP Recommendations in Apache OFBiz guide on the Apache OFBiz Confluence wiki.
Purchase Orders are the operational backbone of procurement in Apache OFBiz. They formalize supplier commitments, ensure traceability from planning to payment, and close the loop between what MRP recommends and what actually gets procured.
By automating PO creation from MRP outputs and integrating tightly with inventory and accounting, Apache OFBiz gives manufacturers a reliable, auditable procurement process, with no manual handoffs or disconnected systems.
Once Purchase Orders are approved and sent to suppliers, the next step is receiving the materials into inventory. The next blog in this series covers Inventory Receiving in Apache OFBiz: how incoming shipments are verified, recorded, and made available for production.
Looking to optimize procurement and manufacturing operations with Apache OFBiz? Partner with HotWax Systems for a tailored implementation built around your supply chain.