Lead time is the customer’s total wait, from the moment an order is placed to the moment it can actually be used. Transit time is the carrier’s movement clock: pick-up to arrival, nothing more. Mixing the two up is how planners end up with stockouts, blown SLAs and carrier contracts that reward the wrong behaviour.
Three things follow from that distinction:
- Promise lead time, not transit time, in customer-facing SLAs, because that’s the number the customer actually experiences.
- Use transit time for carrier scorecards and route decisions — it’s the only fair way to compare one lane or provider against another.
- Base delivery promises on the 95th percentile, not the average — a mean transit time flatters you right up until the shipment that misses it.
What follows covers the exact definitions, the formula that ties them together, a worked example, how to measure both properly, and the practical levers for shortening each.
Key Takeaways
Lead time governs customer promises and inventory buffers, while transit time governs carrier selection, and both must be measured by percentile, not average, to avoid missed deliveries.
| Point | Details |
|---|---|
| Know which clock you’re using | Lead time covers the full order-to-delivery wait; transit time covers only carrier pick-up to arrival. |
| Promise from the 95th percentile | Base SLAs on the 95th percentile of lead time, not the mean, to cut missed promises. |
| Transit time drives 30–60% of lead time | Expect transit to dominate the total on long international lanes, per the logistics and freight statistics guide. |
| Variance beats average for reliability | Two lanes with the same average transit time can have very different on-time reliability. |
| Same-day couriers collapse the gap | Urgent domestic jobs like Frphaulage’s 60 to 120 minute collection service make transit time nearly equal to lead time. |
Table of Contents
- Transit time vs lead time: the precise definitions
- How lead time and transit time fit together
- Why the difference actually matters operationally
- Measuring and reporting lead time and transit time properly
- Practical ways to cut transit time and overall lead time
- Frequently asked questions
- Sources
Transit time vs lead time: the precise definitions
Lead time is the full order-to-usable-delivery clock. It typically comprises five components: order processing, manufacturing or fulfilment, transit, customs or clearance, and receiving/put-away at the destination. Every one of those stages adds days a customer waits, whether or not a vehicle is moving.
Transit time is narrower. It starts when the carrier collects the goods and ends when they arrive at the destination address or port. Nothing before pick-up and nothing after arrival counts. According to the logistics and freight statistics guide, transit time typically makes up 30–60% of total lead time, with the remainder split across processing, fulfilment, and clearance.
Modal ranges give useful context: air freight typically runs several days total, while sea freight FCL port-to-port often takes several weeks, and both figures can climb during seasonal peaks, per the same guide.
A quick glossary, because these terms get blurred constantly:
- Shipping time — often used loosely as a synonym for transit time; avoid it in formal reporting.
- Delivery time — usually means the customer-facing promise date, which should be built from a lead-time percentile, not a raw estimate.
- Cycle time — measures active work within a process step, not the full customer wait. Tulip’s comparison is the clearest breakdown of how it differs from lead time.
Pro Tip: Timestamp every handoff, not just start and end. If you only log “order placed” and “delivered”, you’ll never know whether a slow week was caused by fulfilment queues or a sluggish carrier.
How lead time and transit time fit together
The relationship is arithmetic, not conceptual. Total lead time equals order processing, plus fulfilment or manufacture, plus transit time, plus customs/clearance, plus receiving and put-away. Transit time is one input among several, never the whole equation.
Here’s how that plays out for two very different shipments, using figures consistent with the logistics and freight statistics guide:
Notice how transit time dominates the ocean shipment’s total but is only half the story on the domestic order. That’s the pattern worth remembering: the longer and more international the journey, the more transit time swallows the lead-time budget, and the more the other components fade into rounding error.

Why the difference actually matters operationally
Treat transit time as if it were lead time and you’ll under-order safety stock, quote delivery dates you can’t hit, and pick carriers on the wrong criteria. The consequences show up fast:
- Stockouts from planning against a transit estimate that ignores processing and clearance delays.
- Inflated safety stock in the opposite direction, when planners pad excessively because nobody trusts the numbers.
- Missed customer promises, because averages hide the tail risk that actually causes complaints.
- Poor carrier selection, when procurement compares transit averages instead of variance and reliability.
Averages lie by omission. Two lanes can share an identical mean transit time of five days, yet one might range from four to six days while the other swings from two to eleven. The Cursa analysis on transit variability makes the case that variance, not the mean, is what actually breaks service-level promises.
That’s why the strongest operators set customer commitments from the 95th percentile of the lead-time distribution, not the average. It costs a little in headline speed but saves enormously in broken promises and expedited-freight bills.
Pro Tip: Convert your 95th-percentile lead time into a safety-stock rule directly: multiply the gap between your average and your 95th percentile by daily demand, and that’s roughly the buffer stock you need to stop stockouts caused by tail-end delays.
Measuring and reporting lead time and transit time properly
Reliable numbers start with reliable timestamps. Capture, at minimum: order received, order processed, pick/pack complete, carrier pick-up, carrier arrival at destination, customs cleared, and goods put away. Skip any one of these and you lose the ability to diagnose where delays actually originate.
From those timestamps, report:
- Average and median lead time, so you can see how skew affects your typical customer experience.
- 95th percentile lead time, the figure that should anchor SLAs and delivery promises.
- Transit time mean and variance, tracked per lane and per carrier, not blended into one national number.
- On-time probability to commitment (OTP/OTD), the single metric that tells you whether your promises are holding up.
Data hygiene matters more than dashboard polish. Fix a canonical clock and timezone standard across every system that logs a timestamp, decide upfront whether you’re measuring working days or calendar days, and store raw timestamps rather than pre-aggregated averages. Azure DevOps’s guidance on cycle and lead time dashboards makes the same point for software teams: percentile analysis only works if the underlying event data is clean.
Pro Tip: Never overwrite a raw timestamp with a recalculated or “corrected” one. Keep the original event log intact so percentile and variance calculations stay auditable months later.
Practical ways to cut transit time and overall lead time
Split your improvement effort into two buckets, because the levers are different.
Transit-focused actions:
- Switch modes where the economics allow it (air over sea for time-critical SKUs).
- Reduce lane variance by favouring carriers with tighter delivery windows over marginally faster but erratic ones.
- Optimise routing to cut unnecessary stops and dwell time with professional demolition haul off services.
- Manage delivery appointments proactively. The Cursa research links poor appointment scheduling directly to transit variability.
Non-transit actions:
- Speed up order processing with automated validation rather than manual review queues.
- Pre-clear customs documentation before goods reach the border.
- Expedite receiving and put-away with dedicated dock slots for priority freight.
A same-day courier scenario shows this clearly. A client needing urgent collection typically gets a 60 to 120 minute pick-up window with Frphaulage’s same-day courier service, and because processing and clearance are minimal or absent for a domestic same-day job, transit time and lead time converge almost completely. Shave the transit leg by 30 minutes through better routing, and the entire SLA band tightens by roughly the same margin, something that almost never happens on a multi-modal international shipment.
Pro Tip: Set your SLA at a specific lead-time percentile, then build an automated expedite trigger that fires the moment a shipment crosses that threshold, rather than waiting for a customer complaint to flag it.

Which metric should you actually prioritise?
If the customer relationship depends on a delivery promise, lead time is the contract. It’s the number a customer feels, and every hidden delay in processing or clearance erodes trust just as much as a slow lorry does.
If your job is carrier procurement or lane optimisation, measure transit time directly, because blending it into lead time hides which leg of the journey is actually underperforming. For same-day courier work, the two numbers nearly merge; for multi-modal international freight, transit time is only ever one component to manage, never the full picture. Frphaulage’s same-day courier guide illustrates well for urgent domestic moves.
Frequently asked questions
Is transit time the same as shipping time?
No. Shipping time is often used loosely to mean transit time, but it’s not a standard industry term, so it can also get confused with the entire lead time. Stick to transit time or lead time in formal reporting.
How do I calculate transit time for a shipment?
Subtract the carrier pick-up timestamp from the arrival-at-destination timestamp. That figure excludes processing, fulfilment, customs and put-away entirely.
What’s the difference between lead time and cycle time?
Lead time measures the customer’s full wait; cycle time measures active work time within a single process step, useful for internal process improvement rather than customer commitments, as Tulip explains.
Should I use average or percentile transit time for SLAs?
Percentile, specifically the 95th, because averages hide the tail-end delays that cause the complaints your SLA is meant to prevent.
Why does transit time matter more for international freight than domestic orders?
Because it accounts for a much larger share of total lead time on long international lanes, sea freight in particular, where transit alone can stretch past a month.
Sources
- Transit time, variability, and service‑level tradeoffs | Cursa
- Cycle time vs lead time vs takt time: what’s the difference? | Tulip
- Cycle time and lead time | Azure DevOps documentation
