By
·
14 minute read
Every failed delivery costs you £14.20 in direct fees. But that's not the real number. The real number is £14.20 plus four to five hours of support investigation, plus the 70 % probability that the customer who experienced it will never order from you again. At 300 failed deliveries per month — a completely average figure for a business shipping 2,000 orders — you're looking at over £31,000 monthly in combined direct costs and lost lifetime value. And almost all of it is preventable with a single well-timed SMS.
This guide breaks down exactly what failed deliveries cost, why most businesses are dramatically underestimating that number, and how a properly configured multi-channel notification system turns shipping communications from an operational overhead into your highest-ROI customer retention tool.
.svg)
🗝 Key Takeaways
- Each failed delivery costs £14.20 in direct fees — plus 4 to 5 hours of support time. For a 2,000-order merchant at 15 % failure rate, that's £4,260/month in redelivery fees alone before support costs are counted.
- 36 % of failed deliveries happen because customers simply weren't home. They didn't know the package was arriving. One well-timed out-for-delivery SMS or WhatsApp message eliminates this category almost entirely.
- A single out-for-delivery notification reduces failures by 35 %. For a mid-size merchant, that's £12,000+ per year in avoided redelivery costs — before accounting for support savings and retention impact.
- 70 % of customers won't reorder after a failed delivery. Shipping notifications aren't operational; they're loyalty insurance. The cost of not sending them isn't zero — it's the lifetime value of every customer who had a bad experience.
- Delivery confirmation emails sent within one hour of delivery convert to reviews at 40 to 45 %. Sent three days later, the same request converts at 5 to 10 %. The timing of your post-delivery notification is a direct revenue lever.
The Hidden £31,000 Problem Nobody Is Measuring
The standard P&L view of failed deliveries shows only the direct redelivery fee. It misses the cascade of costs that flows from a single unresolved delivery failure — and it completely omits the lifetime value dimension that makes the real number so much larger.
Here is what actually happens when a customer's delivery fails and your notification system doesn't intercept it in time. The customer buys a £75 item. The package is assigned to a carrier. The customer never receives an out-for-delivery notification. The delivery attempt happens at 2 PM while they're at work. The carrier leaves a card. The customer receives a confusing failure notice with carrier-specific instructions they don't understand. What the customer thinks: "Where's my package? Something went wrong. This company didn't keep me informed." What they don't think: "I should have been home."
The immediate cascade: they email your support team (four to five minutes of agent time). A redelivery is scheduled (£14.20 in carrier fees). Their trust erodes. Even when the redelivery succeeds, the perception is damaged. Four months later, the same customer sees your email promoting a new product. They don't convert. The mental note they filed under your brand name reads: "I had delivery problems with them." Lost lifetime value: £150 to £300 depending on your average customer LTV.
Now scale this to monthly volume. 2,000 orders at 15 % failure rate equals 300 failed deliveries. 70 % of affected customers unlikely to reorder equals 210 customers lost. 210 customers multiplied by £150 average LTV equals £31,500 per month in future revenue at risk — every single month, silently, without appearing as a single line on any report.
Each failed delivery doesn't just cost £14.20 in redelivery fees. It also generates four to five hours of support work: fielding the WISMO ticket, investigating with the carrier, scheduling redelivery, and managing follow-up communication. At £20/hour fully loaded, that's £80 to £100 in support cost per failed delivery — on top of the redelivery fee. For 300 failed deliveries per month, that's £24,000 to £30,000 in support costs that never show up in the carrier invoice but are very real in your operations budget. The total cost per failed delivery is not £14.20. It's closer to £95.
Why Deliveries Fail: The Preventable Majority
Understanding why deliveries fail is important because the solution depends entirely on the cause. Industry data consistently shows the same breakdown: 36 % of first-attempt failures happen because the recipient simply wasn't home. Not because of an address error. Not because of a carrier problem. Because nobody told them the package was coming today.
This is the category that a single well-timed notification eliminates. A customer who receives an out-for-delivery message at 7:30 AM on delivery day has the information they need to be home, ask a neighbour to receive it, redirect to a pickup point, or leave delivery instructions. Without that message, they have no information — and 36 % of them aren't there when the carrier arrives.
The remaining failure categories — wrong address, access issues, carrier errors, customs holds — are harder to prevent at the notification layer. But even there, proactive exception notifications significantly reduce the support burden by communicating what happened and what the customer needs to do before they have to contact your team to ask.
Customer buys. Generic tracking email sent at some point. Customer has no idea when delivery is happening. Carrier arrives at 2 PM. Customer is at work. Failed attempt. Confusing carrier card left. Customer contacts support. Redelivery scheduled. £95 in combined fees and support cost. Customer's trust damaged. 70 % probability they don't reorder. Lost lifetime value: £150 to £300.
Customer buys. Shipment confirmation with tracking link and delivery date sent within 30 minutes. Morning of delivery: WhatsApp or SMS — "Your order arrives today between 2 and 6 PM." Customer arranges to be home. First-attempt success. Delivery confirmation email within one hour. Review request at peak satisfaction moment. 40 to 45 % review conversion. Customer orders again three months later.
What Changed in 2026: Why This Is More Urgent Than Ever
Several developments in 2026 have raised both the opportunity and the stakes around notification strategy — making the gap between optimised and unoptimised notification systems larger than at any previous point.
DHL Express, Royal Mail, Evri, and DPD all updated their real-time tracking data availability this year. Where previously there was a two to four hour delay in status updates, real-time data is now available within 30 minutes across all major carriers. This means out-for-delivery notifications can now be sent with over 95 % accuracy on the day of delivery — significantly narrowing the window between when the carrier updates the status and when the customer needs to act on that information.
Customer expectations have moved sharply. 67 % of UK customers now expect SMS or WhatsApp alerts for delivery — up from 42 % in 2024. Merchants who send SMS and WhatsApp notifications see 40 % higher satisfaction scores than email-only competitors on the same delivery. The channel gap has become a satisfaction gap.
First-attempt delivery success rates have become a visible competitive metric. Major retailers now report these numbers publicly and customers have internalised 95 %+ success as a baseline expectation. When your delivery fails a first attempt, customers don't think "bad luck" — they think "this company isn't as organised as Amazon." The reputational cost of a failed delivery has increased even as the technical cost has remained constant.
EU regulations effective January 2026 have also tightened proof-of-delivery requirements for high-value items. SMS notification confirming delivery now serves as legal protection and customer acknowledgement — making proper delivery confirmation notifications a compliance matter as well as a customer experience one.
The Real Numbers: Full Cost Breakdown for a 2,000-Order Merchant
| Cost Category | Without Optimised Notifications | With Optimised Notifications | Monthly Saving |
|---|---|---|---|
| Failed deliveries/month | 300 (15 % rate) | 195 (10 % rate) | 105 fewer failures |
| Redelivery fees | £4,260/month | £2,769/month | £1,491 |
| Support hours (4.5 hrs each) | 1,350 hrs/month | 877.5 hrs/month | 472.5 hours |
| Support cost (£20/hr) | £27,000/month | £17,550/month | £9,450 |
| Customers lost to churn | 210/month | 137/month | 73 customers retained |
| Lost LTV (£150 each) | £31,500/month | £20,550/month | £10,950 |
| Additional repeat revenue | Baseline | +£15,000/month | £15,000 |
| Total monthly benefit | — | — | £36,891/month |
| Total annual benefit | — | — | £442,692/year |
The setup investment for all of this: four to six hours of configuration in ShippyPro Track & Trace. Payback period: one to two weeks.
Take your monthly order volume. Multiply by 0.15 (industry average failure rate). That's your estimated monthly failed deliveries. Multiply that number by £95 (combined redelivery fee plus support cost). That's your monthly cost of the status quo. If you're at 2,000 orders per month, that number is approximately £28,500 per month. The question is not whether optimised notifications are worth setting up. The question is how much longer you want to operate without them.
The Four Pillars of Revenue-Protecting Notifications
Optimised shipping notifications aren't just about sending more messages. They're about sending the right message, on the right channel, at the right moment — with content specific enough to drive action rather than just inform.
Pillar 1: Shipment Confirmation (The Expectation Setter)
Sent within 30 minutes of label creation. Channel: email. This notification establishes the delivery promise and gives the customer the tracking link before they think to look for it. The content that matters: clear statement the order is on its way, tracking number linked to your branded tracking page, estimated delivery date in plain language, and a single line explaining what to do if something seems wrong. The metric to track: reduction in "did it ship?" support tickets within 48 hours of launch.
Pillar 2: Out-for-Delivery Alert (The Revenue Protector)
Sent on delivery day when the carrier updates the status. Channel: SMS or WhatsApp — not email. This is the single highest-ROI notification in your entire stack. Research shows SMS and WhatsApp alerts reduce first-attempt failure rates by 35 % by keeping customers available to receive their package. For Royal Mail, Evri, DPD, and other UK carriers that make one or two attempts before leaving a card, this notification is the difference between a resolved delivery and a multi-day support chain.
The content must be specific: "Your [Product] arrives today between 2 and 6 PM" outperforms "Your package is out for delivery" because it answers the customer's implicit question — when exactly should I be home? The more specific your time window, the more likely the customer acts on the information.
Pillar 3: Delivery Confirmation (The Loyalty Capture)
Sent within one hour of the carrier confirming delivery. Channel: email. This notification closes the loop and captures satisfaction at its highest point — the moment the package is in the customer's hands. The content that unlocks the review conversion rate: "Your [Product] just arrived. Before you open it — let us know if everything looks perfect. Takes 30 seconds." The framing matters enormously. You're not asking the customer to do you a favour; you're giving them a moment to validate that the thing they were excited about has arrived in perfect condition.
Sent within one hour of delivery, this request converts to reviews at 40 to 45 %. Sent three days later — the industry default — it converts at 5 to 10 %. The timing gap represents a fourfold difference in review generation with identical content. For a merchant shipping 2,000 orders per month, the difference is roughly 700 additional reviews per month. Each review is worth 10 to 15 incremental sales over its lifetime on your product pages.
Pillar 4: Exception Notifications (The Trust Preserver)
Sent whenever something goes wrong — delay, failed attempt, address issue, customs hold. Channel: WhatsApp or SMS immediately, then email with more detail. The principle is simple: a customer who hears about a delivery problem from you first is significantly less frustrated than one who discovers it by checking the carrier's tracking page two days after the fact. The same problem handled proactively generates a "thanks for letting me know" interaction. Handled reactively, it generates a negative review and a lost customer.
The content must explain what happened in plain language, what happens next, and what (if anything) the customer needs to do. "We tried to deliver today but nobody was home. Here's how to reschedule: [link]" is significantly better than "Delivery attempt notification" with a carrier reference number. ShippyPro Track & Trace triggers all four pillars automatically across 160+ carriers — no manual monitoring required.
.svg)
Channel Strategy: Why Email Alone Costs You Money
The channel you use for each notification type isn't a preference — it's a revenue decision. The data on this is unambiguous.
| Notification Type | Via Email | Via SMS / WhatsApp | Revenue Impact of Channel Choice |
|---|---|---|---|
| Out for delivery | Read in 2-4 hours — delivery window already closed | Read in 3 minutes — customer can still act | 35 % failure reduction (SMS) vs. 5-10 % (email) |
| Failed delivery | Read next day — customer already frustrated | Read immediately — customer takes action | 60 % faster redelivery resolution with SMS |
| Delivery exception | Discovered via tracking page — customer already anxious | Proactive — customer feels informed | 40 % reduction in escalated support tickets |
| Delivery confirmation | Within 1 hour: 40-45 % review rate | Backup — email preferred for this one | Review conversion drives 20-35 % higher page conversion |
The operational rule: email for milestones the customer needs to reference (shipment confirmation, delivery confirmation, returns). SMS and WhatsApp for time-sensitive actions where minutes matter (out for delivery, failed attempt, urgent exceptions). Operating email-only for time-sensitive notifications is structurally equivalent to sending the out-for-delivery message after the delivery window has already closed — which, based on average email open timing, is exactly what happens for a significant percentage of your customers.
Smart Conditional Logic: When One Size Doesn't Fit All
The final sophistication layer is conditional notifications — rules that adapt message content, channel, or timing based on specific order attributes. This is where notification systems move from informational to genuinely revenue-protective.
High-value orders above £200 should trigger a delivery confirmation requirement — requiring the customer to acknowledge receipt creates both a customer experience moment and legal protection against chargeback disputes. International orders need customs information added to the shipment confirmation — a customer who doesn't understand that their parcel might be held at customs generates unnecessary support tickets that conditional logic eliminates entirely. Express shipping orders should receive tighter delivery windows — "arriving between 10 AM and noon" rather than "arriving by end of day" for a customer who paid for express is both accurate and satisfying.
Repeat customers warrant personalised language — "Welcome back — your order is on the way" with their name creates a loyalty moment that generic notifications completely miss. The AI Shipping Automation rule builder configures all of these conditions with drag-and-drop if/then logic — no developer involvement required.
Implementation Workflow: Six Steps to Revenue-Protecting Notifications
Pull 100 recent orders. Count: how many received a shipment confirmation? How many received an out-for-delivery alert? How many failed first delivery attempt? How many generated support tickets? How many customers reordered? If your failed delivery count is above 10 out of 100, you're at or above the industry average of £14.20 per failure times 1,000 orders per month equals £14,200 per month in direct costs alone — before support time.
For each carrier in your mix — DHL Express, Royal Mail, Evri, DPD, UPS — identify which status code maps to "out for delivery." These are different for every carrier and sometimes ambiguous. ShippyPro normalises carrier status events across 160+ carriers automatically, so you configure the trigger once and it applies across your entire carrier mix without separate configuration per carrier.
The difference between a notification that reduces failures and one that doesn't is almost entirely in the copy. "Your package is out for delivery. Reference #12345. Track here." does not cause a customer to change their plans. "Your [Product] arrives today between 2 and 6 PM — make sure someone's home!" does. Write all four notification templates before touching any platform settings. Getting the content right first is faster than configuring generic copy and then revising it.
International orders: add customs information to shipment confirmation. High-value orders above £200: add delivery signature requirement. Express orders: tighten the delivery window language. Repeat customers: personalise the greeting. Each rule adds incremental revenue protection — and all are configurable without code in a drag-and-drop interface.
Place orders that cover your typical range: standard domestic, express, international, one high-value. Verify every notification fires at the right time on the right channel with the correct content. Check every notification on mobile first — the majority of customers read delivery notifications on their phones and formatting that looks fine on desktop frequently breaks on mobile screens.
Track four numbers weekly: failed delivery rate (target below 10 % within two weeks), WISMO support ticket volume (target 50 %+ reduction within 48 hours), delivery confirmation review conversion rate (target 35 %+), and repeat purchase rate of customers who previously experienced failed deliveries. The ROI calculation updates every week with real data. Most merchants see payback within the first month.
The Highest-ROI Notification You're Probably Not Sending
Separate from the failed delivery reduction story, there's a standalone revenue opportunity most merchants miss entirely: the delivery confirmation review request sent within one hour of delivery.
The data on review request timing is striking. Sent within one hour of confirmed delivery, review requests convert at 40 to 45 %. The customer is holding the product they were excited about. Satisfaction is at its peak. The ask is immediate and specific. Sent three days later — the industry standard for automated review campaigns — the same request converts at 5 to 10 %. The customer has moved on, the excitement has dissipated, and responding to the request requires effort they no longer feel motivated to make.
For a merchant shipping 2,000 orders per month, the timing difference represents approximately 700 additional reviews per month. Each review drives 10 to 15 incremental sales over its lifetime on your product pages through the conversion lift that social proof provides. The review timing optimisation alone — a single configuration change that takes minutes — generates tens of thousands of pounds in incremental annual revenue through improved product page conversion. The Track & Trace module triggers this automatically on confirmed delivery across all connected carriers.
The framing that converts is: "Your [Product Name] just arrived — before you open it, let us know if everything looks perfect. Takes 30 seconds: [Perfect condition] / [Has issues]." This works because it's sent at the moment of maximum satisfaction, it frames the response as helping you rather than doing a favour, and the two-option format reduces friction to near zero. Do not use: "We hope you're enjoying your purchase! Please leave us a review on Trustpilot." The ask is too generic and too detached from the delivery moment to generate meaningful conversion.
Track & Trace
Automated branded notifications via email, SMS, and WhatsApp — triggered by real-time carrier events across 160+ integrated carriers. Normalises carrier status codes automatically. Delivery confirmation and review request timing included.
Reduce failed deliveries →AI Shipping Automation
Visual rule builder for conditional notification logic — configure rules by order value, destination, carrier, shipping method, or customer type. Drag-and-drop interface. No code required. Runs automatically on every order.
Configure notification rules →Shipping Platform
Central dashboard connecting 160+ carriers and 80+ e-commerce platforms. Carrier selection, label generation, and notification automation from a single interface — no separate tools required.
Explore the platform →Easy Return
Branded self-service returns portal that completes the post-purchase experience loop — automatic return label generation, return tracking, and inventory update triggers. Reduces return coordination overhead while improving customer experience.
Automate returns →How to Eliminate WISMO Emails in 2026
The complete guide to automating 80 % of your support tickets — WISMO reduction pairs with failed delivery reduction as the two primary notification ROI drivers for e-commerce operations teams.
Read the guide →Resources & Guides
Practical guides for e-commerce operations teams on shipping automation, carrier management, post-purchase experience, peak season preparation, and notification strategy.
Browse resources →How much can I realistically save with optimised shipping notifications?
For a merchant shipping 2,000 orders per month at a 15 % failure rate, properly configured multi-channel notifications typically generate £36,000 to £44,000 per month in combined savings and revenue protection: £1,491 in avoided redelivery fees, £9,450 in support cost reduction, £10,950 in retained customer lifetime value, and £15,000 in additional repeat revenue from improved NPS. Payback period on the four to six hours of configuration time is typically one to two weeks. Your specific number depends on current failure rate and average customer LTV — the ROI calculator in this guide gives you your personalised figure.
How do I know if my current notifications are actually working?
Pull 100 recent orders and count how many failed first delivery attempt. If the number is 14 or above, you're at or above the industry average failure rate of 14 % and your current notifications are not preventing failures. The diagnostic question is simpler: are you sending an out-for-delivery SMS or WhatsApp message to the majority of your customers? If not, 36 % of your failures are preventable with a single configuration change.
Can I implement this without a third-party platform?
Technically yes — practically, no, for most merchants. Building it in-house requires developer time to integrate carrier APIs for each carrier in your mix, build message logic and conditional rules, handle SMS and WhatsApp infrastructure including compliance, and maintain all of this as carrier APIs update. ShippyPro handles the full stack in four to six hours of configuration with no engineering involvement. The build-vs-buy calculation typically shows four to eight weeks of developer time to replicate what configuration takes an afternoon.
Why does the out-for-delivery notification need to be SMS or WhatsApp rather than email?
Because of the timing gap. An out-for-delivery email sent at 8 AM is typically read at 10 to 11 AM if the customer is at work — by which time the delivery window may already be partially or fully elapsed. An SMS or WhatsApp message sent at the same time is read within three minutes. For a carrier making a delivery between 10 AM and 2 PM, the difference between a message read at 8:03 AM and 10:47 AM is the difference between the customer being home and the customer not being home. Email is the right channel for milestone notifications; SMS and WhatsApp are the right channels for time-sensitive ones.
What should I measure to know if my notification system is working?
Four metrics tell the complete story. First-attempt delivery success rate — target below 10 % failure rate within two weeks of launch. WISMO support ticket volume — should drop 50 %+ within 48 hours of activating proactive notifications. Delivery confirmation review conversion — target 35 %+ if sending within one hour of delivery. And repeat purchase rate of customers who previously experienced a failed delivery — this is the truest measure of whether your exception notifications are salvaging relationships that would otherwise be permanently lost.
The cost of not optimising notifications: £14.20 × your monthly failures.
Configure revenue-protecting notifications across DHL Express, Royal Mail, Evri, DPD, UPS and 160+ carriers in four to six hours. Free trial, no credit card required. Most merchants see payback within the first two weeks.
Start Free Trial →
As the Growth Manager at ShippyPro, I help online retailers transform their shipping operations from a bottleneck into a growth engine. My expertise lies in ecommerce logistics and automation, specifically helping brands save time and scale efficiently. I write about the tools, strategies, and technologies that are defining the future of fulfillment.