This is the most common cause of containers you did not expect. If more than one booking or B/L arrives on the same file, Dockflow tracks them all,
and the containers from each are attached to the tradeflow.
The symptoms are recognisable:
- containers appear that belong to a different file
- the destination looks wrong, because the second booking has a different port of discharge
- the vessel or ETA does not match what you expect, because it belongs to the other booking
A related variant: a container is removed from a file, but the booking it came in on stays active.
A newly added container then attaches to the shipping information from the old booking, and the
tracking follows the wrong journey.
What to do: identify which reference is correct and remove the other. Once the incorrect
booking or B/L is gone, Dockflow retrieves tracking for the remaining one. If the tradeflow was
created with one reference and corrected to another shortly after, both may still be present.
Example
A tradeflow shows containers that belong to a different file, and the destination, vessel, or ETA does not match expectations. An incorrect booking or B/L remains attached, so Dockflow attaches containers from each reference to the tradeflow. Identify the correct reference and remove the other; tracking then follows the remaining reference.