After the dispatch plan is released, vehicles, carrier resources or loading conditions may change temporarily. Changing the resource number directly will cause the previous confirmation to lose association with the voucher. The TMS should retain the change process so that the site knows which arrangements are valid and which requirements need to be re-examined.

How to arrange records and operations

Check load, volume and cargo restrictions before changing resources, and check whether task time conflicts. Loaded tasks record unloading or transfer steps, and change notifications include new resources and affected goods. The effective execution arrangements will be updated after the shipping confirmation is re-completed, and the old records can still be queried.

The availability period, loading conditions and associated tasks of the capacity resource should be checked together before replacement. When the same vehicle already has other valid tasks, the system prompts an occupancy conflict; when changing a trailer or other load-bearing equipment, the cargo conditions must also be checked. Resource adjustment after departure is an execution event, which records the goods delivery location and actual receipt. You cannot just modify the plan fields. The scheduling interface displays resources before and after replacement side by side, and notifies relevant positions to re-confirm handover and voucher arrangements to prevent documents from still referencing invalid resources.

Specific scenarios that need to be checked

For example, if the original resource is temporarily unavailable and the new resource capacity is insufficient, the test should prevent silent replacement and support reasonable splitting of tasks. Acceptance covers both situations before and after departure, as well as the status after the change is rejected. Key credentials are associated with actual execution resources and cannot only refer to the current plan fields.