Processing time vs. transit time: what should your delivery estimate include?
Separate the warehouse clock from the carrier clock so customers see an arrival range that reflects how an order actually moves.
A carrier may promise two-day delivery, but that does not mean an order placed tonight will arrive two days from now. The parcel still has to become ready for collection. That first clock belongs to the store.
Useful delivery estimates keep processing and transit separate internally, even when the storefront presents one simple arrival range. Mixing the two makes it difficult to update the promise when warehouse capacity or a shipping service changes.
Processing ends when the carrier takes possession
Processing time covers picking, production, personalization, quality checks, packing, and any transfer required before handoff. Count the days the operation actually works. If weekend orders wait until Monday, Saturday and Sunday should not quietly consume two processing days.
The cutoff matters too. An order placed before a 2 p.m. warehouse cutoff may enter today's queue; the same order at 2:05 p.m. starts on the next eligible day. Describe that operational boundary before choosing the dates to display.
Transit starts at handoff, not checkout
Transit time is the carrier's journey from collection to delivery. It varies by service, destination, and working-day calendar. Use the ordinary service the customer is likely to receive, rather than borrowing the fastest result from an express option that has not been selected.
Example: an order needs 1–2 processing days and 3–5 transit days. Its honest delivery window is built from both ranges after applying cutoffs, weekends, and holidays—not presented as “3–5 days” from checkout.
Give each clock an owner
Warehouse changes should update processing rules. Carrier or destination changes should update transit rules. This division makes maintenance much easier than editing one unexplained total across many products.
Review recent ordinary orders, not only the best and worst exceptions. A range should cover the normal path with enough room for expected variation. If a delay becomes common, it belongs in the estimate rather than in an apology email.
Show the outcome in the language customers use
Most shoppers want an arrival date, not a lesson in fulfillment arithmetic. “Estimated delivery: August 12–15” answers the buying question directly. Add a short qualifier only when it changes the decision, such as “order by 2 p.m.” or “business days.”
Keep the two clocks visible in the configuration and testing process. On the storefront, combine them into one credible promise and place it beside the product decision.