In ecommerce fulfillment, lead time is the time needed before an order or item is ready to be handed off for delivery. It can include picking, production, personalization, assembly, quality checks, or other processing work.
Lead timeLead time
It should not be casually treated as the same thing as transit time. A useful timeline is:
order placed → processing or production lead time → carrier handoff → transit time → delivery
Lead time and transit time answer different questions
Lead time asks: > How long until the merchant can hand the order to the carrier or next fulfillment stage? Transit time asks: > How long does the carrier take after handoff to deliver it? Google Merchant Center's current shipping documentation uses closely related language: handling time runs from order placement until carrier pickup, while transit time begins after carrier pickup and ends at delivery.
A customer usually cares about the combined delivery estimate, but operators need the components separated because they are controlled by different systems.
Order cutoff can move the clock
Suppose the warehouse processes orders Monday through Friday with a 3 p.m. cutoff. An order placed Tuesday at 2 p.m. can begin processing Tuesday. The same order placed Tuesday at 5 p.m. may not enter the processing clock until Wednesday. That means "2 business days lead time" is incomplete without the business calendar and cutoff rule.
Lead time can be product-specific
A store can have:
- same-day lead time for stocked accessories
- 2 days for ordinary warehouse picking
- 7 days for custom embroidery
- 21 days for made-to-order furniture
A single storewide promise can therefore be inaccurate when a basket contains products with different preparation requirements. The system may need to calculate the order promise from the slowest relevant item, split the order, or show separate delivery estimates.
Lead time should be a range when variability is real
If custom production takes between 3 and 6 business days, publishing "3 days" because that is the best case creates avoidable disappointment. Useful inputs include:
- minimum processing time
- maximum processing time
- order cutoff
- working days
- production capacity
- queue length
- component availability
- quality-control time
During peak demand, queue length can be more important than the nominal time required to make one unit.
Lead time interacts with preorder and backorder promises
A preorder release date does not necessarily equal its ship date. After release or inventory receipt, the merchant may still need processing lead time. Likewise, a backordered product can arrive at the warehouse on Friday but not ship to all waiting customers until Monday or Tuesday. The customer promise should therefore avoid collapsing availability date and dispatch date.
Set a promise the operation can meet
A useful lead-time promise names the clock and the event that starts it. "Ships within 2 business days" gives the preparation window before carrier handoff. "Arrives 2 business days after dispatch" describes transit. "Made to order in 3 to 5 business days" describes production but may still need a separate shipping estimate. Mixing those clocks is one of the fastest ways to make an accurate internal plan look like a missed customer promise.
Use the slowest relevant item when one order contains products with different preparation needs, or split the promise when the platform can fulfill items separately. Record the order cutoff, local timezone, working calendar, and exception policy. A Friday order placed after cutoff may not enter the queue until Monday, and a public holiday can change the estimate without any change to the nominal processing task.
When actual handoff dates drift, compare the promised and observed intervals by product, warehouse, and season. A rising median can hide a long tail of custom orders that creates most support contacts. Update the promise from observed capacity and component availability, then show customers the remaining uncertainty instead of publishing a best-case number as if it were guaranteed.
Worked example
A merchant sells engraved bottles.
- order placed: Monday morning
- personalization and production lead time: 3 business days
- carrier handoff: Thursday
- transit time: 2 business days
- expected delivery: Monday, assuming the carrier delivers on the relevant business days and no holiday intervenes
Calling this simply "5-day shipping" hides the operational split. If production falls behind, the merchant needs to improve or buffer lead time. If packages leave on Thursday as planned but arrive late, the problem is in transit.
Lead time checklist
- Useful customer-facing language separates stages when necessary:
- "Made to order in 3-5 business days"
- "Ships within 1 business day"
- "Estimated delivery 2-4 business days after dispatch"
- Not every storefront needs all 3 lines. The point is that the merchant's internal model should know which clock it is promising
- Lead time is the merchant-controlled preparation interval. Transit time begins after handoff. The delivery estimate combines the relevant stages plus calendar rules and buffers
Every app on every plan. Connect your store and switch on the flows in an evening.