NDR Full Form: Non-Delivery Report, Explained
NDR stands for Non-Delivery Report. It is the courier telling you a delivery attempt failed and why. What you do in the next few hours decides whether that order gets saved or becomes an RTO.
- NDR means Non-Delivery Report: a per attempt failure record with a reason code, raised while the parcel is still in the buyer's city and still saveable.
- The gap between the first NDR and the RTO mark is your only intervention window. Contact the buyer within hours, not days.
- Do not trust reason codes blindly. Fake attempts exist. Verify with the buyer before accepting what the courier logged.
NDR full form: Non-Delivery Report, the record a courier raises when a delivery attempt fails, along with a reason code for the failure. It is the earliest signal that an order is drifting toward an RTO.
What NDR actually means
Every parcel that goes out for delivery either gets delivered or generates an NDR. The report carries a reason code: address incomplete, customer not available, customer refused, payment not ready on a cash on delivery order, out of delivery area, and a few variants per courier.
An NDR is not a verdict. It is a checkpoint. Couriers typically make a fixed number of attempts before marking the shipment RTO. The gap between the first NDR and that final mark is the only window in which the order can still be saved, and it is measured in hours and days, not weeks.
Where you meet it
- Courier panels. Every courier and aggregator dashboard has an NDR queue with the attempt history, the reason code, and an action button to request reattempt, update the address, or confirm the order.
- Marketplace dashboards. On Amazon and Flipkart the marketplace handles NDR resolution for orders they fulfil. For self ship orders it stays your job, and unresolved failures still land on your metrics.
- Seller agreements. Contracts define how many attempts you get, how long the parcel waits at the local hub, and what a reattempt costs. Three attempts is common. Some aggregators allow more if you respond fast.
- India context. NDR volume in India is inflated by two local realities: a heavy cash on delivery mix, where buyers dodge deliveries they no longer want, and fake attempts, where an agent marks a failure without visiting because the route is overloaded.
The cost or mechanics
An NDR itself costs little. Ignoring it is what costs. Every unresolved NDR converts to an RTO, and the RTO carries forward shipping, reverse shipping, blocked inventory and repackaging on a sale that produced no revenue. The math of follow up is lopsided in your favour: a WhatsApp message or a thirty second call against two legs of shipping and a locked SKU. Saved deliveries also protect the metrics marketplaces grade you on. Repeated delivery failures degrade account health, and a rising undelivered share drags your effective return rate and your unit economics with it.
How operators mishandle it
The first failure is speed. Teams review the NDR queue once a day or once every few days, and by then the courier has burned the remaining attempts. The second is trusting reason codes. Customer not available often means the agent never went. Confirm with the buyer before accepting the code, and dispute fake attempts with proof. The third is resolving inside the courier panel only. Clicking reattempt without contacting the buyer just schedules the same failure again. The fourth is not looking at NDR patterns. If one pincode, one courier or one SKU generates a disproportionate share of failures, that is routing data, not noise.
Work the window
Treat the NDR queue like an inbox with an SLA of hours. Auto message the buyer on the first failed attempt, verify the reason, fix the address or confirm intent, then push the reattempt. Escalate fake attempts with the courier every single time. NDR handled fast is the cheapest RTO reduction program you will ever run.