Real-Time Visibility Coverage in Canada: Why 94% National is 40% Where it Counts

The number that is true everywhere and useful nowhere

A Canadian retailer reports 94% real-time visibility coverage across its shipment base. The figure is accurate, calculated consistently, and presented quarterly.

Split it by geography and it stops being one number. Coverage runs near 99% through the Windsor to Quebec City corridor and the Lower Mainland, where national carriers with mature APIs handle most volume. On long-haul movements to northern and remote destinations it sits closer to 40%, because the final leg is served by regional operators, seasonal carriers, air cargo into fly-in communities, and in some cases marine legs.

The 6% of shipments the operation cannot see is not a random 6%. It is disproportionately the freight that is worth the most, travels the longest, and is hardest and slowest to replace when something goes wrong.

So the reported number is highest exactly where a gap would cost least, and lowest exactly where a gap costs most. It is not wrong. It is weighted by shipment count, which means it describes the corridors and says almost nothing about the part of the network that actually needs watching.

Also Read: 10 Best Real-Time Transportation Visibility Platforms (2026)

Why real-time visibility coverage inverts against consequence in Canada

This inversion is structural rather than accidental, and understanding the cause matters because it determines what can be fixed.

Feed coverage follows carrier integration maturity. Integration maturity follows commercial scale. Commercial scale follows density. National parcel and LTL carriers serving dense corridors have the volume to justify building and maintaining APIs, webhook infrastructure, and event standards. The operators serving low-density geography do not, and reasonably so: a regional carrier running scheduled service to a handful of northern communities has no commercial case for an API program.

Layer Canadian geography on top and the effect compounds. A single shipment to a remote destination may change hands three times, from a national linehaul carrier to a regional operator to a local final-leg provider, with the integration quality declining at each handoff. The shipment becomes progressively less observable the further it travels from the corridor, which is precisely the opposite of what the risk profile requires.

Existing guidance in this category makes a fair point: thinner coverage from regional carriers is expected and should be planned for rather than treated as a defect. That is correct as far as it goes. The problem is not that regional coverage is thin. It is that the standard way of reporting coverage averages that thinness into invisibility, so nobody is planning for anything.

Recovery cost, not shipment count, is the right weighting

If the purpose of visibility is to enable intervention, then coverage should be weighted by what an intervention is worth. Four factors set that value.

Replacement value. What the goods cost to send again, including the freight to send them.

Remaining transit duration. A shipment two days from delivery offers a narrower intervention window than one eight days out. Long transits are where visibility earns most, and they are the ones running through thin-coverage territory.

Recovery difficulty. Whether a replacement can be dispatched at all, and how quickly. Where the destination has scheduled rather than continuous service, a missed shipment may wait a week for the next opportunity regardless of how fast the response is.

Time-sensitivity. Perishables, pharmaceuticals, and equipment holding an operation idle change the cost of a delay by an order of magnitude.

Applying these produces a different picture. Using illustrative figures to show the shape: if the 6% of shipments outside coverage carry roughly 22% of the network’s at-risk value, then consequence-weighted coverage is in the high seventies rather than at 94%. The volume-weighted number was not lying. It was answering a question nobody needed answered.

The practical instruction is simple. Report both. The volume-weighted figure tracks integration progress, which is a legitimate program metric. The consequence-weighted figure tracks risk, which is what a board is actually being asked to accept.

Also Read: The Hidden Cost of Last-Mile Visibility Gaps: Why Tracking Alone Cannot Prevent Failed Deliveries

How to represent a leg you cannot see

This is the design question the category avoids, and it matters more than closing the remaining coverage gap, because some of that gap will not close.

Most platforms render an unobserved leg as “no update since.” An operator reads that as nothing has happened. Something is happening. The shipment is moving. The operation simply is not receiving reports about it, and those are entirely different facts to hold in front of someone making a decision.

Three states need to be visually distinct.

Expected silence. The shipment is on a leg where no feed is anticipated until a known point, and it is behaving normally. A rail movement or a scheduled marine leg with no intermediate reporting is not a problem, and it should not look like one. Rendering normal operation as an absence trains people to ignore absences.

Unexpected silence. A feed that should have reported and has not. Nothing has failed in the shipment, and something has failed in the observation. This deserves an exception even though no status event says so, and it is the state most systems have no concept of at all.

Inferred position. A modelled location and status carrying an explicit confidence level and a next-expected-event time, so the operator knows both what the system believes and how much to trust it.

The distinction between expected silence and unexpected silence is the single most useful thing a Canadian control tower can draw, and almost none draw it. Knowing the difference between “we expect nothing until Thursday and that is fine” and “we should have heard by now” converts a coverage gap from a blind spot into a managed condition.

Three ways to report real-time visibility coverage

The row that changes behaviour is the last one. A gap that has been priced can be argued about: whether to fund an integration, accept the exposure, or route the freight differently. A gap reported as a percentage point of a national average cannot be argued about, because nobody can tell what it costs.

Also Read: Carrier Connectivity: Connect to Any Freight System

What to do about a leg you cannot cover

Once a gap is priced, three responses are available, and the instinctive one is frequently the weakest.

Fund the integration. The obvious move, and it is bounded by the partner rather than by your budget. A regional operator with no API program and no commercial reason to build one will not acquire one because a customer asked. Where volume on the lane is genuinely large this is worth pursuing. Where it is a handful of movements a month, it is a project that will not finish.

Substitute reporting for integration. Where an API is unrealistic, a contractual checkpoint often is not. Requiring the operator to confirm defined milestones through a portal, an email, or a phone call at agreed points converts an unobserved leg into a coarsely observed one. It is low-technology, mildly irritating to administer, and frequently the only option that actually changes the picture. Two confirmations on a five-day leg is not real-time visibility, and it is the difference between knowing on day two and finding out on day six.

Change the shipment rather than the visibility. The response nobody proposes, and often the best value. If a lane cannot be observed, reduce the number of shipments exposed to it: consolidate into fewer and larger movements, pre-position inventory closer to the destination so the unobserved leg carries replenishment rather than customer orders, or accept the exposure explicitly and insure it. Each of these lowers risk without requiring anyone to see anything.

The ordering matters because the first option absorbs most of the attention and delivers the least on exactly the lanes this piece is about. On a genuinely uncoverable leg, the useful question is not how to see the shipments but how to have fewer of them there.

Also Read: AI-Powered Last-Mile Visibility: The Final-Mile Gap

The seasonal layer nobody segments

Canadian visibility has a winter problem that is really two problems arriving together.

Feed availability falls. Weather-driven carrier substitution moves freight onto operators chosen for capability rather than connectivity, and those substitutes are frequently the ones without APIs. Seasonal road access changes which operator can serve a destination at all. Remote infrastructure is less reliable in the conditions where it is most needed.

ETA accuracy falls at the same time and for different reasons. Travel-time models trained largely on non-winter conditions systematically under-forecast winter transit. Spring adds its own version through thaw-period load restrictions, which change permissible weights and therefore which vehicle and which carrier move the freight.

Two consequences follow, and neither is usually measured.

Coverage and accuracy degrade together in the months when consequences peak, so the operation is least observant precisely when weather makes intervention most necessary. And customer notification volume rises exactly when ETA accuracy is lowest, which spends customer patience at the worst possible moment.

The fix is unglamorous: segment ETA accuracy by season and by region, and hold separate accuracy expectations for each. An annual accuracy figure averages a good summer against a poor winter and reports something that describes neither.

What to measure

Consequence-weighted coverage. Reported alongside the volume-weighted figure rather than instead of it, so integration progress and risk exposure are both visible.

Dark-leg duration, median and 95th percentile. How long a shipment goes unobserved. The tail matters more than the median, because the tail is where the northern freight sits.

Unexpected silence rate. Feeds that missed an expected report, as distinct from legs where no report was due. Most operations cannot currently produce this because they do not model expectation.

Inferred-state accuracy on resolution. When an unobserved leg finally reports, was the inferred position and status correct. This is how you learn whether an inference is worth showing.

ETA accuracy split by season and region. Four buckets minimum. An annual national figure conceals the only variance that matters operationally.

Also Read: Real-Time Delivery Visibility: 7 KPIs to Track in 2026

How Locus reports coverage you can act on

Locus, the world’s first Decision-Intelligent, Agentic TMS, is built on the position that a visibility layer should state what it knows and how well it knows it, rather than presenting uniform confidence across uneven data. Its Dispatch, Capacity, and Carrier agents, coordinated by an Orchestrator, run a continuous Sense-Decide-Execute-Learn loop against a model of more than 250 real-world constraints, with the sense stage treated as a first-class part of the loop rather than an assumed input.

Three capabilities address the Canadian pattern specifically. Carrier status normalization resolves every carrier’s proprietary event codes into one standard set, which is what makes a regional operator’s sparse reporting usable in the same view as a national carrier’s rich feed rather than excluded from it. The control tower software provides order-level and milestone-level visibility across owned fleet, contracted 3PLs, and parcel partners, including the multi-carrier handoffs where Canadian coverage degrades. And because each decision retains its inputs and the plan version it produced, an inferred state can be evaluated against what actually happened, which is the only way inference earns the right to be displayed.

Locus is 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. Further analyst recognition is published in full.

Two deployments are relevant to this pattern.

A grocery brand delivering across more than 30 Canadian cities moved fresh and perishable orders to homes through contracted 3PLs. Perishable freight is the clearest case for consequence weighting, because a delay does not degrade the outcome, it destroys the goods, and a third-party network means the operation depends on partner reporting quality it does not control. Orchestrating those carriers through one layer produced 33% faster deliveries and 15% lower fulfillment cost, with customer support resolution 10 to 20 times faster. That last figure is the intervention window widening, which is what visibility is for.

A leading North American retailer consolidated six legacy systems into one orchestration layer across multi-hundred stores and ocean, rail, and road movements. The multimodal mix matters here because rail and marine legs are exactly the movements where expected silence is normal and gets misread as a gap. Exceptions were resolved in under two hours while route compliance held above 95%, alongside $1M+ in savings and break-even inside year one.

Request a Locus visibility coverage assessment to produce a consequence-weighted coverage figure for your network, measure dark-leg duration on your remote lanes, and separate expected from unexpected silence in your current reporting.

Ask for the coverage map, not the coverage number

Before the next quarterly review, ask for your coverage figure broken out three ways: by region, by remaining transit duration, and by replacement value.

If coverage is lowest in the bucket with the highest value and the longest transit, you have the inversion described here, and the national number on the slide is describing the part of the network that was never at risk.

Then ask a second question about the shipments you cannot see. Does the system know whether it should be hearing from them right now. If the answer is that silence looks the same either way, the coverage gap is not the immediate problem. Not knowing which silence to worry about is.