Purchase Order Template for Ecommerce Inventory Control
The useful PO is the one that survives receiving and invoice reconciliation.



A purchase order should capture the exact commercial promise your ecommerce business authorizes: who is buying, what is being bought, at what price and quantity, under which delivery and payment terms, and how receipt and invoice evidence will be checked. A compact template matters only when it controls inventory, cash, and exceptions.
Table of Contents
- Which fields belong in an ecommerce purchase order?
- Which purchase order template can an ecommerce buyer copy?
- What process should surround the purchase order template?
- How does three-way matching control errors?
- Which exceptions need a written path?
- How should the purchase order connect to inventory planning?
- Sources
- FAQ
Which fields belong in an ecommerce purchase order?
The essential fields make identity, money, goods, timing, acceptance, and authority explicit. SellerTrove’s position is simple: a purchase order is not useful because it looks professional; it is useful when its promise can be matched to receipt and invoice evidence.
Use these field groups:
- Identity: buyer, supplier, PO number, issue date, contacts, and relevant addresses.
- Commercial terms: currency, unit prices, taxes, freight, total, payment terms, and payment method.
- Item detail: SKU, description, variant, quantity, and line-level price.
- Delivery: ship-to address, delivery window, and incoterm with named place if applicable.
- Acceptance: inspection requirements, acceptance criteria, receiving owner, and disposition of rejected goods.
- Authority: requester, approver, issuer, approval date, supplier acknowledgement, and change history.
For imported inventory, include the applicable delivery term and named place clearly. Keep business records that support the transaction and its accounting treatment. This template is operational guidance, not legal or tax advice. Whether a PO is binding depends on applicable law and the parties’ terms; it is not always a binding contract in every jurisdiction.
Which purchase order template can an ecommerce buyer copy?
Copy the following field set into a document or purchasing system. Keep commercial changes visible through dated revisions, approvals, and supplier acknowledgements.
| Purchase order field | Required entry |
|---|---|
| Buyer | Business name, billing address, contact, and relevant registration detail |
| Supplier | Supplier name, address, contact, and remittance detail |
| PO number / date | Purchase order number and issue date |
| Currency | Currency used for prices and totals |
| Ship-to | Warehouse or destination address and receiving contact |
| Incoterm | Incoterm and named place, if applicable |
| Delivery window | Requested ship date and arrival window |
| Payment | Payment terms and method |
| Change control | Revision, approved change, date, and acknowledgement status |
| Authorization | Requester, approver, issuer, and approval date |
Line items
| Line | SKU | Description | Variant | Quantity | Unit price | Tax | Line total |
|---|---|---|---|---|---|---|---|
Use one line for each distinct SKU, description, variant, quantity, and price combination. Add rows when the order contains multiple items.
Order totals and acceptance
| Amount or control | Entry |
|---|---|
| Subtotal | Agreed line totals before taxes and freight |
| Taxes | Applicable taxes |
| Freight | Agreed freight charge |
| Total | Subtotal plus taxes and freight |
| Inspection / acceptance | Inspection requirements, acceptance criteria, owner, and date |
| Supplier acknowledgement | Accepted, changes requested, supplier contact, and acknowledgement date |
The PO should preserve the exact promise that later documents will reference. A template from Shopify or Xero can help structure the document, but the operational control comes from the fields and workflow around it.
What process should surround the purchase order template?
A controlled purchase order process separates request, authorization, supplier commitment, physical receipt, evidence review, and closure.
- Requisition: A buyer records the inventory need, requested items, quantities, and supporting planning information.
- Approval: The designated approver reviews the request, commercial terms, timing, and authorization.
- Issue: The buyer assigns the PO number, records the issue date, and sends the authorized PO to the supplier.
- Supplier acknowledgement: The supplier accepts the order or returns identified changes for review.
- Receipt: The receiving team records what arrived, when it arrived, and against which PO lines.
- Inspection: The business checks the received goods against its inspection and acceptance requirements.
- Invoice match: Accounts payable compares the PO, receipt, and invoice before treating the invoice as ready for payment.
- Exception: A mismatch or rejected condition receives an owner, decision, evidence, and resolution.
- Close: The PO is closed when its receipt, acceptance, invoice, and open exceptions have been resolved or documented.
A PO should not silently move from issue to payment. Each state should show the latest evidence and the next responsible action. Shopify’s purchase order guidance provides additional context for managing purchase orders alongside inventory records.
How does three-way matching control errors?
Three-way matching compares the authorized PO with the receipt and the supplier invoice at line level before payment. The goal is to identify whether the billed goods and charges correspond to what was ordered and accepted.
| Check | Purchase order | Receipt | Invoice |
|---|---|---|---|
| Item identity | Authorized SKU, description, and variant | SKU, description, and variant received | SKU, description, and variant billed |
| Quantity | Quantity authorized | Quantity received and accepted | Quantity billed |
| Price and charges | Unit price, taxes, freight, and total | Evidence of received condition; charges are not established by receipt alone | Unit price, taxes, freight, and total billed |
| Timing and terms | Delivery window, payment, and incoterm if applicable | Arrival date and receiving record | Payment terms and billed delivery charges |
| Decision | What the buyer approved | What the business accepted | What the supplier requested for payment |
A match supports closure. A mismatch moves to the exception path rather than changing the record silently. Keep the PO, receipt, inspection result, and invoice connected so the decision can be reviewed.
Which exceptions need a written path?
An exception should keep the original PO, the conflicting evidence, an owner, a decision, and the resolution visible.
| Exception | Written path |
|---|---|
| Quantity difference | Record ordered, received, accepted, and billed quantities; assign an owner. |
| Price difference | Compare the approved unit price with the invoice and document the decision. |
| Substitution | Record the requested substitute, approval, and effect on the PO line. |
| Damage or failed inspection | Record the inspection result, disposition, and supplier response. |
| Lateness or partial receipt | Record the delivery evidence, open quantity, and next action. |
| Invoice mismatch | Hold the mismatch for review and link the corrected invoice or approved decision. |
Do not treat a supplier acknowledgement, receiving adjustment, or invoice correction as a substitute for change control. The record should show what changed, who approved it, and when.
How should the purchase order connect to inventory planning?
The PO should connect the commercial promise to the inventory decision that created it. Before issuing, review inventory tools, inventory planning requirements, MOQ meaning, and landed cost. Use Stack Builder to organize the surrounding operating stack.
This connection keeps the PO useful beyond supplier communication: it links the requested quantity to planning requirements, minimum order quantity, landed cost, receiving evidence, and invoice control.
Sources
FAQ
What is a purchase order?
A purchase order is a buyer’s documented authorization for specified goods or services under stated commercial, delivery, payment, acceptance, and authorization terms. In ecommerce, it also provides the reference used to compare what was ordered with what arrived and what was billed.
Which fields should an ecommerce purchase order include?
Include buyer, supplier, PO number and date, currency, ship-to address, incoterm if applicable, SKU, description, variant, quantity, unit price, taxes, freight, total, delivery window, payment, inspection and acceptance, change control, and authorization fields.
What is three-way matching?
Three-way matching compares three records: the purchase order, the receipt, and the supplier invoice. The buyer checks item identity, quantity, price, charges, and relevant terms before resolving the invoice for payment.
Is a purchase order the same as an invoice?
No. The PO records what the buyer authorizes. The invoice records what the supplier requests for payment. The receipt records what arrived, while inspection records what the business accepted. Matching these records exposes differences.
We track pricing and new tools across the whole catalog. Get an email when prices move or a better tool launches.