What Is NDR? Managing Failed COD Deliveries
An RTO order didn't start as an RTO. It started as an NDR, a single failed delivery attempt that still had a real chance of becoming a completed sale. What happens in the hours right after that failed attempt decides which one it turns into.
In this guide
- What Is an NDR, and How Is It Different From RTO?
- The Clock That Starts the Moment Delivery Fails
- The Most Common NDR Reasons
- Manual vs. Automated NDR Resolution
- The Right Channel, in the Right Order
- What This Looks Like for a Shopify Store
- Prevention vs. Recovery: Where CODFlip Fits
- Where to Learn More
- Frequently Asked Questions
- Sources
TL;DR
An NDR (Non-Delivery Report) is the courier's formal record of a single failed delivery attempt, distinct from an RTO, which is the shipment actually returning to the merchant. Most couriers allow 24 to 72 hours and up to three attempts before an unresolved NDR converts to RTO automatically, and customer patience for a fix drops sharply after roughly 36 hours. Automated NDR resolution workflows report 40 to 60% success turning a failed attempt into a delivery, against just 10 to 20% for manual follow-up, a gap driven mainly by speed: reaching the customer within hours over WhatsApp, rather than whenever staff bandwidth allows a callback.
What Is an NDR, and How Is It Different From RTO?
A Non-Delivery Report is the formal record a courier partner raises the moment a delivery attempt fails, tagged with a reason code: customer unreachable, incorrect address, refused delivery, premises closed, or an external factor like weather or a vehicle issue1. It is industry-standard terminology used across every major Indian courier, Delhivery, Ekart, Bluedart, XpressBees, and DTDC among them2.
The distinction from RTO matters because it is the difference between a problem that is still fixable and one that is not. An NDR is a single failed attempt, still recoverable into a completed delivery. RTO (Return to Origin) is what happens once that failure goes unresolved long enough that the courier gives up and ships the order back2, at full logistics cost and zero revenue, the outcome we covered in detail in COD RTO Rate in India: Cost, Causes & Data (2026). Every RTO passed through an NDR stage first. That stage is the actual point of intervention.
The Clock That Starts the Moment Delivery Fails
Most Indian couriers allow three delivery attempts before automatically flagging a shipment for return2, with 24 to 48 hours typically between attempts, and unresolved NDRs converting to RTO within a 24 to 72 hour window overall depending on the courier3. Customer patience runs out faster than that window suggests: research indicates customers are willing to wait roughly 36 hours after an NDR notification for the issue to actually get fixed4, after which willingness to cooperate on a reattempt drops off.
| Stage | Typical Timing |
|---|---|
| First attempt fails, NDR raised | Day 0 |
| Seller must contact customer, verify the issue | Within 24 to 48 hours |
| Second attempt | Day 1 to 2 |
| Third and final attempt | Day 2 to 3 |
| Unresolved after third attempt | RTO triggered |
Why speed matters more than any single tactic: The single biggest lever in NDR resolution isn't which script or channel you use, it's how many of the 24 to 72 hours you actually have left when you first reach the customer. A follow-up sent within an hour of the failed attempt has a meaningfully different chance of success than the same message sent on day two.
The Most Common NDR Reasons
- Customer not available at the delivery window, consistently cited as the single most common trigger across courier networks.
- Incorrect or incomplete address, especially common given informal addressing conventions in Tier 2 and 3 cities.
- Invalid or unreachable phone number, which prevents the courier from coordinating a reattempt at all.
- Customer refusal or change of mind, common specifically on COD orders where nothing was paid upfront to hold the customer to the purchase.
Two of these four (unreachable numbers and change-of-mind refusals) are exactly what OTP verification and Partial COD are built to reduce before the order ever ships, which is the distinction covered further down.
Manual vs. Automated NDR Resolution
This is the gap that actually matters. Operations running automated NDR resolution workflows report success rates of 40 to 60% turning a failed attempt into a completed delivery, against 10 to 20% for manual, reactive follow-up3. Best-in-class Indian D2C brands land in the 35 to 45% range4, consistent with the automated end of that spread.
Acting on an NDR within 24 hours specifically is estimated to reduce avoidable RTO by 8 to 15% within the first month of implementing a faster response process5, a smaller but directionally consistent figure that reinforces the same point: speed of response, not the sophistication of the message itself, is what separates a recovered delivery from an RTO.
The Right Channel, in the Right Order
Industry guidance for Indian consumers converges on the same sequence: WhatsApp first, since it consistently sees the highest open rates, SMS as a fallback, and a live call reserved for high-value orders where a written message alone may not be enough4. This mirrors exactly what we found on WhatsApp's reach for COD conversion generally in our earlier RTO data breakdown: it is the channel Indian shoppers actually check, not just the cheapest one to send on.
What This Looks Like for a Shopify Store
For a Shopify D2C brand, practical NDR management comes down to a few concrete pieces working together:
- A courier or OMS integration that surfaces an NDR the moment it's raised, not once a day in a batch report.
- An automated WhatsApp message sent within the first few hours, giving the customer a simple way to confirm they're available, or to correct an address, without needing a phone call.
- A clear escalation path (SMS, then a call) for orders that don't respond to the first message, reserved for high-value orders where the extra effort is worth it.
- Tracking NDR-to-delivery conversion as its own metric, separate from overall RTO rate, since it's the number that tells you whether your recovery process is actually working.
For example. A store processing 100 NDRs a month at a 15% manual resolution rate recovers 15 orders. Moving to a 45% automated resolution rate, consistent with published benchmarks, recovers 45, a difference of 30 orders a month that would otherwise have gone to RTO at full logistics cost.
Prevention vs. Recovery: Where CODFlip Fits
NDR management is a recovery layer: it acts after a delivery attempt has already failed. CODFlip works one stage earlier, before the order ever ships, by scoring each COD order's RTO risk and sending a WhatsApp nudge to convert it to prepaid up front, and by using OTP Verification and Partial COD to filter out exactly the unreachable-number and low-commitment orders that turn into NDRs in the first place.
The two are complementary, not competing: a strong prevention layer reduces how many NDRs you generate to begin with, while NDR management determines what happens to the ones that occur anyway. A store doing well on both sees a meaningfully lower RTO rate than one relying on either alone.
Where to Learn More
For the full breakdown of CODFlip's prevention-side features, see COD to Prepaid Shopify App: CODFlip Features (2026).
Frequently Asked Questions
What is an NDR in ecommerce?
A Non-Delivery Report (NDR) is a formal notification a courier raises when a delivery attempt fails, along with a reason code such as customer unavailable, incorrect address, or refused delivery. It is not the same as an RTO; an NDR is a failed attempt that can still be resolved into a successful delivery, while an RTO is the shipment actually returning to the merchant.
How long do I have to resolve an NDR before it becomes an RTO?
Most Indian couriers allow 24 to 72 hours and up to three delivery attempts before automatically converting an unresolved NDR to RTO. Industry research indicates NDRs not addressed within roughly 36 hours become increasingly unlikely to convert to a successful delivery.
What is the most common reason for an NDR?
Customer unavailability at the delivery window is consistently cited as the single most common trigger, followed by incorrect or incomplete addresses (especially common in Tier 2 and 3 cities) and unreachable or invalid contact numbers.
Does automating NDR follow-up actually help?
Industry data shows a significant gap: automated NDR resolution workflows report 40 to 60% success converting a failed attempt into a delivered order, against 10 to 20% for manual, reactive follow-up. The gap comes mainly from speed and consistency, reaching the customer within hours rather than whenever staff bandwidth allows.
Sources
- NDR definition and reason codes, Amazon Shipping India, “What Is NDR in Shipping & How to Manage It”
- NDR-to-RTO process and courier attempt standards, Shiprocket, “What is NDR (Non-Delivery Report) and RTO?”
- NDR resolution window and manual vs. automated conversion rates, ClickPost, “NDR and RTO in E-Commerce: The Complete Operations Guide”
- Channel sequencing and best-in-class resolution benchmarks, Eshopbox, “How to Reduce RTOs in Ecommerce with Smart NDR Management”
- NDR response-time impact on RTO, eShipz, “NDR Management Strategies to Cut RTOs”
See how CODFlip prevents RTO before it becomes an NDR
Read the full feature breakdown, or check out the product page for pricing and setup.