merchmix

Publish Date :

Changing an Order After It's Placed: Keeping Suppliers in the Loop

Changing an order works only when the retailer and supplier can identify the same accepted version. Core shows the planning effect of the request, while Beacon supports supplier visibility and acknowledgement. A proposed reduction or later date must not silently replace the current commitment.

A young buyer comparing linen overshirt order versions beside matching garments.
Editorial image: a young buyer comparing linen overshirt order versions beside matching garments.

THE MERCHMIX DECISION / Beacon + Core

Begin with the accepted order

An order change needs a visible comparison between the current commitment, the requested revision and what the supplier can actually accept.

Independent retail planning example. Financial amounts are US dollars. Forecasts, quantities and proposals are assumptions for this decision, not customer results.

merchmix.Beacon + Core / Linen overshirts / PO-4172 version comparison
Confirmed versionCurrent assumptions

Linen overshirts / PO-4172 version comparison

Confirmed versionDecision comparison
Confirmed quantity240 units
Confirmed goods cost$7,200
Current delivery date8 December
Current order
Change request
Supplier response
Begin with the accepted order
SizeCurrent quantityProposed quantity
Small6040
Medium8060
Large6060
Extra large4040
The supplier commitment is still 240

The delivery date and quantity proposal are separate changes.

Begin with the accepted order

PO-4172 has 240 linen overshirts at $30 goods cost.

THE KEY IDEA

Keep current, requested and supplier-supported order versions distinct until an authorised amendment establishes the new commitment.

Start from the version both sides are already working to

A purchase order can accumulate requests, replies and internal planning changes without a single agreed replacement. Before sending another amendment, establish the current accepted quantity, cost, destination and date meaning. A later email is not automatically the authoritative order.

Merchmix’s public Beacon description places amendments in the retailer-side Merchmix workflow rather than the supplier portal. Beacon supports acknowledgement and order history. Keep that division clear: the supplier response is essential evidence, but it is not an unrestricted editor for every commercial field.

Product evidence and planning referencesMerchmix Beacon: product capabilities and workflow context Merchmix Core: product capabilities and workflow context Oracle: approval and supplier acknowledgement are separate document states

Make the requested change specific at line level

An independent retailer has PO-4172 for 240 linen overshirts at $30 goods cost, totalling $7,200. The size mix is sixty small, eighty medium, sixty large and forty extra large. The current delivery date is 8 December, distinct from any ex-factory milestone.

The buyer requests forty small and sixty medium, leaving the other sizes unchanged, and proposes delivery on 12 December. The requested order becomes two hundred units at $6,000. The forty-unit difference is $1,200 of requested goods commitment reduction, not a cancellation already agreed.

Keep the current plan and the proposed plan distinct

Core can show the stock and intake effect of the two quantities while the amendment is being reviewed. The current order still contains 240 units. A separate scenario can use the requested two hundred, provided the acceptance dependency is visible.

Changing the forecast or intake assumption does not change the purchasing record. If the supplier continues preparing the original quantity, planning against the request as though it were confirmed understates the incoming commitment. Retain both versions until the supported amendment process settles the new position.

THE FIGURES BEHIND THE DECISION

Changing an Order After It's Placed: Keeping Suppliers in the Loop: Current: 240 × $30 = $7,200. Requested: 200 × $30 = $6,000. Conditional supplier alternative: 220 × $30 = $6,600. No reduction is confirmed in this illustration.
VersionQuantityGoods costPosition
Current accepted240$7,200Still authoritative
Buyer request200$6,000Not accepted in full
Supplier alternative220$6,600Awaiting final decision

Current: 240 × $30 = $7,200. Requested: 200 × $30 = $6,000. Conditional supplier alternative: 220 × $30 = $6,600. No reduction is confirmed in this illustration.

Read partial acceptance as a new decision

Suppose the supplier can reduce small by twenty but has already committed the medium production. It supports 220 units, not the two hundred requested. At the unchanged $30 cost, that alternative is $6,600 and would reduce the original commitment by $600 if the change is completed.

The remaining twenty requested units have not disappeared. The buyer must decide whether to accept the alternative or review another route. Keep any cost for changing the order separate from this goods-only calculation, and do not assume that all reductions can be made without commercial consequences.

THE PLANNING REFERENCERead the MFP/WSSI planning guide

Confirm the date independently from the quantity

The supplier’s support for 220 units does not, by itself, accept 12 December delivery. Confirm whether the response concerns ex-factory, dispatch, expected arrival or the requested delivery appointment. A quantity agreement and a date agreement can have different constraints.

Beacon can keep the vendor reference, supported acknowledgement details and order history visible. Core needs the resulting usable intake timing for the merchandise plan. An accepted date remains a commitment or expectation; physical receipt is established by the receiving record, not by the acknowledgement alone.

Reconcile the approved amendment with the order record

After the authorised decision, verify the actual accepted quantities by size, unit cost and relevant dates. If the completed amendment is 220, the plan should not continue using either the old 240 or the rejected two hundred as its confirmed position.

The animation deliberately stops before that outcome. It shows current, requested and conditionally supported versions so their meanings remain clear. A real transaction should be reported as complete only when the supported order workflow and supplier record have been reconciled, including any failure or remaining exception.

SignalMerchmix workspaceDecision to review
Confirmed versionBeacon / evidencePO-4172 has 240 linen overshirts at $30 goods cost.
Requested revisionCore / comparisonThe buyer proposes 200 units and a 12 December delivery date.
Planning reconciliationBeacon / decision reviewCore reflects the accepted commitment; Beacon records the supported supplier response. No receipt is claimed.

Close the loop without losing the original decision trail

Retain the reason for the change, the original scope, supplier constraints and the version ultimately accepted. That record explains why the final quantity may differ from the first request and gives the next planner a credible starting point.

Core connects the accepted intake to the forward stock plan, while Beacon supports the shared supplier response. The improvement is a dependable commitment that both sides can explain, rather than a smaller number in one plan and an unchanged order still being prepared elsewhere.

BEFORE THE NEXT DECISION

  • Planning owner

    The order remains at the current accepted version until the amendment process completes.

  • Commercial owner

    This is a conditional supplier response, not a posted order amendment.

  • Decision owner

    Core reflects the accepted commitment; Beacon records the supported supplier response. No receipt is claimed.

Common questions

Has the forty-unit reduction been accepted?

No. It is the buyer’s request. The current confirmed order remains 240 until an authorised amendment completes.

Why does the supplier alternative contain 220 units?

The supplier supports twenty fewer small units but keeps medium at eighty, leaving the requested twenty-medium reduction unresolved.

Is the $1,200 reduction a confirmed saving?

No. It is the goods-value difference of the requested change. The conditional 220-unit alternative differs by $600, before any amendment costs.

Can the supplier edit all order fields in Beacon?

No unrestricted editing is claimed. Amendments use the retailer-side workflow, with the supported supplier response recorded separately.

Does a new delivery date prove receipt?

No. Requested delivery, accepted milestones, expected arrival and physical receiving records have different meanings.

beacon

PO-4172 has 240 linen overshirts at $30 goods cost.

Explore
core

The buyer proposes 200 units and a 12 December delivery date.

Explore

Continue reading: Why supplier update timing matters

Read the retail planning glossary

FROM THE ARTICLE TO YOUR OWN RETAIL PLAN

Review the decision.
See the workflow.

Bring your planning questions to a demo, or explore a proof of concept on your own data.

Book a demo Explore the proof of concept