# How should I report a merged shipment or a transhipment after the final port when the Console already classes it as an anomaly?

**URL:** <https://community.dockflow.com/t/how-should-i-report-a-merged-shipment-or-a-transhipment-after-the-final-port-when-the-console-already-classes-it-as-an-anomaly/147>\
**Category:** How-to Q&A\
**Tags:** data-is-wrong, area-tracking-data\
**Created:** [November 6, 2026, 3:08pm UTC](https://community.dockflow.com/t/how-should-i-report-a-merged-shipment-or-a-transhipment-after-the-final-port-when-the-console-already-classes-it-as-an-anomaly/147 "2026-11-06T15:08:30Z")\
**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:08pm UTC](https://community.dockflow.com/t/how-should-i-report-a-merged-shipment-or-a-transhipment-after-the-final-port-when-the-console-already-classes-it-as-an-anomaly/147/1 "2026-11-06T15:08:31Z")

</div>

These are worth reporting: merged shipments, milestones in an impossible order, a plan that starts and ends at the same port, or  
a transhipment appearing after the final port. These have names and a definition - see  
[anomaly classification](https://docs.dockflow.com/console/data-quality/anomalies/) - and reporting them with the reference is  
the right move.

**Example**  
A shipment’s milestones appear in an impossible order, and a transhipment is shown after the final port. Because the Console already classes these as anomalies, the reviewer checks the anomaly classification and reports the issues using the matching reference rather than describing them from scratch.