Order cycle time
An order arrives at ten in the morning and the parcel leaves for the carrier at four that afternoon: six hours. The time between a customer order arriving in your system and the goods leaving the building is called order cycle time.
How order cycle time is calculated
Add up the elapsed time of every order in the period and divide by the number of orders. The arithmetic is trivial. What matters is two decisions: where the clock starts and where it stops.
Three start points are in common use: the order arriving in the system, the order being released to the warehouse, and the payment being received. Only the first measures what the customer experiences. The second measures the warehouse alone, which is useful internally and flattering externally, so say plainly which one a report shows. At the stop, handover to the carrier measures your operation and delivery measures your promise.
Then decide what happens to back orders. An order that waits four days for stock is still an order the customer is waiting for. Leaving it out makes the figure shine and tells you nothing.
There is no good number
A wholesaler with a 4 pm cut-off and next-day delivery runs on a completely different clock from a spare parts supplier promising two hours for a machine that has stopped. The number that counts is not anyone else's: it is the gap between what you promise and what you do.
Read it beside the lead time your suppliers give you. A fast cycle in the warehouse does not rescue an order for an item that will not arrive for three weeks.
Worked example
A warehouse ships 1,000 orders in a week. The average order cycle time is 5.2 hours, which reads well against a same-day promise.
Now sort those thousand orders by elapsed time. The median order took 4.1 hours. The slowest fifty took between 19 and 31 hours, because they contained an item from the freezer zone and that zone is picked once a day at 11 am. The average said 5.2; the fifty customers who waited a day and a half are the ones who phoned. One number describes the operation, the other describes the complaints, and only the second shows you where to look. The figures here are an example.
What moves the number
- Cut-off times and wave planning. An order that arrives ten minutes after a wave is released waits for the next one. More, shorter waves lower the average and cost a little efficiency.
- Availability. One line missing from the shelf holds up the whole order, unless you are willing to ship in parts. This is where fill rate comes in.
- Checks before release. Payment authorisation, fraud checks and credit holds run before the warehouse sees the order, and they are often the biggest block of time in the whole figure.
- Zones with their own rhythm. Freezer, hazardous goods or high-value items picked once or twice a day set the floor for every order that touches them.
- Capacity in the peak hour. A warehouse that keeps up over the day can still back up between 2 pm and 4 pm.
- Carrier collection times. An order finished at 16:05 for a 16:00 collection leaves tomorrow, however fast it was picked.
Frequently asked questions
Where does the clock start?
Pick one of three and stay with it: the moment the order lands in your system, the moment it is released to the warehouse, or the moment payment is received. The first is what the customer experiences, so it is usually the honest choice. The second measures the warehouse alone.
Where does it stop?
At handover to the carrier if you are measuring your own operation. At delivery if you are measuring the promise you made to the customer. Both are useful; mixing them in one report is not.
Average or median?
Report both, and put the 95th percentile beside them. The average is pulled by a handful of stuck orders, and those are exactly the orders that generate the phone calls.
Do back orders count?
They must, or the figure only measures the easy orders. Keep them on a separate line, so that an availability problem is not read as a picking problem.
Further reading
Ready to see BizBloqs on your own process?
Book a demo and we will walk your warehouse and order flow end to end — inbound, storage, picking, shipping, returns — and tell you honestly what BizBloqs would change.
Two questions about your own operation
How many of your articles sit in a pick location they empty less than once a month?
Part one: Laying out a warehouse does not start with the racking
After your last integration, how many systems hold a stock quantity for the same item? Name them.