What Is an NDR (Non-Delivery Report) and How Does It Work?
An NDR (Non-Delivery Report) is a structured notification generated by a courier company whenever a delivery executive is unable to hand over a shipment to the consignee during an attempted delivery. The report captures the AWB (airway bill) number, the delivery attempt timestamp, the location, and crucially, a reason code — a standardised label explaining why the attempt failed.
The moment an NDR is raised, the shipment does not simply sit idle. It enters a defined workflow: the courier partner holds the package at the nearest hub, typically for a limited window, and awaits instruction — either to reattempt delivery or to initiate a return-to-origin (RTO). The seller, or the logistics aggregator acting on the seller's behalf, must respond within this window.
On platforms like Shiprocket, NDRs surface in a dedicated panel where each failed shipment is listed with its reason code. The seller can review the reason, update delivery instructions, confirm or correct the buyer's address or phone number, and push a reattempt instruction back to the courier — all without calling the courier's customer-service line manually. Understanding this workflow is foundational because every minute of delay in responding to an NDR narrows the window for a successful resolution.
Common NDR Reasons in Indian E-Commerce and What They Signal
NDR reason codes are not bureaucratic labels — they are diagnostic signals that point to specific corrective actions. The most frequently encountered reasons in Indian e-commerce fall into four broad categories.
Customer unavailability is the single largest driver of NDRs. The consignee was not present at the delivery address during the attempt. The correct response is to contact the buyer, confirm an available time slot, and request a reattempt for that window — not to immediately reschedule without verification.
Incorrect or incomplete address NDRs indicate that the delivery executive could not locate the premises. These require the seller to collect the correct address from the buyer and relay it to the courier before the reattempt. Sellers who pre-validate addresses at checkout using pin-code verification tools reduce this category significantly.
Phone number unreachable is particularly problematic because the courier cannot independently verify the buyer's intent. Here, sellers must attempt contact through alternative channels — WhatsApp, email, or order-confirmation SMS threads — before confirming a reattempt.
Customer refusal is the most commercially damaging reason code because it often signals a cash-on-delivery (COD) hesitation, an impulse order the buyer no longer wants, or a quality concern. A brief outbound call by the seller to address the objection can still convert a refusal, but the conversion rate drops sharply if contact is made more than a few hours after the failed attempt.
The Financial Cost of Ignoring NDRs: Why RTO Is Not an Option
Sellers sometimes treat NDR management as a low-priority back-office task, delegating it to a junior team member or assuming the courier will automatically reattempt. This misunderstanding is expensive. When an NDR escalates to a full RTO, the seller incurs forward shipping charges (already paid), reverse shipping charges (billed on the return), and restocking or re-inspection costs once the package returns to the warehouse. For a COD order, there is also the complete loss of sale.
The compounding effect is significant. A seller shipping hundreds of orders weekly with even a modest unmanaged NDR rate accumulates a return pile that ties up working capital in inventory already paid for, shipped, and returned — inventory that may have suffered transit damage in the process.
Beyond direct costs, high RTO rates damage a seller's courier partner scorecard. Many courier companies apply preferential allocation and priority pickup to sellers with strong delivery metrics. Sellers with persistently poor NDR-to-delivery conversion rates can find themselves deprioritised in dense delivery zones, creating a self-reinforcing cycle of poor delivery performance.
The strategic implication is clear: treating every NDR as a recoverable opportunity rather than a pre-RTO formality is one of the highest-return operational investments an Indian e-commerce seller can make.
How to Manage NDRs Effectively: A Step-by-Step Approach
Effective NDR management follows a structured rhythm that begins the moment the failed-delivery notification arrives.
Step 1 — Acknowledge quickly. Set up real-time NDR alerts through your logistics platform. The reattempt window is finite, and acting within the first few hours of an NDR being raised gives the highest probability of converting the shipment to delivered.
Step 2 — Read the reason code before acting. Each reason demands a different response. Do not apply a generic reattempt instruction without first addressing the root cause — sending the delivery executive back to an incorrect address wastes an attempt and costs money.
Step 3 — Contact the buyer proactively. An outbound call or WhatsApp message explaining that delivery was attempted and confirming availability or correcting the address signals professionalism to the customer and dramatically improves reattempt success rates.
Step 4 — Relay updated instructions to the courier. Through your NDR management panel, submit the verified address, preferred delivery slot, or alternate contact number so the delivery executive has accurate information before the next attempt.
Step 5 — Set escalation rules. Define how many reattempts you will authorise before initiating a controlled RTO. Unlimited reattempts on a clearly unwilling buyer waste courier capacity; a defined threshold forces a decision and limits cost accumulation.
Step 6 — Analyse NDR patterns by reason code, courier, and geography to identify systemic issues — such as a particular pin code with chronic address problems — and address them upstream at the checkout or customer-communication stage.
NDR Management on Shiprocket: Using Automation to Reduce RTO
Shiprocket's NDR management panel is designed to give sellers centralised visibility and control over failed-delivery shipments across multiple courier partners without managing each carrier separately. When a courier partner marks a shipment as undelivered and files an NDR, the event is pushed into the Shiprocket dashboard in near real-time, tagged with the carrier's reason code.
The platform allows sellers to configure automated buyer-communication workflows triggered the moment an NDR is raised — sending an SMS or WhatsApp message to the consignee with a link to confirm their availability or update their address. This removes the manual effort of individually calling each affected customer and ensures no NDR sits unactioned during off-hours.
Sellers can also define reason-specific reattempt rules: for example, automatically approving one reattempt for 'customer unavailable' NDRs while routing 'customer refused' NDRs to a human review queue for an outbound retention call. This layered approach applies intelligent triage rather than treating all NDRs identically.
The reporting layer within the panel allows teams to slice NDR data by courier partner, destination state, pin code, and product category, making it possible to identify structural delivery failure patterns and take pre-emptive action — such as switching carriers on problematic routes or tightening COD eligibility for high-refusal geographies.
Common NDR Mistakes Indian Sellers Make and How to Avoid Them
Even sellers who understand NDR conceptually make process errors that cost them recoverable shipments.
Waiting too long to act is the most prevalent mistake. NDR windows are not open-ended. Courier partners have defined hold periods, after which they initiate RTO automatically. Sellers who check their NDR queues once a day — or less — routinely lose shipments that could have been saved with same-day action.
Applying a blanket reattempt without buyer confirmation is equally damaging. Sending the delivery executive back without verifying the buyer's availability or correcting address information results in a second failed attempt, which exhausts the reattempt allowance and accelerates the RTO timeline while adding to logistics costs.
Treating COD refusals like availability issues is a categorical error. A customer who refused delivery has taken an active decision, and that decision requires a conversation — not a reattempt. Sellers who skip the outbound call on refusal NDRs and simply push a reattempt instruction see very low conversion on second attempts.
Failing to capture NDR data for future prevention means the same problems recur indefinitely. Sellers who never audit their NDR reason distribution cannot know whether their checkout address form needs improvement, whether a specific courier underperforms on certain routes, or whether COD availability should be restricted for certain buyer segments.
Building a lightweight NDR review cadence — even a weekly fifteen-minute analysis of top reason codes — creates a continuous improvement loop that reduces NDR volume over time rather than simply managing the existing rate.