# Why do shipments on the same vessel show different ETAs?

**URL:** <https://community.dockflow.com/t/why-do-shipments-on-the-same-vessel-show-different-etas/158>\
**Category:** How-to Q&A\
**Tags:** vessel-changed, area-vessel-ais\
**Created:** [November 6, 2026, 3:17pm UTC](https://community.dockflow.com/t/why-do-shipments-on-the-same-vessel-show-different-etas/158 "2026-11-06T15:17:23Z")\
**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:17pm UTC](https://community.dockflow.com/t/why-do-shipments-on-the-same-vessel-show-different-etas/158/1 "2026-11-06T15:17:23Z")

</div>

This is expected. With per-tradeflow tracking you see exactly what the sources on _your_ booking  
reported, so shipments on one vessel can legitimately carry different ETAs for the same port  
call. Per-vessel tracking pools them into one consensus time instead. Which you get is an account  
setting - see  
[vessel schedule intelligence](https://docs.dockflow.com/features/vessel-schedule-intelligence/).

**Example**  
A forwarder tracks bookings under per-tradeflow tracking and sees the ETA each source reported for its booking, so shipments on the same vessel can show different ETAs for the same port call. Switching to per-vessel tracking pools those reports into a consensus time instead; which view appears depends on the account setting.