How to Create a Purchase Order (Step-by-Step Guide With Examples)
A practical guide to writing a purchase order — the required fields, common mistakes, and how to get a clean PDF in 90 seconds with a free generator.
A purchase order isn't a complicated document. It has maybe 10 required fields and a list of line items. You can write one in a Word doc, in Excel, on a notepad if you really had to.
The trick is consistency. Most PO problems don't come from missing exotic fields — they come from inconsistent formatting, skipped fields, or PO numbers that collide. This post walks through writing a clean PO from scratch, step by step.
The 9 fields every PO needs
Before you start, here's the checklist. Every PO should have:
- PO number — unique, sequential
- Issue date — when the PO was created
- Buyer information — your company name, address, contact
- Vendor information — seller's name, address, contact
- Ship-to address — where goods get delivered (often same as buyer)
- Line items — what you're buying, with quantities and prices
- Subtotal, tax, and total — the financial summary
- Delivery date — when you expect the goods
- Payment terms — Net 30, Net 60, COD, etc.
That's it. Optional but useful additions: shipping method, special instructions, reference to a quote, signatures.
Step 1: Generate a PO number
Every PO needs a unique identifier. There's no official format — pick one and stick to it.
Common formats:
PO-2026-0001— year + sequentialPO-001— pure sequentialACME-2026-04-001— company prefix + year-month + sequential
The format doesn't matter. Consistency matters. If you mix PO-001, PO-2026-001, and PO-2026-04-001 across the year, you'll lose your audit trail.
Pick a format. Document it somewhere. Use it forever.
Common mistake: Restarting the sequence each month or year and ending up with multiple POs sharing the same number. Solution: keep a continuous sequence (or include the year/month in the number to avoid collisions).
Step 2: Add buyer and vendor information
The buyer block is your business. The vendor block is who you're buying from. Both should include:
- Company name
- Street address (with suite/floor if applicable)
- City, state, ZIP
- Contact person name
- Phone or email
For the vendor block, use the contact details from their most recent quote or website. Don't reuse stale info from a PO you sent six months ago — vendor contacts change.
Common mistake: Putting the buyer's contact details in the vendor block (or vice versa). Read it back before sending. The vendor block describes who you're paying. The buyer block describes who you are.
Step 3: Set the ship-to address
Often the ship-to address is the same as the buyer address. Sometimes it isn't — you might be shipping directly to a job site, a satellite office, or a customer.
If ship-to differs from buyer:
- State the ship-to address explicitly (don't just say "see notes")
- Include a contact person at the ship-to location
- Include any access instructions (loading dock, hours, security check-in)
Common mistake: Buyer office accepts a shipment that should have gone to the warehouse. Truck arrives at the front door of an office tower with two pallets of drywall. Solution: be explicit about ship-to even when it seems obvious.
Step 4: List the line items
Each line item should have:
- Description — clear enough that the vendor can identify the exact item (model number, SKU, part number)
- Quantity — how many units
- Unit price — cost per unit
- Line total — quantity × unit price
Avoid vague descriptions. "Office chair" is useless. "Herman Miller Aeron, Size B, graphite frame, basic posture support" is precise.
If you got a quote, copy line items verbatim from the quote. If the vendor uses SKUs, use the SKUs. If they use part numbers, use the part numbers. Anything that lets the vendor pick the exact item without ambiguity.
Common mistake: Combining multiple items into one vague line. "Office furniture — $5,000" gives you nothing to push back on if the vendor delivers cheap chairs and bills the full amount.
Step 5: Add the financial summary
After the line items, sum up the order:
- Subtotal — sum of all line totals
- Tax — calculated on the taxable portion (depends on jurisdiction)
- Shipping — if quoted separately
- Total — what you'll actually pay
For B2B purchases, sales tax handling depends on your state and the vendor's nexus. If you have a resale certificate or tax exemption, attach or reference it.
Common mistake: Math errors. Manual calculation in a Word document. The line items add up to $4,873.50; the subtotal says $4,837.50; the total is anyone's guess. Solution: use a tool or template that calculates automatically.
Step 6: Specify delivery date and terms
State explicitly when you expect delivery and what the payment terms are.
Delivery date: A specific date, not "ASAP" or "as soon as possible." If timing is flexible, say "no later than [date]." If exact timing matters, say "between [date] and [date]."
Payment terms:
- Net 30 — payment due 30 days after invoice
- Net 60 — 60 days
- 2/10 Net 30 — 2% discount if paid within 10 days, otherwise full amount due in 30
- COD — cash on delivery (rare in B2B; common for new vendors)
- Prepaid — paid before shipment
If the vendor's quote specifies terms, use those. Don't try to impose Net 60 on a vendor who quoted Net 30 — that's a renegotiation, not a PO.
Common mistake: Leaving payment terms blank. Vendor invoices "due on receipt." You assume Net 30. Disagreement six weeks later when they're calling for payment and you're asking for an extension.
Step 7: Reference any prior documents
If the PO is responding to a quote, contract, or RFP, reference it:
- "Per Quote Q-2026-0042 dated April 1, 2026"
- "Per Master Service Agreement dated January 15, 2025"
- "Per contractor proposal #BB-1234"
This anchors the PO to the prior negotiation. If the vendor invoices for something different than the quote, you have grounds to push back.
Step 8: Add signatures (or skip them, depending on your context)
Not all POs need signatures. In many businesses, the PO is sent as an email attachment without any signature; the act of issuing it from an authorized email address is the authorization.
For larger purchases or more formal vendor relationships, signatures help. The PO has a signature line for an authorized buyer. Some workflows also include a vendor signature block returned with acknowledgment.
Common mistake: Adding a signature line that nobody actually signs. If you're not going to sign POs, remove the line — it just looks unprofessional empty.
Step 9: Save, send, track
Once the PO is finalized:
- Save as a PDF (not editable Word/Excel — too easy to alter)
- Send to the vendor by email, with the PO number in the subject line
- Track the PO status in whatever system you use (sheet, accounting software, dedicated tracker)
- Confirm the vendor acknowledges receipt and accepts the PO
The acknowledgment step matters. A PO sent into the void doesn't bind the vendor. A PO confirmed by reply email does.
Full example: Acme Construction PO
Here's a complete PO using all the fields above:
PURCHASE ORDER
PO Number: PO-2026-0142 Date: April 10, 2026
Buyer: Acme Construction LLC 123 Builder Lane Springfield, IL 62701 Contact: Sarah Chen, sarah@acmeconstruction.com, (555) 123-4567
Vendor: Beta Building Supply Inc 456 Industry Park Springfield, IL 62702 Contact: Mike Rodriguez, mike@betasupply.com, (555) 987-6543
Ship to: Acme Construction Job Site 789 Project Avenue Springfield, IL 62703 Site contact: Tom Williams, (555) 246-8101 Delivery hours: 7 AM – 3 PM weekdays
Items:
| Description | Qty | Unit Price | Total | |---|---|---|---| | Drywall, 5/8" x 4' x 8' Type X | 50 | $14.50 | $725.00 |
Subtotal: $725.00 Tax (7.5%): $54.38 Shipping: Included Total: $779.38
Delivery date: April 17, 2026 (no later than) Payment terms: Net 30 Reference: Per Quote Q-2026-0089 dated April 5, 2026
Authorized by: Sarah Chen, Operations Manager [Signature line]
This is the kind of PO that prevents disputes. Every field is filled. The reference to the quote anchors the price. The ship-to and contact at the job site prevent delivery confusion.
How long should this take?
If you're writing it from scratch in Word, 15 minutes minimum (counting math, formatting, double-checking).
If you're using a template, 5 minutes.
If you're using a free PO generator, 90 seconds. You enter the buyer/vendor details, line items, and dates. The PDF generates with consistent formatting and accurate math.
For occasional POs, the template approach is fine. For more than a few POs a month, a generator pays for itself in saved time and reduced math errors.
Common mistakes to avoid
Reusing old POs. Copying yesterday's PO and editing the fields seems efficient until you forget to update the vendor name, ship-to address, or PO number. Half the time you'll catch it; the other half you'll send a PO to the wrong vendor with the wrong items at the wrong address.
Skipping the PO number sequence. If you handle PO numbers manually, two people can issue POs with the same number. The fix is centralized PO number management — even just a sheet that tracks the next number to use.
Math errors. A $50 error in the subtotal compounds when AP pays the wrong amount and the vendor sends a debit memo. Use a tool that calculates automatically.
Vague descriptions. "Construction supplies" tells the vendor nothing and tells your AP team nothing. Be specific.
No payment terms. Defaults to whatever the vendor invoices. You lose negotiating ground.
No delivery date. "When you can" becomes "in three weeks" because there was no deadline. Always specify.
No PO acknowledgment. PO sent ≠ PO accepted. Get confirmation.
Templates and tools
If you want to issue POs without building from scratch:
- Free PO generator — fastest path to a clean PDF
- PO template hub — Word, Excel, PDF formats; profession-specific variants
- Blank purchase order — minimal template if you want to fill it in by hand
- Purchase order maker — same generator, alternate landing
- Purchase order software — for teams with higher PO volume
If you need to send the PO to a vendor who pushes back ("just send me an invoice, I don't need a PO"), see purchase order vs invoice vs sales order for context on why POs matter.
The bottom line
A purchase order is 9 fields and a line-item list. Get the fields right, keep the formatting consistent, and you've eliminated 90% of the disputes that come up around vendor invoices.
The main things that go wrong:
- Inconsistent PO numbers
- Vague item descriptions
- Missing payment terms
- No delivery date
- Math errors
- No vendor acknowledgment
Fix those, and you have a professional PO process that scales from 1 PO a month to 100. Whether you write them in Word or use a free generator is a tooling choice — the discipline matters more than the tool.