CSMS #59989219

Updates to Stow Plans when the Port of Arrival or Discharge Changes

· View this week in context on the trade timeline

Action requiredPolicy GuidanceLow urgency
Share this messageLinkedInEmail
CSMS # 59989219 - Updates to Stow Plans when the Port of Arrival or Discharge Changes U.S. Customs and Border Protection sent this bulletin at 03/29/2024 04:01 PM EDT CSMS # 59989219 - Updates to Stow Plans when the Port of Arrival or Discharge Changes When a vessel carrying containers updates its Stow Plan to a new port of call, the arrival port must be updated as well as the Port of Discharge (POD), if the POD does in fact change. Example: A vessel lists the arrival port on their Stow Plan as Long Beach, CA, but then diverts to call Oakland instead. The arrival port field will need to be updated. Any containers now set for discharge in Oakland will need to be updated on the POD field. Additionally, a vessel with containers calling a location that falls under a larger port code, must provide a Port of Discharge for the actual port code, not the location/terminal. Example : A vessel calling to berth at Gloucester, NJ, which falls under the Philadelphia, PA port code. Arrival port = Philadelphia POD = Philadelphia The location of where the vessel will conduct business will be captured via the berth/dock location as identified on the vessel’s entrance and clearance. Questions regarding Stow Plan updates can be directed to your assigned client representative.
Programs affected
ISF

This week in context

This message came out the week of March 23 to March 29, 2024. See that week against the 90 days before it, with every CSMS message by subject and the trade actions behind them.

Trade timeline preview: the week of March 23 to March 29, 2024 highlighted against the 90 days beforeView this week in context on the trade timeline →