What Is an On-Time Delivery Report?

An on-time delivery report is the primary external performance measurement in any fulfillment operation. Where pick accuracy measures internal warehouse execution and shipment volume measures operational throughput, on-time delivery measures the outcome that the customer actually experiences — did the product arrive when it was promised?

The on-time delivery report compares two dates for every shipment: the promised delivery date (the date committed to the customer at order placement) and the actual delivery date (the date confirmed by the carrier’s tracking system when the shipment was physically delivered). The gap between these two dates — positive if delivered early or on time, negative if delivered late — is the measurement that drives OTD rate.

An OTD report that works well for operational management does more than calculate a percentage. It identifies which specific orders were late, why they were late, and whether the failure was in the warehouse (orders not shipped on time for the carrier to deliver on the promised date) or with the carrier (orders shipped on time but delivered late by the carrier). These two failure modes have completely different root causes and completely different remedies — and an OTD report that does not distinguish between them conflates operational problems with logistics problems, making it harder to take effective corrective action.

For 3PL operators, on-time delivery performance is often a contractual obligation — SLA metrics are written into client agreements, and failure to meet OTD thresholds can trigger penalty clauses, client escalations, or contract termination. For manufacturers with OEM or retail supply chain customers, on-time delivery performance directly affects supplier scorecards and vendor-managed inventory relationships. For distributors and e-commerce businesses, OTD performance drives customer retention — late deliveries are one of the most consistent drivers of customer churn.

Automated, systematic OTD reporting — updated daily from carrier tracking data — is the infrastructure that makes OTD management possible rather than reactive.

What is on-time delivery (OTD)?

On-time delivery (OTD) is a fulfillment KPI that measures the percentage of customer orders or shipments delivered by the promised or committed delivery date. It is calculated as the number of shipments delivered on or before the committed delivery date divided by the total number of shipments in the measurement period, expressed as a percentage. OTD is one of the most important customer satisfaction metrics for any distribution, manufacturing, or logistics operation — because late deliveries are the most visible fulfillment failure from the customer’s perspective.

How is on-time delivery calculated?
On-time delivery rate = (Number of shipments delivered on or before the promised date ÷ Total number of shipments in the period) × 100. For example, if 950 out of 1,000 shipments in a month were delivered by the promised date, the OTD rate is 95%. The metric requires knowing both the promised delivery date — the date committed to the customer when the order was placed — and the actual delivery date — the date the carrier’s tracking system records delivery confirmation at the destination.

Why Organizations Use On-Time Delivery Reports

Customer Satisfaction and Retention Late deliveries are the fulfillment failure customers feel most directly. An order that arrives two days late is visible, memorable, and sometimes unforgivable — particularly in B2B supply chain environments where the customer’s production or inventory planning was built around the promised arrival date. Systematic
OTD tracking allows operations teams to surface late deliveries quickly, proactively communicate with affected customers, and understand whether the failures are isolated incidents or symptoms of a systemic problem.
Carrier Selection and Accountability Not all carriers perform equally on all lanes. A carrier with a 98% OTD rate on regional ground shipments may have a 72% OTD rate on a specific long-haul lane where its network coverage is thin. An OTD report segmented by carrier, service level, and lane surfaces these performance differences clearly — giving transportation managers the data to hold carriers accountable in quarterly business reviews, renegotiate lane-specific rates and commitments, and route freight away from underperforming carriers.
On-Time Ship Rate vs. On-Time Delivery Rate OTD reports serve a second operational purpose beyond carrier management: distinguishing warehouse execution failures from carrier execution failures. An OTD report that also tracks on-time ship rate (whether the order was tendered to the carrier by the required ship date) identifies whether late deliveries are caused by late shipments from the warehouse or by carrier failures after a timely ship. If the warehouse shipped on time but the carrier delivered late, the fix is a
carrier conversation. If the order was shipped late, the fix is a warehouse operations conversation. Without both metrics, you cannot tell which conversation to have.
SLA Compliance Monitoring (3PL and Supply Chain) Third-party logistics providers operating under client service level agreements need systematic OTD reporting to monitor compliance, generate the performance reports required by client contracts, and identify SLA breach risk before reporting periods close. For retail supply chain vendors subject to retailer routing guides and vendor scorecards, OTD performance is often tied directly to compliance fines, chargebacks, or preferred vendor status.
E-Commerce Delivery Promise Management E-commerce businesses that promise delivery windows at checkout — “arrives by Thursday” — need OTD tracking to verify that those promises are being kept and to identify the order types, carrier services, and geographic zones where the delivery promise is consistently missed. This data feeds decisions about which delivery windows to promise for which zip codes and carrier services.
Freight Cost vs. OTD Tradeoffs Choosing a cheaper carrier or a slower service level saves freight cost but may reduce OTD performance. OTD reports that combine delivery performance with freight cost data allow transportation managers to make informed costvs-service tradeoffs — quantifying how much OTD performance they are trading for each dollar of freight cost saved — rather than making these decisions on intuition.

Common KPIs and Data Elements

Shipment-Level OTD Data

Order Number and Shipment Number
Customer Name and Ship-To Address
Order Date
Promised Delivery Date
Required Ship Date (calculated from transit time)
Actual Ship Date
On-Time Ship Flag (yes/no)
Days Early/Late on Ship (actual minus required ship date)
Carrier Name
Service Level (Ground, 2-Day, Overnight, LTL)
Tracking Number
Actual Delivery Date (from carrier tracking)
On-Time Delivery Flag (yes/no)
Days Early/Late on Delivery (actual minus promised)
Exception Type (if late: carrier delay, weather, address issue, missed pickup, warehouse late ship)
Order Value
Freight Cost
Ship-From Location / Warehouse

Lane-Level OTD Summary

Total Inventory Value in Each Aging Bucket ($ and %)
Number of SKUs in Each Aging Bucket
% of Total Inventory Value in 90+ Days Bucket
% of Total Inventory Value in 180+ Days Bucket
Top 10 Highest-Value Aged Items (90+ days)
Top 10 No-Movement Items (zero sales in 180+ days)
Product Categories with Highest Aging Concentration

Carrier-Level Performance Summary

Carrier Name
Total Shipments
On-Time Delivery Rate
1-Day Late Rate
2–3 Days Late Rate
4–7 Days Late Rate
7+ Days Late Rate
Average Days Late (for late shipments only)
Damage/Exception Rate
Cost Per Shipment (for cost-vs.-service comparison)

Portfolio-Level OTD Metrics

Overall OTD Rate (all carriers, all lanes, all service levels)
On-Time Ship Rate (warehouse execution metric)
Perfect Order Rate (OTD + complete + undamaged)
OTD Rate by Ship Method
OTD Rate by Customer Segment or Account Tier
OTD Rate by Product Category
OTD Rate by Origin Warehouse / Location
OTD Trend (weekly, monthly, quarterly)
Carrier Comparison (rank carriers by OTD rate)

Common Filters and Parameters

Date Range — ship date range, delivery date range, or order date range
Carrier — single carrier, carrier comparison, or all carriers Service Level — Ground, 2-Day Air, Overnight, LTL, etc.
On-Time vs. Late — all shipments, late only, on-time only, exception only
Lane — filter by origin zip, destination state, or specific O-D pair
Customer / Account — OTD performance for a specific customer or account tier
Ship-From Location — single warehouse or multi-location consolidated
Order Type — wholesale, retail, e-commerce, intercompany
Days Late Bucket — 1 day, 2–3 days, 4–7 days, 7+ days
Exception Type — carrier delay, weather, missed pickup, address issue, warehouse late
Dollar Value Threshold — show only high-value orders (OTD failures on large orders) Comparison Period — current period vs. prior period, prior year

Common Reporting Challenges

Getting Actual Delivery Data Systematically

The most common OTD reporting gap is the absence of actual delivery confirmation data. Most organizations know when they shipped — the ERP or WMS records the ship date. Few have systematic access to when the shipment was actually delivered, because that data comes from the carrier's tracking system, not from the internal order system. Without actual delivery date data, on-time delivery cannot be measured — only on-time ship rate. Solving this requires carrier API integration, EDI 214 transaction processing from the carrier, or a transportation management system (TMS) that aggregates carrier tracking events automatically.

Promised Delivery Date Not Captured at Order Entry

Many organizations do not systematically capture the delivery date promised to the customer at the time of order entry — it exists in an email confirmation or a quote document, not in the order management system as a structured data field. Without a stored promised delivery date in the OMS, OTD calculation requires reconstructing the promised date from order date, processing time, carrier transit tables, and service level selected — a calculation that can be built into the reporting system but requires careful calibration to match actual customer commitments.

Distinguishing Carrier Failures From Warehouse Failures

An OTD failure can happen at two stages: the warehouse ships late (after the required ship date), giving the carrier insufficient transit time; or the carrier delivers late despite an on-time ship. Without tracking both on-time ship rate (warehouse accountability) and on-time delivery rate (combined accountability), the OTD report cannot direct corrective action to the right team. Many organizations track only OTD without on-time ship, making it impossible to determine whether the problem is internal or external.

Weather and Force Majeure Exception Handling

Carrier delays caused by extreme weather, natural disasters, or force majeure events are typically excluded from OTD calculations in formal supply chain SLAs. Systematically identifying and flagging these exceptions requires either carrier-provided exception codes in tracking data or manual flag creation for affected shipment date ranges and lanes — a data governance challenge that affects OTD reporting accuracy during severe weather periods.

Multi-Stop and Partial Shipment Complexity

When an order is shipped in multiple partial shipments — or when a carrier routes a shipment through multiple stops before final delivery — defining "on time" becomes more complex. Is an order on time if the last piece arrives on the promised date even though earlier pieces arrived late? Is a partial shipment on time if it arrives on the promised date even though the remainder is still in transit? These definitional questions need to be answered and documented before building the OTD calculation — the metric is only meaningful when the measurement definition is consistent.

Carrier Data Feed Reliability

Carrier tracking APIs and EDI feeds occasionally miss scans, delay delivery confirmation events, or provide incomplete tracking histories for certain shipment types. An OTD system that treats missing delivery scans as "not yet delivered" will over-count late deliveries. One that ignores shipments with missing tracking data will under-count total shipments and skew the OTD rate upward. Building data quality validation and missing-scan exception handling into the OTD calculation engine is essential for accurate metric production.

Automation and Scheduling Options

Carrier Tracking Data Integration We build carrier API integrations and EDI 214 processing pipelines that pull actual delivery scan events from UPS, FedEx, USPS, regional carriers, and LTL carriers automatically — updating the delivery confirmation date for every tracked shipment in the OTD database without manual tracking lookups.
OTD Calculation Engine We build SQL Server OTD calculation engines that compare actual delivery dates to promised delivery dates for every shipment, calculate days early/late, assign on-time/late flags, categorize late shipments by exception type, and compute OTD rates at the shipment, carrier, lane, and portfolio levels — updated automatically as new delivery confirmation data arrives.
Exception Alert Automation We build automated delivery exception alert systems that identify shipments flagged by the carrier as delivery exceptions — address not found, recipient unavailable, damage in transit, refused delivery — and generate immediate alerts to customer service, the responsible account manager, and the operations team before the customer calls.
Power BI OTD Dashboard We build real-time Power BI OTD dashboards that give operations leadership an interactive view of current OTD performance — overall rate, carrier comparison, lane performance heat maps, late shipment drill-through, and trend analysis — refreshed automatically from the carrier tracking data pipeline.
Carrier Scorecard Automation We build carrier performance scorecards that aggregate
OTD rate, damage rate, exception rate, and average transit time by carrier and service level — generated automatically for each reporting period and distributed to the transportation team and relevant carrier contacts for quarterly business reviews.
Customer SLA Compliance Reports For 3PL operators and manufacturers with contractual OTD commitments, we build client-specific SLA compliance reports that calculate OTD performance against the specific thresholds defined in each client’s agreement — formatted for client delivery in whatever format the contract requires.

Delivery Methods

ReportingGuru delivers capital account statement automation across the full range of platforms your team and your LPs rely on:

SSRS (SQL Server Reporting Services)

Formatted OTD performance reports — carrier scorecards, weekly OTD summaries, client SLA compliance reports — generated on a scheduled basis and delivered automatically by email to operations leadership, account managers, and carrier contacts.

Scheduled PDF / Email

Daily late shipment alerts, weekly carrier performance summaries, and monthly OTD trend reports automatically delivered to operations leadership and customer service teams without manual report preparation.

Power BI

Power BI is the most effective platform for interactive OTD analytics — carrier comparison dashboards, lane performance heat maps, exception monitoring with drillthrough to individual shipments, OTD trend charts, and freight cost vs. OTD performance quadrant analysis. Refreshed daily from the SQL Server OTD data model.

Excel

Excel OTD workbooks driven by live carrier tracking and order data — for transportation contract reviews, carrier business review presentations, and client reporting in 3PL environments — automatically populated without manual tracking data exports.

Related Report Pages

Shipping & Fulfillment Pages

Shipping & Fulfillment Reporting Hub — Overview of all shipping and fulfillment reporting solutions from ReportingGuru.

Pick List / Pick Ticket Reports — The pick list starts the fulfillment process — accurate, efficient picking is the prerequisite for on-time shipment.

Financial & GL Reporting Pages

Balance Sheet — Automate balance sheet reporting alongside budget vs actual analysis — actual asset, liability, and equity balances vs. budgeted positions with lender covenant ratio tracking.

Income Statement / Profit & Loss — P&L actuals that feed every revenue and expense line in every budget vs actual report — with departmental drill-down, cost allocation, and EBITDA variance analysis.

Statement of Cash Flows — Cash flow actuals vs. projected cash flows and free cash flow forecasts — the liquidity and capital deployment dimension of budget vs actual management.

Trial Balance — The validated, exception-checked GL data that feeds every actual line in every budget vs actual report — the foundational data layer for all variance analysis.

Investor & Fund Reporting Pages

Financial Statements & KPI Reporting — Fund and portfolio company financial statements incorporating inventory on-hand balances and turnover metrics.

Fund Performance Reporting — Days-on-hand, stockout rates, and inventory turnover tracked as PE portfolio company operational KPIs.

Inventory & Warehouse Pages

Inventory & Warehouse Reporting — Overview of all inventory and warehouse reporting solutions from ReportingGuru.

Inventory Aging — Days-in-stock by item and lot — the obsolescence detection tool that identifies items requiring LCM write-down consideration.

Inventory Valuation — The financial value of aged inventory — cost method valuation by lot that determines the dollar impact of the obsolescence reserve.

Frequently Asked Questions

What is a good on-time delivery rate?

Industry benchmarks vary by sector and service expectation. For B2B distribution and manufacturing supply chains, an OTD rate of 95–98% is generally considered acceptable, with world-class performers targeting 98%+ consistently. For e-commerce with committed delivery windows, customer expectations are higher — OTD rates below 95% typically generate significant customer service volume and churn. For 3PL operators, OTD thresholds are often contractually defined at 95% or 97% with penalty provisions below those levels.

What is the difference between on-time ship rate and on-time delivery rate?

On-time ship rate measures whether the order was tendered to the carrier by the required ship date — it is a warehouse execution metric. On-time delivery rate measures whether the order arrived at the customer by the promised delivery date — it is a combined warehouse-pluscarrier metric. An order can be shipped on time but delivered late (carrier failure) or shipped late but delivered on time (carrier makes up time). Tracking both metrics separately allows operations to distinguish warehouse execution problems from carrier network problems.

How do weather delays affect OTD reporting?

Weather delays caused by severe weather, natural disasters, or carrier force majeure events are typically excluded from OTD calculations in formal SLA agreements, since neither the shipper nor the carrier can control weather. In practice, this requires flagging affected shipments with a weather exception code — either from carrier-provided exception data in tracking feeds or through manual exception designation for specific date ranges and lanes — and excluding them from the denominator in OTD rate calculations. The definition of which events qualify for weather exclusion should be agreed upon with customers and carriers before disputes arise.

Can OTD be tracked without a transportation management system (TMS)?

Yes, though it requires direct carrier API or EDI integration to get actual delivery data. We build carrier tracking integrations that connect directly to UPS, FedEx, USPS, and major regional and LTL carriers through their tracking APIs — pulling actual delivery scan events into the OTD database without requiring a TMS. For organizations with many carriers or high shipment volumes, a TMS that aggregates all carrier tracking events in one place simplifies the integration architecture, but it is not a prerequisite for systematic OTD measurement.

What causes most on-time delivery failures?

Common causes vary by operation type but typically include: late ship (order not tendered to carrier by required ship date, usually due to warehouse capacity, pick errors, or fulfillment system delays), carrier network delays (volume spikes, hub congestion, insufficient service in certain lanes), address issues (incomplete or incorrect delivery addresses causing failed delivery attempts), weather events, and residential delivery complications (nobody home, access restrictions). An OTD report that codes each late shipment with an exception type allows operations to identify which cause category drives the largest share of failures and direct corrective action accordingly.

How should OTD be reported to carriers during business reviews?

Carrier business reviews are most productive when OTD data is presented at the lane level — showing which specific origin-destination lanes have the worst performance — rather than only at the overall level. Carriers can address specific lane problems (add capacity on a particular hub route, adjust transit day commitments for lanes where actual transit consistently exceeds contracted transit) more effectively than they can address a single overall number. Presenting carrier-attributed failures separately from weather exclusions and warehouse late ships also ensures the conversation is focused on what the carrier can actually control.