Order fulfillment cycle time from receipt to delivery

Use the same orders to measure warehouse processing, pickup waits, and the time after carrier handoff.

Kartik Deshpande··6 min read

Order fulfillment cycle time is the elapsed time from receiving an order to delivering all the goods the customer is due. For each completed order, subtract the order receipt timestamp from the final delivery timestamp. Average those durations to get the mean, and show the number of open orders alongside it so the report accounts for work still in progress.

If a weekly review shows that orders took longer to arrive, check when each order finished packing and when its last parcel reached a carrier. These checkpoints distinguish time spent getting an order ready from time spent waiting for pickup or delivery. A split order counts once in the customer measure and can have several parcel timelines underneath it.

Set the checkpoints from order receipt to delivery

APQC measures customer order cycle time from customer placement to delivery, including weekends. If orders arrive through a channel that sends them to your ERP in batches, capture the original receipt time (the storefront or order inbox timestamp) so the batch delay shows up in the customer measure. Convert timestamps to UTC before subtracting, then divide elapsed hours by 24 for a calendar-day view.

Ask the warehouse to identify the pack-complete event, then agree with the shipping team on which event shows that a carrier took possession. Use a pickup confirmation when it establishes custody, or use the first qualifying carrier scan and label it as a proxy when pickup time is unavailable. FedEx distinguishes label creation, entry into its network, and delivery in its tracking status definitions. A label timestamp can leave a pickup wait looking like transit time.

Record delivery from a confirmed carrier event or proof of delivery tied to the parcel. An estimated date can be useful in a service queue. Using it to close an order would turn a prediction into a measured duration. Keep the carrier, tracking number, and event timestamp so someone can trace that duration back to the shipment record.

Order milestones and their source records
Order received
Order record
Packing complete
Warehouse event
Carrier handoff
Custody evidence
Delivery confirmed
Delivery evidence
Keep the order identifier through each handoff so shipment and delivery events can be traced to the same order.

Keep the same orders through each stage

Pick a receipt window, an eligibility rule, and a reporting cutoff. For a weekly comparison, use orders received each week and give each receipt cohort the same time to mature, such as one week after its receipt window closes. A completed-order average can fall while slow orders remain open, so show the delivered count, open count, and age of open orders at the cutoff alongside it.

Match each parcel to its order lines and quantities before reducing the data to one row per order. For a split order, the full-delivery timestamp is when confirmed deliveries cover all quantities the customer is due. Keep an order open while any required quantity remains outstanding, even if a first parcel arrived. If tracking evidence is missing, flag that gap within the open count so it can be investigated apart from parcels known to be in transit.

Count quantities from distinct parcels, since repeated delivery events for the same parcel can make an incomplete order look complete. Keep approved cancellations and their effective dates with the order. That preserves the quantities the customer was due at the reporting cutoff and lets you report fully canceled orders outside the delivery measure.

For stage comparisons, take the latest pack-complete event, last carrier handoff, and final delivery across the required parcels. In this calculation, order-to-ship time ends at that last handoff. Compute the differences on the same orders with usable evidence for every stage and show how many complete orders met that requirement. The stage averages describe that subset when some delivered orders lack checkpoints.

Check how the dashboard chooses its orders before copying its stage figures. Shopify’s order reports documentation describes a median for each selected stage and counts orders that completed that stage in the report period. That view can answer how fast recent completions moved. A receipt cohort answers what happened to the orders taken in a particular period.

Calculate the average for a split shipment and an open order

Suppose three parcel orders arrive on Monday, with no cancellations and all timestamps on the same clock. The table shows one row per order and uses the latest required milestone at each stage. Order B has two parcels. The first arrived Tuesday at 12 p.m., and the last arrived Thursday at 10 a.m. The review cutoff is Friday at noon.

OrderReceivedPacking completeLast handoffFull deliveryElapsed to delivery
AMon 8 a.m.Mon 12 p.m.Mon 2 p.m.Tue 2 p.m.30 hours
BMon 8 a.m.Tue 12 p.m.Tue 4 p.m.Thu 10 a.m.74 hours
CMon 10 a.m.Tue 10 a.m.Tue 2 p.m.Open at cutoffPending

The completed-order mean is (30 + 74) ÷ 2 = 52 hours. Orders A and B averaged 16 hours from receipt to complete packing and 3 hours from complete packing to last handoff. They averaged 33 hours from last handoff to full delivery. Those three means add to 52 hours because each uses the same completed orders and the same checkpoints.

Report two orders fully delivered and one open, with the open order at 98 hours of age as of Friday noon. Counting B’s first delivery would give it 28 hours even though the customer waited another 46 hours for the second parcel. Counting C’s age as a delivery time would make the published mean depend on the review hour for an order that has yet to finish.

Explore a fulfillment report on your data

Start with a permitted order export and its parcel events to see which checkpoints the records support.

Find which part of the wait grew

If receipt to complete packing grew, trace the order through release, picking, and packing. A late release with a stock hold calls for different work than an order released on time and left in the pick queue. For a delay inside one repeatable warehouse task, Cycle time: measure completions without hiding delays covers how to isolate the task’s own boundary.

If packing to handoff grew, compare the pack event with the scheduled pickup and custody evidence. Parking a finished order after a missed pickup and waiting for a late first scan can look the same in a feed that starts at carrier network entry. Use that gap to ask for the dock or pickup record before assigning ownership.

For time after handoff, inspect transit by parcel using that parcel’s own custody and delivery timestamps. On a split order, the parcel handed over last may differ from the one delivered last. The order’s last-handoff-to-full-delivery interval measures the remaining customer wait, so keep each parcel’s own transit time when assessing a carrier or service level.

When a delay starts with a shortage, check which quantities were available to ship as a separate measure. Fill rate: calculate units, lines, and complete orders measures how much demand was met under a stated cutoff. Cycle time measures the elapsed wait. Faster deliveries for completed orders can coexist with more demand left unfilled.

How Permute supports a recurring fulfillment review

Permute sells connected business data and custom applications for teams that need to use their data in reporting and AI. We can combine permitted order records and warehouse or carrier exports, then match the records using order, line, and parcel identifiers where the sources provide them.

We apply your declared rules for receipt time, split shipments, and the reporting cutoff to the connected records. An operations manager can use the resulting dataset in a custom app or through governed access in a tool such as Claude. The review can show the late orders by checkpoint and the source events the manager has permission to see.

Confirm event coverage before assigning delays

For this reporting workflow, we read the records and leave order and carrier updates to the teams that own them. Coverage depends on which events the connected sources provide. The review can surface an absent handoff event and identify the orders affected, leaving the shipping team to confirm custody from its own records.

Measure the customer’s wait from order receipt through full delivery, with one duration per completed order. Keep open orders visible at the cutoff so changes in the completed-order mean have context. Compare warehouse and carrier checkpoints on the same orders, and use each parcel’s own timestamps when you need to investigate its transit.

Review the checkpoints in your fulfillment report

Bring your current metric and the order, warehouse, and shipment records behind it to review where the reported time comes from.

Questions about measuring order fulfillment time

What is the difference between order-to-ship time and order-to-delivery time?

In this calculation, order-to-ship time ends at the last required carrier handoff. Order-to-delivery time continues until all required quantities have delivery confirmation. If the warehouse reports a shipping timestamp, check the event behind it before treating it as evidence of carrier custody.

Do weekends count in fulfillment cycle time?

Elapsed customer wait includes weekends, consistent with APQC’s calendar-day approach. If a warehouse measures work against staffed shifts, keep that operating-hours measure labeled separately so it can be compared on its own basis.