Supplier Lead Time Calculator
The formula
What the supplier lead time tells you
The real clock from PO release to usable receipt, measured in completion and judged against the quoted promise — planning honesty in one number.
Calculation: Actual lead = total days ÷ orders; reliability = deviation from promise. Enter your inputs and every substitution is shown below the result.
Reading the result
Lead-time variance is the expensive half: a stable 12-day supplier often beats a 7-day one that sometimes takes 20.
Rules of thumb: OTD ≥ 95% and lead deviation ≤ ±2 days marks a reliable supplier
Limitations and best practice
Receipt-quality rejections extend effective lead invisibly — measure time to usable stock, not time to the dock.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
Quote to suppliers the promise or the actual?
Sample size matters?
Source & methodology
Supplier performance measurement.
Supplier Lead Time explained: formula, worked example and honest limits
Time is the one input nobody can renegotiate, which makes getting the arithmetic right worth the minute it takes. Supplier Lead Time is the kind of number people argue about from memory. This page ends that argument with arithmetic you can watch happen: enter your figures, get Actual supplier lead time in real time, and see every substitution printed below.
There is a habit that separates people who get useful answers from Operations numbers: they decide what question the figure answers before they compute it. Supplier Lead Time answers “Actual supplier lead time?” — and nothing else, which is precisely why the result is trustworthy.
What makes Supplier Lead Time worth calculating is not precision but position: it tells you which side of a threshold you are on, and by how much. A rough figure that settles the direction beats an elaborate one that never commits.
Every figure in the prose is generated by the engine rather than written beside it — the worked example resolves to actual supplier lead time = 5.9 days on the default inputs, and the sensitivity section ranks the inputs that move the result — POs completed first, at ≈11.1 % of the headline for a ten-percent error either way in that input. Work down the page and by the end you could re-derive the result in a spreadsheet from memory.
How Supplier Lead Time is computed, line by line
The engine implements a single stated model: Actual lead = total days ÷ orders; reliability = deviation from promise. There is no hidden coefficient and no login-gated precision — the formula printed is the formula executed, which is also what makes the result citable.
POs completed (example value 135) is a plain measured quantity — the unit shown in the label is the unit the formula expects. Replace the example with the figure from your own records — the tool recomputes instantly and the printed steps follow your numbers.
Sum of their quoted-vs-actual days (example value 790) is a measured number in the unit named by the label; the formula does not convert for you. If the period is partial, decide whether you mean elapsed or planned time and keep that meaning across every field.
Promised lead time (days) (example value 5) is a quantity rather than a category — precision here is cheap and worth having. Use the value as of today, not as of the last time you looked — time fields drift silently.
Supplier Lead Time with real numbers, step by step
Abstract formulas are hard to trust, so here is the complete substitution using the default inputs, written the way an examiner would want it. Starting figures: POs completed, Sum of their quoted-vs-actual days, Promised lead time (days). Run to the end, the actual supplier lead time resolves to 5.9 days — Running 0.9 days over promise — plan on this, not the catalog number on the bands this tool uses.
- Actual = 790 PO-days ÷ 135 = 5.9 days
- Re-plan MRP on the actual distribution; the quoted number is marketing until audited
Deviation vs promise — 0.9 days. Read next to the headline, this is the figure that shows the shape of the trade-off.
Promise reliability ratio — 0.85. Compare it against the main result of 5.9 days before drawing conclusions.
Extra safety days at 95/70 reliability — 1.4. This is the number experienced users quote when the headline alone would mislead.
Keep this worked example open while you enter your own figures: matching the shape of the substitution is the fastest way to spot a unit or convention mistake.
How far Supplier Lead Time can reasonably move
Read this table as the practical error bar on the headline figure. It answers the question people actually have after seeing a single number: how wrong could this be if the main input is off by ten or twenty percent?
| POs completed setting | Actual supplier lead time |
|---|---|
| 80 % of the example value | 7.3 days |
| 90 % of the example value | 6.5 days |
| example inputs | 5.9 days |
| 110 % of the example value | 5.3 days |
| 120 % of the example value | 4.9 days |
Across 5 settings of POs completed, the result spans 4.9 days to 7.3 days. A decision that only works at one row of this table is a decision waiting for an input to move. Reproduce it in the form above by editing POs completed alone; the substitution steps will follow your figures exactly.
The levers behind Supplier Lead Time, ranked by effect
Nobody should have to guess which input matters. The engine was re-run once per field below — ten percent up, ten percent down, everything else frozen — and the results ranked by how far they moved the actual supplier lead time. Read it as a map of where Supplier Lead Time is fragile — drawn for the example inputs, which is the map you want when deciding what to measure carefully.
- POs completed: ten percent up gives 5.3 days, ten percent down gives 6.5 days — ≈11.1 % of the actual supplier lead time either way
- Sum of their quoted-vs-actual days +10 % → Supplier Lead Time = 6.4 days · −10 % → 5.3 days (the actual supplier lead time shifts ≈10.0 %)
POs completed is the dominant lever here: ten percent either way moves the result by about 11.1 %, from 5.3 days to 6.5 days. Measure that input from a document rather than from memory, and treat Sum of their quoted-vs-actual days as the second priority (≈10.0 % per ten percent). The remaining fields can sit at safe defaults without materially changing the answer — knowing which is which is what separates a careful calculation from an anxious one.
Is your Supplier Lead Time good — reading the result bands
A number on its own is trivia; a number against a range is intelligence. The default case lands in the “Running 0.9 days over promise — plan on this, not the catalog number” band, and bands are deliberately wide because real situations overlap. How much of that band is luck? On POs completed alone ten percent either way covers 5.3 days to 6.5 days. The practical reading rules: read the band as a starting hypothesis, then test it: change the two dominant inputs by ten percent and see whether the verdict survives. Verdicts that survive stress are the ones worth acting on.
Set Supplier Lead Time beside its neighbours and it usually plays a specific role: this figure establishes the size of something, and the neighbouring tools establish whether that size is acceptable. Skipping the first step makes the second one arbitrary.
How people get Supplier Lead Time wrong
Receipt-quality rejections extend effective lead invisibly — measure time to usable stock, not time to the dock. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Using stale inputs. Supplier Lead Time is only as current as the numbers behind it — an estimate carried over from a previous season, rate table or report quietly biases every output. Re-measure the inputs first; that single habit fixes more bad Supplier Lead Time figures than any formula change.
This model has its own particular trap: POs completed carries ≈11.1 % of the response per ten percent of error, so effort spent elsewhere is largely decorative.
A final trap is presentation: reporting Supplier Lead Time to more decimal places than the inputs support. The tool prints what the arithmetic gives; you should quote only what your least precise field justifies.
Supplier Lead Time verification checklist
- Confirm the example values are plausible for your own situation before replacing them.
- Recompute once with the dominant input deliberately set low, and see whether the decision changes.
- Put POs completed under a magnifier; the sensitivity table above is the reason why.
- Verify each input against its original source document, not memory.
- Re-run the calculation with a ±10 % stress on the two most sensitive inputs.
- Confirm the answer against one independent method or published benchmark for Supplier Lead Time.
How to use the Supplier Lead Time tool properly
Using a calculator well sounds trivial, but the difference between a decision-grade figure and a throwaway one lives entirely in the routine. The routine for Supplier Lead Time takes a minute to learn and applies to every input above.
Step 1 — gather before you type. Supplier Lead Time depends on pos completed, sum of their quoted-vs-actual days, promised lead time (days). Collect them from a source document — a statement, a report, an invoice, a log — rather than from memory, because recalled inputs are the single largest cause of wrong results. Repeating a calculation with the same numbers proves only that the arithmetic is reliable — which is worth knowing.
Step 2 — start from the case you can defend. Enter pessimistic-but-honest figures first; the optimistic run is a ceiling, not a plan. A conclusion that holds on conservative inputs holds everywhere. Comparisons are cheap: run the identical calculation for the alternative and look at the gap.
Step 3 — isolate your variables. Change one field, observe, revert. The live sensitivity list does the ranking for the default inputs; verify it against your own, because dominance shifts when the starting point shifts. The input you reach for first is usually the one you measured longest ago.
Step 4 — run the scenario trio. Expected, pessimistic, optimistic. The gap between pessimistic and expected is the number to plan against; the optimistic result is useful only as a ceiling. The fastest sanity test is to guess the answer first and see how far the calculation disagrees.
Step 5 — schedule the next run. In Business & Entrepreneurship the inputs drift quietly. Put a reminder a quarter out, re-enter the same fields, and read the change rather than the level. A result worth acting on survives having its two shakiest inputs halved.
Who actually uses Supplier Lead Time — and when
Most Operations disagreements are arithmetic disagreements in disguise. When Actual supplier lead time of 5.9 days sits on the table with its working shown, the conversation stops being about who sounds more confident and starts being about which input is wrong. One decimal place more than your data supports is one decimal place of fiction.
Used properly this is a five-minute filter that saves weeks. Compute Supplier Lead Time, reject what fails, and only then bring in the expensive analysis for the survivors. A calculation you cannot explain to somebody else is a calculation you cannot defend.
There is a personal-administration use people overlook: periodic self-checking. Supplier Lead Time quietly drifts as life changes — rates move, bodies change, costs compound — and re-running it a few times a year catches drift while correction is still cheap. Note the assumption you are least sure about; that is where the real risk lives.
Supplier Lead Time — frequently asked questions
What affects Supplier Lead Time the most?
Measured on this engine, POs completed is the dominant lever: moving it ±10 % shifts the actual supplier lead time across 5.3 days to 6.5 days — about 11.1 % of the headline, with Sum of their quoted-vs-actual days next at ≈10.0 %. The ranked list in the sensitivity section is computed live, not asserted from a template.
Which matters more: sum of their quoted-vs-actual days or pos completed?
POs completed, by a factor of about 1.1. Concretely: ten percent on POs completed is worth ≈11.1 % of Supplier Lead Time, the same nudge on Sum of their quoted-vs-actual days only ≈10.0 %. That ranking is re-computed for each page from that page’s own defaults.
What is a typical Supplier Lead Time?
With the example inputs on this page the result is 5.9 days, labelled “Running 0.9 days over promise — plan on this, not the catalog number”. “Typical” varies with situation, which is why every result here ships with its verdict band and its sensitivity list: they turn one figure into a range you can locate yourself inside.
How do I calculate Supplier Lead Time by hand?
Actual lead = total days ÷ orders; reliability = deviation from promise is the entire method. Work the inputs in that order — Actual = 790 PO-days ÷ 135 = 5.9 days — and you will reach 5.9 days on the default figures, the same number this tool prints.
What happens to Supplier Lead Time if pos completed changes by 10 %?
Try it in the form above and the printed substitution will follow you; the pre-computed answer for the defaults is 5.3 days to 6.5 days across the ten-percent probe, i.e. ≈11.1 % sensitivity on the actual supplier lead time.
Is the Supplier Lead Time result of 5.9 days good or bad?
Good and bad are comparisons, so the honest test is three questions: where does your own Supplier Lead Time sit against the 5.9 days reference above, how far would a plausible input error move it (≈11.1 % per ten percent on POs completed), and what does the alternative option compute to?
How do I calculate Supplier Lead Time manually?
Write down the inputs, then follow the printed steps in order — Actual lead = total days ÷ orders; reliability = deviation from promise. A spreadsheet replicates it with two or three cells. The manual route is worth doing once to build intuition; after that the calculator saves time and eliminates transcription slips.
Should I use Supplier Lead Time before launching?
Yes — a Supplier Lead Time run on honest inputs before spending is the cheapest consulting an entrepreneur can buy. Re-run at every pricing change; the number moves more often than founders expect.
Quote to suppliers the promise or the actual?
Negotiate the promise to the actual you measure; chronic gap silently transfers buffer cost to you in safety stock.
Sample size matters?
Fifty-plus receipts before trusting the distribution tail — small samples understate p90 and the risk you are insuring against.
Is my data private on this page?
Yes — computation happens locally in your browser, with no account, no tracking of your inputs and nothing sent to a server. The printed formula is the whole story of what happens to your figures.
Key terms on this page
- Deviation vs promise
- 0.9 days for the Supplier Lead Time worked case; it sits next to the main result because it carries context the headline leaves out.
- Promise reliability ratio
- 0.85 on the example inputs — a companion figure printed beside the headline of Supplier Lead Time so that no result is read in isolation.
- Extra safety days at 95/70 reliability
- 1.4 for the Supplier Lead Time worked case; it sits next to the main result because it carries context the headline leaves out.
- Actual supplier lead time
- The primary output of this tool: 5.9 days for the default inputs, computed exactly from Actual lead = total days ÷ orders; reliability = deviation from promise.
- Worked example
- The step-by-step substitution printed above, so the arithmetic can be re-derived by hand or in a spreadsheet.
- Verdict band
- The interpretation attached to a result (“Running 0.9 days over promise — plan on this, not the catalog number” on these inputs), which turns a bare number into a position on a scale.
- Sensitivity (±10 %)
- How far the Supplier Lead Time moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Method, sources and what this tool cannot tell you
Everything above runs on one stated formula, applied without hidden coefficients: Actual lead = total days ÷ orders; reliability = deviation from promise. Source of record: Supplier performance measurement. Any other implementation of this model should return the same figure for the same inputs. If one does not, the difference is in its assumptions — which this page prints and that one probably does not.
Nothing here replaces a qualified professional, and nothing here is approximate either — the arithmetic is exact, and the honesty is in the inputs you supply. The sensitivity table above is part of that promise rather than a bonus: it lets you see how much of the result depends on how carefully you measured.
Next steps after the calculation
Mark the computed date or span in your calendar with its assumptions attached; plans drift when the inputs do.
The audience here is people planning around a point or span in time. Everything you need to defend the result — formula, substitution, sensitivity, source — is printed above, so the only remaining variable is the honesty of your inputs.