To confirm a purchase order change, define the exact difference, obtain the required internal approval, send the supplier an identifiable revision, and reconcile its response against that revision. Then verify that the accepted change is implemented in the order record and understood by the people executing it.
A revised PDF proves what was sent. It does not, by itself, prove supplier acceptance, implementation, or that a warehouse has stopped following the previous instruction. The PO change control worksheet (Excel) separates those steps and preserves the evidence for each.
Start with the currently effective order
Open the current PO, revision history, applicable agreement, supplier acknowledgement, and any change already in progress. Determine what the supplier is presently expected to execute and which proposals remain unresolved.
Record the PO, line, schedule, revision, affected quantity, and reason for change. State whether the request originated with the buyer, planning, engineering, the supplier, or another owner. Check for goods already produced, packed, dispatched, received, or invoiced, because those events constrain what can still change.
Oracle’s change-order lifecycle distinguishes pending changes from implementation and revises the active purchasing document when an external change order is implemented. Check your own system’s lifecycle and configuration rather than equating a draft or approval with an effective revision. Oracle change-order lifecycle.
If the effective baseline is unclear, resolve it before issuing another amendment. Adding a third interpretation does not resolve disagreement between the first two.
Describe the difference at field level
For each affected line, show the old value, requested value, reason, effective scope, and consequences. Keep unchanged fields explicitly within the same baseline rather than rewriting the whole commercial offer in an email.
Examples include quantity, unit price, currency, specification revision, delivery destination, schedule, packaging, and required documents. Identify whether the change affects all remaining supply or only a named lot or shipment.
Use a compact change statement:
PO [number], current revision [revision], line [line]
Change requested: [field], from [old value] to [new value]
Scope: [quantity / lot / schedule / unshipped balance]
Requested effective date: [date]
Reason: [reason]
Other affected terms or assumptions: [details]
Other lines remain as documented in [baseline reference].
Avoid “please update accordingly.” The supplier should be able to identify exactly what production, dispatch, and commercial records need to change.
Separate approval of the request from supplier agreement
The authorized buyer approves commercial changes within the organization’s rules. Planning evaluates quantities and required dates. Engineering or quality decides whether a technical change or substitute is acceptable. Logistics and receiving assess routing and arrival constraints. These approvals can depend on each other.
Record the authority for the specific action. Permission to change a delivery date does not automatically authorize a price increase or a different material. Where several fields change together, collect every required decision before representing the package as approved.
Internal approval authorizes the organization to make the request or accept a proposal. Supplier acknowledgement establishes what the supplier has agreed to execute through the applicable process. Keep those evidence records separate.
If a supplier proposes a cost for an acceleration or cancellation, treat it as a proposal for the commercial owner. Do not infer an entitlement or obligation from the operational urgency. Reference the existing agreement and route disputed terms through the established review process.
Send one clear revision and ask for a bounded answer
Use the normal PO change mechanism, with a revision or change identifier and approved supporting documents. State that it amends the existing PO and identify the portions superseded. Avoid wording that could be read as a second order.
Ask the supplier to confirm the changed fields, affected quantities, and feasibility by a stated time. If the supplier has already started work under the old instruction, ask it to identify that quantity and status so the buyer can decide the disposition.
Please acknowledge change [ID] to PO [number], revision [revision].
Confirm the revised quantity, specification and receipt schedule for
the affected lines, or list each proposed exception separately.
Please identify any affected material already produced, packed or
dispatched under the earlier revision. Reply by [time and time zone].
Check that the supplier received the correct attachments and can open them. If a portal is the formal response channel, make the message point to that event. A discussion in email may provide useful evidence while still requiring the configured acknowledgement process.
Review the reply for partial or conditional acceptance
Read the complete reply and attachments. “Confirmed” at the top can coexist with a line note changing price, quantity, or timing. Use the confirmation checklist for field-level reconciliation.
Classify each changed line as accepted, rejected, accepted with proposed differences, or unclear. Capture conditions such as receipt of a drawing release or agreement to a fee. A condition is part of the proposed commitment, not background text.
When only part of the change is accepted, ask whether the accepted portion can stand independently. For example, a supplier might accept an address change for the unshipped balance but be unable to reroute goods already collected. The buyer needs two dispositions, not one header-level confirmation.
Do not silently combine a favorable price from one response with an earlier delivery from another. Obtain a single coherent accepted package or clear evidence linking the terms that remain in effect.
Worked example: reduce quantity after part has shipped
In this illustrative example, revision two of PO 8104 orders 1,000 housings at $12 each. The supplier has already dispatched 300. Planning asks to reduce the total requirement to 800 and move the destination for the remaining supply from Plant A to Plant B.
The buyer first establishes the baseline: 300 in transit to A, 700 unshipped, no receipts posted. The requested change is a reduction of 200 from the unshipped balance, leaving 500 to go to B. The 300 already dispatched are not silently redirected or cancelled.
The change comparison is:
Original authorized total: 1,000
Already dispatched to Plant A: 300
Original unshipped balance: 700
Requested reduction of unshipped balance: 200
Proposed new unshipped balance to Plant B: 500
Proposed revised order total: 800
The supplier confirms the 300 shipment is unchanged and can send 500 to B, but proposes a $150 cancellation charge because some cancelled units were already packed. The buyer records a conditional response and sends the charge to the authorized commercial owner. It does not mark the full change accepted while that condition is unresolved.
Suppose the owner approves the charge and the revised commercial document makes it explicit. The supplier acknowledges the final revision. The authorized updater implements the 800-unit total and 500-unit remaining schedule to B, retaining the 300-unit shipment to A and the charge evidence.
Receiving at both sites gets the relevant final instruction through the established handoff. The buyer verifies 300 plus 500 equals the revised 800 and that the cancelled 200 has not become an unexplained open balance. The example’s revised material value is $9,600, with the separately approved $150 charge; finance handles invoicing and treatment.
Resolve overlapping changes without losing history
Two people may amend different fields while the supplier is responding. Before sending or implementing a revision, check for another open change and compare its baseline. If a newer revision supersedes yours, reconcile the combined intent with the responsible buyer instead of applying an outdated response.
Keep one authoritative change log. Note which request supersedes which, which fields remain valid, and which decisions need to be repeated. Cancel follow-ups tied to obsolete revisions and issue a new specific request for the current one.
If the supplier replies against the previous revision after the new one has been sent, preserve the answer as history. Reuse it only for unchanged fields where the meaning is unambiguous and your process allows it. Obtain confirmation of materially changed fields under the current revision.
For urgent changes discussed by phone, write the agreed details into the formal process and obtain the required evidence. A buyer’s recollection should not become the only record guiding production or later invoice review.
Handle amendments that collide with physical events
If goods ship during the change process, refresh the scope before implementation. Identify the shipped quantity, route, and applicable revision. Ask logistics what is still controllable and give the buyer the actual alternatives and costs.
If goods have already arrived, receiving retains the actual receipt. Do not rewrite the receipt history to resemble a later quantity reduction. Use the approved return, correction, or commercial process for the real disposition.
For a specification change, determine the affected lots and work already completed. Quality or engineering decides whether earlier material can be accepted, reworked, or rejected. Collecting a supplier’s statement that the change is “equivalent” does not authorize acceptance.
If the supplier rejects the change, retain the existing effective commitment and route the unresolved need to the buyer. A system request that remains pending should not be treated as supply the team can rely on.
Verify implementation and measure unresolved changes
After implementation, read back the active PO, schedules, quantities, prices, destinations, and required documents. Confirm that the final supplier evidence corresponds to the effective revision. Check that planning, receiving, and any dependent process can see the relevant change.
If the update fails, preserve the error and assign a repair action. If it partially applies, state exactly which fields remain wrong. A successful message transmission or approval does not prove the system record changed.
Measure completed changes as changes with required decisions, supplier disposition, implementation, and read-back evidence divided by changes in the selected cohort. Report open age separately, with time waiting internally, with the supplier, and on a system update. Define when the clock starts and how cancelled or superseded changes are counted.
For example, nine fully completed changes out of 12 raised in a week is 75% for that cohort. Two awaiting a buyer decision and one awaiting supplier confirmation explain the remaining work. Counting all 12 as complete because they were emailed would obscure it.
Close the amendment and leave the order executable
The amendment closes when its final disposition is documented, the effective order reflects the authorized outcome, downstream owners have the instruction they need, and obsolete actions are cancelled. Supplier delivery and invoice work continue under their own closure rules.
Mandel’s purchase order management work helps carry changes through the supplier response and record update. The buyer retains commercial decisions about quantity, supplier, and terms; engineering and quality own technical changes and acceptance under the team's rules. The work finishes with an order everyone can execute consistently.
