Click-to-Ship: Delivery Process Times

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:

shmula.com, delivery process times

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.

shmula.com, mean

Then, we would calculate the standard deviation.

shmula.com, 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.

Share This Post:



  • Digg
  • Facebook
  • Yahoo! Buzz
  • del.icio.us
  • FriendFeed
  • Suggest to Techmeme via Twitter
  • Reddit
  • Google Bookmarks
  • Live
  • StumbleUpon
  • LinkedIn
  • Slashdot
  • MySpace
  • E-mail this story to a friend!

2-pizza teams (9)
3 C's (3)
5S (37)
A3 Report (9)
adoption (6)
agile/software (59)
ajax (4)
amazon (50)
apple (2)
apple iphone (6)
axiom (3)
Aza Raskin (8)
backcountry.com (2)
berlin (1)
bill gates (1)
bill marriott (1)
blog tag (1)
book reviews (4)
bullwhip effect (5)
business (381)
business plans (3)
busm361 (13)
BzzAgent (12)
call center and queueing (11)
car buying (2)
Carbonite (1)
chicago (1)
click fraud (1)
click-to-ship (21)
clocky (2)
colin powell (2)
community (2)
company interviews (18)
company interviews (6)
complexity (32)
costs (8)
culture (1)
customer experience (4)
customer obsession (45)
customer segmentation (8)
customer service (13)
design thinking (11)
digg (4)
drum-buffer-rope (38)
dublin (1)
dynamic systems (24)
eBay (6)
economics (3)
efficiency (3)
ethnography (28)
family (18)
featuritis (15)
flexibility (1)
forecasting (2)
four performance dimensions (2)
Fun With The 2×2 Matrix (1)
game theory (7)
Gemba (60)
genchi genbutsu (65)
general (136)
germany (1)
google (15)
heijunka (64)
holidays (1)
how to be a human (1)
image uploading (1)
iphone (4)
ishikawa (67)
IT at Toyota (66)
just-in-time (4)
kaizen (1)
kanban (42)
law of instinct (1)
Leadership (33)
lean (148)
Lean Consumption Maps (94)
learning curve (1)
licketyship (1)
mark cuban (1)
martin luther king (1)
mary poppendieck (1)
metrics (73)
microsoft (6)
milton friedman (1)
moving average (1)
muda (64)
nba fines (1)
net promoter score (nps) (1)
obeya (36)
Off-Topic (1)
onstar (1)
operations (108)
pageviews (3)
pareto principle (38)
patent (1)
peanut butter manifesto (2)
philosophy (3)
Poka-Yoke (3)
poppendieck (3)
powerpoint sucks (2)
private equity (4)
process measures (5)
product development (19)
productivity (4)
quality (39)
queueing theory (40)
Raffle (1)
rational choice (2)
regression analysis (18)
respect for people (3)
root cause analysis (56)
sarah+palin (2)
seth godin (1)
simplicity principle (10)
six sigma (122)
snowboarding (2)
social media (3)
spam (1)
statistical process control (46)
strategy (44)
suburban (1)
supply chain (24)
takt time (8)
teaching (2)
team size (9)
technology (105)
the beer distribution game (1)
the profit tree (7)
The Visual Factory (11)
theory of constraints (41)
time (2)
timeline (3)
tony+hsieh (9)
toyota (73)
travel (1)
trump bankruptcy (1)
twitter (8)
uspto (1)
utah deal flow (2)
variation (69)
venture capital (1)
Visual Management (9)
waste (56)
website traffic (2)
Wing Chun (2)
wisdom of crowds (1)
wisdom teeth (1)
word-of-mouth marketing (18)
yahoo (2)
zappos.com (9)
zero defects (3)

WP Cumulus Flash tag cloud by Roy Tanck requires Flash Player 9 or better.


If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.

Comments

[...] Click-to-Ship: Delivery Pr… [...]

[...] Click-to-Ship: Delivery Pr… [...]

[...] Click-to-Ship: Delivery Pr… [...]

[...] Click-to-Ship: Delivery Pr… [...]

[...] The Apple Shenzhen, China facility assembles the hardware, holds inventory, and handles the pick, pack, and ship steps of the fulfillment process. [...]

[...] Click-to-Ship Processes [...]

[...] Click-to-Ship Processes [...]

[...] Click-to-Ship Processes [...]

[...] Click-to-Ship Processes [...]

Leave a comment

(required)

(required)


Additional comments powered by BackType