26% of COD shipments in India get returned to origin. In Pakistan and Egypt, that number climbs past 30%. Most COD merchants know these numbers. What they don't know is that proper NDR management — responding to failed delivery reports within hours, not days — can recover 99% of those lost orders. The playbook below turns failed COD deliveries into completed sales.
The difference between a 15% RTO rate and a 30% RTO rate usually isn't better fraud prevention or smarter OTP verification. It's what happens after the courier marks the delivery as failed. That moment — the Non-Delivery Report — is where most COD merchants lose orders they already paid to acquire, pack, and ship. And most of them don't even have a system for responding to it.
What Is an NDR in Ecommerce (And Why It's Different From an RTO)?
A Non-Delivery Report (NDR) is a status raised by a courier when a delivery attempt fails. It means the order is sitting in a courier warehouse, waiting for instructions — not returned yet. You typically get 24-48 hours to provide those instructions before the courier automatically initiates a return shipment.
That distinction matters. An RTO is final — the package is on its way back to you, and you're eating the forward and reverse shipping cost. An NDR is a window. The order is still alive. The customer may still want it. But the clock is ticking, and every hour you wait reduces your recovery rate.
Most COD merchants treat NDRs the same way they treat RTOs: as a cost of doing business. That's a mistake worth thousands of dollars per month.
The 5 NDR Reason Codes and What to Do About Each One
Couriers don't just mark a delivery as "failed." They attach a reason code. Each code requires a different response, and treating them all the same is why most recovery efforts underperform.
Customer not home. This is the #1 reason for failed COD deliveries — not fraud, not refusal. The customer wants the product. They just weren't there. Response: send an automated WhatsApp message within 30 minutes asking for a preferred rescheduled time. Include two or three specific time slots for the next day. Recovery rate: 85-90% when you respond within 4 hours. (Adding delivery time slot selection at checkout prevents many of these NDRs in the first place.)
Wrong address or incomplete address. The courier couldn't find the location. Response: send an SMS with a short link to a form where the customer can correct or complete their address. Include a Google Maps pin-drop option if your system supports it. Recovery rate: 70-80%.
Customer refused delivery. This one stings, but it's not always a lost cause. Sometimes the customer forgot they ordered, or the delivery took so long they bought elsewhere. Response: a WhatsApp message acknowledging the refusal and offering a 5-10% discount on the same order. Recovery rate: 25-35%. Lower than other codes, but still worth the automated message.
Customer unreachable (phone off or not answering). The courier tried calling and got nothing. Response: send both an SMS and a WhatsApp message. If no response within 6 hours, make one human phone call during business hours. Recovery rate: 50-60%.
Incorrect phone number. This usually signals a fake order, but not always — typos happen. Response: check if you have an email address on file. If yes, send a delivery confirmation email. If no secondary contact exists, flag for manual review and don't attempt redelivery without confirmation. Recovery rate: 15-20%. If you're seeing this code frequently, you likely have a fake order detection problem that needs a separate fix.
The 4-Hour Rule That Separates Good Recovery From Bad
Most guides say you have 24-48 hours to respond to an NDR. That's technically true — the courier won't ship it back for at least a day. But the actual recovery window is much shorter.
Data from logistics platforms like Shipway and Shipmozo shows that NDR responses sent within 4 hours have a 75-85% recovery rate. Responses sent between 4-12 hours drop to 50-60%. After 24 hours, you're below 30%.
Why? Because the customer's intent decays fast. The person who was excited about their order yesterday is already rethinking the purchase today. By tomorrow, they've moved on — or worse, ordered the same product from someone else.
This means your NDR response system can't be a person checking a spreadsheet every evening. It needs to be automated. The first touch — a WhatsApp or SMS message — should fire within minutes of the courier updating the delivery status, not hours.
Build Your Automated NDR Management Stack
You need three layers working together. None of them are expensive, but all of them need to be in place before your next batch of NDRs hits.
Layer 1: Real-time NDR alerts. Your courier or logistics aggregator — Shiprocket, iThink Logistics, Delhivery, or similar — should push NDR notifications via webhook or API. If your courier doesn't support webhooks, most logistics aggregators do. Set up a Zapier or Make.com workflow that triggers the moment an NDR status appears. Manual NDR management doesn't scale past 20 orders/day. If your courier has no automation support, switch to a logistics aggregator.
Layer 2: Automated first response. The webhook triggers a WhatsApp message (primary) and SMS (fallback) to the customer. Make the message specific to the NDR reason code — not a generic "your delivery failed" template. Use the WhatsApp Business API through providers like Wati, Interakt, or BusinessChat. Cost: $0.03-0.08 per message, depending on country and provider.
Layer 3: Human escalation for high-value orders. Set a threshold — say, orders above $30 or 2,000 INR. Any NDR on orders above this threshold gets routed to a human caller within 2 hours, in addition to the automated message. A 3-minute phone call on a $50 order that costs you $0.10 is the highest-ROI support interaction in your business.
Triage by Order Value (Don't Treat Every NDR the Same)
A $10 order and a $100 order shouldn't get the same recovery effort. The math doesn't support it.
For orders under your average order value, the automated stack handles everything. WhatsApp message, SMS fallback, one automated rescheduling attempt. If the customer doesn't respond within 24 hours, let the courier return it. The cost of a second human follow-up exceeds the margin on the order.
For orders above your AOV, add the human call. For orders above 3x your AOV, consider offering a discount to incentivize acceptance. A 10% discount on a $150 order costs you $15 — the reverse shipping alone costs $3-5, plus you've already spent $5-8 on forward shipping. The math is obvious.
Track recovery rates by order value tier. Most merchants find that their high-value orders have better recovery rates (the customer actually wants the product) while low-value orders have higher refusal rates (impulse buys with weak intent). Your automation should reflect this.
The Metrics That Tell You If Your NDR Recovery Is Healthy
You can't improve what you don't measure. Track these four numbers weekly:
- NDR rate — percentage of total shipments that generate an NDR. Healthy: under 15%. Concerning: 15-25%. Critical: above 25%.
- NDR response time — median time between NDR creation and first customer contact. Target: under 2 hours. Acceptable: under 4 hours. Failing: above 12 hours.
- NDR-to-delivery conversion rate — percentage of NDRs that ultimately result in successful delivery. Good: above 70%. Average: 50-70%. Poor: below 50%.
- NDR-to-RTO rate — percentage of NDRs that become full RTOs. This is the inverse of the above, but tracking it separately makes the cost visible. Every percentage point here has a direct dollar value you can calculate.
If your NDR-to-delivery conversion is below 50%, the problem is almost always response time. Fix that first. If response time is under 4 hours and conversion is still below 50%, the problem is message quality — your templates aren't giving customers a clear, easy path to reschedule.
The NDR Cost Calculator Most Merchants Have Never Done
Take your monthly NDR count. Multiply by your average forward shipping cost plus your average reverse shipping cost. That's your current monthly NDR cost.
If you're shipping 100 COD orders/day with a 20% NDR rate, that's 20 NDRs daily. At $3 forward + $3 reverse shipping, each unrecovered NDR costs you $6. With a 40% recovery rate (no system), you lose 12 orders/day x $6 = $72/day = $2,160/month in shipping alone — not counting the lost margin on those orders.
Improving recovery from 40% to 75% (achievable with the automated stack above) saves 7 orders/day x $6 = $42/day = $1,260/month. The entire automation stack costs under $100/month to run. That's a 12x return.
Start Here, Today
If you're doing nothing about NDRs right now, don't try to build the full stack in one day. Start with one thing: set up an automated WhatsApp message that fires when a delivery attempt fails. Use your courier's built-in notification system or a simple Zapier workflow. Make the message specific: include the order number, the product name, and two time slots for rescheduling.
That single automation will recover 30-40% of your current NDR losses. Once you see those numbers, you'll build the rest of the stack yourself — because the ROI is too obvious to ignore. And if you want to reduce NDRs before they happen, tools like EasySell let you add phone verification and address validation directly on the order form — catching bad data at checkout instead of at the customer's door.