Every failed delivery attempt in India generates an NDR — a Non-Delivery Report — with a reason code: customer not available, customer refused, address incomplete, phone unreachable, and so on. Couriers usually make two to three attempts before the shipment flips to RTO and heads back to you. The window between the first NDR and the final RTO is the single most valuable, and most neglected, opportunity in your fulfilment.
Why NDRs are worth obsessing over
An NDR is not yet a lost order. It is a paused one. If you reach the customer within the reattempt window with the right information, a large share of NDRs convert to delivered. Miss the window, and you pay for reverse freight plus a blocked SKU. The economics are lopsided in favour of acting fast.
The common NDR reason codes and what they really mean
- Customer not available — often just bad timing; a scheduled reattempt fixes it.
- Customer refused — for COD, this is frequently remorse or 'ordered by mistake'; a quick call can save it.
- Address incomplete / not found — needs a landmark or corrected address from the buyer, not another blind attempt.
- Phone unreachable — the courier could not confirm; you may have a better number on file.
- Out of delivery area — a genuine serviceability limit that a reattempt will not solve.
The mistake most sellers make is treating all reason codes the same and simply clicking 'reattempt'. A blind reattempt on an incomplete address just burns another attempt and pushes the order closer to RTO.
Building an NDR workflow that recovers orders
- 1Ingest NDRs from every courier in near real-time, normalised into one status vocabulary so 'customer not available' means the same thing across partners.
- 2Auto-classify by reason code and route each to the right action — reattempt, buyer outreach, or address correction.
- 3Reach the customer immediately on WhatsApp with a one-tap 'confirm delivery' or 'reschedule' response, and capture a corrected address if needed.
- 4Push the buyer's response back to the courier before the reattempt window closes.
- 5Escalate stuck NDRs to a human queue with full context instead of letting them silently roll to RTO.
Speed is the whole game
The difference between a recovered order and an RTO is almost always time-to-first-contact. A buyer who gets a WhatsApp within minutes of the failed attempt, while they still remember ordering, responds far more often than one contacted a day later. Automating that first touch is where the recovery rate lives.
“Half our RTOs were just NDRs we reacted to too slowly. The moment buyer contact went automatic, the recovery rate stopped depending on how busy the ops team was that day.”— Illustrative composite of a mid-size D2C seller
Metrics for your NDR desk
- NDR-to-delivery conversion rate, tracked weekly and by courier.
- Median time from NDR raised to buyer contacted.
- Reattempt success rate by reason code.
- Share of NDRs that end in RTO despite outreach — your true undeliverable floor.
Frequently asked
An NDR (Non-Delivery Report) is a single failed delivery attempt with a reason code — the order is still in the field and can still be delivered on a reattempt. RTO (Return to Origin) is what happens after all reattempts fail and the courier ships the parcel back to you. NDR is the recovery window; RTO is the outcome you are trying to avoid.
Most couriers attempt delivery two to three times over roughly 24–72 hours before converting the shipment to RTO. The exact number and window vary by courier and service tier, which is why centralising NDRs into one queue with a consistent clock matters.
RouteOneX consolidates NDRs across all your courier partners into a single live queue, classifies each by reason code, and automatically reaches the buyer on WhatsApp to confirm, reschedule, or correct the address before pushing the instruction back to the courier — recovering orders that would otherwise slip into RTO.