NDR management: cut failed deliveries
Most RTOs aren't doomed from the start — they're failed deliveries that nobody rescued in time. The difference between a delivery and a return is usually what happens in the 24–48 hours after the first failed attempt. That window is NDR management.
What NDR means
NDR — Non-Delivery Report — is the status a courier raises when a delivery attempt fails: customer unavailable, address incorrect, customer refused, didn't answer, asked to reschedule. Each NDR is a fork: rescue it and it becomes a delivery; ignore it and it becomes an RTO.
Why deliveries fail in India
- Customer unreachable / unavailable at the attempt time — the biggest bucket.
- Address incomplete or wrong — missing landmark, wrong pin.
- Refused — especially COD impulse orders.
- Payment not ready for COD.
A step-by-step NDR workflow
- Capture the NDR instantly. Pull courier statuses in near-real-time, not once a day — every hour of delay shrinks the rescue window.
- Auto-contact the customer. WhatsApp/SMS/IVR within minutes: confirm address, get a preferred re-attempt slot, or collect a "yes I still want it".
- Feed the instruction back to the courier. A re-attempt with a confirmed slot and corrected address converts far better than a blind retry.
- Escalate by attempt. Different messaging on attempt 1 vs 2; switch channel if one isn't answered.
- Convert COD to prepaid on the rescue contact where it makes sense.
- Only then RTO. After 2–3 genuine, contacted attempts — not after one miss.
Automate it or lose it
Done by hand on spreadsheets, NDR management misses the window — there's simply not enough time to chase each one. The fix is automation: auto-detect NDRs, auto-trigger the right customer outreach, capture the response and re-push to the courier within SLA. Delv's orchestration layer runs NDR retry flows automatically, so failed attempts get rescued instead of quietly turning into returns.
● From Delv ExpressSee Delv's NDR retry automation →Frequently asked questions
What is the full form of NDR?
NDR stands for Non-Delivery Report — the status a courier raises when a delivery attempt fails (customer unavailable, wrong address, refused, reschedule requested). It's the moment to rescue a delivery before it becomes an RTO.
How many delivery attempts should I allow before RTO?
Aim for 2–3 genuine attempts on consecutive days with customer contact between them, rather than an instant RTO after one miss. Most failed first attempts can be converted with fast NDR outreach.
Can NDR management be automated?
Yes, and it should be — manual NDR handling misses the 24–48h rescue window. Automation auto-detects NDRs, triggers WhatsApp/SMS/IVR outreach, captures the customer's instruction and re-pushes to the courier within SLA.