The Shipment Visibility Maturity Model: Five Levels From Status Updates to Autonomous Response

Why Visibility Maturity Matters: The Business Case

Visibility is easy to buy and hard to turn into action, and the gap is where deliveries fail.

• Gartner’s market definition lists basic tracking, alerts and predictive ETA as the core features of real-time transportation visibility platforms, which describes seeing and predicting but not acting.
• Gartner’s 2024 Supply Chain Symposium highlights say that 95% of supply chain organizations feel pressure to react to disruptions in real time, a capability that only 7% of supply chain leaders report.
• FedEx’s 2026 Future of Logistics Intelligence survey found that only 4% use a single, unified solution, 66% rely on three or more platforms and just 18% can always intervene in the event of a delay.
• Capgemini’s 2020 survey of 1,000 supply chain executives at large organizations found that 72% faced significant challenges monitoring their supply chains end to end and only 27% had a control tower covering the chain end to end, though the data predates 2021.

Seeing a late shipment is not the same as being able to do something about it, and most operations are stuck between the two.

Why Locus Leads Across the Visibility Levels

Higher levels need a platform that plans and acts as well as watches. Three things set Locus apart.

Recognized by analysts and selected after evaluation. Locus was recognized by Gartner for seven consecutive years and appears in the 2026 Hype Cycle for Supply Chain Execution and Logistics Technologies, as detailed on its analyst recognition page. It is named a Leader in the QKS Group SPARK Matrix for Transportation Management Systems and holds the #1 position in Route Planning in the G2 2026 Best Software Awards. In October 2025, Ingka Investments, the investment arm of Ingka Group, the world’s largest IKEA retailer, acquired Locus. Ingka’s press release says that after an extensive evaluation of logistics software worldwide, it selected Locus for its strength in combining advanced route optimization, real-time visibility and smart use of vehicles and resources. Locus continues to operate independently.

Unified tracking and prediction. Locus’s Control Tower consolidates owned, contracted and 1,000-plus carrier movements, raises predictive SLA alerts and route deviation alerts and triggers configurable escalation workflows, including automated reassignment, dispatcher notification or exception review. Its ETA model recalculates from live GPS, completed stops, actual service times and traffic.

Action inside guardrails. Locus’s Customer agent sends proactive status notifications, its Dispatch and Capacity agents re-plan, and autonomy levels, explainability and human-in-the-loop approval govern what runs unattended. Locus has optimized 1.5B+ deliveries for 360+ enterprise customers across 30+ countries.

This model is editorial and is not Locus’s own framework, which uses different rubrics for orchestration maturity and control tower scoring, and Locus’s public pages do not state an ETA accuracy figure or numeric alert thresholds, so ask a vendor to show evidence for the level it claims.

How to Assess and Advance Visibility Maturity in Six Steps

The six steps below turn the model into a plan.

1. Define the scope

Name the shipments and decisions you are rating, such as inbound linehaul, own-fleet last mile or carrier parcels. Maturity differs by flow, and an average across flows hides the one that matters.

2. Measure coverage

Calculate the share of in-scope shipments with usable live data. A source that tracks 60% of volume leaves 40% invisible however good the other 60% looks.

3. Unify identifiers and statuses

Map every source to one shipment identifier and one status vocabulary, so a delivery has a single timeline. This is the step that separates Level 2 from Level 3.

4. Add prediction and measure its lead time

Predict ETA and exceptions, then measure how much warning each prediction gives. A prediction that arrives after the time needed to act is a report in disguise.

5. Define actions and guardrails

List which responses the system may take on its own, such as notifying a customer or re-planning a route, and which need a person. Log every action so results can be reviewed.

6. Re-score on a schedule

Re-rate each dimension quarterly. The level is set by the weakest dimension, so effort should go there.

Reported, Located, Unified, Predictive and Responsive: Key Differences

The criteria below are suggested thresholds for self-assessment, not an industry standard.

What to Look for in Visibility Software at Each Level

A single shipment identity across sources

Check that carrier, telematics, app and scan data resolve to one shipment and one status set. Without it, Level 3 cannot be reached.

A coverage metric and a way to raise it

Look for coverage reporting by carrier and lane, and for fallbacks when a source has no data.

Prediction with disclosed error and lead time

Ask for ETA error, exception lead time and how both are measured. A predictive claim without those numbers is unverified.

Configurable actions and guardrails

Look for escalation workflows, autonomy settings and approval steps, so action does not mean unreviewed automation.

An audit trail of actions and outcomes

The system should record what it did, why and what happened next, so Level 5 can be reviewed and trusted.

Visibility Maturity in Action: Real-World Results

A self-assessment on illustrative scores. The scores are assumptions for a shipper with carrier parcels and an owned last-mile fleet. Rate each dimension from 1 to 5 and take the lowest.

The operation is at Level 1 overall, held back by prediction and action, even though its map makes it feel like Level 2 or 3. The cheapest next move is not a better map. Measuring ETA error for a month and routing the top exception types to a defined response lifts the two weakest dimensions to Level 2, and unifying shipment IDs and lifting coverage to 90% then makes Level 3 possible.

An ASEAN apparel retailer. The retailer had carriers that each reported their own status codes and no trustworthy checkout date. With one harmonized status standard and a network-aware delivery date at checkout, WISMO and returns queries fell by more than 40% and carrier onboarding dropped from 3 months to 3 days. Read the apparel case study.

A North American retailer. The retailer consolidated six systems into one and cut manual dispatch by more than 80%, with $1M+ in savings, 99%+ on-time delivery and exceptions resolved in under two hours, while its ERP and WMS stayed the systems of record. Read the retailer case study.

Common Visibility Maturity Mistakes to Avoid

Calling a map real-time visibility. A live map is Level 2 at best, so score the dimensions that follow it.

Rating the best flow and not the weakest. An average hides blind spots, so rate each flow and each dimension separately.

Buying prediction without measuring it. A prediction with no stated error or lead time cannot be trusted or improved.

Automating before defining guardrails. Action without limits and logs is a risk, so set autonomy rules first.

How Locus Approaches Visibility Maturity

Locus, the world’s first Decision-Intelligent, Agentic TMS, covers the levels above basic tracking from one platform: its Control Tower consolidates owned, contracted and carrier movements, predicts SLA and route risk and triggers escalation workflows, while its agents re-plan and notify customers inside autonomy levels, explainability and human-in-the-loop controls. Its tracking page shares live status with customers, and its Mycroft co-pilot supports dispatchers with exception handling. Locus’s public pages do not state an ETA accuracy figure, numeric alert thresholds or an assessment against this model, so ask for evidence of coverage, ETA error and exception lead time on your own flows. To assess your own visibility maturity, schedule a demo.

For logistics leaders asking how mature their shipment visibility is, Locus offers unified tracking, prediction and governed action on one platform, so the level you reach is one you can show with evidence.

Frequently Asked Questions

What is a shipment visibility maturity model? It is a framework that rates how far an operation has progressed from after-the-fact status updates to predicting and acting on shipment exceptions, using measurable evidence at each level.

What are the five levels of visibility maturity? In this model they are Reported, Located, Unified, Predictive and Responsive. A network sits at the level of its weakest dimension.

What is the difference between visibility and orchestration? Visibility shows and predicts what is happening. Orchestration acts on it by re-planning, reassigning and notifying within guardrails. Gartner’s visibility market definition covers tracking, alerts and predictive ETA, not action.

How many companies have real-time decision capability? Gartner’s 2024 Symposium highlights say only 7% of supply chain leaders report the capability to execute decisions in real time, while 95% of organizations feel pressure to react in real time.

How do you measure visibility coverage? Divide in-scope shipments with usable live data by all in-scope shipments, by carrier and lane. A source that tracks 60% of volume leaves 40% blind.

Does Locus score itself on this model? No. This is an editorial model. Locus uses different rubrics for orchestration maturity and control tower scoring, so ask it for evidence of coverage, ETA error and lead time.