Real-Time Visibility Across the Great Britain and Northern Ireland Divide: Where the Status Chain Breaks

What the tracking gap actually is

A shipment leaves a GB distribution centre for a Northern Ireland customer. The carrier scans it out. Events flow normally for a while. Then they stop.

At some point later, events resume and the delivery completes, or it does not. Nobody watching the tracking view can tell, during the silence, whether the shipment is progressing normally, sitting in a queue, or held pending a documentation query.

This is not a carrier failing to report. The carrier is reporting its own legs competently, and the interval between those legs involves documentation and clearance processes performed by parties who are not the carrier and who generate no events in the carrier’s stream. From the tracking system’s perspective the shipment has simply gone quiet, which is indistinguishable from a feed outage.

Operations teams learn to interpret the silence, and that works until volume grows past the point where interpretation scales, or until a customer asks a question during it.

The administrative weight behind these processes is documented. The UK National Audit Office estimated that when fully implemented, post-EU exit customs controls will cost traders approximately 469 million pounds a year. And the friction has proven persistent: the British Chambers of Commerce has found that 45 percent of UK exporters still cite customs procedures as their biggest barrier to trade with the EU.

Also Read: The 28-Interpretation Problem: Why EU Compliance Isn’t One Compliance Standard

Why a domestic status model cannot represent it

Most UK operations run a status taxonomy built for domestic movement: collected, in transit, at delivery depot, out for delivery, delivered, with exception states for failures.

There is no state in that list for “in documentation” or “awaiting clearance.” So even where the information exists somewhere, whether in a broker’s system, a forwarder’s portal, or an email, there is nowhere in the operational record to put it. The shipment holds its previous status while something is happening to it.

Three consequences follow, and each one compounds the last.

You cannot distinguish normal from stalled. Without an expected duration for the stage, a two-hour gap and a two-day gap look the same until the second becomes obvious for other reasons.

You cannot attribute the delay. When the shipment eventually arrives late, the carrier’s data supports the carrier’s position and there is no record of the interval where the time was actually lost.

You cannot tell the customer anything useful. The most valuable message in this situation is a revised time with a reason, and the operation has neither.

The wider pattern is that visibility platforms aggregate what carriers report, which improves coverage of the legs and leaves the transitions between them exactly as dark. Gartner found that only 22 percent of shippers with more than 1 billion dollars in revenue believe their supply chain control tower is highly effective at driving action.

What to model

Four additions, and the first is the prerequisite for the rest.

A clearance state as a first-class status. With an entry event, an exit event, and its own exception reasons: documentation query, inspection, held pending information, released. Until the state exists, there is nowhere to attach a duration or a threshold.

Expected duration per lane and direction, from your own history. GB to NI and NI to GB behave differently, and so do different consignment types and different times of week. Your own data is the only credible source, since no published benchmark for these lanes exists at research grade.

Threshold-based exception detection calibrated to the lane. A domestic threshold applied here will either fire constantly or never. Set it from the observed distribution rather than from the domestic default.

Non-carrier event ingestion. Somebody knows what is happening during the gap, whether a broker, a forwarder, or a customs agent. If the only integration is to carriers, the operation is structurally limited to what carriers report regardless of platform quality.

Also Read: Cross-Border Fulfilment and Returns in Europe: The Operational Complexity Reality for E-Commerce Operations Heads

The promise problem

The customer-facing consequence is worth separating out, because it is where the cost lands.

A delivery promise for a GB to NI lane built on GB domestic transit assumptions will be optimistic, because it excludes a stage with real duration and real variance. The result is not occasional lateness but systematic lateness on a specific set of lanes, which customers experience as unreliability rather than as complexity.

Two design responses. Compute the promise for these lanes against observed end-to-end transit including the clearance stage, rather than applying a domestic lead time with a buffer. And widen the window on these lanes rather than narrowing it, since a held Thursday promise outperforms a missed Tuesday one on every measure that matters.

The customer preference supports the trade. McKinsey found that speed fell from consumers’ number one delivery priority in 2022 to fifth by 2024, displaced by reliability and predictability, with around 90 percent of consumers willing to wait two to three days when delivery is free and arrives within the stated window.

And the loyalty consequence of getting it wrong is asymmetric. Gartner’s customer effort research found 96 percent of customers who have a high-effort service experience become disloyal, against 9 percent of those with a low-effort experience. A customer chasing a parcel through an unexplained silence is having a high-effort experience produced by an information gap rather than by a delivery failure.

What to measure

Four measures, all specific to these lanes and none of which appear in a blended UK report.

Silent interval duration, meaning the elapsed time between the last event before the gap and the first event after it. This is the number that quantifies the problem, and most operations have never calculated it.

Silent interval variance. A consistent interval is a duration you can plan around. A highly variable one is where promises are being invalidated, and the variance matters more than the mean.

Promise accuracy on GB to NI lanes specifically, separated from domestic. Blending them conceals the pattern, since domestic volume will dominate the average.

Proactive rate during the silent interval, meaning the share of cases where you told the customer something before they asked. This will start near zero, which is itself the finding.

Also Read: Multi-Carrier Unified Visibility in 2026: From Fragmented Carrier Tracking to Unified Architecture

Where Locus fits

Locus, the world’s first Decision-Intelligent, Agentic TMS, represents a shipment as connected legs rather than as separate records, which is the structural requirement for modelling a stage that sits between two carrier legs.

Within DiSCO, the Hub agent manages facility-side constraints and multi-leg handoffs as one chain of custody, the Dispatch agent recalculates downstream feasibility when an upstream stage runs long, and the Customer agent issues the revised commitment. Carrier statuses are harmonised into one taxonomy at ingestion, which is what allows a non-carrier event to occupy a modelled state alongside carrier events rather than sitting outside the record.

Locus has been recognized by Gartner for seven consecutive years, featured in the 2026 Hype Cycle for Supply Chain Execution and Logistics Technologies, named a Leader in TMS by QKS Group (SPARK Matrix), and ranked #1 in Route Planning on G2’s 2026 Best Software Awards. In October 2025, Ingka Investments, the investment arm of Ingka Group, the world’s largest IKEA retailer, acquired Locus. Locus continues to operate independently.

Two deployments show the mechanism, in other geographies with the same structural problem. A leading North American retailer moved freight across ocean, rail, DC, hub, and store with nothing tracking it end to end, so exceptions surfaced only after delays had reached store service. With the Hub agent orchestrating transit stages as a single chain, on-time delivery passed 99 percent with exceptions resolved in under two hours across the network.

A Fortune 50 parcel and logistics provider integrates Locus with legacy systems including customs alongside live regulatory feeds, across a 120-country network moving 1M+ freight shipments a year. That customs integration is the closest available analogue to the requirement described here: clearance data reaching the layer that plans rather than sitting in a separate system.

Also Read: The Delivery Promise Paradox: Why UK Retailers Keep Promising Speed Their Networks Can’t Support

The calculation to run this week

Take a month of GB to NI shipments and measure the interval between the last carrier event before the gap and the first after it. Then plot the distribution.

That distribution is your blind spot, quantified in hours, and its width tells you how much of your promise accuracy problem on these lanes is attributable to a stage your systems do not represent.

If your current platform cannot produce that measurement, you have established something useful about the platform as well.

Also Read: TMS for UK Operations: The Constraints Generic European Platforms Don’t Model