The Real Cost of a Failed Last-Mile Delivery (And How to Reduce It)

Industry estimates put failed-delivery re-attempt cost between $8 and $17 per stop. But that number misses the cascade: overtime, customer complaints, and route displacement for tomorrow.

Delivery van parked at address with door closed indicating missed delivery stop

The $8–$17 per failed-delivery re-attempt figure gets cited often enough in last-mile logistics discussions that it's become accepted shorthand. It's a reasonable estimate for the direct cost of a second-attempt dispatch: driver time, fuel, vehicle depreciation, and the administrative overhead of rescheduling. Industry analysts at groups like CBRE Supply Chain Advisory and Transport Intelligence have cited figures in this band for suburban and mixed-density operations.

The problem with that number isn't that it's wrong. It's that it's incomplete. The real cost of a failed delivery doesn't live in the re-attempt line item. It lives in the three operational cascades that the failed stop triggers downstream.

Cascade One: The Overtime Problem

A failed delivery isn't an event that concludes cleanly at the moment the driver marks a stop as "attempted." When a stop fails — recipient not present, access code wrong, business closed, incorrect address — the driver has to record the attempt, complete proof-of-attempt documentation (required for EDI 214 carrier shipment status reporting to shipper systems), and make a disposition decision: leave a door tag, contact dispatch, or immediately re-attempt if within proximity.

That adds 4–8 minutes per failed stop in driver time. On a route with 4 failures in a day — not uncommon during peak periods or in high-residential-density zones — that's 16–32 minutes of added driver time. On routes already running close to HOS limits under 49 CFR 395, that time isn't free. It either forces the driver into electronic log device (ELD) compliance pressure, or it pushes 1–3 remaining stops past the window and creates additional failures on the same run. Failed stops propagate.

For carriers on fixed-cost driver contracts, overtime triggering above a threshold — typically 8 or 10 hours — runs $22–$35 per hour loaded. A single route that triggers an overtime hour because of failed-stop documentation time costs more in driver premium than the entire re-attempt cost estimate. Multiply that by a 20-route depot with a 4% failed-attempt rate and you're looking at $440–$700 in overtime premium per operating day.

Cascade Two: Tomorrow's Route Displacement

The failed stops from today don't disappear. They re-enter the planning cycle for tomorrow as priority re-attempts. In most regional carrier operations, re-attempts are treated as priority inserts — they need to be slotted into the following day's routes, typically in the same geographic zone as the original stop.

This creates a route displacement problem. Tomorrow's static route plan was optimized for tomorrow's confirmed stop list. When 12 re-attempt stops get inserted at planning time, the route planner has to accommodate them. If they're geographically concentrated (as they often are — certain building types and neighborhoods consistently generate higher failure rates), they can cluster in one zone and force a vehicle assignment change or route count increase.

At a 400-stop depot with a 4% daily failure rate, that's 16 re-attempts entering tomorrow's plan. Industry experience suggests that 60–70% of re-attempts succeed on second try, so roughly 5 of those 16 will fail again and cascade further. Each insertion round degrades tomorrow's route optimality by a small but real percentage — in our analysis of pilot deployment data, re-attempt insertion added 3–6% route miles to the affected zones compared to clean-plan days.

At $2.50–$3.50 per mile, 3–6% excess mileage on a 400-stop operation running 40 routes averaging 80 miles is $240–$672 in added fuel and vehicle cost per day. That's a structural drag that doesn't show up in the $8–$17 re-attempt line item — but it's there every day the failure rate isn't controlled.

Cascade Three: Client SLA Exposure and Contractual Risk

For carriers operating under EDI 204/990 load tender agreements with e-commerce clients or retail fulfillment accounts, failed deliveries aren't just operational — they're contractual. Most commercial last-mile contracts include OTD (on-time delivery) SLA thresholds, often stated as a percentage of stops successfully delivered on the committed date. Common thresholds in regional carrier contracts run 95–98% OTD; below that, penalty clauses or volume reallocation rights activate.

A depot running 400 stops per day with a 4% failure rate is delivering at 96% OTD on failed-stop days — which sits at the edge of a typical SLA threshold, and below it if even a portion of those failed stops were committed for same-day delivery. The SLA exposure isn't just financial; in competitive freight markets, clients with volume to allocate will shift load away from carriers whose OTD consistently sits at the boundary.

We're not saying every failed delivery directly triggers a penalty clause. Most clients understand that weather, access exceptions, and incorrect shipper addresses create unavoidable failures. What they track is whether the carrier's process minimizes controllable failures — the ones caused by sequence inefficiency, late route changes, or stop-time overruns. The carriers that win volume over time are the ones who can demonstrate that their failure rate is controlled, not just acknowledged.

Where the Failure Rate Is Actually Controllable

Not all failed deliveries are preventable. Address errors from the shipper, recipient not-at-home for a signature-required parcel, and business closures are partly outside carrier control. But a meaningful share of failed stops — industry practitioners estimate 20–35% of failures — trace back to controllable sequence and timing issues: a stop arriving at a business address outside business hours because the route sequence put it last; a residential stop attempted at 7:30 p.m. in a gated community that closes at 7 p.m.; a cluster of apartment complex stops arriving after the leasing office closes.

Time-window-aware sequencing catches these. A VRPTW solver that knows the delivery time constraints for each stop type — business vs. residential, signature required vs. not, access-code locations — will sequence stops to maximize the probability of first-attempt success. A sequence that drops a time-sensitive commercial stop in a good window and clusters gated-access stops in the 2–5 p.m. window recovers 15–25% of the controllable failure rate in pilot deployments observed by our customers.

The compounding effect matters. Recovering 25% of a 4% failure rate brings the failure rate to 3%. At a 400-stop depot, that's 4 fewer failed stops per day. At $8–$17 direct re-attempt cost plus cascade effects, that's $32–$68 in direct savings plus the overtime drag, mileage premium, and SLA cushion restored. Annualized, the numbers justify route re-optimization investment without needing to stretch the math.

The Post-Cutoff Piece

Pre-dispatch VRPTW planning captures most of the controllable failure rate reduction during the planning cycle. The remaining piece is what happens when the route plan changes after cutoff — when address corrections arrive at T-minus-10-minutes and the sequence needs to update to keep time windows intact.

A manually re-sequenced post-cutoff route doesn't carry the time-window intelligence of the original plan. A dispatcher inserting a corrected address by visual judgment on a map typically optimizes for geographic proximity, not delivery window fit. That produces routes that look geographically reasonable but have a higher failure-risk profile for time-sensitive stops.

The carrier operations page covers how Parcelarc addresses both the pre-dispatch VRPTW optimization and the post-cutoff re-sequencing problem in a single constraint-aware pipeline. The re-optimization engine detail explains how live constraint ingestion keeps time-window awareness intact through the post-cutoff update.