When creating an Amazon FBA shipment, the freight-ready date field can become frozen — displaying an old date and refusing to update even after logging out, logging back in, or refreshing the browser. This is a known UI bug in Amazon's shipment creation flow.
The fix is counterintuitive: changing the contact information on the shipment triggers a page refresh that forces the freight-ready date field to repopulate with the correct, current date.
During shipment creation, the freight-ready date is set at a later step in the workflow. If the shipment was started on an earlier date and left incomplete, the date field can freeze to that original creation date. Standard remedies — browser refresh, logout/login, switching carriers and switching back — do not resolve it.
Deleting and recreating the shipment is technically an option, but it is often not viable because:
In one instance, 9 of 11 shipments in a single send (totalling ~64 boxes) were affected, with dates frozen from the prior week.
Repeat for each affected shipment. The fix takes only seconds per shipment once the trigger is known.
"There's always something on the page that if you change it, it refreshes. But it's totally counterintuitive — who'd have thought changing the contact would do it?"
— Mark Hope, [1]
Amazon's shipment workflow uses partial page refreshes driven by field-change events. Certain fields — including contact information — trigger a broader data reload when modified. The freight-ready date field depends on this reload to pull current availability. Standard browser refreshes do not fire the same event, which is why they fail to resolve the freeze.