OCLT

Free decision tool

NDR Recovery ROI Calculator

For COD e-commerce operators: enter your order volume, NDR rate, and average order value to see what failed deliveries cost today, what a systematic recovery workflow would save, and where the line sits between them.

ClickPost reports that Indian e-commerce logistics NDR rates run 20% to 40% by category, manual NDR handling converts 10% to 20%, and automated or systematic workflows convert 40% to 60%.

Order volume

Formatting only. Changing currency loads its editable AOV and per-case cost starting inputs.

Your input. Use completed orders from a normal month.

Your input. Currency changes load the starting value listed in Methodology.

NDR exposure

%

Share of shipments that hit at least one failed delivery attempt.

ClickPost: 20%–40% by category. Source

Your input: re-attempt fee, call or message time, and staff handling on every case, recovered or not. OCLT's published estimate for India is roughly ₹80–120, described there as an industry figure from vendor marketing, not an audited study.

Recovery scenario

Sets the current recovery rate default below. Both remain editable.

%

Share of NDR cases you already save today.

ClickPost: manual NDR handling converts 10%–20%. Source
%

What a WhatsApp-first, human-escalation NDR workflow would recover.

ClickPost: automated NDR workflows convert 40%–60%. Source

Net revenue saved per month

₹2,16,000

₹25,92,000 annualized at the same mix.

Based on 600 NDR cases per month.

Currently lost

₹6,48,000

Systematic workflow recovers

₹2,88,000

Currently recovered

₹72,000

What chasing every case already costs you

₹60,000

600 cases at your ₹100 per-case cost, whether the case gets rescued or not. Shown separately from the revenue figures above so it isn't double-counted.

Assumption recap

Currencyyour input
INR
Monthly ordersyour input
3,000
Average order valueyour input
₹1,200
NDR ratesource
20%
Cost per NDR caseyour input
₹100
Current NDR handlingyour input
Manual calling
Current recovery ratesource
10%
Systematic workflow recovery ratesource
40%

Model this against your own delivery data.

Bring your courier NDR report and a normal month of orders. We'll show you where the rescue ladder pays for itself.

Methodology and assumptions

The full chain, with no hidden multiplier.

The NDR rate and recovery-rate ranges come from ClickPost, an NDR and logistics tooling vendor: NDR rates of 20% to 40% by category, manual conversion of 10% to 20%, and automated or systematic conversion of 40% to 60%. Those are a vendor's operating figures across its own client base, not an audited industry census. Every slider below starts at the low end of its range on purpose and stays editable, so replace it with your own courier data the moment you have it.

ndrOrders = monthlyOrders × ndrRate

revenueAtRisk = ndrOrders × AOV

currentlyRecovered = revenueAtRisk × currentRecoveryRate

currentlyLost = revenueAtRisk × (1 − currentRecoveryRate)

systematicRecovered = revenueAtRisk × systematicRecoveryRate

netRevenueSaved = systematicRecovered − currentlyRecovered

handlingCostToday = ndrOrders × costPerCase

An NDR case is a failed delivery attempt, not a returned order. Some of those cases resolve on their own; the calculator asks what share you actually recover today, and what share a WhatsApp-first, human-escalation workflow would recover instead. The gap between the two, applied to your order value, is the net revenue figure at the top.

Cost per NDR case is charged once per case regardless of outcome. It sits in its own card, separate from the revenue figures, so a case you spend money chasing and still lose doesn't get counted twice.

Defaults are editable starting inputs, not public benchmarks: 3,000 orders, 20% NDR rate, manual current handling at a 10% recovery rate, and a 40% systematic recovery rate. Set each one to your own figure before making a decision.

Currency only changes formatting. INR starts at 1,200 AOV and a ₹100 cost per case; AED and SAR start at 180 and 12; EUR starts at 45 and 3. These are editable inputs supplied for scenario setup, not market data.

FAQ

Questions behind the model

What counts as an NDR case in this calculator?

A non-delivery report is a failed courier attempt: wrong address, an unreachable customer, a refusal at the door, or a re-attempt request that never gets resolved. Not every NDR case turns into RTO. Some get rescued with a callback or a WhatsApp reconfirmation. This calculator models how many of your NDR cases you keep versus lose, not your full order book.

Where does the 20% to 40% NDR rate range come from?

ClickPost, an NDR and logistics tooling vendor, publishes that Indian e-commerce logistics NDR rates range 20% to 40% by category. That's a vendor's operating figure across its client base, not an audited industry census, so the calculator starts at the low end and asks you to confirm it against your own courier dashboard.

Where do the recovery-rate numbers come from?

The same ClickPost source states that manual NDR processes convert 10% to 20% of failed deliveries, while automated or systematic workflows convert 40% to 60%. Both sliders here start at the low end of those ranges on purpose. Undersell the opportunity, then push the numbers up as your own data supports it.

How is this different from the RTO Loss Calculator?

The RTO Loss Calculator prices what already came back to origin. This one prices the failed-delivery attempt itself, the point before a case is decided either way. An NDR case that goes unrescued usually becomes an RTO later, so the two tools cover adjacent moments in the same failure. Run both if you want the full before-and-after picture.

Is my calculator data stored?

Your inputs stay in this browser, saved only in localStorage under oclt-ndrroi-v1 so the tool can restore your last session. OCLT does not receive the values unless you choose the WhatsApp option, which places the displayed numbers into a prefilled message you send yourself.

How does OCLT fit into fixing an NDR problem?

RxFlow's delivery-rescue module opens a case the moment a delivery attempt fails, sends a WhatsApp reconfirmation first, and escalates to a telecaller on a call SLA when the customer doesn't respond. Across OCLT's live deployments that combination holds RTO at 12% against a typical 30%+, with 60% fewer returns after it went live. Your own NDR volume and recovery ceiling will differ. This calculator is the starting math; the deployment on /ndr-rto-rescue is the mechanism behind it.