Delivery and pickup date adjustments.

The problem

The owner re-dated delivery appointments in the TMS by hand, load by load, from a table he received by email. A recurring owner-level chore, done at owner-level cost.

How it works

• Paste the table, review what the tool plans to do, click Apply. Each row resolves to its single live shipment; the final stop's estimated delivery window moves to the appointment date.
• When the shipper re-tenders a load, the same reference matches several shipments. The resolver enumerates the candidates and keeps the only live one. The probe itself sends an empty update so probing can never stamp a field as a side effect.
• Two TMS landmines are documented right in the module: the endpoint re-labels wall-clock times without converting them, and there is no undo.
• Nothing writes until a human clicks Apply, loads process one at a time, and every write is read back to confirm it stuck.
• A second page handles pickup dates with the same resolver, stamping the standard 09:00 to 16:00 window on every pickup it moves.

// nothing writes until a human clicks Apply; every write is read back to verify

The result

The owner's manual re-dating chore replaced by paste, review, apply. In daily use by the owner, who found two edge cases in his first week; both shipped as fixes the same day.