Antwerp can arrive with a code other than the port code BEANR

Status: Fixed since May 2026

How to recognise it
A shipment through Antwerp could show a location code you did not expect, or the plan could look as if the container visited two different places in the same port. The stop itself was correct, but it did not read as the port of Antwerp.

Which shipments this affects
Shipments through Antwerp where a location arrives with a code for a place inside the port, such as BEANT, instead of the port code.

Cause
Terminals and other locations inside a large port can carry a code of their own. The port of Antwerp itself is BEANR, and BEANT is one of the codes that points inside it.

What changed
Dockflow now reads BEANT as the port of Antwerp, code BEANR, so the plan shows one port for these stops.

Is past data corrected?
No. The fix applies from that month on; earlier data stays as it was.

How to check your shipment
Open the shipment and check that the stop reads Antwerp, BEANR. If the plan still shows two places for one port call, contact support with the reference.

Do you need to do anything?
Nothing.