Interested in a free 25+ eBook on the 7 Wastes? Please DOWNLOAD HERE.
Most online businesses that sell hardgoods explain delivery times as the following:
{[click + buffer + fulfillment processes] + [delivery time]} = [Total Delivery Time]
The equation above is common in fulfillment operations, assuming the inventory is housed somewhere, such as a warehouse, not at a 3rd party vendor.
From a company’s perspective, the equation above shows where the improvement can be made — yes, the fulfillment process because that is the part that is within control. Once it leaves the warehouse, it is up to the Third Party Logistics Vendor — UPS, FEDEX, USPS, etc. Amazon explains this relationship with the following diagram:

From the customer’s perspective, it is good to know the overall process, such as described above. To find out, however, how the company is doing in reality is a different story — that is, empirically, how is the company doing in regards to getting stuff to the customer in an ecommerce environment?
Time based data is critical in empirical studies of this sort. For the process above, we need to know the “click” timestamp and the time the customer signed for the product. That would give us an end-to-end picture of our service in terms of getting the customer’s order to them within some timeframe. Using the data I suggested, you would end up with continuous data over time t. This aggregate data can give us several key measures of how the company is actually doing in regards to delivery times, using empirical data.
The first measure we would arrive at is the mean, or the average.

Then, we would calculate the standard deviation.

Given the data set, we would want to know the distribution of the data; the data will most likely be approximated by the Normal Distribution. We want to know this, so that we can apply the above measures in an important way: Given the Mean, we can calculate that (1 Standard Deviation) from the Mean (+/-) what 68% of the orders will be delivered in.
For example, if we determine that we are, on average, delivering orders at 5 days, with a standard deviation of 3 days, then, we can conclude or approximate, that 68% of orders will be delivered within 2 to 8 days. The 68% number can be used if and only if the data is described by a normal distribution. Here’s a picture of what I’m trying to explain:
Below is a hypothetical map of what an order system might look like. This system involves a front-end store, credit card verification, and warehousing activities:
Click on the image for a larger view.
The image above shows a data set that fits a normal distribution; the mean is calculated and so is the standard deviation. Given that the data fits the normal distribution, we can conclude that the data shows delivery times to be between ~3 and 12 days.
Why is this Important?
It’s important in several ways: (1), knowing this will help us better understand the customer experience — that is, when do they typically receive their stuff. The range of ~3 to 12 days is arguably a bad customer experience — there’s no smoothing effect here, but highly variable. The goal is to reduce variability so that the customer can have confidence in the company’s delivery estimates; (2) this empirical data can help the company pin-point where improvement opportunities might be; (3) this data might provide insight into product or lead to new product or shipment types.
*NOTE: The above is relevant in any process where there is a vendor-partner relationship or build-to-order process.
It’s about the Customer
Again, it’s about the customer. Online shopping is the norm and online companies need to know, empirically, how they are doing; what their service level is like. Following the above will help in that process and allow the company to better understand the customer experience and improve accordingly.1
- Related WMS or Warehouse Management System searches: inventory control management software,computer inventory management software,asset inventory software,web based inventory software,event management software,facilities management software,barcode inventory tracking software,freight management software,warehouse floor plan software,retail pos software,retail point of sale software,business inventory software ↩
search terms for this article:
amazon delivery process, amazon warehouse management, amazon warehouse management system, apple warehouse management system, shmula amazon delivery, amazon shipping process, warehouse delivery process, er diagram for supply chain management, Amazon supply chain management system, er diagram for amazon, entity relationship diagram for pizza delivery system, er diagram for warehouse management system, wms system at amazon, er diagram of supply chain management, turnaround time warehouse, delivery system ERD, er diagram of supply chain management system, manage a warehouse amazon case, amazon warehouse deliveries, warehouse management amazon, product order delivery system erd, sample shipping processes system, sample wms er models, pizza delivery process times data, shipping process control measures, shipping process flow chart, shipping process flow chart diagram, how to use warehouse delivery order, process workflow of pizza delivery, need a pictuire of a entity-relationship diagram for warehouse management systems, order product ship supply e-r diagram customer e-commerce, pizza delivery process flow chart, pizza delivery erd diagram, pizza delivery er diagram, pizza delivery data flow diagram, pizza management system erd, order to delivery process flow chart, process flow amazon, process flow diagram for pizza delivery system, pizza management system ER, standard shipping process flow chart, supply chain amazon case study, warehouse management of Amazon com, warehouse management system amazon, warehouse management system entity relationship diagram, Warehouse management system eR diagram, supply and delivery diagram, warehouse management system image, warehouse point of sale system er diagram, warehouse process with pictues, warehousing management data flow diagram, what is delivery data in supply, what is meant by deviation in warehouse management system, what is standard deviation for shipping time, warehouse management erd, warehouse management er diagram, supply chain diagram mapping, supply chain erd model, supply chain flows Amazon, supply chain management and its processes flowchart, supply chain management erd, supply chain management system process diagram, Supply Chain Process Flow Diagram push system, third party logistics diagram, turnaround time supply chain, ware house management system amazon, warehouse delivery diagram, apple warehous management system, why is time important throughout the shipping process, flowchart of management shipment & deliveries, amazon chain management system, data flow model diagram of pizza delivery, data flow shipping system in warehouse to the customer, delivery order in shipping flow chart, delivery order system erd, delivery process flowchart in pizza retailers, delivery process in data warehousing, delivery time item to the warehouse, delivery times online shipping, dfd diagram for supply management, dfd diagram of warehouse management system, diagram supply chain management of fedex, data flow diagram warehouse management system, data flow diagram of an warehouse inventory system, data flow diagram from scm for online shopping, amazon delivery processing time, amazon erd diagram, amazon shipping process study, amazon supply chain management diagram, amazon warehouse picking method, Amazon warehouse procedures, amazon warehouse processing, amazons supply chain management software, case study on amazon com warehouse management, data flow diagram examples wms, data flow diagram for scm, diagram the supply chain for amazon, e pizza entity relationship diagram, er diagram for image processing system, er diagram of pizza manufacturingRelated Articles:
![]() |
![]() |
![]() |
||
This post was written by Pete Abilla | ||||











The Apple iPhone Supply Chain
Jeff Bezos and Root Cause Analysis
The Toyota A3 Report
Queueing, Disneyland, and FastPass
Zipcar Customer Experience: Variability, Utilization, and Queueing
Process Control and Luck
Poka Yoke Example: Prevent Error Through Embarrassment and Humiliation
Queueing Theory: Part 3
Emergency Room (ER) Wait Times
Quality and Continuous Improvement;