When carriers talk about failed delivery attempts, the number they usually cite is fuel cost. Driver went to the stop, nobody was there, driver came back, you burned a gallon of diesel. Call it $4 or $5. Not great, but not a crisis.
That framing is wrong by a factor of roughly ten.
A failed delivery attempt — a stop the driver arrives at where no proof of delivery can be obtained — carries a fully-loaded cost that most operations managers don't track because it spans four different cost buckets. When we sat down to build out the unit economics of failed stops, the number that emerged was consistently in the $35 to $65 range per event, depending on delivery type, customer tier, and what rescheduling looks like. That math changes how you think about route optimization investment.
Cost bucket one: driver time at the stop and return
The driver shows up, knocks, waits the required dwell period (typically 3-5 minutes per company policy), marks the stop as attempted, and moves on. That dwell time is dead — you've paid for it and received nothing. Then there's the travel time back into the sequence. On a spread-out suburban route in central Ohio, the next viable stop might be 10-18 minutes away. That transition time was already built into the route plan; the failed stop has now added a 3-5 minute standstill at zero productivity.
More importantly, the failed stop disrupts the time windows for subsequent stops on the manifest. If the driver had a customer window at 11–1 and they arrive at 1:15 because an earlier failed stop burned 25 extra minutes across stops 8 through 14, you've now turned one failed stop into a second one. The cascade effect is where failed delivery costs really compound.
Driver time loaded cost: $18–$28 per failed attempt (factoring hourly CDL driver wage, loaded labor overhead, and lost productive stop time).
Cost bucket two: dispatcher overhead to reschedule
Every failed delivery attempt generates a reschedule event. The customer calls in or the driver logs the no-contact. The dispatcher has to find the next available window, coordinate with the customer, update the dispatch queue, and figure out whether the re-delivery fits on tomorrow's route or requires a dedicated run. In a well-run operation, that takes 8-15 minutes of dispatcher time. In a chaotic one, it can run to 25 minutes with back-and-forth.
That's not dramatic per individual stop. But a 20-vehicle fleet running a 3% failed-stop rate on 400 daily deliveries is looking at 12 failed stops per day, which is 1.5 to 3 hours of dispatcher reschedule overhead. Every single day. That's a material fraction of your dispatcher's productive capacity being consumed by recovery work.
Dispatcher overhead loaded cost: $6–$12 per failed attempt.
Cost bucket three: re-delivery fuel, labor, and route disruption
This is where the fuel cost lives, but it's rarely just fuel. Re-delivery means a driver is visiting that stop a second time. If it's a next-day re-delivery that fits into an existing route, the marginal cost is maybe $8-$12 (fuel plus the disruption it causes to that route's optimization). If it requires a dedicated run or a significant detour, you're looking at $20-$35 for the re-delivery event itself.
Re-delivery cost range: $8–$35 depending on routing fit.
Cost bucket four: customer relationship cost
This is the hardest to quantify and the one carriers most consistently skip over. A failed delivery attempt is a service failure from the customer's perspective. They arranged to receive a delivery. It didn't arrive. For B2B accounts — a restaurant that needed produce by 10 AM, a contractor who needed materials on-site — a failed attempt isn't an inconvenience, it's an operational disruption on their end.
The cost shows up three ways: customer service calls that take your team's time, formal service credits or penalties for accounts with SLA language in their contracts, and longer-term churn risk for customers who experienced repeated misses. A mid-size grocery distributor we worked with calculated that customers who experienced two or more failed deliveries in a 60-day window had a materially higher churn rate than those with zero failures. That relationship cost, amortized across the failed delivery events that triggered it, adds $5-$15 per failed stop to the real fully-loaded figure.
We're not saying every failed delivery destroys a customer relationship — occasional failures happen and most customers understand that. We're saying the second and third failures on the same account are measurably expensive, and your route performance data should be surfacing accounts at risk before it becomes a retention problem.
What the number actually looks like
Add the four buckets: $18-28 driver time, $6-12 dispatcher overhead, $8-35 re-delivery, $5-15 customer relationship. You get a range of roughly $37 to $90 per failed delivery attempt, with the middle of that range sitting around $52-$58 for a typical regional B2B carrier.
At 3% failed-stop rate on 400 daily deliveries, that's 12 failed stops per day at $52 average. $624 per operating day. $156,000 per year on a 250-day operating calendar. For a carrier with 20 trucks and around $8-10M in annual revenue, that's a cost line that's roughly 1.5-2% of revenue disappearing into failed delivery recovery.
A 35-vehicle grocery distributor we onboarded in late 2024 was running at roughly 4.1% failed-stop rate before going live. That's not unusual for a carrier managing a high-window-density route structure where customer availability windows are tight and change frequently. Their fully-loaded failed-stop cost was tracking close to $2,400 per day. Getting that rate to 1.8% (which took about six weeks of the system learning their customer windows) moved $830 per day back into margin.
Where route optimization fits into this math
Most of the failed delivery attempts we see come from one of three causes: driver arrived outside the customer's window, customer's window changed and the driver wasn't notified, or the stop was simply sequenced at the wrong point in the day given actual traffic conditions. The third category is directly addressable through continuous re-sequencing. The first two require accurate time-window data flowing back into the route in real time.
That's the product decision Routely is built around. We didn't build a better morning planning tool. We built a system that updates the driver's manifest throughout the day as windows change and traffic changes — because that's where the failed-stop cost actually lives.
The carriers who see the fastest impact on failed-stop rates are almost always the ones who were previously managing exceptions purely through dispatcher phone calls. Not because their dispatchers were doing it wrong, but because phone-based exception management can't keep 15 drivers' sequences current in real time. Something always falls through the gaps.
Tracking this number in your own operation
If you want to calculate your own fully-loaded failed-stop cost, start with your POD scan data — every stop that shows a failed attempt or no-contact scan. Layer in your driver hourly rate loaded (wage plus benefits plus payroll taxes, typically 1.35-1.4x base wage). Add the time your dispatcher spent on reschedule calls last week and divide by the number of failure events. Add your average re-delivery cost from fuel and time logs. Add any SLA credit line items from customer invoicing.
Most carriers are surprised by the number. It's almost always higher than they expected because the dispatcher time bucket and the cascade disruption to other stops on the route were never tracked as failed-stop costs — they just showed up as general inefficiency.
