Supply Chain Lead Time Calculator
Calculate end-to-end time from purchase-order release to stock being available in your warehouse. Model international stages, turn elapsed time into an estimated delivery date or latest safe order date, and compare a proposed supplier or freight plan with your current process.
1. Set dates and assumptions
2. Build and compare scenarios
All enabled stages are treated as sequential and non-overlapping. Enter elapsed values using one day convention throughout. “Current” and “Proposed” can represent suppliers, freight modes, or improvement plans.
Inventory planning (optional)
Lead-time demand uses the Current scenario’s buffered planning days. Stockout date assumes constant calendar-day demand, no receipts, and the order date as the inventory as-of date.
Advertisement
Planning summary
Expected arrival range
Each date uses the corresponding optimistic, typical, or delayed enabled-stage total plus the full planning buffer. Fractional date totals round up to the next countable day.
Current vs. Proposed
| Measure | Current | Proposed |
|---|---|---|
| Operational days | — | — |
| Planning days | — | — |
| Expected arrival | — | — |
| Largest contributor | — | — |
Current operational timeline
Bar widths show each enabled stage’s share of raw operational lead time. A dark inset marks the largest contributor.
Inventory planning
How to build a useful lead-time estimate
Supply-chain lead time is the full elapsed interval from releasing a purchase order until the goods are usable. Include only stages that occur in your flow, define each stage’s start and finish, and avoid double-counting. This calculator sums enabled stages sequentially; if production, documentation, or transport activities overlap, use a dependency-based schedule instead.
- Use historical timestamps: group comparable orders by supplier, lane, freight mode, product, and season. A median is often a stronger typical value than a simple mean when rare delays skew the data.
- Keep day conventions consistent: use calendar days for continuously elapsed lane data or business days for working schedules. In business mode, add the relevant supplier, customs, and warehouse holidays manually.
- Separate expectation from commitment: operational lead time is the expected process total. Planning lead time adds a visible safety buffer for order promises and replenishment timing.
- Interpret the largest contributor carefully: it is a bottleneck candidate, not a calculated critical path. Prioritize it only after checking cost, variability, dependencies, and feasibility.
The stage vocabulary is aligned with the professional terminology collected in the ASCM Supply Chain Dictionary. Customs values must reflect the applicable country and entry type; for example, U.S. Customs and Border Protection describes document review and examination as separate sources of processing time.
Formulas and notation
| Symbol | Meaning | Formula or rule |
|---|---|---|
sᵢ | Typical time for enabled sequential stage i | Non-negative days using the selected convention |
Lₒ | Operational lead time | Σ sᵢ for enabled stages |
B | Safety buffer | Separate non-negative planning allowance |
Lₚ | Planning lead time | Lₒ + B |
W | Weeks | Lₚ ÷ 7 |
A | Arrival date | order date + ceil(Lₚ) countable days, adjusted for the selected start convention |
Oₗ | Latest safe order date | need-by date − ceil(Lₚ) countable days, adjusted for the selected start convention |
pᵢ | Stage share | sᵢ ÷ Lₒ × 100% |
I | Scenario improvement | (Current Lₚ − Proposed Lₚ) ÷ Current Lₚ × 100% |
Dₗ | Lead-time demand | average daily demand × Lₚ |
Date inputs and copied timestamps use the unambiguous ISO 8601 year-month-day format. Calendar mode counts weekends and entered holidays; business mode excludes Saturdays, Sundays, and entered holidays. Decimal durations remain in numeric totals but round up only when mapped to a date.
Worked planning examples
| Case | Inputs and arithmetic | Date and result | Decision supported |
|---|---|---|---|
| Domestic replenishment | Processing 1 + production 3 + quality 1 + packing 1 + last mile 2 + receiving 1 + putaway 1 = 10 operational days; buffer 2 = 12 planning days. | Order 2026-07-06; calendar days; start excluded → arrival 2026-07-18. Production is largest: 3/10 = 30%. | Order by 6 July to make an 18 July availability commitment. |
| Ocean import | 2 + 10 + 2 + 2 + 2 + 3 + 24 + 4 + 2 + 3 + 1 + 1 + 1 = 57 operational days; buffer 7 = 64 planning days. | Order 2026-07-06; calendar days; start excluded → arrival 2026-09-08. Transit is largest: 24/57 = 42.1%. | Compare a faster sailing with the cost of holding at least 64 days of demand coverage. |
| Air-freight proposal | Comparable air flow = 26 operational + 3 buffer = 29 planning days, versus the 64-day ocean plan. | Saves 35 days; improvement = (64 − 29) / 64 = 54.7%. Order 2026-07-06 → arrival 2026-08-04. | Value 35 days of time saved against the air-freight premium and emissions policy. |
| Reverse need-by plan | 12 operational business days + 3 buffer = 15 planning business days; no holidays; start excluded. | Need by Friday 2026-10-30 → latest safe order Friday 2026-10-09. Production 5/12 = 41.7%. | Release the order no later than 9 October; enter local holidays before committing. |
Frequently asked questions
What does supply-chain lead time include?
Include every sequential elapsed stage from releasing the purchase order until usable stock is available: supplier processing, production, inspections, packing, documentation, origin and destination handling, transport, customs, final delivery, receiving, and putaway. Disable stages that do not apply.
How are lead time, cycle time, and transit time different?
Lead time is the full request-to-availability interval. Cycle time is the time spent completing a defined process, such as production. Transit time is only the movement between locations, so it is normally one part of lead time.
Should I use calendar days or business days?
Use the convention in the source data. Calendar days include weekends; business days exclude Saturdays, Sundays, and any holidays you enter. Do not add calendar-day stage averages as business days without converting them.
Does the order date count as day one?
You choose the convention. Excluding the order date makes the next countable day day one and is the default. Including it makes the order date day one when it is countable; a weekend or excluded holiday moves day one to the next business day.
How does the calculator treat weekends and holidays?
Calendar-day mode counts every date. Business-day mode skips Saturdays and Sundays plus valid ISO-format holiday dates entered in the holiday field. Holidays are not fetched automatically, so enter the calendars relevant to the supplier, carrier, customs authority, and warehouse.
How should I estimate customs time?
Use clearance history for the same product, country pair, port, broker, and entry type. Separate routine document processing from inspections or holds, and use optimistic, typical, and delayed values when the history varies materially.
How can I calculate a missing stage value?
Use timestamped historical records and calculate the elapsed time between the stage's defined start and finish. Prefer the median for a robust typical value, a lower percentile for optimistic time, and an upper percentile for delayed time; document the day convention used.
How is a planning buffer different from safety stock?
A planning buffer adds time to the schedule. Safety stock adds inventory units to absorb demand or supply variability. They address related risk in different units and should not be treated as interchangeable.
How does lead time affect the reorder point?
Lead-time demand equals average daily demand multiplied by planning lead time. A basic reorder point is lead-time demand plus safety stock, so longer lead time generally requires an earlier order or more inventory.
How should I use actual supplier history?
Measure each stage with consistent start and finish timestamps, segment records by supplier, lane, mode, and season, then refresh typical and range values regularly. Investigate outliers rather than silently deleting them, because they may reveal repeatable delay causes.
Methodology, assumptions, and review
Method: enabled stage values are summed as a sequential process; a separate buffer creates planning time; countable-day arithmetic converts the result into dates; uncertainty totals use the optimistic, typical, and delayed columns independently. The largest value is reported as a contributor, not a critical path.
Evidence: terminology is checked against the ASCM Supply Chain Dictionary; customs guidance is linked to U.S. Customs and Border Protection; date display follows ISO 8601. For UK schedules, verify manually entered exclusions against the official UK bank-holiday calendars.
Review: reviewed 18 July 2026 by the Starlight Tools Operations Research Team for formula consistency, date-counting behavior, international stage coverage, and accessibility. This is a deterministic planning model, not a live tracking or forecasting service.
Planning estimate disclaimer
Outputs are estimates, not delivery guarantees. Validate assumptions against current supplier, carrier, broker, port, customs, and warehouse data before making commitments. The tool does not fetch live schedules, disruptions, holidays, inventory transactions, or clearance status.