As Indian ecommerce expands into Tier 2 and Tier 3 cities, last-mile delivery has become more complex — and more consequential. A growing share of orders now faces failed delivery attempts, and each one generates a Non-Delivery Report (NDR). Left unaddressed within a narrow time window, that NDR becomes an RTO (Return to Origin): a shipment that returns to you at full logistics cost with zero revenue.
For small and medium businesses where margins are tight and every order counts, understanding what is NDR in shipping — and building a structured response to it — is one of the most direct levers for protecting profitability.
TL;DR — What Is NDR in Shipping?
A Non-Delivery Report (NDR) is a formal notification raised by a courier partner when a delivery attempt fails. It records the reason the shipment could not be handed to the recipient — such as the customer being unavailable, an incorrect address, or a refused delivery. The NDR is not a return. It is a warning. It gives the seller a fixed window — typically 24 to 48 hours — to resolve the issue before the courier exhausts its attempts and converts the shipment to an RTO (Return to Origin).
NDR meaning in ecommerce: An NDR is the early signal between a failed delivery attempt and a full return. It is the moment where a seller’s action determines whether an order gets delivered or becomes an avoidable cost.
In India, unresolved NDRs that escalate to RTOs cost brands ₹180–₹240 per order in combined forward shipping, reverse logistics and processing — with zero revenue generated. (Source: Pragma Analysis of 142 Indian D2C Brands, 2024)
What Triggers an NDR?
Not every failed delivery has the same cause — and the cause determines how fast you need to act and who you need to contact. Couriers attach a reason code to every NDR they raise. Here are the most common ones in the Indian ecommerce context:
NDR Reason Code |
What It Means |
Who Needs to Act |
Customer not available |
Recipient absent at time of delivery |
Seller — reschedule via courier |
Incorrect / incomplete address |
Address details insufficient to locate recipient |
Seller — confirm correct address with buyer |
Customer refused delivery |
Buyer declined to accept the order |
Seller — confirm order intent with buyer |
Phone unreachable |
Delivery agent unable to contact recipient |
Seller — verify and update contact number |
Premises closed |
Business or residence locked at time of attempt |
Seller — coordinate preferred delivery time |
Pin code unserviceable |
Address outside courier’s delivery zone |
Seller — arrange alternate delivery point |
Fake delivery attempt |
Agent marked attempt without visiting |
Seller — escalate to courier for accountability |
Understanding the reason code is the first step. It tells you whether this is a logistics coordination issue (customer unavailable, premises closed) or a data problem (wrong address, wrong phone number) — and that distinction changes how you respond.
How NDR Differs from RTO
These two terms are often used interchangeably. They are not the same thing.
An NDR is a status. An RTO is an outcome.
NDR |
RTO |
|
What it is |
Notification of a failed delivery attempt |
Shipment returned to origin warehouse |
When it occurs |
After each unsuccessful attempt |
After all attempts are exhausted or order is canceled |
Is it reversible? |
Yes — if actioned within the response window |
No — once RTO is triggered, the forward journey ends |
Cost to seller |
No additional cost yet |
₹180–₹240 in combined logistics spend, zero revenue |
Seller action required? |
Yes — urgently |
Too late for delivery recovery |
The NDR is the intervention point. Once a shipment moves to RTO, the cost is locked in. How to manage NDR in ecommerce is one of the most operationally important questions, a growing Indian SMB needs to answer.
The 36-Hour Rule: Your Action Window Before RTO
Speed is the single most important variable in NDR management. Research from ClickPost shows that nearly every failed delivery not resolved within 36 hours of the NDR being raised ends in cancelation and RTO. (Source: ClickPost NDR and RTO Guide)
Courier SLAs in India typically allow 24 to 48 hours between delivery attempts. That is your working window. If you do not update the courier with corrected information — or confirm buyer availability — the agent will attempt again without new instructions, fail again and move the shipment closer to RTO.
The NDR Escalation Timeline
Day 0 — First delivery attempt fails → NDR raised by courier
↓
Seller receives NDR notification (SMS / dashboard / API)
↓
Within 24–48 hrs — Seller must contact buyer, verify issue, update courier
↓
Day 1–2 — Second delivery attempt (with or without seller action)
↓
Day 2–3 — Third and final attempt (most couriers make 2–3 total)
↓
If unresolved → RTO triggered → Shipment returns to origin
The earlier you act after receiving the NDR, the higher your conversion rate on reattempts. Delayed action means the delivery agent arrives again with the same incomplete information and fails again.
NDR vs RTO in Ecommerce India: The Cost Comparison
Understanding NDR vs RTO in ecommerce India is fundamentally a cost conversation.
Scenario |
Seller Cost |
Revenue |
NDR resolved → successful delivery |
₹0 additional cost |
Full order value |
NDR unresolved → RTO triggered |
₹180–₹240 (forward + reverse + processing) |
₹0 |
NDR unresolved → COD RTO specifically |
₹180–₹240 + COD handling fee |
₹0 |
For sellers running on tight margins, a high NDR-to-RTO conversion rate can erode profitability on a significant share of orders. Industry data shows RTOs accounted for 25–30% of failed orders across mid-size Indian D2C brands in 2024. (Source: eShipz NDR Management Report, 2025)
If–Then Framework: Responding to NDRs by Reason
Not all NDRs need the same response. Use this framework to act fast and act right:
If the NDR reason is… |
Then your next action is… |
Target resolution time |
Customer not available |
Call / WhatsApp buyer to confirm availability window; update courier with preferred time slot |
Within 4 hours of NDR |
Incorrect / incomplete address |
Contact buyer immediately for full corrected address; update courier dashboard before next attempt |
Within 2 hours of NDR |
Customer refused delivery |
Call buyer to confirm order intent; check for COD hesitation; offer prepaid conversion if possible |
Within 4 hours of NDR |
Phone unreachable |
Attempt alternate contact (WhatsApp, email); update with any reachable number |
Within 6 hours of NDR |
Fake delivery attempt |
Escalate to courier grievance team with shipment ID; request fresh attempt with accountability |
Same day |
Premises closed |
Coordinate preferred delivery day or alternate pickup point with buyer |
Within 4 hours of NDR |
NDR Response Checklist for Indian SMBs
Use this checklist every time you receive an NDR notification:
- Read the reason code first. Do not treat all NDRs the same. Reason determines action.
- Contact the buyer within 2–4 hours. WhatsApp and phone calls outperform email for speed of response in Indian markets.
- Confirm or correct the delivery address. Even one missing line in an address causes repeat failures.
- Update the courier dashboard or API with new instructions before the next attempt window closes.
- Log the interaction. Keep a record of what was communicated and when — essential for courier escalations.
- Flag high-risk NDRs for priority follow-up. COD orders with “customer refused” codes need immediate attention; they are the most likely to escalate to RTO.
- Set a reminder if resolution takes more than 24 hours. Assume the courier will reattempt on schedule whether or not you have updated them.
How to Reduce NDR Rate India: Proactive Steps Before Dispatch
The most effective reduce NDR rate India strategy is not reactive — it starts before the shipment leaves your facility.
- Verify address and phone number at checkout. An incorrect address cannot be fixed after dispatch without cost and delay. Address verification at checkout catches errors before they become NDRs.
- Send a pre-delivery notification. A WhatsApp or SMS message 24 hours before delivery — with the delivery date and a contact option — increases first-attempt success rates. Customers who know a delivery is coming are more likely to be available or to flag issues in advance.
- Reduce COD dependency where possible. COD orders carry RTO rates of 28–35% compared to 4–8% for prepaid orders. (Source: Pragma, 2024) Offering a small incentive to switch to prepaid at checkout lowers your NDR exposure without eliminating payment flexibility for customers who need it.
- Offer flexible delivery time slots. Customers offered evening delivery windows (6–9 PM) show 47–53% lower RTO rates compared to standard daytime delivery. The cost of enabling an evening slot — approximately ₹15–₹20 per order — is a fraction of the ₹180–₹240 cost of an RTO. (Source: Pragma, 2024)
- Choose a logistics partner with real-time NDR visibility. You cannot act on an NDR you have not received. Real-time NDR alerts — via SMS, dashboard or API — are a prerequisite for a fast response. Delayed notifications mean your 36-hour window is already partially gone before you begin.
Amazon Shipping India’s tracking infrastructure gives sellers real-time shipment status visibility across its 14,000+ pin code network, including delivery attempt updates — so sellers can act on NDRs before the reattempt window closes. Learn more at Amazon Shipping India.
Common Misconceptions About NDR Management
Misconception 1: “NDRs are the courier’s problem to fix.”
The courier raises the NDR — but it is the seller’s responsibility to resolve it. The courier has no information about why a customer refused or whether an address is wrong unless the seller provides it.
Misconception 2: “The courier will keep trying until it delivers.”
Most couriers in India make two to three attempts. After that, the shipment is marked for RTO. Waiting for more attempts without taking action is not a strategy.
Misconception 3: “NDRs only happen with low-quality couriers.”
NDRs occur with every logistics partner because delivery failures are partly driven by customer behavior and address quality — factors no courier controls entirely. What varies between partners is how quickly they notify sellers and how effectively they support reattempts.
Misconception 4: “A low order volume means NDRs are not a big concern.”
The absolute number of NDRs may be small at low volumes; the margin impact per unresolved NDR is not. Each RTO costs ₹180–₹240 with zero revenue — that is a fixed cost regardless of your scale.
When NDR advice does not apply:
If your courier marks a parcel as “delivered” and the customer reports non-receipt, that is a false delivery report — not an NDR. The escalation path for that is through the courier’s dispute mechanism.
An NDR is a notification generated by a courier partner after a failed delivery attempt on an ecommerce order. It records the reason the shipment could not be delivered — such as the customer being unavailable, an incorrect address or a refused parcel — and signals to the seller that intervention is required before the next delivery attempt. If not resolved, an NDR escalates to an RTO (Return to Origin).
In ecommerce, NDR meaning refers to the formal record of a failed last-mile delivery attempt, along with a reason code. It is the industry-standard term used by all major Indian couriers — including Amazon Shipping, Delhivery, Ekart, Bluedart, XpressBees and DTDC — to flag undelivered shipments. For sellers, an NDR is an action trigger: respond within 24–48 hours or risk a full return at your cost.
Most Indian couriers allow 24 to 48 hours between delivery attempts. Research from ClickPost indicates that NDRs not resolved within 36 hours are highly likely to convert to RTOs. Sellers should treat NDR notifications as urgent and aim to contact the buyer and update the courier within 2–4 hours of receiving the alert.
An NDR is a delivery attempt failure — a status update, not a final outcome. An RTO is the outcome when all delivery attempts have been exhausted or the order is canceled. NDRs are recoverable with fast action. RTOs are not. Each RTO costs ₹180–₹240 in combined logistics expenses with zero revenue. The NDR-to-RTO conversion rate is the key metric sellers should track and work to minimize.
To reduce NDR rate in India, focus on three areas: prevention (address verification at checkout, pre-delivery WhatsApp notifications), channel optimization (reduce COD dependency, offer evening delivery slots) and response speed (act on NDR alerts within 2–4 hours with buyer contact and courier updates). Sellers using automated NDR management workflows report over 80% reduction in out-of-delivery rates.
The most frequent NDR reasons are: customer not available at delivery time, incomplete or incorrect address, customer refused delivery (most common for COD orders) and phone number unreachable. Address errors and COD refusals together account for the majority of NDRs in Tier 2 and Tier 3 markets, where address standardization is lower and COD dependency is higher.
Not entirely — some failed delivery attempts are unavoidable. However, pre-delivery customer communication, accurate address capture at checkout and COD-to-prepaid conversion can significantly reduce NDR frequency. For the NDRs that do occur, a fast and structured response process is what separates sellers with low RTO rates from those absorbing significant losses.
Yes, in two ways. First, how quickly the courier notifies you after a failed attempt determines how much of your 36-hour response window remains. Partners with real-time NDR alerts give you the maximum time to act. Second, courier behavior during the delivery attempt — including whether the agent makes a genuine attempt and whether flexible rescheduling is supported — directly affects first-attempt success rates. Sellers should review NDR reason code data by courier partner regularly to identify patterns.
For sellers looking to apply these practices at scale, Amazon Shipping India provides real-time shipment tracking, delivery attempt updates and coverage across 14,000+ pin codes — giving SMBs the visibility they need to act on NDRs before the window closes. Get started at Amazon Shipping India.
Disclaimer:
The information provided on this blog is for general informational purposes only. While we strive to keep the information up-to-date and accurate, we make no representations or warranties of any kind, about the completeness, accuracy, suitability or availability of the information contained on this blog. All content on this blog is protected by copyright law. Unauthorized use of this material without express written permission is strictly prohibited.
