Building an NDR Workflow That Saves Orders

A non delivery report is not a failure. It is a second chance with a clock on it. When a courier marks an order not delivered, the package is usually still in the local hub and eligible for another attempt over the next day or two. What happens in those hours decides whether the order is saved or returns to origin at close to full shipping cost and lost packaging.

Most brands lose recoverable orders not because the customer changed their mind, but because nobody reached the customer in time. Here is how to build a workflow that closes that gap.

Understand what an NDR actually tells you

Every NDR carries a reason code. The common ones in India are customer not available, customer refused, incomplete or wrong address, and customer requested reschedule. These reasons demand different responses.

• Not available needs a reschedule confirmation for a time the customer will be home.
• Wrong or incomplete address needs a correction before the next attempt, or the reattempt will fail identically.
• Refused needs a conversation, because it often hides a payment concern, a delivery delay or a duplicate order rather than a real change of mind.

Treating all NDRs the same way is why generic reattempts fail. Sort by reason first.

It also helps to separate NDRs by payment type. A cash on delivery NDR behaves differently from a prepaid one. Prepaid customers have already paid and almost always want the order, so a prepaid NDR is nearly always worth an aggressive reattempt. A COD NDR carries more genuine hesitation, because the customer can still walk away at no cost. Knowing which bucket an NDR sits in tells you how hard to push and where a confirmation call earns its keep.

Move fast in the first window

The recovery window is measured in hours. Couriers usually make up to three attempts across consecutive days, so a response that arrives the next morning has already missed the second attempt. Design the first touch to happen the same day the NDR is raised.

• Automate the first contact through SMS, WhatsApp and IVR. Confirm the address, confirm availability, and offer a reschedule slot. This handles the majority of NDRs at scale.
• Capture intent, not just delivery. Ask the customer to confirm they still want the order. A confirmed reattempt succeeds far more often than a blind one.
• Escalate exceptions to a human. High value orders, second and third NDRs on the same shipment, and address corrections deserve a phone call. The economics justify the labor.

Tag reasons and fix the root cause

NDR handling that only reacts is a treadmill. The compounding wins come from tagging every NDR and reading the pattern.

• If a particular pincode or courier route generates repeated not available NDRs, the issue may be attempt timing, not customers.
• If wrong address NDRs cluster around checkout, the fix is address validation at the point of order, not more calls after dispatch.
• If refused NDRs rise on COD orders above a certain value, the fix may be a prepaid nudge or an order confirmation call before dispatch.

Route these patterns back to the teams that can act on them: product for checkout address capture, marketing for confirmation flows, and your 3PL for route level performance. NDR data is some of the cleanest operational feedback you will get.

Watch for false NDRs

Not every NDR is genuine. Couriers under route pressure sometimes mark deliveries as failed without a real attempt. This inflates your RTO rate and angers customers who were home waiting. Detect it by asking, in your reattempt contact, whether anyone actually came to the door. When a courier or route shows a consistent gap between reported attempts and customer experience, raise it with hard numbers. A false NDR rate that goes unchallenged becomes an accepted cost.

A related habit is to keep a light record of every reattempt outcome against the courier and route that raised it. Over a month this record turns anecdote into evidence. Instead of telling a courier partner that deliveries feel unreliable in a certain area, you can show that a specific route reports failed attempts at twice the rate of comparable routes while customers report no one arrived. That kind of number gets a route fixed. Complaints without data rarely do.

Measure the few numbers that matter

Run the workflow on a weekly review of a small set of metrics.

• Reattempt success rate. Of NDRs you acted on, how many were eventually delivered. This is the headline number.
• Time to first contact. How long between the NDR being raised and your first touch reaching the customer. Push this down toward the same day.
• False NDR rate. The share of NDRs where no genuine attempt appears to have been made.
• RTO rate by reason. So you know which root causes are actually converting to lost orders.

A disciplined NDR workflow will not save every order. But moving reattempt success up by even a few points pulls straight through to contribution margin, because you have already paid to acquire the customer and ship the order. The cheapest order to win is the one you were about to lose.