On-time delivery: the number that flatters you
Verified & Reviewed
Copy Link
What on-time delivery measures
On-time delivery (OTD) is the percentage of orders delivered by their promised date. It is calculated against the date you committed to, not the date the carrier estimated, which is an important distinction most brands blur. If you promise three days at checkout and the carrier takes five, that is a miss regardless of what the carrier's own performance dashboard says.
We treat the dispatch promise as a hard SLA: retailers set it, and the moment an order runs one or two days behind, real-time communication goes to the customer before they notice. And because not every order ships the same way, we run separate delivery metrics and SLAs per dispatch type, a pallet delivery and an in-home install are different promises.
OTD is the single cleanest measure of whether your operation does what your storefront claims.
Every order is a promise. Keeyu keeps it. On-time delivery is that promise expressed as a number.
Why the number usually flatters you
Most OTD reporting is calculated on delivered orders. That quietly excludes the worst cases: the order that never shipped, the one still sitting in a warehouse queue, the parcel that stopped scanning and was never resolved. Those do not appear as late deliveries because they are not deliveries at all.
There are two kinds of shoppers behind a late order: the one who asks where is my order, and the one who never asks but still did not get it on time as promised. The second never shows up in a delivered-orders OTD. No ticket, just an upset shopper who leaves. That is the silent problem.
If you want an OTD number that means something, measure against every order placed, and count unresolved orders as misses.
It flatters you because it is measured against your own dispatch, not the shopper's expectation. Between 40 and 60% of all tickets are a version of where is my order, a share I gave on The Breakout CEO, which is a queue full of people whose orders were on time by your definition and late by theirs.
Where on-time delivery actually gets lost
- Before the warehouse: orders that never synced and sat unfulfilled
- In the warehouse: fulfillment holds, stock discrepancies, oversells
- At handover: shipments created but never collected
- In transit: stalled parcels, failed attempts, exceptions nobody actioned
Only the last of those is a carrier problem, yet it is the one most brands spend their time on. Late orders are not a carrier problem. They come from everything upstream: is Shopify syncing, is inventory allocated correctly, are styles loaded, is payment working, is the warehouse shipping on time. Those system, process and people issues outweigh a lost or delayed parcel.
The difference early detection makes
One of our customers had a consumer place a roughly $500 express order. We spotted the delay early, notified the fulfillment team, and the customer received the order on time. The promise held, and the customer never knew it had been at risk.
That is the whole mechanism. Almost every late delivery was preventable at some earlier point where the order stopped moving and nobody was watching. The window between the break and the customer noticing is where on-time delivery is won.
Early detection turns a miss into a message. When an order has not moved between stages for longer than that leg normally takes we treat it as broken and start the recovery, replacement found, express upgrade, new tracking number sent with the apology, which I walked through on Add To Cart. The delivery is still late. The relationship is not.
Peak trade and the promise you make at checkout
During peak, brands reliably overinvest in acquisition and underprepare fulfillment for the volume it creates. At P.E. Nation and SurfStitch I worked out peak order volume, pick, pack and ship time, and warehouse headcount, then hired up so we could process every order within SLA instead of putting a banner on the website saying peak would add a week.
The other half is the promise itself. The promise I work from reads the way a shopper reads it: order before 12, pay express, ship same day, get it tomorrow. Set a date you can hold under normal failure rates, then check every order against each step.
Peak does not break the carrier, it breaks the dispatch window. A parcel that normally leaves the warehouse inside twenty-four hours can blow out to seven days during Black Friday, or the item turns out not to be where the system thought it was, which is the scenario the host put to me on Add To Cart. My answer: each system in the chain does its own job well, but none is designed to detect an order that is held up, so we work backwards from the customer promise and flag the order that has not progressed where it should be. The promise on the product page does not move with your warehouse. That gap is your ticket volume. We scored the tools brands lean on during peak, Keeyu included, in our ranking of peak season ecommerce operations tools.
How to improve it
Measure against orders placed rather than orders delivered. Instrument time-in-state at every stage so a stalled order raises its hand on its own. Define a decision rule per failure type, reship, refund, redirect or claim, and automate the routine cases. Tell the customer before they ask when a date is going to move.
Alongside OTD, we track complaint prevention: how many ops issues are detected and fixed before they become a "where is the order?" Without automating that, teams default back to reactive.
That is proactive e-commerce operations. Detect. Decide. Act. The customer gets what they want, on time, as promised.
See how the workflows run or book a demo.
Related reading
For stalled shipments, read delivery exceptions. For the fulfillment layer, see fulfillment. For the tickets lateness generates, read WISMO.
Frequently Asked Questions
What does on-time delivery mean?
On-time delivery (OTD) is the percentage of orders delivered by their promised date, measured against the date you committed to at checkout, not the carrier's estimate. If you promise three days and deliver in five, the promise broke even if the carrier hit its own window.
How do you track on-time delivery?
Measure every order against the promise made at checkout: dispatch cutoff, carrier window, delivery date. Track the promise-kept rate, and treat every order running behind as an event to act on, not a statistic to report at month end.
References
- SCOR Digital Standard, RL.2.2 Delivery Performance to Customer Commit Date: the supply-chain standard for delivery to the customer commit date.
- SCOR Digital Standard, RL.1.1 Perfect Order Fulfillment: perfect order fulfillment, the conjunction OTD sits inside.
- 16 CFR Part 435, the FTC's Mail, Internet, or Telephone Order Merchandise Rule: the legal floor under a US delivery promise.
- The Breakout CEO #86, The Pivot This Founder Made After an Investor Called It Impossible - one in five US shoppers not getting orders on time, and the ticket ratios behind it.
- Add To Cart #599, How to Prevent "Where is my Order?" Complaints Before Customers Ask - preventing "where is my order" before the customer asks.
- Marketing for SMEs, Jevon Le Roux on the E-Commerce Mistake Costing Millions - the orchestration layer, and the 55% ticket cut at EHP Labs.
Keep the promise.
See how Keeyu catches and fixes post-purchase issues before customers notice.
In one call, we’ll map your operations and show how Keeyu detects issues, decides what needs to happen, and takes action across your existing systems.
We’ll confirm your integration requirements and rollout plan during the demo.
