# Why does my tradeflow show a transhipment the carrier skipped?

**URL:** <https://community.dockflow.com/t/why-does-my-tradeflow-show-a-transhipment-the-carrier-skipped/133>\
**Category:** How-to Q&A\
**Tags:** data-differs-from-carrier, area-tracking-data\
**Created:** [November 6, 2026, 3:04pm UTC](https://community.dockflow.com/t/why-does-my-tradeflow-show-a-transhipment-the-carrier-skipped/133 "2026-11-06T15:04:28Z")\
**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, 3:04pm UTC](https://community.dockflow.com/t/why-does-my-tradeflow-show-a-transhipment-the-carrier-skipped/133/1 "2026-11-06T15:04:28Z")

</div>

A routing can list a transhipment that the carrier later drops. The carrier’s own site sometimes  
keeps showing the original call for a while. A tradeflow can therefore show a leg that no longer  
happens, or show a routing that no longer matches the carrier page.

The same pattern occurs when a container is first assigned to one booking and later moved to  
another shipment.

**Example**  
A routing lists a transhipment, but the carrier later drops it. The carrier’s site still shows the original call for a while, so the tradeflow displays a leg that no longer happens and a routing that no longer matches the carrier page. Later, the container is moved from a booking to another shipment, and the same mismatch appears.