How to Create a Purchase Order (Step by Step)

Your supplier just emailed back "which SKUs and what terms?" because the PO you sent was missing half its fields. Now the order is a conversation, the lead-time clock hasn't even started, and the stock you needed in three weeks is arriving in five. A clean PO prevents all of it.

To create a purchase order, fill a template with your details, the supplier, each SKU with quantity and agreed price, delivery date, and payment terms. Then assign a unique PO number, get it approved, and send it. A complete PO gives the supplier everything needed to fulfill the order without back-and-forth.

Key takeaways

• An incomplete PO isn't an order, it's a question: missing fields turn your order into an email thread while the lead-time clock stands still.
• Seven fields make it enforceable: PO number, buyer, supplier, SKU lines with prices, ship-to, delivery date, payment terms.
• The quantity is decided upstream: it comes off the reorder plan and the forecast, never copied from last time.
• Silence is not confirmation: a sent PO needs the supplier's acknowledgement of items, price, and date, chased on a 48-to-72-hour clock.

What fields go on a purchase order?

A usable PO needs seven things: a unique PO number, your company details, the supplier's details, SKU lines with quantities and unit prices, the ship-to address, the required delivery date, and payment terms. Miss any one of them and you've sent the supplier a question, not an order.

• PO number. example: PO-2026-0341; why it matters: The reference every later document (confirmation, delivery, invoice) hangs off
• Buyer details. example: Your legal name, billing address, contact; why it matters: Who's ordering and who to invoice
• Supplier details. example: Vendor legal name, contact; why it matters: Who's fulfilling; matters when a vendor has multiple entities
• SKU lines. example: SKU, description, quantity, unit price; why it matters: The order itself; price stated so the invoice can be checked against it
• Ship-to address. example: Warehouse or 3PL address; why it matters: Wrong or missing ship-to is the classic mis-delivery
• Delivery date. example: Required-by date, not "ASAP"; why it matters: Starts the lead-time clock and makes lateness measurable
• Payment terms. example: e.g. 30% deposit, balance net 30; why it matters: Prevents the after-the-fact terms negotiation

The fields people forget

Three omissions cause most of the back-and-forth:

• Unit price: leave it off and you've agreed to whatever the invoice says. The PO price is what three-way matching checks against later.
• A required-by date: "as soon as possible" is not a date, can't be chased, and makes lateness unmeasurable. Name the day.
• Currency and shipping terms: who pays freight, and where ownership transfers, ideally as a named Incoterm for imports. Small print until a shipment goes missing, then suddenly the whole conversation.

How do you fill in supplier, quantity, and terms?

Pull each from its source of truth instead of memory. Supplier details come from your vendor record, matched to the entity you actually contract with. Quantities come from your reorder plan, not a round number that feels right; the trigger and order-quantity math live in the reorder point formula and economic order quantity, so the PO just carries the plan's answer. Prices and terms come from your agreed rate card or the supplier's quote, stated explicitly so the invoice has something to be checked against.

Getting the quantity right

The quantity on the PO is the last step of a decision made upstream: how much cover you want given velocity, lead time, and what's already inbound. Copying last month's quantity is how a slowing SKU gets overstocked and a surging one runs dry. This is also where drafting from a system beats drafting from a blank template: Conative AI turns the demand forecast into the suggested line quantities on the draft PO, so what lands in the template already reflects this month's velocity, and a quantity that would have taken an afternoon of spreadsheet math is worked out for you in minutes. See how draft POs come off your own forecast: book a call.

What are the steps to create and send a PO?

Five steps, in order: assign the number, fill the template, route for approval, send it through one channel, and log it as open. The sequence matters less than the discipline that every PO takes the same path, because the same path is what makes orders trackable later.

• Assign a unique PO number from one running sequence. Never reuse numbers, even for a reissued order.
• Fill every field in the template above. If a field genuinely doesn't apply, mark it so the supplier knows it wasn't forgotten.
• Route for approval per your workflow rules. An unapproved PO is a draft, not an order.
• Send through your one agreed channel, whether that's your platform, a portal, or a dedicated email address. Orders sent from personal inboxes are the ones nobody can find in receiving week.
• Log it as open with its required-by date, so the weekly review chases what's unconfirmed or late.

Confirmation and follow-up

A sent PO isn't a done PO until the supplier confirms items, prices, and the delivery date. Silence is not confirmation. Set a chase clock (48 to 72 hours is typical), and treat any change the supplier confirms back (a substituted item, a pushed date) as a PO revision you record, not a verbal footnote. The wider system that tracks the order from here to invoice match is purchase order management.

Frequently asked questions

What does a purchase order template look like?

A single page with a header (your details, supplier details, PO number, date), a line-item table (SKU, description, quantity, unit price, line total), and a footer (ship-to address, required delivery date, payment terms, authorized signature). Any format works, spreadsheet included, as long as every field is present and the PO number is unique.

What payment terms should a PO include?

State when payment happens and against what: for example, 30% deposit on order and the balance at net 30 from delivery, or simply net 30 against invoice. Include the currency, and note who pays freight. The right terms are whatever you negotiated; the PO's job is recording them so the invoice can be checked against something written.

What's a PO number and how do you assign one?

A PO number is the unique identifier every later document refers back to: the supplier's confirmation, the delivery paperwork, and the invoice. Assign it from one sequential register (a prefix plus a running count, like PO-2026-0341, works fine). What matters is uniqueness and one sequence for the whole company, not the numbering scheme.

Do you need a PO for every order?

For anything that affects inventory or meaningful spend, yes: the PO is what makes the order trackable and the invoice checkable. Many brands skip POs for small operational purchases below a set value, which is a reasonable line to draw. Skipping them for stock buys is how phantom inbound inventory and surprise invoices happen.

What's the difference between a PO and a purchase requisition?

A requisition is the internal ask: someone requests that a purchase be made, and it goes through approval. The purchase order is the external document that actually places the approved order with the supplier. Small teams often collapse the two into one step; the distinction starts mattering once approval and ordering are done by different people.

How do you cancel or amend a sent PO?

In writing, referencing the PO number, before the supplier ships. Issue a revised PO (or a cancellation notice) rather than relying on a phone call, and get written acknowledgement of the change. Check your terms for cancellation windows on made-to-order goods. Update the PO's status in your register so receiving isn't expecting a shipment that was cancelled.