This is the most common cause of a shipment with no data. If the carrier does not recognise the B/L or booking number you supplied, Dockflow has
nothing to show.
Three variants, all seen regularly:
- A mistyped B/L. A single wrong character is enough. One case was a missing trailing zero:
the shortened number was unknown at the carrier, so tracking stopped. - The carrier has not released the B/L yet. The number is correct but not yet active on their
side. This resolves on its own once they publish it. - The number belongs to a different shipment. Check it against the carrier’s own tracking page
first. That is the fastest way to separate a bad reference from a platform issue.
What to do: verify the reference on the carrier’s tracking page. If the carrier returns
nothing there either, correct the reference in Dockflow. If you also have the container number, remove the unrecognised B/L. That often recovers the shipment immediately.
If you have both a B/L and a container number, keep the container number. It is the more reliable
of the two when a carrier is being difficult.
Example
A user supplies a B/L number, but the carrier does not recognise it and returns nothing. The user checks the carrier’s tracking page, sees no result there either, and corrects the reference in Dockflow. Because the user also has a container number, they keep that number, since it is the more reliable option when the carrier is difficult.