A small order can create a surprisingly long trail of messages. One person asks for supplies, another confirms the price, and someone else receives two boxes a week later. When the invoice arrives, the team has to reconstruct what was requested and whether the delivery is complete.
A clear purchase order gives that work a common reference. It identifies the buyer and vendor, lists the requested items and quantities, records delivery details, and provides a number people can use when discussing the order. A simple receipt log then tracks what actually arrives.
The template in this guide is an operational starting point for small teams. The example uses a fictional workshop buying packaging supplies. Adapt it to your organization’s approval process, accounting practices, and agreed commercial terms rather than assuming one template fits every purchase.
Decide which step the document represents
Before filling in a template, identify the document’s role. Are you requesting internal approval, preparing an order for a vendor, or recording an order already sent? Those stages should remain distinguishable. A working draft can contain unresolved details; a document being sent should clearly state the information the vendor is expected to act on.
Keep the status visible. A small team might use draft, approved internally, sent, vendor response received, partially received, received, and closed. These are example workflow labels. Choose the states your team can maintain reliably, and explain what must be true before an order moves to the next one.
Also identify who can authorize the purchase. The person preparing the document may not be the person approving it. Record the approval through your existing business process before sending an order that commits the organization. A well-formatted PDF does not resolve unclear authority.
Use a header people can identify later
The header should make the order easy to recognize without opening several attachments. Include a unique order number, the issue date, the buyer’s business name and contact details, and the vendor’s name and contact information.
Use one dependable numbering method. For example, a fictional business could use PO-2026-0042 for its forty-second order in a yearly sequence. The exact format matters less than uniqueness and consistency. Do not assign the same number to different orders, and do not let an edited draft quietly replace a previously sent document without a version record.
Include a project or department reference when it changes how the order will be handled. “Workshop packaging replenishment” may be sufficient for a small team. Avoid putting information in the header merely because a large enterprise template contains a field for it.
Confirm the vendor details from the source your business normally trusts. A copied address from an old email can send a delivery question to the wrong place. If the vendor has provided a quote reference, record it so the order can be connected to the pricing discussion.
Make each line item understandable on its own
A useful line item contains a description, an item or catalog reference when available, the quantity, the unit, the unit price, and the line total. The description should be specific enough that the person preparing the shipment and the person receiving it can identify the intended item.
Units deserve particular attention. Ten boxes, ten packs, and ten individual pieces can represent very different quantities. If a pack contains several pieces, record the pack size where it matters. A unit price is only meaningful when the unit is clear.
For a customized item, connect the line to the agreed specification or approved reference. “Printed labels” may leave the size, material, and artwork version unclear. A concise description plus a stable specification reference is usually more useful than placing an entire technical discussion into one crowded cell.
Separate alternatives. If two products are possible but no one has selected one, mark that decision as unresolved in the draft. Listing both without explanation may lead the vendor to assume that both are being ordered.
A compact purchase order template
You can reproduce the following structure in a document or spreadsheet. Keep the header, item table, delivery instructions, and approval information readable together. Supporting specifications can remain separate if the order clearly identifies them.
| Field | What to record |
|---|---|
| Order number and status | Unique reference and current workflow stage |
| Buyer and vendor | Business names and appropriate contact details |
| Issue date | Date the document is issued |
| Quote or project reference | The relevant source for the request |
| Line items | Description, quantity, unit, unit price, total |
| Adjustments | Clearly identified discounts or agreed charges |
| Currency and total | The currency used and the calculated amount |
| Delivery | Destination, requested date, contact, constraints |
| Terms and approval | Agreed references and the internal approval record |
Use plain labels rather than abbreviations that a recipient may misunderstand. If your business uses an internal project code, add a short description when the vendor needs to understand its purpose. The document should help the next person act correctly.
Work through a fictional order
Imagine a workshop preparing an order for packaging supplies. It needs ten packs of mailing boxes and four rolls of label stock. The numbers below are invented solely to demonstrate the template and arithmetic; they are not vendor prices or purchasing recommendations.
| Item | Quantity | Unit | Unit price | Line total |
|---|---|---|---|---|
| Mailing boxes, agreed size | 10 | Pack of 20 | USD 18.00 | USD 180.00 |
| Label stock, agreed format | 4 | Roll | USD 12.50 | USD 50.00 |
The item subtotal is USD 230.00. If the parties have agreed on a USD 15.00 delivery charge, the illustrated total before any other applicable amounts is USD 245.00. This example does not calculate taxes or determine whether they apply. Record those amounts using your business’s established treatment and the relevant verified information.
The delivery section names the workshop location, the receiving contact, and the requested delivery date. A note identifies the source quote. An internal approval reference connects the order to the person who authorized it. The result is short enough to scan while retaining the information needed to discuss the purchase.
Check calculations and commercial details separately
A document can have correct arithmetic and still describe the wrong order. Review quantities, units, descriptions, and delivery details before checking the total. Then compare the calculation with the agreed pricing source.
Show adjustments where the reader can understand them. If a discount applies to a particular line, connect it to that line. If a charge applies to the whole order, identify it separately. Hidden adjustments make it harder to explain why the total differs from a straightforward quantity-times-price calculation.
Keep currency explicit. A symbol alone can be ambiguous when businesses operate across countries. Also use consistent decimal precision and a calculation method that handles currency amounts predictably. If you use a spreadsheet, protect formula cells from accidental editing and inspect the final exported document as well as the worksheet.
Review commercial terms through the appropriate business process. The purpose of the template is to organize information clearly. It should not lead you to invent payment conditions, delivery obligations, or other terms that have not been agreed.
Review the final PDF before sending
A draft that looks clear on a wide monitor may become difficult to read when exported. Preview the page size you intend to send. Check that the item descriptions fit, the totals are visible, and the order number appears where it can be found quickly.
Inspect page breaks if the order has several lines. A long description should not become detached from its quantity or price. Repeated column headings can help the reader understand a continuation page. Avoid shrinking the entire document until the text becomes impractically small.
Check attachments and referenced specifications too. If the order refers to an approved artwork version or a quote, confirm that the intended recipient can identify or access it. Sending the wrong reference can create confusion even when the main document is accurate.
Preserve the version you actually send. Keep its issue date, order number, and relevant approval evidence together. If the document changes afterward, use a clear revision process rather than silently editing the saved copy that represents the earlier communication.
Track partial deliveries without losing the original request
Once the order is sent, the next useful record is what arrives. Record receipts separately from the ordered quantities. The original request and the delivery history answer different questions and should remain distinguishable.
In the fictional example, six packs of boxes arrive first, followed by the remaining four packs and the label rolls. After the first receipt, the log shows ten packs ordered, six packs received, and four packs still outstanding. The order remains partially received rather than being treated as complete because a parcel arrived.
Record the receipt date and the person checking the delivery. If an item is missing, damaged, or different from the requested specification, describe the discrepancy and the next action. Do not force an uncertain delivery into a completed state merely to clear a task list.
Keep the unit consistent with the order. If the original line uses packs of twenty, a receipt recorded as individual pieces needs an explicit conversion. Clear units prevent a delivery of six packs from being misread as six individual boxes.
Connect the order, receipt, and invoice references
When the vendor’s invoice arrives, use the order number and receipt history to connect the records. Your team’s accounting process determines how invoices are reviewed and approved. The operational record should make it easy to find what was requested and what was received.
If the invoice differs from the expected amount, identify the difference before assuming it is an error. A shipment charge, an agreed change, or a partial delivery may explain it. Record the question and the person responsible for resolving it rather than overwriting the original numbers to make the records appear consistent.
Keep the relevant documents together by reference. You may choose a shared folder, a purchasing system, or an app that supports exports. The important retrieval test is simple: can another authorized team member move from the invoice reference to the order and its receipt history without reconstructing an email conversation?
Do not use this filing method as a substitute for your organization’s record-retention requirements. Decide where the authoritative records belong and how they are backed up through the business’s existing policy.
Choose a tool around the order lifecycle
A document template is often enough for occasional simple orders. A spreadsheet can help with repeated calculations, provided someone maintains its formulas, numbering, and saved versions. As order volume or handoffs grow, consider whether your current tool can keep the request and receipt stages connected.
Vendraft is a focused option for this workflow. Its first-party product information describes preparing purchase orders, dependable numbering, PDF previews and exports, preserved sent-document snapshots, and receipt-status tracking. It describes offline use on iPhone and iPad. Check the current product page and App Store listing for compatibility and availability.
Evaluate any tool with a realistic example that includes a partial delivery and a corrected draft. You should be able to identify the original request, the version sent, and the remaining quantities without guessing. Those ordinary exceptions reveal more about the workflow than a perfectly completed demonstration order.
Put the template to work on your next order
Start by defining the numbering method and the approval step. Fill in one real draft, check every unit, and preview the document you intend to send. Ask the person who receives deliveries whether the descriptions and quantities will be clear when the boxes arrive.
After the order is completed, review any questions the vendor or receiving team had to ask. Add a field only when it would have prevented a meaningful problem. Remove fields that no one uses. The aim is a dependable shared reference that makes the next action easier throughout the order’s lifecycle.
Product reference: Vendraft’s first-party product page. The workshop, quantities, prices, and order history are fictional examples created for this guide.