Purchase Orders · April 16, 2026

What Is a Purchase Order? A Complete Guide for Small Businesses

A purchase order (PO) is a buyer's formal commitment to buy specified goods or services from a vendor at agreed prices. Here's what to include, when to use one, and how POs fit alongside invoices and sales orders.

A purchase order — usually shortened to "PO" — is a document a buyer sends to a vendor that says: I commit to buying these specific items, at these prices, by this date, on these terms. When the vendor accepts the PO, it becomes a binding contract.

That's the whole concept. What follows is everything around it: what fields a PO needs, when small businesses actually use one, and how POs interact with invoices and sales orders so the paperwork stays clean.

What goes on a purchase order

A complete PO has three blocks of information:

Buyer and vendor identification

  • Buyer name, address, and contact for questions
  • Vendor name and address
  • Unique PO number (the buyer's reference, used to match incoming invoices)
  • Date issued
  • Requested delivery date and ship-to address

Line items

  • Description of each item or service
  • Quantity
  • Unit price
  • Line total
  • Currency

Totals and terms

  • Subtotal, tax, shipping
  • Grand total
  • Payment terms (Net 30, Net 60, due on delivery, etc.)
  • Special instructions or terms

If you want a head start, our free PO generator renders all of this from a form and exports a clean PDF. No signup needed.

When small businesses actually use POs

The textbook answer is "always, for every purchase." The honest answer is: most small businesses don't issue POs for office supplies under $200. POs become worth the friction when at least one of these is true:

  1. You need to lock in pricing before delivery. Without a PO, the vendor's invoice price is what you owe — even if it's higher than what you discussed.
  2. You're spending real money. Anything north of a few hundred dollars deserves a paper trail. POs document exactly what was agreed.
  3. You need internal approval. POs are the natural place to gate spend. "Approved POs only" is a simple AP control that works.
  4. You're a contractor ordering materials. A PO to your supplier creates the paper trail you need to bill the client back accurately.
  5. You're working with a new vendor. A PO formalizes the deal and removes ambiguity. If something goes wrong, the PO is the source of truth.

If none of these apply, a clean invoice from the vendor is enough.

Purchase order vs invoice vs sales order

This is where people get confused, so let's be specific:

| Document | Who creates it | When | Purpose | |---|---|---|---| | Purchase order | Buyer | Before fulfillment | Commit to a purchase | | Sales order | Seller | After receiving the PO | Confirm the order internally; trigger fulfillment | | Invoice | Seller | After fulfillment | Request payment |

The flow on a typical B2B transaction:

  1. Buyer sends purchase order to vendor: "Here's what I want to buy."
  2. Vendor creates a sales order internally: "OK, I'm filling this order. Here's the picking list."
  3. Vendor delivers the goods or services.
  4. Vendor sends invoice to buyer: "Pay me for what I delivered."
  5. Buyer matches the invoice against the original PO. If they line up, AP pays.

That last step — PO matching — is the entire reason POs exist. It catches pricing errors, quantity mismatches, and unauthorized purchases before money goes out the door.

If you're on the seller side and need the SO half of this picture, see our sales order template hub.

How to write a good PO

A few patterns that separate well-run procurement from chaos:

Number your POs sequentially. PO-2026-0001, PO-2026-0002, etc. Don't reset every month. Sequential numbers make missing POs obvious.

Reference the quote. If the vendor sent a quote, reference its number on the PO. This eliminates "which price did we agree to?" disputes.

Be specific in line items. "Office chairs" is too vague. "Herman Miller Aeron, size B, graphite frame, polished aluminum base — 3 ea." removes ambiguity.

State payment terms in writing. Net 30 is a default in many industries, but say it on the PO. Surprises later cost more than clarity now.

Include shipping terms. Who pays freight? Where does title transfer? FOB Origin vs FOB Destination matters when something gets damaged in transit.

When the invoice doesn't match the PO

This happens. The vendor invoices for a higher quantity, a different price, or includes a "fuel surcharge" you never agreed to. Your options:

  1. Short-pay the invoice to the PO amount. Pay what you agreed to and let the vendor explain the difference. Most reputable vendors accept this.
  2. Hold the invoice until the discrepancy is resolved. Slows their cash flow, motivates a quick fix.
  3. Issue a PO change order if you actually agreed to the change. This documents the new terms so AP can pay cleanly.

The reason POs work is that they give you grounds to push back without it being personal. The PO is the agreement. Anything different is a renegotiation.

Do you need procurement software?

For a small business doing under 50 POs/month: no. A consistent PO template, sequential numbering, and a folder of signed PDFs covers it.

When you might want software:

  • More than ~100 POs/month
  • Multiple approvers in your AP chain
  • Three-way matching (PO + receiving doc + invoice) requirements
  • Integration with QuickBooks or your ERP

For everyone else, our free PO software (no signup, no per-user fees) handles creating, saving, and downloading POs without the cost.

Templates and tools

The bottom line

A purchase order is a paper trail that protects you when money is on the line. For small businesses, it's worth the friction whenever the spend is meaningful, the vendor is new, or your internal AP process needs a gate.

Use a template, number your POs sequentially, and match every incoming invoice against the PO before paying. That's 90% of what enterprise procurement systems do, executed in 30 seconds with a free tool.

← Back to all posts