NDR and RTO appear constantly in courier and e-commerce operations, usually in the same sentence and often interchangeably. They are not the same thing, and the relationship between them is where the money is.

NDR: non-delivery report

An NDR is the record of a delivery attempt that did not succeed. The parcel is still in the network, still yours to deliver, and something can still be done about it.

Common reasons: nobody at the address, customer unreachable, address incomplete or wrong, customer refused, customer asked to reschedule, payment not available for a COD order, or the location was inaccessible.

RTO: return to origin

An RTO is a parcel travelling back to the sender because delivery could not be completed. It is the end state, and the expensive one.

An RTO parcel has consumed the full forward journey, some number of delivery attempts, and now a return journey — and it generates no revenue. On a low-margin order, a single RTO can wipe out the profit from several successful deliveries.

The relationship between them

This is the part that matters: every RTO started as an NDR that nobody resolved.

Typically a parcel gets a fixed number of attempts — often three — before it converts to RTO automatically. So the window between the first failed attempt and the final one is the entire opportunity to save the parcel. Operations that treat NDR as a status to record rather than a task to action simply watch that window close.

Why "failed" is not a reason

The most common NDR problem is useless reason codes. If your delivery staff can close an attempt with a generic "not delivered", you learn nothing and you can do nothing.

The difference between reasons is the difference between actions:

• Customer not available → call and agree a time; reattempt is likely to work
• Address incomplete → get the correct address; reattempting the same one will fail identically
• Customer refused → reattempting is wasted; move to return and stop spending
• COD amount unavailable → offer digital payment; this one often resolves on a phone call

Three of those four have a specific next step. Recorded as "failed", all four get the same treatment, and most of that treatment is wasted.

What reduces RTO

Contact before arrival

A message or call before the delivery attempt converts a proportion of would-be failures into successes, simply because the customer knows to be available. This is cheap and it is the single highest-return intervention.

Address quality at order time

Bad addresses are created at the point of order, not at the point of delivery. Validation, pincode checks and a required landmark field cost the customer seconds and save a whole delivery attempt.

Same-day NDR action

An NDR raised today and actioned today has a materially better chance of resolving than one picked up in two days. The system should be generating a work queue, not a report.

Giving the customer a way to self-serve

A link that lets a recipient reschedule, correct an address or authorise a neighbour removes a phone call from your team and resolves the NDR faster than calling would.

Knowing when to stop

A refused parcel or a genuinely wrong address will not be rescued by a third attempt. Converting to RTO early saves the cost of attempts that were never going to work.

What to measure

• First-attempt delivery success rate
• NDR rate, broken down by reason
• NDR-to-resolution rate — how many failed attempts eventually delivered
• Time from NDR raised to first action taken
• RTO rate, by client, by area and by reason

NDR-by-reason and time-to-action are the two that change behaviour. A rising "address incomplete" share is an order-form problem, not a delivery problem — and that is a fix in an entirely different part of the business.

A note on benchmarks

People frequently ask what a good RTO rate looks like. It varies enormously by category, payment mode, geography and customer base — COD orders return far more often than prepaid, for instance. Rather than chasing someone else's number, measure your own rate, segment it by reason, and track whether your changes move it. Your own trend is the only reliable benchmark.

Where we come in

NDR capture with real reason codes, follow-up workflows and RTO tracking are part of the delivery management software we build, and feed the economics discussed in last mile delivery software.