toolbox
Home / Shipping & Supply Chain / Delivery Window Service Level Estimator

Delivery Window Service Level Estimator

The Delivery Window Service Level Estimator calculates the percentage of deliveries that met a defined delivery-window commitment. It is designed for a batch of completed orders or a reporting period where each delivery can be classified as on time, late, or otherwise outside the agreed window.

The result provides a simple service-level rate and the corresponding miss rate. Operations teams can use it to compare routes, carriers, depots, or time periods as long as the same definition of an in-window delivery is applied consistently. Because the metric depends on how exceptions are classified, document your rule for cancellations, customer-caused delays, and rescheduled appointments before comparing results across teams.

Service-level counts

deliveries
deliveries
deliveries
Result
—
Delivery window service level
Measured deliveries—
Window misses—
Miss rate—

1. Enter total deliveries
Use the full count of deliveries considered for the reporting period.

2. Count in-window deliveries
Enter the deliveries that satisfied your documented delivery-window rule.

3. Add exclusions
Enter cancellations or other cases your policy removes from the performance denominator.

4. Check measured volume
The calculator subtracts exclusions from total deliveries before computing the service level.

5. Review service and miss rates
Use both percentages when comparing lanes, carriers, or operating periods.

Measured deliveries = Total eligible deliveries − Excluded deliveries
Window misses = Measured deliveries − Deliveries within window
Service level (%) = Deliveries within window ÷ Measured deliveries × 100
Miss rate (%) = Window misses ÷ Measured deliveries × 100

Where:

  • Total eligible deliveries = all deliveries initially considered
  • Excluded deliveries = cases removed under the reporting policy
  • Deliveries within window = measured deliveries meeting the commitment
  • Measured deliveries = denominator after exclusions

Assumptions: Deliveries within the window cannot exceed the measured delivery count. Exclusion rules should remain consistent between periods.

What the result means

Use the primary result together with the supporting values to evaluate the specific supply-chain scenario represented by your inputs.

This calculator is a planning estimate. Operational definitions, data quality, and local business rules can change how the result should be applied.

Given:

  • Total eligible deliveries = 420
  • Deliveries within window = 391
  • Excluded deliveries = 8

Calculation:
Measured deliveries = 420 − 8 = 412
Window misses = 412 − 391 = 21
Service level = 391 ÷ 412 × 100 = 94.90%
Miss rate = 21 ÷ 412 × 100 = 5.10%

Result: 94.9% delivery-window service level.

Interpretation: About 95 of every 100 measured deliveries met the defined window in this sample; 21 measured deliveries missed it.

What counts as a delivery within the window?

Use the commitment your operation actually reports, such as arrival between a scheduled start and end time. Apply the same timestamp and exception rules to every delivery in the comparison.

Should customer-requested reschedules be excluded?

They can be if your reporting policy treats them as non-carrier exceptions. Record that policy explicitly so the service level is not improved simply by changing exclusions.

Why can the calculator reject my in-window count?

The in-window count must be no greater than total deliveries after exclusions. Otherwise the numerator is larger than the valid denominator.

Can I compare this percentage between carriers?

Yes, provided the carriers are evaluated using the same window definition, exclusions, and delivery population. Differences in route difficulty or customer mix may still affect interpretation.

How is this different from average lateness?

Service level is a pass/fail rate against a window. Average lateness measures the magnitude of delay and can distinguish a few minutes late from several hours late.