Order Cycle Time: Formula, Segments, and Why the Tail Matters

Order cycle time is the time from the moment a shopper places an order to the moment it is delivered, averaged across your orders. For a DTC or Shopify brand, the useful version measures that clock against the delivery date you promised at checkout, not against a warehouse target.
Every order is a promise. Keeyu keeps it.
I'm Jevon Le Roux, founder of Keeyu, a proactive e-commerce operations company. That is a new category, not a better helpdesk. This guide gives you the formula, a spreadsheet method, the four segments where time leaks, and why the slowest orders matter more than the average.
Order cycle time formula and how to calculate it
The order cycle time formula adds up the elapsed time from order placed to order delivered for every delivered order in a period, then divides by the number of those orders. The result is an average, usually expressed in days.
My take: the clock starts at the buy button
When a shopper hits the buy button, the clock starts for them. In my view, about 80% of shoppers feel some anxiety at that moment that they won't get what they ordered on time, as promised. That is the clock order cycle time should measure.
The money clears and the promise clock starts before the warehouse can act. So I'd never start the count at warehouse release or stop it at carrier pickup. Start at checkout, stop at the doorstep.
The basic formula
- Order cycle time = total time from order placed to order delivered / number of orders delivered
As reported by OneCart, 200 orders that took 600 days combined give an average order cycle time of 3 days.
Calendar days or business days
OneCart notes that some sellers count calendar days and others count business days, and calls calendar days usually the more honest number. I agree. The shopper waits through the weekend too, and the promise you showed at checkout was a date, not a count of working days.
How to compute it in a spreadsheet
You need one row per order with six timestamps or dates. Most come from your store's order export and your 3PL or WMS. The delivered date comes from carrier tracking, not the order export.
- Order placed
- Released to the warehouse
- Packed
- First carrier scan
- Delivered
- Promised delivery date shown at checkout
Then add three formula columns:
- Cycle time (days) = Delivered minus Order placed
- Late? = IF(Delivered > Promised date, 1, 0)
- Days late = MAX(0, Delivered minus Promised date)
Average the cycle time column with AVERAGE, and take the 90th percentile with PERCENTILE.INC(range, 0.9). Sum the Late? column and divide by the order count to get your late share.
A worked example (made-up numbers)
These ten orders are illustrative only. Every order was promised within 4 days.
Order | Cycle time (days) | Late against 4-day promise |
|---|---|---|
1 | 2.1 | No |
2 | 2.4 | No |
3 | 2.6 | No |
4 | 2.8 | No |
5 | 3.0 | No |
6 | 3.1 | No |
7 | 3.3 | No |
8 | 3.6 | No |
9 | 5.8 | Yes |
10 | 7.2 | Yes |
The average is 3.59 days, comfortably inside the 4-day promise. The 90th percentile is 5.94 days. Two orders out of ten, or 20%, broke the promise. The average says you are fine. Two shoppers would disagree.
Order cycle time benchmarks
An order cycle time benchmark is a reference range that tells you whether your average is fast or slow for standard domestic ecommerce. Treat any published range as a rough guide, because each brand ships different products, distances, and carrier services.
What the published ranges say
As reported by OneCart, these are commonly cited ranges for standard domestic ecommerce. The article does not cite a study behind them.
Average order cycle time | How OneCart describes it |
|---|---|
1 to 2 days | Excellent, on par with the fastest marketplace fulfillment |
3 to 5 days | Solid and acceptable for most product categories |
5 to 7 days | Shoppers grow impatient and abandonment rises |
More than 7 days | A warning sign for standard goods |
My take: the benchmark that matters is your own promise
A 5-day average is fine if you promised 6 days and disastrous if you promised 3. I'd benchmark against the date shown at checkout before any industry range.
Last year, one in five online shoppers in the US didn't get what they ordered on time, as promised. I call that a $213 billion problem for e-commerce businesses, revenue that left silently. Those shoppers don't complain. They just go to a competitor.
Where order cycle time bleeds: the four segments
Order cycle time segments are the stages between checkout and doorstep, each with its own start and stop timestamp. Splitting the total into segments shows whether the delay sits in your systems, your warehouse, or the carrier network.
My take: the dangerous delays are the silent ones
Without the tools and processes to watch each stage, "where is my order" complaints become an ongoing cycle. Most brands only see the total. The segment tells you who to call.
At the start of COVID, our online warehouse sale took off and our Shopify store oversold. It had stopped syncing orders with the warehouse. We ended up with a thousand shoppers who paid but weren't going to get what they ordered, then a chaotic manual refund process. Every one of those orders was stuck in the first segment, and nothing told us.
As I said on EGGS! The Podcast, Tracy's verdict afterwards was simple: "if I could have seen that happening in real time, I could have prevented it." That is the case for watching each segment, not just the total.
Segment 1: order to release
From order placed to the order reaching the warehouse in a state it can act on. Payment checks, fraud holds, address validation, and the store to ERP or WMS sync all live here. If the order never lands in an actionable state, nobody is paged and the shopper is the first to notice.
Segment 2: release to pick and pack
From release to a packed, labeled parcel. OneCart splits this into order processing time and pick and pack time. Wave timing, stockouts discovered on the shelf, and same-day cutoff times drive most of the variation.
Segment 3: pack to carrier first scan
From packed parcel to the carrier's first scan. OneCart calls this dwell time. A parcel can show as shipped in your store while it sits on the dock waiting for collection. The first scan is the honest timestamp.
Segment 4: first scan to delivery
Transit time through the carrier network. This is the segment you control least, but carrier choice and service level still matter. For the delivery leg in depth, see our guide to final mile delivery tracking.
Segment | Start timestamp | Stop timestamp | Usual owner |
|---|---|---|---|
Order to release | Order placed | Released to warehouse | Store, ERP, ops |
Release to pick and pack | Released | Packed | Warehouse or 3PL |
Pack to first scan | Packed | First carrier scan | 3PL and carrier |
First scan to delivery | First carrier scan | Delivered | Carrier |
Every order is a promise. Keeyu keeps it.
Average vs 90th percentile: why the tail is where promises break
The 90th percentile order cycle time is the time within which 90% of your orders were delivered. The slowest 10% sit above it. Reporting it beside the average shows how long your worst common delay really is.
My take: shoppers don't experience your average
No shopper receives the average order. Each one receives their own. In the worked example above, the average looked healthy at 3.59 days, while the p90 was 5.94 days and 20% of orders were late.
Averages hide the tail because a few fast orders offset a few very slow ones. The tail is where the stuck sync, the lost parcel, and the missed carrier pickup live. Those are the orders that turn into tickets.
Why the tail drives your ticket queue
In my experience, 40% to 60% of all customer service tickets are "where is my order" inquiries. Most of those come from orders in the tail.
Response time metrics don't help here either. The response clock only starts once the shopper has discovered a broken promise and taken the trouble to report it. A cycle time p90 shows you the same problem days earlier.
What to report each week
- Average order cycle time
- 90th percentile order cycle time
- Share of orders delivered after the promised date
- The segment where late orders spent the most extra time
Order cycle time vs fulfillment cycle time, lead time, and dock-to-stock
Order cycle time is the end-to-end, shopper-facing clock. The related metrics below each measure a narrower slice, which is why a team can hit all of them and still deliver late.
- Fulfillment cycle time: from order release to shipment, the warehouse's share of the clock, without transit.
- Lead time: the time to replenish stock from a supplier, from purchase order to goods available.
- Dock-to-stock: the time from inbound goods arriving at the warehouse to being shelved and sellable.
On-time delivery rate is the closest partner metric. Cycle time tells you how long orders took. On-time delivery tells you how many met the date. Our guide to measuring on-time delivery covers that side.
How to reduce order cycle time
Reducing order cycle time means shortening the slowest segment and catching stuck orders before they blow past the promised date. Cutting the average helps, but cutting the tail is what keeps orders on time.
My take: fix problems at the source
I want systems that check each other and fix problems at the source. No tickets. No chasing. Orders arrive on time, as promised. The practical version of that starts with watching every open order against its promise.
Practical steps
- Set the promise honestly. Show a delivery date at checkout that your p90, not your average, can meet.
- Watch segment 1 first. Alert on any paid order that has not reached the warehouse within your release target.
- Tighten cutoffs. Align your same-day cutoff with real pick capacity and carrier collection times.
- Measure dwell. Compare packed time with first carrier scan, and raise any gap over a day with your 3PL.
- Review carrier service levels by lane. Our guide to ecommerce shipping best practices covers carrier and service choices.
- Tell the shopper first. When an order will miss its date, a delay message before the promised date beats an apology after a complaint.
Where proactive operations fit
Proactive e-commerce operations means monitoring the whole order journey, from payment through fulfillment and delivery to returns, and resolving issues before the shopper asks "where is my order?". Keeyu gets shoppers what they want, on time, as promised.
We are on a journey to end "where is my order?" forever. Read more in our guide to proactive e-commerce operations, or book a demo to see your own order cycle time against the promise.
Every order is a promise. Keeyu keeps it.
Frequently Asked Questions
What is order cycle time?
Order cycle time is the time from the moment a shopper places an order to the moment it is delivered, averaged across delivered orders. It covers the whole journey: release to the warehouse, pick and pack, carrier pickup, and transit. For DTC brands, it is most useful when compared with the delivery date promised at checkout.
How do you calculate order cycle time?
Add up the elapsed time from order placed to order delivered for every delivered order in the period, then divide by the number of those orders. In a spreadsheet, subtract the order date from the delivered date on each row, then use AVERAGE. Add PERCENTILE.INC with 0.9 to see your slowest common orders.
What is a good order cycle time for ecommerce?
As reported by OneCart, commonly cited ranges for standard domestic ecommerce are 1 to 2 days as excellent and 3 to 5 days as solid. Beyond 5 to 7 days, shoppers grow impatient. The more useful test is whether your 90th percentile beats the delivery date you show at checkout.
Does order cycle time include weekends?
It depends on how you define it, and some sellers count business days only. As reported by OneCart, calendar days are usually the more honest number. Shoppers wait through weekends too, and the promise shown at checkout is a date, so calendar days match their experience.
What is the difference between order cycle time and fulfillment cycle time?
Order cycle time runs from order placed to delivered, so it includes carrier transit. Fulfillment cycle time covers only the warehouse share, from order release to shipment. A 3PL can hit its fulfillment target while orders still arrive late, because dwell time and transit sit outside its clock. Track both side by side.
Why track the 90th percentile instead of the average order cycle time?
An average hides slow orders behind fast ones, so it can sit inside your promise while a fifth of orders arrive late. The 90th percentile shows how long your slowest common orders take. Pair it with the share delivered after the promised date, which our guide to on-time delivery explains.
How can I reduce order cycle time?
Split the total into four segments and fix the slowest one first. Alert on paid orders that have not reached the warehouse, compare packed time with first carrier scan, and review carrier service by lane. Our guide to proactive e-commerce operations explains how to catch stuck orders before the promised date.
References
- 1. OneCart, "Order Cycle Time: Formula, Benchmarks & How to Improve", https://www.getonecart.com/order-cycle-time/. Order cycle time formula, the 200 orders over 600 days example, commonly cited benchmark ranges (1 to 2, 3 to 5, 5 to 7, more than 7 days), the four stages including dwell time, and calendar days as the more honest count.
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.
