Purchase order acknowledgement: checklist and confirmed dates
Turn supplier order acknowledgements into confirmed ship dates on every PO line, handle changed dates and prices, and know when to chase.
A supplier who replies "PO received, thanks" has told you the order arrived, but not when the parts will ship. Teams that keep asking until every order line carries a confirmed date see a slipping delivery earlier, while there is still time to expedite or replan. This method turns an acknowledgement into a date your schedule can rely on.
What is a purchase order acknowledgement?
A purchase order acknowledgement is the supplier's reply to your purchase order saying the order was received and, ideally, accepted. On its own it tells your planner only that the order arrived. It becomes a confirmation when the supplier commits, line by line, to a quantity, price and ship date that your team can plan against.
Three terms get used loosely. Separating them keeps the schedule honest. An acknowledgement says the supplier has the PO. A confirmation says what the supplier will ship on each line, when, and at what price. A commitment is a confirmed date that your team has checked against the need date and recorded as the date the plan uses. Promise date vs need date covers what to do when those two dates disagree.
An acknowledgement without a ship date on each line only tells your planner that the PO arrived. Keep chasing until every line has a confirmed date, since until then the planner is working from the date you asked for, a request rather than a promise.
What should a supplier acknowledgement contain?
A useful acknowledgement names your PO number and revision and then answers each line separately. For every line it gives the part number and revision, the quantity, the unit price and a confirmed ship date. It also says whether the supplier accepts your terms and who at the supplier confirmed the order.
Before a line counts as confirmed, check each element against the PO:
- Revision: the acknowledged revision matches the PO's current revision, since an acknowledgement of revision 2 does not confirm changes sent in revision 3.
- Part number and revision: match the PO, not an old drawing.
- Quantity: matches the PO, or a shortfall is a separate scheduled delivery with its own date.
- Price, currency and unit of measure: match the PO.
- Ship date: one confirmed date per scheduled delivery, at the point you agreed (supplier's dock or yours), not a header status such as "order accepted."
- Terms: the supplier's acceptance, or its exceptions, is recorded, along with who confirmed the line and when.
When a supplier ships part of a line now and the rest later, record two scheduled deliveries, each with its own date, instead of one date that fits neither.
EDI-connected suppliers send the same information as an X12 855 or EDIFACT ORDRSP message, which carries the same accepted quantity and ready date for each line. EDI 855 explains the codes. Many suppliers confirm by email, and the same check applies to both.
How does a PO become a confirmed date?
A purchase order becomes a dependable date in five stages, starting when the PO is sent. The supplier acknowledges receipt, confirms a date on each line, your team approves or rejects any changes, and the confirmed dates are tracked until the parts arrive. A line that stalls partway through is still an open question for the build plan.
The figure shows what each step proves and what is still missing.
From PO to confirmed date
A five-step left-to-right flow from a purchase order to a tracked confirmed date. Step one, PO sent, proves the order exists but not that the supplier has it. Step two, acknowledged, proves receipt only, with no line dates. Step three, line dates confirmed, proves the supplier committed a quantity, price and date on each line, but changes may be unreviewed. Step four, changes approved, proves your team accepted each change against the need date. Step five, dates tracked, keeps the confirmed dates under watch until receipt.
- 1
PO sent
- What it proves
- The order exists and states what you asked for and when
- What is still missing
- Evidence that the supplier received it
- Who acts next
- Supplier replies
- 2
Acknowledged (receipt only)
- What it proves
- The supplier has the PO
- What is still missing
- A confirmed quantity, price and ship date on each line
- Who acts next
- Buyer chases for line dates
- 3
Line dates confirmed
- What it proves
- The supplier committed a quantity, price and ship date per line or scheduled delivery
- What is still missing
- Your review of any change against the PO and the need date
- Who acts next
- Buyer and planner review changes
- 4
Changes approved
- What it proves
- Your team accepted or rejected each change in writing, and the PO revision matches
- What is still missing
- Evidence that the date still holds as it approaches
- Who acts next
- Buyer records the commitment in the ERP
- 5
Dates tracked
- What it proves
- The confirmed date is the date the plan uses and is checked until receipt
- What is still missing
- Nothing at this stage; later slips go to PO tracking and expediting
- Who acts next
- Expediter or buyer follows up before the due date
Each step proves something different, and a line is only dependable once it has a supplier date and any change to it has been approved.
Treat a line as confirmed only once it has a supplier date and any change to it is approved by your team. From there, purchase order tracking checks that the date still holds as it gets closer.
What do you do when the acknowledgement changes the order?
Don't let a changed date, quantity or price flow into your records unreviewed. Compare every line with the PO, check any later date against the need date, and accept or reject each change in writing. A change that nobody reviews becomes the new plan without anyone deciding that the build can absorb it.
Handle each kind of change on its own terms:
- A later date needs a check against the need date: accept and record it if the build still has cover, or ask the supplier for the earliest possible date and start expediting if it doesn't.
- Accept a shorter quantity or a split only as separate scheduled deliveries, each with its own date.
- Route a higher price to the buyer who holds approval authority, so it doesn't surface first as an invoice mismatch.
- Send substituted parts or revisions to engineering or quality before anyone accepts them.
Whoever approves a change issues a PO revision, so both sides work from the same document, and records the reason for it.
In the United States
Under UCC Article 2, an acknowledgement that accepts your PO can form the contract even when it adds or changes terms, unless the supplier makes acceptance expressly conditional on your assent. Between merchants, the supplier's added terms become part of the contract unless your PO limits acceptance to its own terms, the new terms materially alter the deal, or you object within a reasonable time. UCC § 2-207(1)–(2). Comment 6 says conflicting clauses on the two forms drop out, and courts often fill the gap from the Code instead. UCC § 2-207, Official Comment 6. An acknowledgement on the supplier's own terms can add to your PO or knock out conflicting terms. State on the PO that acceptance is limited to its own terms, and object in writing to terms you reject. States enact the UCC with variations, so check your contract and counsel.
Selling into the EU?
EU law does not harmonize how a sales contract is formed, so German law is shown here. Changing your order in the confirmation (Auftragsbestätigung) is a rejection and a new offer under German law. § 150(2) BGB. Silence alone does not accept it, although taking delivery without objection can (BGH, 26.09.1973, VIII ZR 106/72, BGHZ 61, 282, 287 f.), especially where the supplier made clear it would deliver only on its own terms. If your PO terms expressly reject the supplier's terms, German courts generally treat the conflicting clauses as not agreed. §§ 154, 155, 306 BGB. A commercial letter of confirmation (kaufmännisches Bestätigungsschreiben) differs: between merchants and businesses that trade like them, one sent promptly after negotiations binds the recipient unless objected to without delay or so far off the agreement that consent couldn't be expected. BGH, 27.01.2011, VII ZR 186/09, BGHZ 188, 128, Rn. 21–22. For sales between businesses in different CISG Contracting States (every EU member state except Ireland and Malta), a reply changing price, quantity, quality or delivery time is a counter-offer, and silence is not acceptance. CISG Art. 1; Art. 18(1) and 19(1), (3). Contracts can exclude the CISG (Art. 6), so check yours.
How long should you wait before chasing an acknowledgement?
Put the response window on the PO itself, for example a line in your terms asking for a line-level confirmation within a set number of business days. Chase on the first business day after the window closes. A PO that has no confirmed dates after a second request needs a phone call rather than a third email.
The window is an internal rule, so choose one that fits the lead time. A part needed in three weeks cannot wait a week for a reply, while a six-month casting can. What matters most is that every open line without a confirmed date is on someone's list every day, rather than surfacing when the parts fail to arrive.
At scale, that daily pass is where lines get missed. When an order has no confirmed date, a readiness signal opens a task, and Cartograph hands it to your team or Scout Agent, who emails and calls the supplier for a line-level date, within the permissions your team sets. When a supplier stays silent anyway, supplier not responding covers escalation.
In the United States
For most DPAS-rated orders, regulation sets the window. A supplier must accept or reject a rated order in writing or electronically within 15 working days of receiving a DO order and within 10 working days for a DX order, and must give reasons for any rejection. 15 CFR 700.13(d)(1). Emergency-preparedness orders instead set their own window, which can be as short as 6 hours after receipt (a hazard that has occurred) or 12 hours (an imminent hazard). 15 CFR 700.13(d)(2). A supplier may not accept a rated order for a date it cannot meet, and must offer the earliest date it can. 15 CFR 700.13(b)(1). After accepting, the supplier must notify you immediately of any delay, give a new date, and confirm a verbal notice in writing or electronically within one working day. 15 CFR 700.13(d)(3). The DPAS rated orders lesson covers the rest of the rules. The DPAS rests on Title I of the Defense Production Act, which expires on December 11, 2026 unless Congress extends it. 50 U.S.C. 4564(a).
What should you record from each acknowledgement?
Record enough that someone else can see, without opening the email thread, what the supplier committed to and whether your team agreed. The minimum is the confirmed date and quantity per scheduled delivery, the PO revision acknowledged, who confirmed it and when, and any change with its approver and reason.
Keep the original acknowledgement attached to the PO. When a delivery slips later, the record shows whether the supplier missed a date it confirmed or a date it never agreed to, and that difference decides who bears the cost. Update the confirmed date in your ERP, not a side spreadsheet, so MRP and the planner see the same date.
Questions teams ask
Is an order acknowledgement legally binding?
It can be. An acknowledgement that accepts a PO can form the contract, and the terms that apply depend on the governing law and each side's documents. Check your contract and counsel.
What is the difference between a PO acknowledgement and a PO confirmation?
An acknowledgement confirms that the supplier received the order. A confirmation states, for each line, the quantity, price and ship date the supplier will meet.
Should we accept a later date in the acknowledgement if it still meets our need date?
Yes, if the planner has checked it against the current need date and recorded the approval. Record it as the confirmed date, so later checks compare against what the supplier actually agreed to.
Do we need the supplier to re-acknowledge a PO revision?
Yes. Each revision that changes dates, quantities, prices or part revisions needs its own confirmation, since an earlier acknowledgement doesn't cover the changes.
If your team spends hours chasing unconfirmed order lines, talk to our team about how Cartograph's readiness signals open those tasks.
This article is general information, not legal or tax advice. Check how the rules apply to your business with your legal or tax advisor.
Sources (8)
- UCC § 2-207, Additional terms in acceptance or confirmation (Cornell LII)
- UCC § 2-207 with Official Comments, as enacted in D.C. Code § 28:2-207
- 15 CFR 700.13, Acceptance and rejection of rated orders (eCFR)
- § 150 BGB, Verspätete und abändernde Annahme
- § 306 BGB, Rechtsfolgen nicht einbezogener und unwirksamer Bestimmungen
- BGH, Urteil vom 26.09.1973, VIII ZR 106/72, BGHZ 61, 282 (cited in body by reporter only; this dejure.org entry is a secondary citation index, not the primary source)
- BGH, Beschluss vom 27.01.2011, VII ZR 186/09, BGHZ 188, 128
- United Nations Convention on Contracts for the International Sale of Goods (UNCITRAL), Arts. 1, 6, 18, 19