Tracking Event Quality

The Tracking Event Quality concept helps a freight operations team understand what happened when a connected sender delivered tracking updates. A repeated delivery should not quietly add another copy of the same keyed event. A changed payload under an existing key needs a visible conflict rather than an overwrite. This illustration brings accepted updates, duplicates, conflicts and rejections into one readable review, using fictional shipments and event keys.

The sample screen presents four outcome cards above a delivery table. Each row pairs its event key and shipment with an outcome and a plain explanation of the tracking result. A highlighted conflict opens a detail panel showing that the key matches an existing delivery while its payload differs. The panel states that no tracking event was added and asks the operator to review the incoming reference before linking a shipment. Notes explain that updates without an event key are not deduplicated, and that a delivery exceeding five updates is rejected before any updates are applied.

An operator selects an integration, inspects the ordered outcome of every update in each delivery, and opens the shipment summary behind any resolved outcome when their permissions allow it. Identical keyed repeats reuse the original result, and conflicts are held for reconciliation rather than overwriting the original event. Late updates never silently rewind status, and every event shows its source and freshness. The illustration uses fictional shipments, keys and counts.