How to Write a Purchase Order in 2026: Fields, Examples, and Common Mistakes

A purchase order (PO) is a binding document a buyer sends to a supplier to authorize a specific purchase at specific terms. When the supplier accepts it — explicitly or by performance — it becomes a contract. Done well, the PO is the single source of truth for the order: what was bought, at what price, on what terms, and when it's expected. Done badly, it's the start of a six-week email thread.

This guide covers the structure of a modern PO, the fields that matter, the fields that don't, an annotated example, and the automation that makes most of the manual work redundant.

The eight required fields

Every PO — printed, faxed, emailed, or sent by EDI — needs these eight fields. Anything less is a request, not a purchase order.

The fields that prevent disputes

These aren't legally required but eliminate 80% of the back-and-forth that follows a typical PO.

• Required delivery date or window. "Asap" means nothing to a supplier with a route schedule. Specify a date or a window.
• Pack size and unit of measure. "1 case" vs "1 each" is the most common source of order errors. Always state the pack and the unit.
• Supplier part number (SKU). Their SKU, not yours. If you order off your internal SKU and they have to map it, you will get sub-quantities, substitutions, or wrong items.
• Substitution policy. "Do not substitute" or "Substitute up to $X" or "Substitute and notify before shipping." Pick one.
• Acceptance trigger. "Please confirm by 5pm Tuesday or this order is void" prevents you from waiting on stale orders.
• Special instructions. Dock hours, lift gate required, call on arrival, signed delivery only. Whatever your receiver needs.
• Reference to terms. "Subject to our standard terms at [URL]" or attached. Saves you in disputes.

An annotated example PO

PURCHASE ORDER

PO #: KEV-2026-0428-001                  Date: 28 April 2026

FROM:                                    TO:
Kev's Bar & Grill                        Charlie's Produce Co
715 E Pine Street                        2201 Western Ave
Seattle, WA 98122                        Seattle, WA 98121
ar@kevsbar.com                           wholesale@charliesproduce.com
Contact: Kev L., (206) 555-0142

SHIP TO:                                 PAYMENT TERMS:
715 E Pine Street, Seattle WA 98122      Net 14
Required delivery: Wed 30 Apr, 6-9am     Currency: USD
Dock notes: Use side door, ring buzzer

LINE ITEMS:
SKU         Description               Pack    Qty   Unit Price   Line Total
014-02643   Strawberries, whole       30 lb   2     $76.00       $152.00
013-01044   Avocados, Hass ripe       Case    1     $64.15       $64.15
031-02266   Juice, Lemon Perricone    1 gal   3     $23.00       $69.00

Subtotal:                                                           $285.15
Shipping:                                                            $12.00
Tax (exempt, resale cert on file):                                    $0.00
Grand total:                                                        $297.15

SUBSTITUTION POLICY: Notify before substituting. Do not substitute strawberries.
ACCEPTANCE: Please confirm receipt of this PO by 5pm Tuesday 29 Apr.
TERMS: Subject to our standard terms at kevsbar.com/po-terms.

Approved: Kev L. / Owner / 28 Apr 2026

Every field above maps to one of the items in the previous tables. Nothing is decorative.

The eight common mistakes

1. No PO number. When the invoice arrives, you can't reconcile. Always assign one before sending.
2. Ambiguous quantity-vs-pack. "1 strawberries" means one flat to one supplier and one case to another. Always state the unit.
3. Buyer's SKU instead of supplier's SKU. Forces a translation step that often goes wrong.
4. No delivery date. The supplier defaults to their preference, which may or may not match yours.
5. No payment terms. Defaults to whatever the supplier prefers, which is COD or prepaid for new buyers.
6. Currency not stated. Common for cross-border. Costs you 2–5% on the wrong assumption.
7. Tax status unclear. If you're tax-exempt, attach the resale certificate; otherwise expect tax on the invoice.
8. No acceptance request. Without a deadline, the order can sit unconfirmed for days. Always ask for confirmation.

Channels: email, EDI, portal, WhatsApp

How you transmit the PO matters. Each channel has trade-offs.

• Email (PDF or inline). Most common for SMBs. Universal, but unstructured — the supplier types your PO into their system manually, and 1–3% of orders have transcription errors. Modern systems read confirmation replies automatically.
• EDI (X12 850). The B2B standard. Suppliers parse it programmatically. Best for high-volume relationships. Setup is non-trivial but the error rate is near zero.
• Supplier portal. The supplier's website. Works fine for one supplier. Painful when you have twenty.
• WhatsApp. Increasingly common in SMB B2B, especially Latin America and parts of Asia. Modern systems format POs as structured WhatsApp messages.
• Phone or fax. Still alive. Don't use them as your primary channel; you have no audit trail.

What modern automation actually does

If you're writing POs by hand in 2026, you're doing the work the system should be doing. A modern procurement platform like LineNow:

1. Generates the PO from your ordering decision. You add items to a cart from the inventory tab; the PO is built automatically with all eight required fields and the dispute-prevention fields, pre-filled from your saved supplier and buyer details.
2. Suggests quantities from real consumption. Statistical replenishment computes order quantity per item based on the last 30 days of POS sales, decay rate, lead time, and target service level. You don't guess.
3. Sends through the supplier's preferred channel. Email, WhatsApp, EDI, or platform portal. The system stores the supplier's channel preference and routes accordingly.
4. Reads the confirmation. When the supplier replies, AI parses the message: did they confirm? What changed? Any substitutions? New ETA? The PO updates automatically; you review the diff.
5. Reconciles the invoice. When the invoice arrives, the system matches it to the PO, flags discrepancies, and pushes the bill to QuickBooks or Xero with the correct COGS classification.
6. Logs everything. Every email, every reply, every status change is in one timeline per PO. When you have a dispute six months later, the receipts are right there.

The PO becomes a workflow, not a document. The eight required fields are still there — they have to be — but you're not typing them. You're reviewing them.

The legal status of a PO

A PO is an offer to purchase at specific terms. It becomes a binding contract when the supplier accepts. Acceptance can be:

• Explicit: a written confirmation, signed acknowledgment, or order number assigned
• Implicit: shipping the goods, sending an invoice

If the supplier's reply changes any material term (price, quantity, delivery date), it's a counter-offer, not an acceptance. You should explicitly confirm the new terms before goods ship. This is the "battle of the forms" problem in commercial law — courts generally enforce the last-set-of-terms-the-other-party-accepted, so getting the final terms right matters.

For SMBs, the practical implication is: if your supplier replies "confirmed but price up $0.50/lb," that price increase is binding only if you accept it (or accept delivery without objecting). Modern systems flag price changes for explicit operator approval before the order ships, which protects you from silent margin erosion.

The takeaway

A purchase order, properly written, has eight required fields and seven dispute-prevention fields. Anything more is template clutter. The act of writing one by hand — and worse, retyping the supplier's confirmation when it comes back — is exactly the work that modern procurement systems eliminate. The fields stay; the typing goes away.