Purchase order email to supplier: what it needs to avoid disputes

A purchase order email that prevents disputes contains nine things: a PO number, your supplier's product codes, quantities, the agreed unit price, a required-by date, the delivery address, payment terms, shipping terms, and an explicit request to confirm. Most dispute-causing emails are missing at least three of them — usually the price and the required-by date, which are precisely the two fields suppliers argue about later. Below is the exact checklist, two copy-paste templates, and the confirmation habit that quietly improves every other number in your inventory operation.

Why email POs go wrong

Verbal and informal ordering works until it doesn't. "Can you send 200 more of the mugs, same as last time?" fails in four predictable ways:

• "Same as last time" is ambiguous. Same price? Last quarter's price, before their increase? The SKU the supplier changed the code for in March?
• No required-by date means no commitment. If you never said when you need it, "late" doesn't exist. Their lead time becomes whatever it becomes.
• No PO number means no shared reference. Every later conversation about this order starts from scratch: "you know, the big one, the mugs."
• No confirmation request means no proof. If they never acknowledged the terms, your screenshot of the sent email is just your opinion with a timestamp.

Shopify's native purchase orders (Help Center, accessed October 2026) give you the structure — PO numbers, line items, quantities, expected dates — and can help you draft and send; the email is where the shared, quotable record gets created. The PO document and the email are not competitors: the email transmits the PO and captures the confirmation. (The mechanics of creating, receiving, and closing POs natively are covered in Shopify purchase orders.)

The nine-item checklist

Before you hit send, verify every line exists:

1. PO number — sequential and unique (PO-2026-114 style). Use the same number Shopify generated if you issued the PO natively, so your records and theirs match.
2. Supplier product codes — their codes, not just yours. Your SKU means nothing at their warehouse; their code is what they'll pick against.
3. Quantities per line item — units, and the unit of measure if it's ever ambiguous (200 units, not "200").
4. Agreed unit price per line — even when it's unchanged. If you don't restate it, their invoice will restate it for you.
5. Currency — mandatory on cross-border orders, where a number without a currency is a 10% dispute.
6. Delivery address — full and specific, including the 3PL's receiving hours if relevant.
7. Required-by date — a date, not "ASAP." ASAP means whenever they get to it. If your lead time measurement runs order-date-to-sellable-date, the required-by date is where you encode what "on time" means.
8. Payment terms — deposit split, balance due date, method. Restate even long-standing terms; suppliers change their own policies without telling small buyers.
9. Confirmation request — "Please reply confirming price, quantity, and delivery date, or flag any line you cannot meet." This line is the whole ballgame.

Template 1: new PO

Subject: PO-2026-114 — Cedar & Salt — 3 SKUs, required by Nov 14

Hi Marta,

Please find our purchase order below.

PO number: PO-2026-114
Delivery address: Cedar & Salt, 418 Fraser Ave, Vancouver BC, V5X 1B2
Required by: Friday, November 14, 2026
Payment terms: 30% deposit on confirmation, balance net 30 from delivery
Shipping: FOB our dock, freight prepaid by us (account: FedEx 7721)

Line items:
| Supplier code | Description           | Qty  | Unit price (USD) |
|---------------|-----------------------|------|------------------|
| MUG-11OZ-WHT  | 11oz mug, white       | 400  | 2.85             |
| MUG-11OZ-NVY  | 11oz mug, navy        | 200  | 2.95             |
| LID-SIL-11OZ  | Lid, silicone, 11oz   | 600  | 0.62             |

Order total: 1,200 units / $3,048.00

Please reply confirming this PO — price, quantity, and the delivery
date you can commit to — or flag any line you can't meet and we'll
adjust. If any line will ship partial, tell us now, not at the dock.

Thanks,
Dana
Cedar & Salt

Notice what the last sentence does: it makes partial shipments a disclosure obligation before the fact. That single line converts your most common receiving surprise into something you planned around.

Template 2: chasing a late delivery

Keep it factual and give one clean ask. Escalation lives in the paper trail, not in the tone.

Subject: PO-2026-114 — required-by date Nov 14 is now at risk

Hi Marta,

PO-2026-114 (1,200 units, 3 SKUs) was confirmed on Oct 6 with a
required-by date of Nov 14. As of today, Nov 17, we haven't received
a ship notice or tracking number.

Can you reply today with:
1. The current ship date, and
2. Whether the full 1,200 units will ship together.

If the date has moved, we need the new date in writing so we can plan
our stock cover. If it helps resolve this faster, I'm happy to jump
on a call this week.

Thanks,
Dana

Two details worth stealing: the subject line names the PO and the risk, so it gets opened; and "in writing" is stated politely but plainly. If this is the third chase for the same PO, the email thread is now the evidence you'll use in your next supplier scorecard review — and, if it comes to it, in the conversation about whether they keep your volume.

The confirmation reply is your data, not just your receipt

Merchants file the confirmation email and forget it. It's actually two datasets in disguise:

• It's your lead-time record. The date they confirmed plus the date they committed to, stamped against the date the goods were actually sellable, is one row in your real lead time history. Six confirmed POs and you have a measured average and p80 instead of a marketing number. Stores that skip this are the ones "guessing when to reorder" — and reordering against a quote no one ever validated.
• It's your price record. The confirmed unit price is what you compare the invoice against, line by line. Invoices drift; the confirmation email is the anchor you dispute from. When you sit down to renegotiate with suppliers, your confirmed-price history is the factual spine of the conversation.

The discipline tip: log the confirmation date

Add one column to your PO tracking sheet: date confirmed, plus promised date as they wrote it (not as you wished it). That's the entire habit. Two columns, entered when the reply lands, and you get, for free:

• A follow-up trigger: no confirmation within 2 business days → chase on day 3, not week 3.
• An honest promised-date field for the on-time % and p80 math in the supplier scorecard method.
• A dispute anchor: "you confirmed Nov 14 on Oct 6" beats "but you said it'd be fast" in every possible argument.

If you issue POs natively in Shopify, keep the sheet anyway as of October 2026 — the admin records order and expected dates, but the confirmation event (their reply, their wording, their committed date) lives in your inbox, and nothing in the admin reads your inbox. One minute per PO to log it; one spreadsheet column that quietly powers three metrics.

Common questions

What should be in a purchase order email to a supplier? Nine things: PO number, supplier product codes, quantities per line, agreed unit price per line, currency, full delivery address, a required-by date (a real date, not "ASAP"), payment terms, and a request to confirm in writing. Send the checklist with every PO, even repeat orders — repeat orders are where "same as last time" ambiguity does its damage.

Should I restate the price if it hasn't changed? Yes. If the PO email doesn't restate the unit price, the invoice will state it for you, and at that point you're disputing after the goods shipped instead of before. The confirmed price on the email thread is also the anchor for your price-stability tracking and any later negotiation.

How do I chase a late purchase order by email? Name the PO and the risk in the subject line, state the confirmed date and the required-by date factually, and make one clean ask: current ship date and whether it ships complete. Ask for the new date in writing. Keep tone neutral — the thread itself is the paper trail you'll use in your quarterly supplier review.

Why does the supplier's confirmation reply matter? It converts your order from a request into an agreement, and it timestamps their committed delivery date — which is the input for measuring their actual lead time. Log the confirmation date and promised date when the reply arrives: that one-minute habit gives you a chase trigger, an honest on-time metric, and a dispute anchor.

Can I just send a PO from Shopify instead of emailing? Shopify's admin supports native purchase orders with PO numbers, line items, and expected dates, and can send them to your supplier (Help Center, accessed October 2026). That covers the document side well. The email matters for what it captures: the supplier's explicit confirmation of price and delivery date, which you'll log back into your tracking.

Next step

Take your most recent PO and check it against the nine-item list — count what was missing. Then start the confirmation log: one sheet, columns for PO number, sent date, confirmed date, promised date, actual sellable date. Six POs in, you'll have a real measured lead time per supplier, and the reorder math built on it stops being a guess.