What Is a Purchase Order? Definition and Required Fields

Purchase order definition

A purchase order (PO) is the document a buyer sends a seller to order goods or services. It states what is being bought, in what quantity, at what price, where and when it should be delivered, and on what payment terms. The buyer issues it, which is what separates it from a quote (issued by the seller before the sale) and from a sales order (the record the seller creates internally once the PO is accepted).

Every PO carries a number assigned by the buyer. That number is the thread that ties the rest of the transaction together: the seller quotes it on the order acknowledgment, the packing slip and the invoice, and the buyer's accounts payable team uses it to match what was ordered, what was received and what is being billed.

Companies use purchase orders for control as much as for communication. A PO commits budget before money is spent, records who approved the purchase, and gives both sides a written reference if a delivery or an invoice does not match what was agreed.

When a purchase order becomes a binding contract

A purchase order on its own is usually an offer to buy. It becomes a contract when the seller accepts it. In the United States, sales of goods are governed by Article 2 of the Uniform Commercial Code, adopted by the states. Under UCC 2-206, an order for prompt or current shipment invites acceptance either by a prompt promise to ship or by the shipment itself, so a seller who simply ships the goods has accepted the order.

Acceptance does not always come on the buyer's terms. Sellers often reply with an order acknowledgment carrying their own conditions of sale. UCC 2-207, the rule behind what lawyers call the battle of the forms, treats such a reply as an acceptance even when it adds or changes terms, unless the acceptance is expressly conditional on those terms. Between merchants, the added terms become part of the contract unless the offer limited acceptance to its own terms, the new terms materially alter it, or the buyer objects in time.

Writing matters above a threshold. Under UCC 2-201, a contract for the sale of goods for $500 or more is not enforceable unless there is a writing signed by the party against whom enforcement is sought, and between merchants a written confirmation that goes unanswered for 10 days can satisfy that requirement. A signed PO and a written acknowledgment are the simplest way to meet it. State law varies in the details, so a disputed order is a question for counsel, not for this article.

What a purchase order should include

No statute lists the fields a commercial purchase order must contain. What makes a PO usable is that the seller can fulfill it without calling the buyer, and that both sides can check the delivery and the invoice against it later.

Identification comes first: the buyer's and the seller's legal names and addresses, the PO number, the date of issue and a contact on the buying side. Then the lines, which are the heart of the document: the buyer's item number and the supplier's item number where they differ, a description precise enough to pick the right product, the quantity, the unit of measure, the unit price, any discount, and the extended amount for each line.

Then the execution terms: the requested delivery date, the ship-to address, the shipping terms (an Incoterms rule for international orders), the payment terms such as Net 30, applicable taxes, the order total, and a reference to the terms and conditions that govern the purchase. Last comes the approval: the name or signature of the person authorized to commit the spend.

Purchase order vs quote, sales order and invoice

The quote comes from the seller and proposes a price. The purchase order comes from the buyer and commits to buy, usually on the quoted terms. The sales order is the seller's internal copy of the order, keyed into its own ERP with its own item numbers, and it drives picking, production and shipping.

The packing slip or delivery note travels with the goods and shows what was actually shipped. The invoice comes last and requests payment. On the buyer's side, accounts payable runs a three-way match between the PO, the receiving record and the invoice before paying: a price that differs from the PO, or a quantity billed but never received, stops the payment until someone resolves it.

That is why the PO stays the reference from start to finish. An error made when the order is first read, a wrong unit or a wrong price, does not disappear. It resurfaces at the three-way match weeks later, as a disputed invoice or a short payment.

What happens after the purchase order is sent

On the seller's side, purchase orders rarely arrive in a clean format. Manufacturers and distributors receive them as PDF attachments, in the body of an email, through EDI, from supplier portals, sometimes as a scan or a photo. Each customer uses its own layout, its own item numbers and its own way of writing units and discounts.

Before anything ships, someone has to turn that document into a sales order in the ERP. That means finding the customer, translating each of the customer's item numbers into an internal SKU, converting units (a case of 12 ordered as 1, or as 12), checking prices against the quote or the contract price list, and entering delivery dates and ship-to addresses. This is the step where order entry errors are born, and the root causes of order entry errors tend to repeat from one company to the next.

Done by hand, the work is slow in proportion to the variety of formats rather than to the number of orders, and it concentrates risk on the lines that differ from what the ERP expects. It is also invisible until it goes wrong: nobody measures the time spent re-keying a clean PO, but everyone sees the credit note that follows a wrong one.

Processing purchase orders with an AI agent

Template-based OCR extracts text from a known layout and breaks when a customer changes its form. The choice between OCR, AI extraction and agents comes down to what happens after the text is read: an agent does not stop at extraction, it carries the order through to the ERP.

In practice, the agent reads the PO in whatever format it arrived, identifies the customer, maps each customer item number to the internal SKU using the cross-reference and the catalog already in the ERP, normalizes units, and checks quantities and prices against the price list or the quote. When every line is consistent, it creates the sales order. When a line is ambiguous, an unknown item number or a price outside the agreed one, it hands that line to a person with the reason instead of guessing.

Every decision is logged, which gives the order desk something it rarely has with manual entry: a record of why each line was accepted, corrected or escalated. That record is what makes the next dispute with a customer short.

Implementation: automate without replacing the ERP

Automating purchase order processing does not require a new ERP. Mirage deploys agents on top of the ERP already in place, whether SAP, Microsoft Dynamics, Sage or a specialized system, through its API or its user interface, with engineers working inside the customer's environment to connect them.

The first step is measurement: how many POs arrive each week, in how many formats, which fields cause corrections, and what re-keying and errors actually cost. The cost of manual order entry is the baseline every later result is compared with, and it varies too much between companies for a generic figure to mean anything.

The return then comes from three places: order desk time moved from typing to the exceptions that need judgment, fewer invoice disputes and credit notes, and orders entered the day they arrive. It grows when the same agents take on the next documents in the chain, order acknowledgments, delivery notes and supplier invoices.