Practical perspectives
PO Change and Supplier Acknowledgment: A Buyer Checklist
A line-level checklist for reconciling purchase-order revisions, supplier counterproposals and ERP records.
A buyer can update a purchase order in the ERP while the supplier still plans against an older version. The reverse happens when a supplier proposes a new date but the buyer never approves it. The useful question is which version both sides have accepted.
This checklist tests one changed PO line. The purchase-order change software guide covers the software shortlist; this article defines the evidence a reviewer should retain.
1. Identify the accepted starting version
Record the PO number, line, revision, quantity, unit price, delivery date, supplier reference and timestamp of the last accepted acknowledgment. Keep the signed contract or pricing schedule beside it. A proposed date should never silently replace the accepted promise.
| Field | Accepted version | Proposed version | Decision evidence |
|---|---|---|---|
| Delivery date | June 12 | June 19 | Supplier proposal and buyer reply |
| Quantity | 1,000 units | 700 now, 300 later | Planning approval and supplier capacity |
| Unit price | US$20 | US$20 plus expedite fee | Commercial approval and cost basis |
2. Preserve the supplier proposal and its reason
A supplier may propose a date, quantity, price or cancellation. Capture the original message, affected lines and reason before converting it to a structured change. SourceDay’s PO collaboration documentation ↗ shows supplier and buyer proposals linked to an order line.
- Provenance: who proposed the change and through which channel?
- Scope: which lines and open quantities are affected?
- Status: is it a proposal, counterproposal, accepted amendment or rejected request?
3. Route the decision before communicating an accepted term
A changed date can affect inventory; a changed price can require a different approver. Split the decisions if needed. The buyer should approve the commercial and operational result before a system tells the supplier that revised terms are accepted. If the buyer counters, retain both proposals.
An AI agent may draft a response or suggest a split delivery. Require it to show the source signal, contract constraint and authorized action. Fragment’s change-order page ↗ describes cross-system automation, which makes approval limits and write-back behavior important demo questions.
4. Check ERP, supplier and downstream records
After acceptance, compare the supplier acknowledgment to the ERP line, planning date, receiving expectation and invoice-match basis. If one write-back fails, keep the change in an exception state and assign an owner. Do not present partial synchronization as a completed amendment.
| Checkpoint | Pass condition | Exception to investigate |
|---|---|---|
| Supplier | Acknowledges exact revision and line terms. | Silence or an older confirmation. |
| ERP | Stores authorized accepted version. | Write-back rejected or wrong currency/quantity. |
| Receiving and AP | Uses the revised date and price basis. | Invoice still matches the former order. |
5. Repeat with a counterproposal and a failed write-back
For a software pilot, use one supplier-initiated change and one buyer-initiated change. Then introduce a counterproposal and a failed ERP update. Measure whether a reviewer can reconstruct the accepted state, responsible person and unresolved exception without reading a separate email chain. Mandel AI’s PO follow-up article ↗ emphasizes keeping open lines and commitments visible.