What happens when delivery instructions change after dispatch?

A customer asks a logistics service to deliver shipment `SHP-2187` to a staffed reception desk instead of a loading bay. A customer service officer opens `CASE-0412`. The shipment has already moved from warehouse control to a driver's active route.

The customer profile accepts the new delivery preference, but changing that profile does not amend the dispatched job. The officer must submit a route amendment linked to `SHP-2187`. The dispatch coordinator can accept the amendment, reject it because access is unsuitable, or leave it awaiting driver acknowledgement.

The environment's state changes from an unrecorded request to a pending operational amendment. Until acknowledgement arrives, the existing delivery instruction remains active. Closing the case as completed would conceal an unresolved handover and could send the shipment to the wrong entrance.

A generated environment could let the agent inspect dispatch status, lodge the amendment and respond to its outcome. The scenario teaches that authority moves between roles as work progresses. An agent must identify who can now execute the change and communicate the difference between a requested update and a confirmed delivery instruction.