# Why did containers I never uploaded appear under my B/L?

**URL:** <https://community.dockflow.com/t/why-did-containers-i-never-uploaded-appear-under-my-b-l/96>\
**Category:** How-to Q&A\
**Tags:** area-tracking-data\
**Created:** [November 6, 2026, 2:47pm UTC](https://community.dockflow.com/t/why-did-containers-i-never-uploaded-appear-under-my-b-l/96 "2026-11-06T14:47:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dockflow](https://community.dockflow.com/letter_avatar_proxy/v4/letter/d/a9a28c/32.png) [@dockflow](https://community.dockflow.com/u/dockflow)\
**Post date:** [November 6, 2026, 2:47pm UTC](https://community.dockflow.com/t/why-did-containers-i-never-uploaded-appear-under-my-b-l/96/1 "2026-11-06T14:47:39Z")

</div>

Extra containers on a B/L are usually not a fault. By default, Dockflow tracks every container the carrier reports under the booking or B/L you sent, not only the ones you listed. If you want only the containers you supply, tick the setting “Do not import unknown containers from booking and B/Ls” under Power Settings → Organisation. That setting is off by default and you can change it yourself.

If the containers do not belong to that B/L at all, check these causes:

- Multiple bookings may have reached the same tradeflow. Identify which reference is correct and remove the other.
- A container may not belong to the booking according to the carrier. It is marked with the container not in booking/BL flag and gets no tracking data. If the link is wrong, correct it yourself. If the link is right and the carrier disagrees, tell support.
- The same container may appear in several shipments because containers are reused across journeys. Supply a booking or B/L reference wherever you have one.

**Example**  
A B/L upload lists a container, but the carrier reports more containers under that B/L. Dockflow shows them by default. If those extra containers are not wanted, the organisation setting is ticked so only supplied containers are tracked. If a container has no data and carries the container not in booking/BL flag, the link is corrected if it is wrong, or support is told if the link is right.