The RTO Report Worth Building

“Our RTO is 18 percent” is a fact you cannot act on. Eighteen percent of what, where, on which courier, for which products, paid how? The blended number hides five different problems with five different fixes. This is the RTO report worth building: the five cuts, what each one tells you, and the decision each one drives.

Cut one: by payment mode

COD RTO against prepaid RTO. If COD is 24 percent and prepaid is 5, your RTO problem is a COD problem, and the fixes are confirmation, prepaid incentives and partial COD. If prepaid is also high (over 10 percent), the problem is addresses or delivery execution, and the fixes are checkout validation and courier choice.

Decision: which family of tactics to invest in.

Cut two: by courier, on the same lanes

RTO by courier is meaningless unless the lanes are comparable; a courier that carries your Zone E parcels will always look worse. Compare couriers within a zone, or within a set of pincodes both serve. A courier running 8 points higher RTO than another on the same Zone D pincodes is failing more deliveries: fewer attempts, worse NDR handling, or poor last-mile coverage there.

Decision: courier rules. Move that zone’s volume to the better courier, or raise it with the carrier through the platform.

Cut three: by zone and pincode

RTO by zone shows the transit-time effect: Zone A at 8 percent, Zone D at 22, Zone E at 35 is normal shape. RTO by pincode, over the last 90 days with at least 20 orders per pincode, shows the outliers: the specific towns where a third of parcels come back.

Decision: COD caps or prepaid-only on the worst pincodes; faster courier on long lanes; a second pickup location if one distant region dominates volume.

Cut four: by product

RTO by SKU, or by category. A product with double the store’s RTO rate has a listing problem (photos, size, description), a quality problem, or is being ordered on impulse. Fashion SKUs with size confusion, and anything heavily promoted on social, tend to lead this list.

Decision: fix the listing, add a size guide, restrict COD on the SKU, or change the promotion.

Cut five: by NDR reason and attempt

Every failed attempt has a courier-supplied reason: customer not available, address incorrect, refused, out of delivery area, phone unreachable. The mix tells you what is failing. “Refused” is a confirmation problem. “Address incorrect” is checkout. “Not available” and “phone unreachable” are communication: the buyer did not know the parcel was coming.

And by attempt: how many NDRs convert on the second attempt, and how many go to RTO. If under 40 percent of NDRs convert, the NDR process is not reaching buyers fast enough.

Decision: which step of the funnel to fix, and whether NDR automation is set up.

The report

One page, monthly, with the current month and the previous two:

Cut	Metric	This month	Last month	Change
Blended	RTO percent
Payment mode	COD RTO, prepaid RTO
Courier (within Zone C, D)	RTO by courier
Zone	RTO by zone
Pincode	Top 10 worst, with volume
Product	Top 10 worst SKUs, with volume
NDR	Reason mix; second-attempt conversion
Cost	RTO freight this month; lost margin estimate

The last row is the one to show whoever approves budgets. RTO freight is on the invoice; lost margin is RTO count times average gross margin. Together they justify the confirmation tooling, the prepaid discount and the NDR automation many times over.

Where the data comes from

Courier Uncle records the payment mode, courier, zone, pincode, status history with NDR reasons, and the RTO charge on every shipment, and reports RTO by courier and period on the dashboard. The shipment export carries every field for the pivots above; the list endpoint on the API does the same for a BI tool.

Reading it without fooling yourself

• Minimum volume per cell. A pincode with 3 orders and 1 RTO is 33 percent and means nothing. Twenty orders per cell before drawing a conclusion.
• Same lanes when comparing couriers. Otherwise you are comparing zones.
• Lag. An order shipped on the 28th is not an RTO or a delivery until mid next month. Report on orders shipped in the month, measured 15 days after month end.
• One change at a time. If you launch confirmation and a prepaid discount in the same week, you will not know which worked.

Frequently asked questions

What RTO rate should I aim for?

Under 8 percent prepaid, under 15 percent COD, under 12 percent blended. The report tells you which cut is furthest from that and therefore where to start.

How often should I look at it?

Monthly for the full report; weekly for the NDR conversion rate, which responds to process changes within days.

Should I compare couriers on RTO or on cost?

Both, and on the same lanes. A courier that is Rs 5 cheaper and 6 points worse on RTO is far more expensive per delivered order.

Can I get the RTO reason from every courier?

Most integrated couriers supply an NDR reason code with each failed attempt. It appears on the shipment timeline and in the NDR list. Some smaller carriers supply only “undelivered”; for those, your own NDR calls fill in the reason.

How do I estimate lost margin from RTO?

RTO count in the month times average gross margin per order. It is an estimate, but it is the right order of magnitude and it is the number that gets the budget approved.

Is a pincode-level block ever the right answer?

For a handful of pincodes with over 40 percent RTO on adequate volume, prepaid-only is reasonable. Blocking delivery entirely is rarely necessary and loses the 60 percent who accept.

Ship smarter with Courier Uncle

Every cut in this report comes from fields the platform records on each shipment. Start free and export a month.