Replan supply when inbound ETAs change without treating every delay alike

Two late receipts do not necessarily need the same response

A control report lists two purchase orders as delayed. Both are two days late, so both receive the same urgent flag. Yet one affects an order due tomorrow, while the other supplies a depot with enough stock for the relevant period.

The operational question is which commitments become unserviceable under the revised receipt assumptions. Lateness is useful context, but it is not a complete priority rule. A replanning workflow should connect the changed inbound quantity and timing to the demand it was expected to cover.

This also prevents unnecessary expedites. Paying to accelerate every late shipment can consume budget without improving the customer commitments that are actually at risk.

Build the exposure view from dated quantities

Identify the affected SKU, location, quantity and expected usable-receipt time. The physical arrival time may precede unloading, inspection or other required steps before stock is available. Use the relevant availability assumption for the planning decision.

The Microsoft Dynamics 365 — Inventory Visibility reservations describes reservations against configured available measures. For delay replanning, verify how the local system represents existing commitments and future supply. An expected receipt should not be treated as current usable stock merely because a purchase order exists.

Record the source and age of the revised ETA. A carrier estimate, supplier promise and confirmed appointment may have different meanings. If the last update is stale, expose that uncertainty and assign someone to obtain current evidence.

A useful view also shows the planning horizon. “Enough stock” means little unless it states which dated requirements have been considered.

Illustrative comparison: one delay exposes twenty units

Assume two fictional products at separate depots. Product A has 80 usable, uncommitted units available for a 100-unit order due tomorrow. An inbound receipt of 100 units was expected to support that order but is now expected two days later.

Product A has a 20-unit gap against tomorrow’s requirement. The entire delayed 100-unit receipt is not necessarily tomorrow’s shortage. The planner should focus on the quantity and timing needed to protect that commitment.

Product B has 200 usable units and 80 units of confirmed demand within the same review horizon. Its delayed inbound order does not create a shortfall in that horizon under the stated assumptions; 120 units remain after serving the identified demand.

The two delays therefore need different responses. Product A requires a recovery or customer-commitment decision. Product B may need monitoring and a later-horizon review. Neither classification should remain fixed if new demand, stock restrictions or receipt evidence changes.

Evaluate options for the exposed quantity

For Product A, the planner might assess an approved transfer, alternative supply, partial delivery or revised customer date. Each option needs its own feasibility and authority. A nearby stock balance is not a confirmed transfer, and an available carrier is not automatically suitable.

Suppose an illustrative expedite option covers the required 20 units at an incremental premium of ₹50 per unit. The additional quoted transport premium is ₹1,000. That is the amount to present for the relevant approval, alongside timing and service consequences.

The calculation does not establish that the expedite is worthwhile. The commercial owner must assess the commitment and alternatives. If the quote covers 100 units rather than 20, or includes other charges, the comparison must use the actual scope.

Avoid embedding an automatic financial penalty for every late unit unless the applicable contract and circumstances support it. Where a service consequence is qualitative or uncertain, show it clearly instead of manufacturing a precise benefit.

Replan without erasing the original commitment

Preserve the previous ETA, the revised estimate, its source and the decisions made in response. This history helps the team distinguish a supplier change from a stale internal record or a delayed notification.

A customer promise should change only through the authorised process. The planning system can propose a new date, but customer service or the responsible commercial role must handle the communication and acceptance requirements.

When a partial receipt arrives, update the actual usable quantity and review the remaining exposure. Do not close the entire inbound exception because one portion reached the gate. Similarly, a receipt placed on hold should not satisfy demand in the availability calculation.

If a recovery transfer or expedite is already approved, retain it as a commitment during subsequent planning runs. Otherwise a refreshed ETA can generate duplicate recovery orders for the same shortage.

Compare lateness reports with exception-driven replanning

A lateness report is a useful starting point for inbound follow-up. Its limitation is that it ranks dates without explaining customer or depot exposure. A planner may still need to reconstruct stock and demand manually for every row.

An ERP exception view may already connect supply dates and requirements. Test its actual availability assumptions and how it handles partial receipts, holds and changed demand. A generic warning code is not enough if the planner cannot explain the exposed quantity.

An extension can combine inbound updates with inventory and order data where the systems are separate. Its value should be demonstrated through clearer recovery decisions and less reconciliation work. It should not claim to predict all delays or resolve commercial choices automatically.

Use Products A and B as a common evaluation case. The system should identify the 20-unit immediate gap for A and the absence of a gap for B within the stated horizon, while keeping both receipt changes traceable.

Test stale estimates and conflicting updates

Replay a newer carrier message arriving before an older supplier update. The system should preserve both sources and apply the agreed source and timing rules, rather than blindly replacing the ETA with the last message received.

Test an estimate without a confirmed quantity. A delivery date for “the shipment” may not establish when every line will arrive. The inbound owner must resolve the scope before the planner relies on it.

Include an outage in the inbound feed. Missing updates should not imply that the old ETA is still dependable. The team needs a manual follow-up route and a visible age of evidence.

On recovery, reconcile actual receipts, existing recovery actions and open customer decisions before generating new recommendations. The objective is a consistent current plan, not a fresh set of actions that ignores work already done.

Assess the quality of the priority decision

Track exposed units and commitments at the decision point, recovery actions approved, avoidable duplicate actions and unresolved ETA evidence. Keep raw lateness measures as context, but do not use them alone to judge operational impact.

Review cases where the priority changed. A previously covered product may become urgent after a stock hold or a new accepted order. The system should explain that change through the inputs, not just move the row to the top of the list.

For a focused review, prepare a redacted late receipt with an immediate shortage and one without. The assessment should establish the availability calculation, review horizon and approval handoff before broader automation.

Supply replanning becomes more useful when it asks what the delay prevents the business from serving. That question directs attention to the right quantity, decision and owner.

Next actions

1. Define usable-receipt timing and the source of each ETA.
2. Connect changed receipts to stock and dated commitments within a stated horizon.
3. Compare recovery options for the actual exposed quantity.
4. Test partial receipts, stale updates and existing recovery commitments before rollout.