Purchase Order Change

Orders sometimes need revision after issue: a buyer may need more units, or a supplier may report a delay, and the change process keeps both sides, receiving and finance working from the same terms. A fictional buyer orders 100 parts for June, demand increases so it proposes 120, and the supplier confirms whether the extra 20 can be delivered on the same date.

Record the original purchase order number and affected lines, because a message saying "add ten" without a line reference can attach to the wrong item, and put the old and new values side by side. In a fictional order with two lines, the buyer specifies that line 2 rises from 50 to 60, leaving line 1 unchanged.

A purchase order change can alter quantity, item specification, price, tax, currency, delivery site or schedule, where some changes affect only one line and others alter the whole order, so check related fields for knock-on effects. Authority matters too, since an employee may request a change but approval should follow the organisation's buying limits and contract, and the supplier may also need to accept revised commercial terms; a fictional project lead who asks for a larger order sees procurement get budget approval and supplier confirmation before treating it as committed.

A supplier's proposed difference is not automatically an approved buyer change, and X12's EDI example has a supplier acknowledge an order with proposed quantity or date changes, then the buyer responds with a purchase order change request, which illustrates a workflow, not universal legal effect. A fictional supplier offers 80 units rather than 100, and purchasing updates the order only after agreeing to the split or finding another source.

X12 describes an 860 transaction for buyer-initiated purchase order changes and an 855 for supplier acknowledgement, and email or portal revisions can serve a similar business purpose when properly controlled, so choose the agreed channel. Timing can create conflicts, since goods may already be picked, made or shipped when a change arrives, so ask the supplier what can still be changed and who pays any resulting cost.

A fictional buyer cancels a custom-made item after fabrication begins, and checks the contract and supplier response rather than assuming the order can be cancelled without cost. Do not overwrite the original silently, but preserve a revision number, date, reason, approver and record of supplier response, because history helps settle later questions.

Price changes need careful calculation, since a unit price shift can affect commitments, budgets, tax and invoice matching, so recalculate extended totals and confirm the currency. A fictional order rises from 50 units at $10 to 60 units at $11, so the new line total is 60 x $11 = $660, not the $600 that a quantity-only change would give, and finance reviews the revised commitment.

Quantity changes may interact with minimum order quantities and package sizes, and a change from cases to individual units is not a small text edit, so confirm the unit, and for regulated or safety-sensitive goods technical review may precede a substitution because commercial agreement is not evidence of engineering approval. Delivery changes should update receiving and operations, since an unchanged purchase order in the warehouse can cause a shipment to be rejected at the correct new address, as when a fictional team moves delivery to another plant and sends the approved change to the supplier and both receiving sites.

Ensure the invoice matches the final accepted order and actual receipt, because a retrospective change can hide a control failure: a fictional supplier that bills at a higher price before approval has the difference paused by accounts payable until procurement provides the agreed record. A change request can be declined, so preserve the supplier's refusal and decide whether to keep the old order, negotiate or cancel within contractual rights, noting that silence is not a reliable acceptance signal, and after approval notify planning, logistics, receiving and finance so that a single current version reduces avoidable discrepancies, since a purchase order change is the controlled history of a deal evolving.