Measure supplier lead time from the event that planning can use

Supplier lead time can mean several different things. A buyer may measure purchase order release to dispatch, a transport team may measure collection to arrival, and a planner may need release to usable stock. Each interval can be valid for its own decision, but substituting one for another changes the replenishment assumption.

Define the question first. To assess a dispatch promise, compare the agreed dispatch commitment with dispatch evidence. To determine how long an order must protect customer demand, follow it through receiving and any required release. A supplier can dispatch on time while the depot still receives usable inventory later than planning assumed.

Put the endpoints on one timeline

Consider an illustrative purchase order for 100 units. All timestamps below use India Standard Time in October 2026. The system retains actual event time separately from the time someone entered the record.

Release to dispatch is three elapsed days. Transit from dispatch to arrival is one day. Release to arrival is therefore four days, or 96 hours.

The full order becomes usable seven days after release, or 168 hours. For the last 40 units, the interval from arrival to usable release adds three days, or 72 hours. A planning parameter based only on the arrival date would miss that final exposure.

If the supplier's agreed promise was dispatch on 4 October at 09:00, it met that promise in this example. The remaining delay belongs in the end-to-end replenishment record and in the relevant receiving or release investigation. It should not silently become a supplier dispatch failure.

Keep partial availability visible

The first 60 units become usable after five days and the last 40 after seven. A quantity-weighted average is:

(60 × 5 + 40 × 7) ÷ 100 = 5.8 days.

That number can summarize the order for a stated analytical purpose. It does not mean that 100 units were available at day 5.8. The actual availability curve steps from zero to 60 at day five, then to 100 at day seven.

A planner needing 80 units on day six faces a 20-unit gap even though the weighted average appears to fall before that date. Preserve quantities and release events at the receipt-line or lot level that the operation actually controls.

Choose the metric deliberately: time to first usable receipt, time to full usable quantity, or a quantity-weighted interval. Publish the label beside the value. A supplier sending a token early quantity should not appear to have completed the entire order.

Decide when the clock starts

Order creation is not necessarily order release. A draft purchase order waiting for internal approval may not yet be actionable by the supplier. If that internal delay matters to the business, measure it separately or define an additional request-to-usable interval.

Acknowledgement is also not automatically the correct start. Starting only when a supplier acknowledges can hide the time between sending the order and receiving acceptance. Preserve both events, including delivery failures or rejected orders.

For call-off arrangements, the operational trigger may be an authorised schedule release under an existing contract. For make-to-order supply, technical approval may be a prerequisite. The definition must match the actual transaction rather than reuse a field solely because it is populated.

Store the original agreed dates and subsequent revisions. Replacing the original promise with the latest reschedule makes a moving target look consistently on time. Report original-commitment performance and performance against accepted revisions as separate views.

Record evidence without confusing it with availability

An event needs an identifier, business object, quantity, location, time zone and provenance. It also needs enough context to distinguish a physical observation from a system update. A status entered the next morning should not automatically move the actual arrival into the next day.

GS1's EPCIS materials provide a standard framework for sharing visibility events. They are relevant to recording and exchanging event context; they do not decide which receipt or release event this business should use as its planning endpoint. GS1 — EPCIS and CBV artefacts

Similarly, Microsoft's safety-stock replenishment documentation explains planning behavior around coverage settings. It does not make a gate-arrival timestamp equivalent to usable supply. The organization must map its availability definition to the planning data it actually supplies. Microsoft Dynamics 365 — Safety stock fulfillment for items

When inspection is unnecessary for a particular item and receipt immediately makes it usable, those events may coincide. When goods require checks, documentation or putaway before they can satisfy the relevant demand, retain that interval. Avoid assuming one release process applies to every item.

Do not lose the orders that are still late

A report of completed receipts alone can improve while the oldest orders remain open. The slowest observations have not yet reached the endpoint, so treating the completed sample as the whole population can understate exposure.

Maintain two linked views. The completed view has measured durations and explicit exclusions. The open-order view has elapsed age, outstanding quantity, current promise and the reason completion remains uncertain. Do not assign today's date as a fictional receipt, and do not give an incomplete order a zero duration.

Use a defined order cohort and reporting cut-off when comparing suppliers. If supplier A's sample contains only small replenishments and B's contains custom production, their averages do not describe equivalent work. Segment material differences in item, route, order size and release process.

Show the distribution and sample size alongside the mean. Investigate a long tail before changing parameters: repeated transport delays, internal release queues and inaccurate event entry require different responses. A corrected timestamp should retain an audit trail so historical metrics can be reproduced.

Feed planning a defensible duration

The useful lead-time measure describes when a particular quantity can serve demand and explains the stages that consume that time. It should help purchasing challenge promises and help operations remove delays without assigning every interval to the same owner.

Next actions

1. Write the start event and usable-stock endpoint for one replenishment process, including time-zone and calendar rules.
2. Reconcile one order's dispatch, arrival and quantity-linked release events against original evidence.
3. Review completed durations together with the age and outstanding quantities of open orders.
4. Update planning assumptions only after separating recurring exposure from data errors and documenting the approved definition.