12 Real-Time Metrics to Track on a Logistics Visibility Dashboard

Most retail logistics teams track more numbers than they act on. Carrier scorecards, weekly SLA reports, and end-of-day exception summaries all produce data. None of it reaches dispatchers in time to prevent the SLA breach that shows up in the Monday morning review.

A logistics visibility dashboard solves a different problem. Its job is to show your ops team, in real time, what is happening right now and what requires immediate attention. The metrics you put on it determine whether your team monitors or acts.

This guide defines the 12 real-time ops metrics your dashboard should include, explains the layout and hierarchy that makes them actionable, and shows how to sequence the rollout for immediate impact.

Why a Logistics Visibility Dashboard Matters for Retail Ops

Retail delivery networks operate under two pressures that other industries manage less acutely:

1. Customer expectations for delivery accuracy and communication are high, and missed windows can increase customer-service contacts and damage delivery satisfaction
2. Retailer compliance programs impose financial penalties for delivery windows that are missed, creating a direct cash cost for every SLA failure that goes uncorrected

Both pressures require the same thing: your ops team needs to know about a potential failure before it becomes an actual one. That means real-time data and the right metrics, not a comprehensive list of every data point your systems produce.

The metrics on your dashboard should answer two questions: what is happening in the network right now, and which specific situations require immediate action? Everything else belongs in a reporting tool.

Also read: What is Retail Logistics? A Complete Guide

Real-Time vs. Lagging Metrics: The Consequence Gap

A lagging metric tells you what happened after the fact. Your end-of-day OTIF report tells you how many deliveries missed their windows on Tuesday. That information is useful for trend analysis, carrier reviews, and process improvement, but not for preventing Wednesday’s SLA failures.

The consequence of operating on lagging metrics is a specific kind of loss. You cannot prevent a chargeback when you learn about the missed window after the window closed. You cannot redirect a driver when you learn about the failed delivery from a customer call. You cannot fix an ETA calculation error that has already generated a customer notification promising delivery at the wrong time.

Real-time metrics close that gap by moving the detection window from hours to minutes. An OTIF deviation detected at 10 AM on a delivery with a 1 PM window leaves time to intervene. The same deviation detected in an end-of-day report does not. This is the Consequence Gap: the window between when a problem occurs and when your team learns about it. The financial and operational cost of the consequence gap is precisely the value that a real-time dashboard delivers.

The design principle that follows from this is straightforward: every metric on your dashboard should be sourced from live data, and every metric should have a defined threshold that triggers an alert when crossed. A number with no threshold is a data point, while a number with a threshold and an alert is an operational signal.

Also read: Delivery Notification Architecture: European Retail

The 12-Metric Logistics Visibility Framework

The 12 metrics below group into four areas: delivery performance, accuracy, exceptions, and efficiency. The quick-reference table summarizes each metric’s definition and the action it should trigger.

Metric	Category	What It Measures	Primary Action It Triggers
1. OTIF	Delivery performance	Percentage of deliveries completed on time and in full within the agreed window	Drill down by carrier, route, and store to locate the failure point
2. ETA accuracy	Accuracy	Gap between predicted and actual arrival time for each delivery	Review routing model inputs, carrier data quality, and service-time estimates for affected routes
3. Delivery exceptions	Exceptions	Volume and type of events that deviate from the planned delivery path, tracked by severity and age	Segment by exception type and severity to trigger the appropriate resolution workflow
4. Projected SLA-breach risk	Exceptions	Number of active deliveries currently predicted to miss a committed window	Prioritize at-risk deliveries for dispatcher review and corrective action while recovery is still possible
5. First-attempt delivery success rate	Delivery performance	Percentage of deliveries completed successfully on the first attempt, with failure causes tagged by root cause	A below-target rate triggers route, zone, and driver investigation; the failure-cause breakdown guides upstream fixes
6. On-time pickup/dispatch rate	Delivery performance	Percentage of pickups or route departures completed within the scheduled window	A low rate for a carrier or depot triggers a capacity or scheduling review
7. Fleet/vehicle utilization	Efficiency	Used capacity against planned or available capacity for each vehicle per shift	Under-utilization prompts route re-clustering; over-utilization flags capacity risk
8. SLA adherence by commitment type	Delivery performance	Percentage of each defined SLA tier (2-hour, same-day, next-day) met within its specific parameters	Declining adherence for a specific tier triggers a review of that tier’s route planning and carrier assignment
9. Estimated cost per delivery	Efficiency	Current estimated logistics cost divided by completed deliveries, updated periodically as cost data settles	Rising estimated cost without a corresponding volume increase prompts a review of carrier and routing efficiency
10. Dwell/turnaround time	Efficiency	Time spent at a stop or hub beyond the planned transit duration	Persistent excess dwell at specific nodes triggers a process or site access investigation
11. Route plan adherence	Accuracy	Deviation between dispatched and executed routes by stop, sequence, and timing	Large, recurring deviations on specific routes trigger a review of planning inputs
12. Exception recovery rate	Exceptions	Percentage of at-risk or exception-flagged deliveries resolved within the original or revised commitment window	A declining recovery rate indicates that the response workflow is not converting alerts into corrective outcomes

12 metrics for a retail logistics visibility dashboard, grouped into four operational categories

1. On-time in-full (OTIF)

OTIF in retail measures the percentage of orders or deliveries completed within the agreed time window and with the complete expected quantity. It is the primary SLA metric for retail delivery networks because it captures both timing and completeness in one number. Some retailer compliance programs and customer SLA contracts use OTIF or related service measures when assessing performance or financial penalties.

When OTIF drops below your defined threshold, the dashboard should immediately surface the contributing deliveries and allow drill-down by carrier, store, route cluster, and time window. The goal is to identify whether the failure is concentrated in a specific area or is network-wide, because the corrective action differs significantly between the two.

2. ETA accuracy

ETA accuracy measures the difference between the predicted arrival time shown to the customer and the actual delivery time. Inaccurate ETAs create two separate problems: customer dissatisfaction when the delivery does not arrive when expected, and downstream planning errors when store or warehouse teams schedule based on the stated ETA.

Persistent ETA inaccuracy on specific routes can indicate weaknesses in travel-time assumptions, service-time estimates, carrier data quality, geocoding accuracy, or update frequency. The root cause affects which input needs correcting, which is why the investigation should start at the route and carrier level.

The action is to review and correct the inputs feeding the routing model for the affected routes and carriers.

3. Delivery exceptions

Delivery exceptions are events that deviate from the planned delivery path. On a visibility dashboard, the exception metric should show total exception volume and a breakdown by type: ETA drift, failed attempt, carrier capacity gap, address or data error, and compliance failure.

The exception-type breakdown is the primary action signal. A spike in address errors requires a different response than a spike in carrier capacity gaps. The dashboard should surface exceptions in real time with type classification, severity rating, age, and recovery status so your team can trigger the appropriate resolution workflow without manual triage.

Exception count alone can rise simply because detection has improved; severity and age prevent a growing exception queue from masking the fact that fewer high-impact issues are slipping through.

Also read: Delivery Tracking Software: What Enterprises Must Know

4. Projected SLA-breach risk

Projected SLA-breach risk is the number of active deliveries currently predicted to miss a committed delivery window, based on live route progress, current position, and ETA calculations. It is the only metric on this list that enables intervention before the breach rather than after. OTIF tells you what happened.

Projected SLA-breach risk tells you what is about to happen. A dispatcher who sees six deliveries projected to miss their 2 PM windows at 11 AM has time to re-sequence, escalate, or communicate. A dispatcher reading the previous day’s OTIF report at 9 AM does not. This is the metric that should sit in the most prominent position on the live operations view, not buried beneath rolling outcome averages. 

5. First-attempt delivery success rate

First-attempt delivery success rate is the complement of the failed delivery metric: the percentage of deliveries completed successfully on the first attempt. It is the single strongest indicator of delivery efficiency because it captures whether your network is delivering orders correctly the first time without the extra cost and CX damage of re-attempts.

When first-attempt success falls below target, investigate by route, zone, time window, and carrier. A fall concentrated in a specific time window often indicates that delivery windows are being scheduled too tightly for the route density in that zone. Customer unavailability points to ETA communication or slot-selection problems upstream.

Address errors point to data quality at order capture or dispatch. Access restrictions point to delivery instruction gaps. Each cause has a different resolution path, which is why raw failure count is less useful than failure count by root cause. 

6. On-time pickup/dispatch rate

On-time pickup rate measures the percentage of pickups completed within their scheduled window. It is an upstream leading indicator: a late pickup does not guarantee a late delivery, but it increases the probability.

In a high-volume retail network, monitoring pickup rate in real time gives dispatchers the advance warning they need to adjust downstream plans before a cascade of delays materializes.

Low pickup rates concentrated in a specific carrier or depot typically indicate a scheduling or capacity mismatch between the committed pickup window and the carrier’s available resources at that time.

Also read: Boost Retail Deliveries with a Transportation System

7. Fleet/vehicle utilization

Fleet utilization measures used capacity against planned or available capacity per vehicle per shift. Capacity may be measured by stops, weight, cube, pallets, or driver hours depending on the operation. Choose the denominator that reflects your network’s primary constraint.

It sits at the intersection of service performance and operating cost: a vehicle running at low utilization is not covering its fixed cost; a vehicle running above capacity risks delivery quality and driver compliance.

When utilization is persistently below target on specific routes, evaluate whether route clustering can be adjusted to increase stop density.

When utilization is consistently above target, evaluate whether the affected routes need additional vehicles or adjusted delivery windows to maintain service quality.

8. SLA adherence by commitment type

SLA adherence by commitment type measures the percentage of each defined service tier met within its specific parameters: 2-hour, same-day, next-day, or any other named commitment your network runs.

This metric breaks adherence down by commitment tier so you can see which specific promise your network is struggling to keep.

A retail network running same-day and next-day commitments simultaneously may show acceptable OTIF overall while systematically failing same-day windows. Without the tier breakdown, that pattern is invisible. Declining adherence on a specific tier triggers a review of that tier’s route planning, carrier allocation, and order cut-off timing.

9. Estimated cost per delivery

Estimated cost per delivery is total logistics cost for a period divided by total deliveries. It is the metric that connects operational decisions to margin: a routing adjustment that improves utilization reduces cost per delivery; a carrier with a lower rate but a higher re-delivery rate may produce a higher total cost per successfully delivered order.

Note that some cost components, such as carrier invoices, accessorial charges, and settlement data, may only be confirmed after the period closes. Label this metric as estimated on the dashboard and show when the data was last refreshed so users understand the precision of what they are reading.

Rising estimated cost per delivery without a corresponding volume increase indicates a routing or carrier efficiency problem that needs investigation.

Also read: How to Cut Last-Mile Costs and Delivery Times

10. Dwell/turnaround time

Dwell time measures how long a vehicle spends at a stop beyond the planned service time for that stop. Turnaround time measures the same at hubs: the time between vehicle arrival and vehicle departure.

Excess dwell cascades downstream. A vehicle that spends 20 extra minutes at each of its first five stops arrives late at every remaining stop on the route.

Persistent excess dwell at specific stops indicates a recurring condition at that location: an access delay, a loading process issue, or a customer who requires extra service time. Identifying and addressing that condition improves every route that passes through that stop.

11. Route plan adherence

Route plan adherence compares routes as dispatched to routes as executed. It tracks deviations in stop completion, stop sequence, and timing.

A small number of deviations is expected. Persistent, large deviations on specific routes indicate that planning inputs are not reflecting real-world conditions.

When a route consistently deviates from plan in the same way, the planning parameters that generated it are wrong: travel time estimates, stop service times, or delivery window assignments need updating. Route plan adherence is the data source that makes that visible before the deviations accumulate into SLA failures.

12. Exception recovery rate

Exception recovery rate measures the percentage of at-risk or exception-flagged deliveries that are resolved within the original or revised commitment window. It answers the question the other 11 metrics cannot: are your alerts and playbooks actually changing outcomes?

A high exception volume with a high recovery rate means your detection and response system is working. A high exception volume with a low recovery rate means exceptions are being detected but not resolved in time. A low exception volume with a low recovery rate may indicate that detection is too slow or thresholds are too permissive.

Recovery rate turns the dashboard from a monitoring tool into an accountability system.

How to Design the Dashboard Around These Metrics

Metric selection and dashboard design are separate decisions, and both matter. A dashboard with the right 12 metrics in a layout that buries the most critical information is not useful to an ops team managing deliveries in real time.

The Seven-Principle Dashboard Design Model produces a logistics dashboard your team will use daily. Four principles govern layout and response:

• Hierarchy: Place OTIF, first-attempt delivery success rate, and SLA adherence at the top of the dashboard. These are the metrics with the most direct financial consequence, and your team should see them first. Metrics that require context or investigation belong in drill-down views, not the headline view
• Exception-first alerting: Configure thresholds for every metric. When a metric crosses its threshold, the dashboard should surface an alert that pushes to the relevant dispatcher or manager, not one that waits for them to notice the number has changed
• Drill-down by carrier, route, and store: Every headline metric should link to a breakdown view. An OTIF number of 87% is not actionable. An OTIF number of 87% driven by one carrier on two routes in the southeast is actionable
• Role-based views: A dispatch manager needs to see active routes and exceptions in real time. A carrier relationship manager needs to see carrier-level performance trends. An operations director needs to see network-level KPIs. Build role-based default views so each user sees the metrics most relevant to their decisions

The remaining three principles improve daily usability:

• Show refresh cadence: Label each metric with how frequently it updates. Projected SLA-breach risk and active exceptions should update continuously. OTIF and cost per delivery may update hourly or at the end of each shift. Mixing refresh cadences without labeling them trains users to distrust the entire dashboard
• Assign alert ownership: Every threshold breach should have an assigned owner, a response deadline, and a status field. An alert without an owner is a notification, not an accountability trigger
• Avoid alert fatigue: Thresholds should be calibrated to SLA risk, financial exposure, and available recovery options. A dashboard that flags every deviation as critical produces the same outcome as one that flags nothing: dispatchers stop acting on alerts

The hierarchy and alerting principles together produce a dashboard that functions as an early warning system. The drill-down and role-based view principles make the warning actionable for the right person.

Image
Source	https://locus.sh/dispatch-management-software/
Alt text	Locus DispatchIQ platform showing real-time logistics visibility dashboard with OTIF, exceptions, and route performance metrics for retail ops teams
Caption	DispatchIQ surfaces OTIF, exceptions, and route adherence metrics in real time, giving ops teams the current-state view they need to act before SLA windows close

Which Metrics Should You Add First?

Implementing all 12 metrics simultaneously is not the most effective rollout approach. Your team needs time to build the habit of checking a dashboard before reacting to exceptions, and that habit forms faster when the dashboard shows a focused view of the highest-impact metrics.

The right starting set depends on your operating model. A B2B replenishment network typically starts with OTIF, on-time pickup rate, and hub turnaround time. A same-day consumer network typically starts with projected SLA-breach risk, exceptions, and first-attempt success. A 3PL typically starts with carrier SLA adherence by tier and exception recovery rate.

Regardless of model, the One-Two-One Rollout Sequence applies: start with one primary outcome metric, two or three predictive or exception metrics that explain risk, and one recovery metric. For most retail delivery networks, that means starting with OTIF, projected SLA-breach risk, delivery exceptions, and exception recovery rate.

Next, add ETA accuracy, first-attempt delivery success rate, and on-time pickup rate. These metrics explain why OTIF and exceptions are at the levels they are. They shift the conversation from “how many failures did we have?” to “where is the performance problem originating and what do we fix?”

Add the efficiency metrics, fleet utilization, cost per delivery, dwell time, and route plan adherence, once the SLA and accuracy foundation is stable. These metrics require a baseline period to be meaningful and should be read in the context of the performance metrics, not in isolation.

First-attempt delivery success rate and SLA adherence work at both ends of the rollout: as headline health indicators at launch and as composite trend metrics once the full dashboard is in operation.

How Locus Connects Logistics Metrics to Live Operations

Locus is the world’s first Decision-Intelligent, Agentic TMS. The platform is built for retail and e-commerce, FMCG and CPG, 3PL, and manufacturing operations, with dispatch management, route planning, and end-to-end supply chain visibility as core capabilities.

Eight specialized AI agents within the DiSCO framework (Capacity, Dispatch, Carrier, Hub, Customer, Settlement, Copilot, Orchestrator) coordinate the dispatch lifecycle and generate data that feeds specific metrics on the dashboard: the Capacity Agent for fleet utilization, the Carrier Agent for on-time pickup rate and SLA adherence by tier, the Customer Agent for notification lead time, and the Copilot Agent for exception detection and recovery rate.

A unified real-time visibility layer within Locus’s agentic TMS aggregates status signals from active routes, carrier networks, and delivery events into a single operational view.

The data that feeds the 12 metrics in this guide, route adherence, carrier pickup timing, exception events, ETA calculations, stop completion status, and delivery outcomes, flows from live dispatch and routing data, not from batch carrier reports imported on a delay.

DispatchIQ generates the dispatch execution data that feeds OTIF, exceptions, failed attempts, fleet utilization, and active vs. planned routes.

Image
Source	https://locus.sh/route-optimization/route-optimization-software/
Alt text	Locus Fireworks Routing Engine providing the planned route baseline for ETA accuracy, dwell time, and active vs. planned route metrics on the logistics visibility dashboard
Caption	The Fireworks Routing Engine provides the planned route baseline against which ETA accuracy and route adherence metrics are measured, making the comparison between planned and actual performance meaningful

Because the Fireworks Routing Engine generates the planned route baseline from 250+ real-world constraints, ETA accuracy and dwell time are measured as deviations from a specific plan. That distinction is what makes the metric diagnostic: it identifies which planning input was wrong, not just that the delivery ran late.

ShipFlex covers 160+ active carriers from a broader network of 1,000+ pre-integrated partners, feeding carrier-level performance breakdowns across the SLA adherence, on-time pickup, and cost per delivery metrics. The Driver Companion App captures the stop completion, arrival, and departure events that populate route plan adherence and dwell time metrics from the field.

Mycroft AI Co-Pilot surfaces exception risk signals and performance deviations as they emerge across the delivery fleet, giving dispatchers the context they need to act on alerts before they become SLA failures.

For WISMO and customer communication metrics, the Customer Agent sends automated delivery updates that reduce WISMO contacts for retail operations without dispatcher involvement in each notification.

For seven consecutive years, Gartner has cited Locus in its coverage of last-mile delivery and supply chain execution technologies. Locus currently serves 360+ enterprise customers in 30+ countries, with $320M+ in logistics cost savings and 99.5% on-time SLA adherence.

In October 2025, Ingka Investments, the investment arm of Ingka Group, acquired Locus, adding long-term institutional backing to a platform that continues to operate independently.

Image
Source	https://locus.sh/ship-flex/
Alt text	Locus ShipFlex carrier management dashboard providing carrier-level performance data for SLA adherence, on-time pickup rate, and cost per delivery metrics across a multi-carrier retail network
Caption	ShipFlex feeds carrier-level performance data across 160+ active carriers into the visibility dashboard, enabling the drill-down by carrier that makes SLA adherence and on-time pickup metrics actionable

Surface Relevant Metrics With a Logistics Visibility Dashboard

A logistics visibility dashboard is only useful if it surfaces the right metrics in real time and presents them in a layout that prompts your ops team to act. The 12 metrics in this guide cover the performance, accuracy, exception, and efficiency dimensions that determine your delivery network’s SLA health and cost structure.

The design principles, headline metrics at the top, exception-first alerting, drill-down by carrier and route, and role-based views, are what convert a metric list into a tool your team uses every day. And the sequencing approach, SLA metrics first, then accuracy, then efficiency, ensures the rollout produces results before it is complete.

The underlying requirement for all of it is real-time data. A dashboard built on batch reporting produces lagging awareness. A dashboard built on live dispatch and routing data produces the ability to intervene before consequences become permanent.

Schedule a demo with Locus today to see how these 12 metrics surface through a unified real-time visibility layer.

Frequently Asked Questions

What is the difference between OTIF and SLA adherence on a logistics dashboard?

OTIF measures whether orders were delivered on time and in full within the agreed window. SLA adherence by commitment type breaks performance down by specific service tier, such as same-day or next-day, so you can see which commitments are being met and which are not. A network can show acceptable OTIF overall while consistently failing a specific service tier; the tier-level breakdown is what makes that visible.

Which logistics metrics need live data, and which can be updated periodically?

Projected SLA-breach risk, active exceptions, and route plan adherence need continuous or near-real-time updates because they support decisions that must be made within minutes. OTIF, first-attempt delivery success rate, and exception recovery rate are rolling outcome metrics that are meaningful with hourly or shift-level updates. Estimated cost per delivery typically requires settled cost data and should be labeled as an estimate on the live dashboard.

What should a logistics visibility dashboard show besides delivery outcomes?

Outcome metrics such as OTIF show what happened. A useful operational dashboard also shows projected risk (which deliveries are likely to miss their windows), active exceptions (what is going wrong right now), recovery rate (whether responses are working), and efficiency indicators (fleet utilization, dwell time, and route plan adherence). The combination of predictive, live, and rolling metrics is what makes a dashboard actionable rather than retrospective.

How does Locus connect logistics metrics to dispatch and route planning?

A unified real-time visibility layer within Locus’s agentic TMS aggregates status signals from active routes, carrier networks, and delivery events into a single operational view. DispatchIQ generates the dispatch execution data that feeds OTIF, delivery exceptions, fleet utilization, and route plan adherence metrics. The Fireworks Routing Engine provides the planned route baseline against which ETA accuracy and route plan adherence are measured. ShipFlex feeds carrier-level performance data across 160+ active carriers from a broader network of 1,000+ pre-integrated partners, enabling the carrier-level drill-downs that make SLA adherence and on-time pickup/dispatch metrics actionable. Mycroft AI Co-Pilot surfaces risk signals as they emerge so dispatchers can focus on exceptions that require judgment.