Change a purchase order after supplier confirmation

An apparel buyer for a 14-store menswear chain issues confirmed Purchase Order PO-7740 v1 for a linen casual shirt (SKU-LIN-M), ordering 80 units of Size M at ₹650.00 net per unit (₹52,000 on that line) as part of a 240-unit size-curve order worth ₹1,56,000. Four days after the supplier confirms PO-7740 v1, strong early store sales prompt the buyer to increase the Size M line from 80 units to 120 units (+40 units, +₹26,000) and negotiate a revised volume unit price of ₹635.00 across all 280 units (PO-7740 v2, revised order value ₹1,77,800). The buyer emails the amended PDF to the vendor's sales inbox and overwrites the ERP order quantities immediately. Unknown to the buyer, the vendor's factory dispatch team had already packed and handed over the original 240 units (80 units of Size M) with a ₹650.00/unit invoice (₹1,56,000) to the carrier two hours before the amendment email was read. When the shipment arrives at the distribution centre, the warehouse clerk sees 120 units expected on screen against 80 units in the carton, while accounts payable receives an invoice at ₹650.00/unit against an ERP line now showing ₹635.00/unit.

The operational decision for a procurement operations manager is how to govern post-confirmation purchase-order amendments—separating buyer-requested revisions from vendor-acknowledged versions, locking lines once an advance shipping notice (ASN) or dispatch is confirmed, and propagating the active version to receiving and accounts payable (Shopify Help Center — Managing suppliers and purchase orders, Microsoft Learn — Accounts payable invoice matching in Dynamics 365 Finance). By linking this control to partial purchase-order receipt controls and open-to-buy budget reconciliation, procurement operations manager teams prevent downstream inventory and accounts-payable breaks before stock or cash moves.

Why overwriting confirmed purchase orders breaks receiving and AP

In multistore and apparel retail, purchase orders rarely remain static between initial issue and dock receipt. Buyers adjust size curves, bring forward delivery dates, cancel late styles, or renegotiate landed unit prices when raw-material costs shift. However, when an ERP or inventory tool (such as Shopify's purchase-order workflow) allows a buyer to overwrite an already-confirmed PO in place without version states, three operational failures occur:

1. Silent baseline destruction: Overwriting 80 units @ ₹650 with 120 units @ ₹635 erases the baseline that the supplier actually agreed to fulfil. If the supplier never saw or accepted the email change, the retailer's open-to-buy (OTB) budget and incoming stock projections are built on a unilateral wish rather than a bilateral commitment.
2. In-transit version collision at the receiving dock: Once goods leave the vendor's factory under PO v1, changing the ERP order to PO v2 guarantees a artificial receiving variance. The dock clerk either rejects a valid v1 delivery or books a spurious 40-unit vendor shortage that corrupts partial purchase-order receipt tracking.
3. False three-way match holds in accounts payable: Under standard accounts-payable three-way invoice matching, the vendor's invoice is compared against the active PO line price and the product receipt quantity. If PO v2 overwrote the unit price to ₹635.00 while the vendor validly invoiced the v1 shipment at ₹650.00, the invoice fails price-tolerance matching and blocks vendor payment until AP reconstructs the email trail manually.

Track the financial and quantity delta of every proposed amendment before activation using these relationships:

Line Quantity Delta (Units) = Proposed v2 Quantity − Confirmed v1 Quantity

Net Order Commitment Delta (₹) = (Proposed v2 Total Units × Proposed v2 Unit Price) − (Confirmed v1 Total Units × Confirmed v1 Unit Price)

In-Transit Collision Exposure (Units) = Dispatched v1 Units − Proposed v2 Units

Separating Amendment Sent from Amendment Acknowledged ensures that internal ERP screens never get ahead of physical reality on the supplier's loading dock.

  <path d="M219 85 L248 85" stroke="#475569" stroke-width="1.8" marker-end="url(#arrow-r004)"/>

  <rect x="248" y="40" width="195" height="90" rx="8" fill="#fef9c3" stroke="#ca8a04" stroke-width="1.5"/>
  <text x="262" y="64" font-weight="700" fill="#854d0e">2. Amendment Sent (v2)</text>
  <text x="262" y="84">Raise Size M: 80 -> 120 (+40)</text>
  <text x="262" y="102">New price: ₹635 across 280 u</text>
  <text x="262" y="118" font-size="11" fill="#475569">v2 Total: ₹1,77,800 (+₹21.8k)</text>

  <path d="M443 85 L472 85" stroke="#475569" stroke-width="1.8" marker-end="url(#arrow-r004)"/>

  <rect x="472" y="40" width="195" height="90" rx="8" fill="#ffedd5" stroke="#ea580c" stroke-width="1.5"/>
  <text x="486" y="64" font-weight="700" fill="#9a3412">3. Dispatch Collision</text>
  <text x="486" y="84">Vendor ships v1 (240 u) early</text>
  <text x="486" y="102">v2 unacknowledged at dispatch</text>
  <text x="486" y="118" font-size="11" fill="#475569">Dock receives 240 u against v1</text>

  <path d="M667 85 L696 85" stroke="#475569" stroke-width="1.8" marker-end="url(#arrow-r004)"/>

  <rect x="696" y="40" width="200" height="90" rx="8" fill="#dcfce7" stroke="#16a34a" stroke-width="1.5"/>
  <text x="710" y="64" font-weight="700" fill="#166534">4. Controlled Resolution</text>
  <text x="710" y="84">Match Drop 1 (240 u) @ ₹650</text>
  <text x="710" y="102">Issue Drop 2 (40 u) @ ₹545</text>
  <text x="710" y="118" font-size="11" fill="#475569">Combined 280 u = ₹1,77,800</text>

  <rect x="24" y="166" width="872" height="164" rx="8" fill="#ffffff" stroke="#cbd5e1" stroke-width="1.2"/>
  <text x="44" y="194" font-weight="700" font-size="13" fill="#0f172a">Governance rule: An unacknowledged PO amendment never overwrites an active receiving or AP baseline</text>
  <text x="44" y="220" fill="#334155">• Gate A: Internal OTB gate requires planner sign-off whenever a PO amendment increases net commitment above ₹15,000.</text>
  <text x="44" y="246" fill="#334155">• Gate B: Acknowledgement gate holds v2 in 'Sent — Pending Vendor Ack' until vendor confirmation reference and dispatch status are verified.</text>
  <text x="44" y="272" fill="#334155">• Gate C: Collision recovery rule matches already-dispatched v1 goods to v1 receipt/invoice and settles retrospective price discounts on Drop 2 or credit note.</text>
  <text x="44" y="302" font-weight="600" fill="#0369a1">Outcome: 240 units received cleanly on Drop 1 without false dock discrepancy; 40-unit increment and ₹4,200 retrospective discount settled cleanly.</text>
</g>
<defs>
  <marker id="arrow-r004" viewBox="0 0 10 10" refX="8" refY="5" markerWidth="6" markerHeight="6" orient="auto-start-reverse">
    <path d="M 0 0 L 10 5 L 0 10 z" fill="#475569"/>
  </marker>
</defs>

Worked illustrative example: resolving a mid-dispatch PO quantity and price amendment

Illustrative example (hypothetical scenario): Examine the menswear chain's amendment on PO-7740 for linen shirts (SKU-LIN-S, SKU-LIN-M, SKU-LIN-L, SKU-LIN-XL) where the buyer increases Size M quantity and negotiates a retrospective tier discount while Shipment 1 is already leaving the vendor's factory.

Step 1: Establish the baseline operational and commercial parameters

• Confirmed Baseline (PO-7740 v1, confirmed Day 1):
  • Size S: 40 units, Size M: 80 units, Size L: 80 units, Size XL: 40 units
  • Total v1 ordered quantity: 40 + 80 + 80 + 40 = 240 units
  • Confirmed v1 unit price: ₹650.00 per unit (GST-exclusive)
  • Total v1 purchase commitment: 240 units × ₹650.00 = ₹1,56,000
• Proposed Amendment (PO-7740 v2, requested Day 5 at 11:00):
  • Buyer increases Size M by +40 units (80 + 40 = 120 units), bringing total order quantity to 280 units (240 + 40 = 280 units).
  • Because crossing the 250-unit tier unlocks a ₹15.00 per unit volume discount, the proposed v2 unit price across all 280 units is ₹635.00 per unit (₹650.00 − ₹15.00 = ₹635.00).
  • Proposed v2 purchase commitment: 280 units × ₹635.00 = ₹1,77,800
  • Net OTB commitment increase: ₹1,77,800 − ₹1,56,000 = +₹21,800 (composed of 40 extra units × ₹635.00 = +₹25,400 volume addition minus 240 original units × ₹15.00 = −₹3,600 price reduction).

Step 2: Reconcile packs, exceptions, and financial commitment

1. Detect the pre-acknowledgement dispatch collision on Day 5 at 14:00:
   • The supplier replies at 14:00 confirming they accept the 280-unit tier (PO-7740 v2), but their warehouse already dispatched the original 240 units (80 units of Size M) at 09:30 under Delivery Challan DC-901 and commercial invoice INV-901 for ₹1,56,000 (240 × ₹650.00).
2. Contrast uncontrolled overwrite against version-controlled resolution:
   • If the buyer had overwritten PO-7740 in place at 11:00: The warehouse dock would see 280 units expected (120 of Size M), flag a 40-unit shortage on DC-901, and AP would block INV-901 for a ₹3,600 price variance (240 units × (₹650 − ₹635) = ₹3,600).
   • Under controlled PO versioning: Because DC-901 was dispatched at 09:30 before v2 acknowledgement at 14:00, Procurement keeps Drop 1 (240 units) mapped to the v1 receipt and invoice baseline (₹1,56,000), and creates an approved v2 amendment schedule for Drop 2 (40 units of Size M) plus the retrospective tier adjustment:
     • Option A (Credit note on Drop 1 + standard v2 price on Drop 2): Receive and match Drop 1 (240 units @ ₹650.00 = ₹1,56,000), link a ₹3,600 supplier credit note (240 × ₹15.00), and receive Drop 2 (40 units @ ₹635.00 = ₹25,400). Total net settlement: ₹1,56,000 − ₹3,600 + ₹25,400 = ₹1,77,800.
     • Option B (Netted price on Drop 2 where tax rules permit): Keep Drop 1 at ₹1,56,000 and bill the remaining ₹21,800 commitment across the 40 units on Drop 2 (₹21,800 ÷ 40 units = ₹545.00 per unit). (Note: confirm GST invoice and discount-note rules with finance/tax advisors before netting retrospective discounts across separate tax invoices.)

Because the system preserved PO-7740 v1 until the vendor acknowledged v2 and logged the dispatch timestamp of DC-901, the distribution centre received all 240 units on Drop 1 with zero false shortage flags, and accounts payable reconciled the exact ₹1,77,800 net commitment across INV-901 (₹1,56,000), CN-901 (-₹3,600), and INV-908 (₹25,400).

Purchase-order change control workflow and exception gates

To eliminate unacknowledged order overwrites across buying, warehouse receiving, and accounts payable, enforce four operational rules:

1. Freeze confirmed POs against direct field edits (Owner: ERP / Procurement Administrator). Once a purchase order moves to Confirmed, lock line quantities, unit prices, pack ratios, and promised delivery dates. Any modification must generate a numbered revision (v2, v3) recording the requester, timestamp, and reason code.
2. Route material amendments through OTB and approval limits (Owner: Merchandise Planner / Procurement Manager). If the net commitment delta (v2 Total − v1 Total) exceeds the buyer's threshold (e.g., ₹15,000 or 5% of PO value) or pushes a unit cost above the approved quote basis, require planner approval against the open-to-buy budget before transmitting v2 to the supplier.
3. Keep v1 active for receiving and AP until vendor acknowledgement is logged (Owner: Category Buyer + Supplier). Transmit v2 via supplier portal or structured email acknowledgment link. Until the vendor confirms v2 and states whether any goods have already been dispatched, warehouse receiving screens continue to match against v1 while displaying a pending-amendment banner.
4. Execute split-version recovery when goods ship before acknowledgement (Owner: Procurement Operations + AP). If a shipment left the supplier before v2 was acknowledged, receive that shipment against the v1 snapshot (using partial-receipt controls if needed) and apply the amendment only to the unshipped balance line and linked credit/debit adjustment in AP three-way matching.

Choosing the right mechanism: If your ERP supports native purchase-order versioning with Confirmed versus In Review states, enable mandatory version archiving and block receiving against unconfirmed revisions. If supplier confirmations still happen by email alongside a basic inventory tool, maintain a lightweight PO Amendment Register that holds ERP edits in staging until the vendor replies with a confirmation reference and dispatch status.

Bounded pilot scope, baseline measurement, and stop/recovery criteria

Because this workflow alters operational control gates across procurement and financial reconciliation, run a bounded 30-day pilot in one category or location before enabling enterprise-wide enforcement:

During the pilot window, hold a weekly joint review between procurement operations manager, store or warehouse operations, and commercial finance to inspect every quarantined exception record. Do not expand the rule set to additional categories or automate ledger adjustments until the pilot achieves zero unexplained reconciliation breaks across two consecutive weekly cut-offs.

Observable acceptance tests for your retail systems

Before relying on this workflow in production, execute three deterministic acceptance tests (ACT-R004-01 to ACT-R004-03) in your staging environment or controlled worksheet:

Implementing PO change control across buying, receiving, and AP

To stop post-confirmation order edits from causing dock delays and accounts-payable reconciliation backlogs:

1. Sample your last 30 AP invoice-matching exceptions and count how many price or quantity variances were caused by a buyer editing a purchase order after the supplier had already confirmed or dispatched an earlier version.
2. Separate Amendment Sent from Amendment Acknowledged in your procurement workflow so no post-confirmation quantity or price change updates warehouse receiving or AP matching rules until vendor acceptance and dispatch status are recorded.
3. Establish a standard collision-recovery protocol between buying, warehouse receiving, and AP for shipments that leave the supplier's dock before an amendment takes effect.
4. Run the 30-day pilot and acceptance tests (ACT-R004-01 to ACT-R004-03) on one category with frequent mid-season size or quantity adjustments before enforcing version locks across all merchandise departments.