Purchase order template: every field, with a filled example

A purchase order is two documents in one: the request for goods, and the record both sides reach for when something goes wrong. That second job is why a template matters — when a shipment goes wrong, the outcome turns on whether three fields were on the PO at all: the incoterm, the payment terms, and the cancellation window. Here is every field a small store's PO should carry, plus a filled example.

The header fields

Six lines; two cause most of the trouble:

• PO number and date. The unique reference everything hangs from — receiving, invoices, disputes. Scheme design is the PO number guide's job; the date anchors terms that run from issuance or deposit clearance — say which.
• Supplier block with remit-to details. Legal name plus the address or account payments go to. Confirm remit-to in writing before the first payment — changed bank details are a classic way money disappears.
• Ship-to. The exact location receiving the goods, not "our warehouse." With two locations, this field decides where units land and which counts they correct.
• Requested delivery date. A real date, not "ASAP" — it anchors the lead-time term.
• Buyer/contact. The one person whose yes counts when the supplier emails "can we ship 550 instead?"

The email carrying the PO is a separate skill (the cover email guide); the issued-to-received lifecycle is the purchase order process.

The line-item fields

One row per product, built to survive the factory floor and the receiving dock.

• SKU / part number. Both, if the supplier has one — theirs catches their attention, yours is the join key when goods hit your system.
• Description with the spec that matters. "Notebook, A5, dotted, hardcover, heather gray" — not "notebook." This is where "gray" becomes "heather gray" becomes a claim.
• Quantity in sell units AND case units. 600 units is what your inventory counts; 25 cases of 24 is what physically arrives and what freight prices on. Carry both or someone translates at the dock from memory.
• Unit cost and its basis. "USD 2.85" means different purchases depending on incoterm and currency — the basis rides on the line.
• Extended total. Do the multiplication on the document: 600 × $2.85 = $1,710.00 — one number both sides check, so discrepancies surface before shipping.

The totals block

Subtotal, freight terms (a pointer to the incoterm), estimated freight if you arrange it (labeled until the forwarder quotes), and a taxes/duty note naming who handles import duty and VAT — ten words that prevent the surprise duty invoice.

The terms block: where disputes are actually decided

Most templates end at the totals. Backwards — the terms block is the part that gets enforced, and three fields here cause more disputes than every header field combined.

1. The incoterm. "$2.85 per unit" isn't a price until you know whether it's ex works (you pay every leg from the factory door) or FOB a named port (supplier loads the vessel; you take over). The difference is the whole first freight leg — and where risk sits if a container goes into the water. Name the term and the place: FOB Shanghai, not just FOB. The Incoterms guide for small importers covers the handful you'll use.

2. Payment terms and deposit schedule. "Net 30" and "30% deposit, 70% against shipping documents" are both fine; unstated terms default to whatever the supplier invoices. For made-to-order overseas production, a workable default is 30% with the order, balance against a copy of the bill of lading — final payment tied to evidence of shipment. Vocabulary and negotiation: the net-30 explainer.

3. Lead-time confirmation and cancellation window. "45 days" is incomplete — from what? Deposit clearance, PO acceptance, materials arriving? Measuring the real number is the supplier lead time guide. The cancellation window is the field nearly everyone skips: how late you can trim without penalty, and what partial cancellations cost once production starts. Without it, a shifted forecast leaves you absorbing goods or renegotiating from weakness.

4. Inspection window. Days after receipt to inspect and raise claims — 7 is a workable default. Without it, "you should have told us sooner" is a fair answer to a claim raised in week three. What to check: the inspection checklist.

5. Packaging spec. Units per case, carton labeling (your SKU and count on each carton), pallet configuration if it matters. Labeled cartons turn a two-day putaway into an afternoon; packaging decisions that affect inventory walks the trade-offs.

The full template

Copy this into your spreadsheet; one row per field.

Header

Each line item

Totals and terms

A filled example: 600 notebooks

Note the gap on purpose: the 45-day lead runs to the vessel; the delivery date carries the ocean leg — production ends in December, sellable stock lands in January.

If you run InventoryX, the weekly Buying List exports as a draft PO in this shape — drafts only, and every field stays yours to confirm. The tool sketches the document; the terms block is still your judgment call.

The fields are the dispute record

When a shipment goes wrong, resolution runs on paper: the PO states what was agreed, the supplier's confirmation shows acceptance, your receiving report shows what arrived — and the invoice is checked against all three, the three-way match. This template's fields are exactly the lines being matched. A complete terms block is the evidence file, written before anyone is angry.

Three mistakes that show up on real POs

1. A per-unit price with no incoterm. USD 2.85 ex works and USD 2.85 FOB Shanghai differ by the entire first freight leg, and the estimated-freight line is meaningless until the basis is fixed. Quote silent? Ask first.
2. No cancellation window. Without a written window you either absorb unwanted goods when the forecast shifts or renegotiate from weakness. Write it even if the supplier counters with penalties — knowing the penalty beats discovering it.
3. Quantity in cases only. "25 cases" on the PO, a team counting 600 units, an invoice saying 25 cases — the mismatch manufactures its own discrepancy. Both numbers, always: 600 units (25 cases × 24).

Common questions

What fields must a purchase order include? PO number and date; supplier with remit-to details; ship-to location; requested delivery date; buyer contact. Per product line: SKU, description, quantity in sell and case units, unit cost with incoterm basis, extended total. Then the terms block: incoterm, payment and deposit schedule, lead time with clock start, cancellation window, inspection window, packaging spec.

Who decides the incoterm on a PO? The buyer proposes it and the supplier confirms it — either way it must appear on the document with a named place. Ex works and FOB differ by the whole first freight leg and by where risk transfers. If the quote was silent, ask before issuing.

Is a PO binding without payment terms? Generally a PO becomes binding once the supplier confirms it; missing payment terms don't void that — they default to whatever the supplier invoices and when. Stating terms shifts the defaults to yours. General context, not legal advice.

How much deposit should a PO ask for? For made-to-order overseas production, 30% with the order and 70% against a copy of the bill of lading is a workable default — the balance stays tied to evidence of shipment. Domestic stock goods often run net-30 with no deposit; custom tooling may demand more.

Next step

Fill the terms block first on your next order — it's the part that gets enforced — then save the filled notebook example as your master template and change only what differs per order. If any of your goods are custom-made, the description line is only a summary; the tech pack is where the full specification lives. And if the line-item identifiers are a mess before the PO even goes out, SKU vs UPC vs GTIN untangles which number goes where. The PO is the last step of the weekly decision — the weekly reorder list is how that decision stops living in four tools.