Most small e-commerce businesses manage purchase orders through email and spreadsheets until the volume makes that unsustainable — by then they've experienced the consequences.
What a PO System Needs to Do
A functional PO system creates and sends POs, tracks status of open POs, matches received inventory to open POs for accuracy verification, and posts liability to accounts payable when goods are received.
Three-Way Match for Financial Accuracy
Compare the PO (what you ordered), the receiving report (what arrived), and the supplier invoice (what they're billing for) before payment is approved. This prevents most purchasing-related financial errors.
Standardize Your PO Format
Every PO should include: PO number, issue date, required delivery date, line items with description, quantity, and agreed unit cost, shipping terms, and payment terms.
The fix: Create a standardized PO template in Excel or Google Sheets. Implement a process where every supplier order generates a PO with a unique number. Track open PO status in one place. These three steps can be implemented this week.
Define the PO lifecycle
Map request, approval, issuance, supplier acknowledgement, change management, shipment, receipt, invoice matching and closure. Each stage should have an owner and status that can be understood without opening an email thread.
Use consistent item and supplier data
Purchase orders depend on accurate SKUs, units of measure, costs, currencies, supplier lead times and ship-to locations. Clean master data prevents many receiving and invoice problems before they occur.
Separate ordered, confirmed, shipped and received quantities
Do not treat an issued PO as inventory on the way. Track supplier confirmation and shipment evidence separately so planners know which quantities are genuinely expected.
Design exception handling
Late production, partial shipments, cost changes, damaged receipts and quantity discrepancies should follow a defined process. Record the decision and revised dates so inventory plans update accordingly.
For systems and reporting work around purchasing, see e-commerce systems & reporting.
Add approval rules that reflect risk
Not every PO needs the same review. Set thresholds for spend, new suppliers, cost changes, deposits or unusual lead times so higher-risk orders receive the right approval without slowing routine replenishment.
Build a PO exception dashboard
Flag overdue acknowledgements, changed ship dates, partial shipments, cost variances and receipts that do not match the order. Exceptions are where purchasing teams need attention; a list of every open PO is rarely enough.
Define change-order rules
When quantity, price or ship date changes, preserve the original order and record the approved revision. This helps receiving and finance understand why supplier documents differ from the first PO.
Connect purchase orders to inventory planning
Open POs should feed replenishment views with realistic confirmed dates, not simply the requested date. Flag overdue or unconfirmed supply separately.
Measure supplier acknowledgement time
Track how quickly suppliers confirm quantity, price and timing. Slow acknowledgement reduces the planning value of issuing POs early.
Close POs deliberately
Define when residual quantities are cancelled, short receipts are accepted and the order is financially complete. Old open POs can distort expected inventory and cash commitments.