Key takeaways
- NDR (Non-Delivery Report) is a courier's record that a delivery attempt failed — and it is the single most recoverable point in the RTO journey.
- A failed first attempt is not a lost order; it becomes RTO only when nobody intervenes before the courier's reattempt window closes.
- A fast, automated NDR workflow — WhatsApp alert, address re-confirm, reschedule, then a call — can recover a large share of failed deliveries.
- Courier accountability matters: some undelivered attempts are fake, and you need proof (like a recorded confirmation) to challenge them.
- Brands that run a disciplined NDR process can cut RTO by up to 40%, because they win back orders that would otherwise silently bounce.
Ask most D2C founders where their RTO comes from and they will point at bad COD orders. But a huge slice of returns comes from a quieter failure: perfectly good orders that failed one delivery attempt and were never rescued. That failed attempt is recorded as an NDR — a Non-Delivery Report — and how you handle the next 24 to 48 hours decides whether the order gets delivered or returns to origin. Strong NDR management is arguably the highest-leverage, most overlooked lever in the entire RTO fight, and done well it can cut RTO by up to 40%. This guide breaks down what NDR is, why it spirals, and the exact workflow to recover it.
NDR management is the post-ship counterpart to the pre-ship checks in our guide to reducing COD RTO. Pre-ship checks stop bad orders from shipping; NDR management saves good orders that stumbled after shipping.
What is NDR?
A Non-Delivery Report is the status a courier logs when a shipment could not be delivered on an attempt. The courier assigns a reason code — customer not available, address incomplete or wrong, customer refused, phone unreachable, customer asked to reschedule, or cash not ready for COD. Each attempt that fails without resolution moves the parcel closer to RTO, because couriers make only a limited number of reattempts (often two or three) before automatically returning the package to the seller.
Why a failed first attempt spirals into RTO
The dangerous thing about NDR is the clock. Once an attempt fails, you typically have a narrow window — sometimes a single day — before the courier tries again or gives up. If nobody re-confirms the address or tells the customer the delivery is coming back, the second attempt often fails for the same reason as the first, and the third seals it as RTO. The order was never bad; the silence after the first failure is what killed it. This is why speed is the entire game in NDR: a same-day response can rescue an order that a next-week response cannot.
| Attempt | Typical outcome without intervention | Outcome with fast NDR action |
|---|---|---|
| 1st attempt fails | NDR logged, no action | Instant WhatsApp alert + address re-confirm |
| 2nd attempt | Fails for same reason | Rescheduled to a confirmed slot — delivered |
| 3rd attempt | Auto-marked RTO | Not needed — order already delivered |
The NDR resolution workflow
Recovering NDR at scale is impossible by hand — you cannot manually chase every failed shipment across couriers within a one-day window. It has to be an automated workflow triggered the instant a courier posts an NDR status. Here is the sequence that works.
Step 1 — Instant WhatsApp alert on failed delivery
The moment a shipment is marked undelivered, fire an automated WhatsApp message to the customer: Hi Rohit, our delivery partner tried to deliver your order today but could not reach you. Would you like us to try again tomorrow? with reschedule and confirm-address buttons. Reaching the customer within minutes — while they still remember missing the doorbell — is what makes the difference. WhatsApp works here where SMS and email fail because it is read and it is interactive.
Step 2 — Re-confirm and complete the address
The most common resolvable NDR reason is a wrong or incomplete address. Your flow should let the customer correct or complete their address right in the chat — add the missing landmark, fix the flat number, drop a location pin. A quick address-completeness fix at this stage turns an undeliverable parcel into a deliverable one before the reattempt.
Step 3 — Reschedule to a slot the customer confirms
Customer not available is only a problem if the next attempt lands at the same wrong time. Let the customer pick a day or time they will actually be home, and push that confirmed instruction back to the courier. A reattempt aimed at a confirmed slot succeeds far more often than a blind retry.
Step 4 — Escalate to a call
If the customer does not respond to the automated messages within a few hours, escalate to a voice call. A quick WhatsApp call to re-confirm the address and intent recovers the orders that text alone could not, and it works especially well for COD parcels where cash-not-ready was the real reason. Record the call so the confirmation is documented.
Automate your NDR recovery on WhatsApp
Kwikfy fires an instant WhatsApp flow on every failed delivery — re-confirm address, reschedule, and call — so good orders don't slip into RTO.
Start Free →Courier accountability and fake-undelivered detection
Not every NDR is the customer's fault. A known problem in Indian logistics is the fake undelivered attempt — a delivery agent marks a parcel as customer not available or customer refused without ever attempting delivery, often to hit route targets or avoid a difficult drop. If you take courier NDR reasons at face value, you will wrongly blame customers and lose recoverable orders.
Two habits protect you. First, cross-check the courier's story with the customer: if the courier logs customer refused but the customer tells you on WhatsApp that nobody came, that discrepancy is evidence. Second, keep records — a recorded confirmation call proving the customer wanted the order lets you challenge a fake-undelivered NDR with your courier and push for a genuine reattempt rather than an RTO. Over time, tracking fake-undelivered rates by courier and by pincode tells you which partners and lanes are silently inflating your RTO.
Signals that an NDR may be fake
Patterns worth flagging include a delivery marked failed within minutes of being marked out-for-delivery, a customer who confirms they were home and reachable, repeated refused statuses clustered on one delivery agent or route, and NDRs logged with no call attempt to the customer's phone. None of these is proof on its own, but clustered together they point at a courier problem, not a customer problem.
The metrics that matter
You cannot improve what you do not measure. Track NDR as its own funnel, separate from overall RTO, so you can see how much you are recovering:
- NDR rate — share of shipments that hit at least one failed attempt. Rising NDR is an early warning that RTO is about to climb.
- NDR resolution rate — share of NDR shipments you successfully deliver after intervention. This is the number your workflow directly moves.
- Time-to-first-response — how fast you reach the customer after an NDR is logged. The faster this is, the higher your resolution rate.
- Fake-undelivered rate by courier — helps you hold logistics partners accountable and choose better lanes.
- Reattempt success rate — how often a rescheduled, address-confirmed reattempt actually delivers.
Watch these together and the compounding effect is clear. If you can lift your NDR resolution rate and shrink your time-to-first-response, a large fraction of shipments that would have returned instead get delivered — which is how disciplined NDR management translates into an RTO reduction of up to 40%. The orders were always winnable; NDR management is simply the practice of not letting them slip away in silence.
Where Kwikfy fits
Kwikfy runs NDR automation as part of its WhatsApp suite: when a delivery fails, it triggers the alert-reschedule-reconfirm flow automatically, lets customers fix addresses in chat, escalates to a recorded WhatsApp call when needed, and keeps the whole thread against the order so your team has full context. Combined with pre-ship RTO scoring, it means you are defended at both ends — screening risky orders before they ship, and rescuing good orders that stumble after they ship.