Order cycle time is the average time from a customer placing an order to receiving it. Add up each order's days from order to delivery, then divide by the number of orders delivered. It matters because every day an order waits, the goods have left your shelves and the money hasn't reached you.
This page works the formula through ten orders in Kenyan shillings. It also fixes two common formula mistakes, and shows how to measure it in ArmPOS.
The Formula for Order Cycle Time
Order cycle time is the sum of each order's own cycle, divided by the number of orders. Each order's cycle is its delivery date minus its order date.
Order cycle time = sum of (delivery date − order date) for each order ÷ number of orders delivered
| Input | What it is | Where it comes from |
|---|---|---|
| Order date | The day the customer placed the order | The order or sale record |
| Delivery date | The day the customer received the goods | Your delivery record, or the courier's |
| Number of orders delivered | Orders delivered in the period you measure | A count of the rows |
APQC, a benchmarking body, measures it this way: in days, weekends included, from the customer placing the order to delivery (APQC's measure). Some sellers stop the clock when the order leaves their door instead. Pick one end point and keep it.
Two mistakes in the formula most pages print
Many pages print "(delivery date − order date) ÷ total orders shipped", as if one date gap could be shared between orders. It can't: each order has its own two dates, and you add up the gaps first.
The second mistake divides the length of the period by the number of orders. Thirty days ÷ 600 orders = 1.2 hours tells you how often an order arrives, not how long each one waits.
For example: ten orders at a wholesaler in Nairobi
Take a wholesaler in Nairobi that delivers to shops, and ten of its orders from one fortnight. The figures are an illustration, not a real business's.
| Order | Placed | Delivered | Days |
|---|---|---|---|
| 1 | Monday | Tuesday | 1 |
| 2 | Monday | Tuesday | 1 |
| 3 | Monday | Wednesday | 2 |
| 4 | Tuesday | Thursday | 2 |
| 5 | Tuesday | Thursday | 2 |
| 6 | Wednesday | Saturday | 3 |
| 7 | Wednesday | Saturday | 3 |
| 8 | Thursday | Monday, week 2 | 4 |
| 9 | Friday | Thursday, week 2 | 6 |
| 10 | Wednesday | Friday, week 2 | 9 |
| Total | 33 |
Order cycle time = 33 days ÷ 10 orders = 3.3 days.
The median, the middle of the ten, is 2.5 days, and half the orders arrived within 2 days. Two late orders, at 6 and 9 days, pull the average up.
Report three numbers, not one
Report the average, the median and the share delivered on time. The average tracks the total waiting, the median shows the usual order, and the share on time is what customers feel.
| Measure | Spreadsheet formula | Result |
|---|---|---|
| Average | =AVERAGE(D2:D11) | 3.3 days |
| Median | =MEDIAN(D2:D11) | 2.5 days |
| Delivered within 2 days | =COUNTIF(D2:D11,"<=2")/COUNT(D2:D11) | 50% |
With the order date in column B and the delivery date in column C, =C2-B2 gives each order's days. The formulas work the same in Excel and Google Sheets.
Why order cycle time matters: cash, customers and stock
A shorter cycle brings the money in sooner, keeps customers, and ties up less stock in orders. The cash effect is the one most owners can put a number on.
Little's Law puts a number on it: orders in progress = orders a day × cycle time in days. At a steady flow of orders, the only way to have fewer waiting is to shorten each wait, as John Little sets out.
For the Nairobi wholesaler: 40 orders a day × 3.3 days = 132 orders in progress at any moment. At an average of KES 25,000 an order, paid on delivery, that is KES 3,300,000 out of stock and not yet paid.
At 2 days, it falls to 80 orders, or KES 2,000,000. Cutting 1.3 days collects KES 1,300,000 sooner, once, and keeps it working.
Those goods cost you money while they wait, at your holding costs. Customers notice the wait too: a shop that gets its stock next day has less reason to try another wholesaler.
Steps to Measure Order Cycle Time Accurately
Measure the same way every time, or the trend means nothing. Five steps keep it consistent.
Pick the Right Time Frame
Use a week if you deliver many orders a day, and a month if you deliver a few. Keep the same length each time, so periods compare.
Track Each Order's Key Dates
Record two dates per order: when it was placed and when the customer received it. Record when it was packed and when it left too, and you can see which stage is slow.
Count the orders delivered, not the orders placed
Count the orders delivered in the period, whenever they were placed. Leave out orders still on the road, and note cancelled ones separately.
Use the Formula
Subtract each order's dates in a spreadsheet column, then take the average, the median and the share on time. The formulas are in the example above.
Repeat and Compare
Compare each period with your own last one, not with another company's figure. A rise of half a day three weeks running is a signal; one bad week usually isn't.
Order Cycle Time by Industry
No reliable public benchmark fits a small African business. APQC's figures are for its members, and the ranges on vendor pages carry no source, so compare yourself with your own last quarter.
Retail and eCommerce
For an online shop, the clock starts at checkout and stops at the customer's door. A courier or boda boda rider often runs the last stage, so record their pick-up and drop-off times.
B2B and Wholesale
Wholesale orders arrive by phone, WhatsApp or a sales rep, and the clock starts then, not when someone types them in. Credit checks and part deliveries add days, so record each part delivery with its own date.
Manufacturing
Made-to-order goods add production time to the cycle. Measure order to delivery for the customer, and production on its own, so you know which part grew.
Subscription Businesses
A subscription ships on a schedule, so measure lateness against the promised date rather than cycle time. The share delivered on the promised day is the number to watch.
Dropshipping
In dropshipping, the supplier holds and ships the stock, so most of the cycle is theirs. Measure each supplier's cycle separately, and drop the slow ones.
Common Mistakes That Slow Down Order Cycles
Six habits add days without anyone noticing. Each has a cheap fix.
1. Manual Order Entry
Orders taken on WhatsApp and typed in later wait in a phone until someone has time. Record each order as it arrives, with its date.
2. Disorganized Warehouse Layout
Pickers who hunt for products lose minutes on every order. Put the fast sellers nearest the packing table, and label every shelf in the warehouse.
3. No Clear Fulfillment Protocols
Without a fixed routine, each order waits for someone to decide. Write down who picks, who checks and who packs, and when restocks and stock checks happen.
4. Out-of-Stock Inventory
An order for something you don't have waits for the supplier, and that wait lands in your cycle time. Both late orders in the example waited for stock.
A reorder point per product, set as in how to avoid stockouts, is the fix.
5. Lack of Real-Time Tracking
If nobody knows which orders are packed and which are on the road, delays surface only when a customer calls. A status on each order, updated as it moves, shows them while there is still time to act.
6. Ignoring Cycle Time Data
A figure measured once and filed changes nothing. Put the median and the share on time on the weekly meeting's list.
Strategies to Reduce Order Cycle Time
Fix the slowest stage first: speeding up a fast one changes little. Order fulfillment strategies covers the wider choices.
Fix Warehouse Bottlenecks
Time one order through each stage: taking it, picking, packing, waiting for transport, the road. The longest wait is your bottleneck, and it may be the wait for transport rather than the work.
Set Clear Protocols
Set a cut-off: orders confirmed before 11:00 leave the same day, later ones the next morning. Customers plan around a promise they can rely on.
Monitor Cycle Times Often
Check the week's median every Monday. A slow week caught in days costs less than one found at the end of the month.
Automate What You Can
Let orders from your online shop arrive in the same system as your stock, so no one types them twice. Automate the record, and keep a person on the decisions.
Outsource to Speed Things Up
A courier or a delivery rider service can shorten the last stage if your own van runs once a day. Measure their stage separately, and keep them only if it shrinks.
How to Use Order Cycle Time to Improve Operations
Treat the figure as a running test: set a baseline, change one thing, measure again.
Set Benchmarks
Your first month's median and share on time are your baseline. Set a target you can reach in a quarter, such as 80% of orders within 2 days.
Identify Delays
Split the cycle into stages and time each one. For the Nairobi wholesaler, the split might look like this.
| Stage | A usual order | The two late orders |
|---|---|---|
| Order taken and confirmed | The same day | The same day |
| Waiting for stock | None | 3 and 6 days |
| Picking and packing | Under a day | Under a day |
| Waiting for the van, and the road | 1 to 2 days | 2 days |
The delay is the wait for stock; the warehouse and the van are fine. That points the fix at buying, not at packing.
Improve Weak Areas
Fix only the stage that grew. Moving shelves won't help an order that is waiting for a supplier.
Measure Changes
After a change, measure for at least four weeks before you judge it. One fast week proves little.
Train Your Team
Show the team the weekly median and what moved it. People speed up a number they can see.
Use Tools That Help
A system that keeps every order's date and status saves the spreadsheet's typing. The ArmPOS steps are below.
Order Cycle Time vs Lead Time: Know the Differences
Order cycle time is your customer's wait for you; lead time, in stock planning, is your wait for your supplier. The same formula measures both, from opposite sides of your business.
Order Cycle Time
It runs from your customer's order to their delivery, and measures how fast you serve.
Example: a shop orders on Monday and receives the goods on Wednesday, so the order cycle time is 2 days.
Lead Time
It runs from your purchase order to the goods arriving in your store, and measures how fast your supplier serves you. Some guides use "lead time" for the customer's whole wait instead; this page uses it as stock planning does.
Example: you order from a Mombasa importer on Monday and the goods reach Nairobi on Friday, so the lead time is 4 days.
Why the Difference Matters
A long order cycle is yours to fix. A long lead time is your supplier's, and you plan around it with a reorder point that covers the wait.
Measure both with the same two columns: date ordered, date received. Your purchases give you the lead time the way your sales give you the cycle time.
How to measure order cycle time in ArmPOS
ArmPOS keeps each order's date and its delivery status in one list. You add the delivery day in a spreadsheet, and the formulas above do the rest.
- Record each order the day it arrives. An order taken by phone goes in through Sales › Add sale, dated the day it arrived. Set its Status to ordered, which moves no stock yet (Add a sale without the POS).
- Online orders arrive on their own. They wait in Store › Online Orders with their date, and confirming one turns it into a sale (Online orders).
- Follow it to the door. In Sales › All Sales, the row's Edit Shipping sets the status: Packed, Shipped, then Delivered (Shipments and deliveries).
- Complete the sale when the goods leave. Only a completed sale takes the stock (The sales list).
- Note the delivery day. A shipment holds one status at a time, so write the day it became Delivered in your spreadsheet.
- Export and calculate. All Sales and Sales › Shipments both download as EXCEL. Put the two dates side by side and use the formulas from the example.
- Do the same for your suppliers. Record a purchase as ordered on the day you order, and edit it to received when the goods arrive (Record a purchase). The days between are your lead time.
The steps are the same in every country ArmPOS serves, including Kenya.
Frequently asked questions
How do you calculate order cycle time?
Subtract each order's order date from its delivery date, add up the results, and divide by the number of orders delivered. Ten orders that took 33 days in total average 3.3 days.
What is a good order cycle time?
The one you promised your customers, kept for most orders. No public benchmark fits every trade, so set your own baseline and improve on it quarter by quarter.
Does order cycle time include delivery?
In APQC's measure, yes: it runs from the order to delivery. Some sellers stop at dispatch; either works if you say which and never mix the two.
What is the fastest way to cut order cycle time?
Find the stage where orders wait longest and fix that one. In the example it was the wait for stock, which a reorder point fixes; elsewhere it may be the van's timetable.
Pull last month's orders, put the two dates side by side, and work out your median and share on time. To keep every order's date and delivery status in one place, create a free ArmPOS account.
