Purchase Order Document Template: Fields and How to Use It

A purchase order document template is a reusable form for listing what a buyer intends to purchase, from whom, in what quantity, and under which delivery and payment terms. Use the blank template below to prepare a clear order, then send it to the supplier and keep a copy with the related approval and invoice records.

What a Purchase Order Does

A purchase order, often shortened to PO, is a document a buyer creates to request goods or services from a supplier. It gives both sides a written reference for the requested items, quantities, prices, delivery details, and other agreed information. Organizations commonly use POs to authorize spending internally and to make orders easier to track.

A PO is not the same thing as proof that goods were delivered or that a bill was paid. It records the order; a receiving record can document what arrived, and an invoice requests payment. Depending on the circumstances and applicable terms, a PO and a supplier’s acceptance may also have contractual significance. Its legal effect is not identical in every situation, so avoid treating a template as a substitute for reviewing the terms that apply to a particular transaction.

For a small one-time purchase, an organization may not need a formal PO. For repeat orders, larger purchases, or teams with approval rules, a consistent document can reduce confusion about what was requested and who authorized it.

When to Use a Purchase Order

A PO is useful when a buyer needs a documented request before a supplier ships goods or begins work. It can also help an accounts or purchasing team match the order with delivery records and the supplier’s later invoice. The document is especially helpful when several people take part in requesting, approving, receiving, and paying for a purchase.

• Goods with multiple line items: A PO can spell out product descriptions, quantities, and unit prices rather than relying on a brief email.
• Repeat or scheduled orders: Separate POs can identify each order, even when the supplier, products, or prices are familiar.
• Purchases requiring approval: The document can show the requester, approver, department, and any internal reference number.
• Services with a defined scope: A PO can summarize the service, expected dates, deliverables, and price. Detailed work requirements may need a separate attachment.

Use the purchasing process your organization has established. A PO does not automatically replace a required contract, quote, statement of work, or supplier onboarding step.

Fields to Include

A useful template captures enough information to identify the order and act on it without making the form needlessly complicated. The exact fields depend on the buyer’s process and the supplier’s requirements, but most purchase orders include the following:

• PO number and date: A unique identifier and the date the order was created help people find and discuss the same transaction.
• Buyer and supplier details: Include the relevant organization names, contact names, addresses, and email or phone details. Distinguish the billing address from the delivery address when they differ.
• Item or service lines: Describe each product or service clearly. Add a supplier part number or specification when it helps prevent ambiguity.
• Quantity, unit, and price: State the quantity and unit of measure, such as each, hour, or box, along with the agreed unit price and line total.
• Delivery information: Specify the requested delivery date or service period, delivery location, and any useful instructions.
• Totals and terms: Show subtotal, applicable charges, discounts, and total, plus payment or delivery terms that the parties have agreed to use.
• Approval and notes: Provide space for the requester or authorized approver and for relevant references, such as a quote number or project code.

Use clear labels and consistent units. If a price includes or excludes a charge, say so rather than expecting the supplier to infer it. Where an item has important specifications, attach them or identify the relevant document by name and date.

Purchase Order Template

How to Prepare and Send a PO

A reliable process starts before the form reaches the supplier. Confirm what is being bought, check the requested price and timing, and follow any internal authorization rules. Then complete the PO, review its details, send it through the agreed channel, and store the final copy where colleagues can retrieve it.

1. Confirm the request. Ask the requester to define the goods or services, quantity, need-by date, delivery location, and any specifications.
2. Check the supplier information. Use the correct supplier contact and address, and confirm the quoted price and terms against the appropriate reference.
3. Assign and review the PO number. Follow a consistent numbering method so each order can be identified without confusion.
4. Obtain approval. Route the order to the people required by the organization’s purchasing policy before committing to it.
5. Send the approved order. Make clear that it is the current version and ask the supplier to confirm receipt or flag any discrepancy.
6. Track fulfillment. Record changes, deliveries, service completion, and the related invoice against the same PO number.

If a supplier cannot meet the requested date or price, update the order through a traceable process rather than leaving different versions in circulation. Keep the original and the revised document if your organization’s records process calls for both.

How to Customize the Template

The blank form is a starting point, not a rule that every organization must follow. A buyer with a small number of straightforward purchases may need only the basic identification, line-item, delivery, price, and approval fields. A larger team may add department codes, project references, budget approvals, shipping instructions, or a field for partial deliveries.

Customize the template around the decisions people actually need to make. For instance, if buyers often order products sold by the case but report quantities as individual units, add a unit-of-measure field and define it plainly. If services are ordered, use a description that states the work and period covered, and refer to a separate scope document where needed. Avoid putting sensitive details in a document that will routinely be sent outside the organization unless they are necessary.

Decide how changes are handled. A revision date or version field can help when an order changes after approval. Make clear who may approve amendments and how the supplier will be notified. If contractual obligations, tax treatment, or regulated purchasing rules raise questions for your circumstances, ask a qualified professional.

Example: Ordering the Same Supplies Clearly

Imagine a studio ordering two reams of a particular paper from a supplier. A vague request might say, “Please send paper.” That leaves questions about the product, amount, destination, price, and timing. A more useful PO names the paper or its reference number, states the quantity and unit, lists the agreed unit price, and gives the delivery address and requested date.

If the supplier’s quote lists a different product code or price from the PO, the buyer can pause and resolve the mismatch before shipment. If the delivery arrives as two boxes, the receiving record can note what was received, while the invoice can be checked against the order and receipt. This does not guarantee that every discrepancy will be prevented, but it gives the people involved a shared reference for identifying and resolving one.

Common Problems and How to Avoid Them

Many PO errors are small omissions that become time-consuming when an order is already in progress. A missing delivery address can delay shipment; an unclear unit can produce the wrong quantity; and a stale price can create an avoidable invoice dispute. A quick review before sending is often more effective than trying to reconstruct the request later.

• Unclear descriptions: Replace broad labels such as “parts” with a useful description, specification, or supplier reference.
• Mixed units: State whether the quantity means individual items, packs, hours, or another unit.
• Unmatched totals: Check that quantity multiplied by unit price agrees with each line total and that the summary is consistent.
• Missing delivery details: Identify the destination and contact for delivery, especially when it differs from the billing address.
• Unapproved orders: Confirm required approval before sending a document that could be understood as authorization to proceed.
• Untracked changes: Share revisions with the supplier and internal approvers, and make clear which version is current.

Do not use a PO number as the only description of an order. The document should be understandable on its own, while the number makes it easier to connect the order to other records.

Purchase Orders, Quotes, Invoices, and Receipts

These documents are related, but they serve different points in a purchasing transaction. A supplier quote or estimate describes proposed items, prices, or terms before the buyer places an order. A PO is created by the buyer to state what it is requesting. An invoice is generally sent by the supplier to request payment for goods or services supplied. A receipt or receiving record documents what arrived or what work was recorded as complete.

Comparing the documents can help an organization spot differences. For example, a buyer can check whether an invoice refers to the correct PO and whether its quantities and prices align with the order and receiving information. The right checking process depends on the organization and the transaction; a PO alone does not prove that a delivery occurred or that an invoice is accurate.

Filing and Internal Controls

Store the approved PO with its supporting quote, approval, delivery or service record, and invoice when appropriate. Use a consistent naming or filing method based on the PO number, supplier, or order date. Limit access to people who need the records, and follow your organization’s retention and privacy policies rather than assuming one universal retention period applies.

For organizations with multiple buyers, a consistent numbering system and a defined approval path make it easier to see which orders are authorized and where they stand. Separating request, approval, receipt, and payment responsibilities can also help create a clearer review trail. The degree of control should fit the organization’s scale and purchasing process.

Frequently Asked Questions

Can I use a purchase order template for services?
Yes. Describe the service, location or period, expected deliverables, and price. If the work needs detailed requirements, refer to a separate scope or agreement rather than squeezing every detail into the PO.

Does a purchase order guarantee that an order has been accepted?
No. A PO records the buyer’s order, but it does not by itself confirm that the supplier received or accepted it. Follow the agreed process and request confirmation when appropriate.

Is a purchase order the same as an invoice?
No. The buyer typically issues the PO to place or document an order; the supplier typically issues an invoice to request payment. The two documents can be compared during review.

Do I need a PO number?
A unique number is useful for locating and matching order records. For a one-off purchase, an organization may use a simpler reference, but follow its own purchasing and filing procedures.

Can I change a purchase order after sending it?
Often an order can be revised, but notify the supplier and any required approvers clearly. Identify the updated version and retain a record of the change so people do not rely on conflicting copies.

Related

• Inventory and Purchase Order Template: What to Include
• Internal Purchase Order Template: Fields and Approval Steps
• Internal Order Form Template: Fields, Workflow, and Use