The numbers at a glance
- Measure RTO as returned ÷ shipped, split by payment mode — a blended number lies.
- COD RTO: single digits is excellent, low-teens common, 25%+ is a fire.
- Prepaid RTO: usually low single digits — paid buyers rarely refuse.
- The gap between the two is the whole reason prepaid conversion and COD confirmation matter so much.
"Is my RTO normal?" is the wrong first question. The right one is "normal for what?" — because a store that’s 90% prepaid and one that’s 90% COD live in completely different worlds. Before you panic (or relax), you need to measure RTO correctly and compare against the right benchmark. Let’s do both.
How to measure RTO correctly
The formula is simple; the discipline is in the denominator and the splits.
Two mistakes wreck most people’s RTO numbers. First, dividing by placed orders instead of shipped — that flatters the number by including orders you cancelled before dispatch. Second, reporting one blended percentage. A 12% blended rate could be 3% prepaid and 22% COD, or 10% and 14% — and those two businesses need completely different fixes. Split by payment mode first, then by courier and by pincode, and the real story jumps out.
The benchmarks: what "good" looks like
Ranges vary by category, price point and audience, but here’s a practical read for Indian D2C:
| RTO rate (COD) | Verdict | What it usually means |
|---|---|---|
| Under ~8% | Excellent | Tight confirmation, good addresses, quality traffic |
| ~8-15% | Healthy / normal | Solid ops with room to optimise |
| ~15-25% | Needs work | Gaps in confirmation, address quality or targeting |
| Over ~25-30% | Urgent | Something is broken — audience, pincodes, or no confirmation |
| Prepaid RTO | Verdict |
|---|---|
| Low single digits | Expected — paid buyers rarely refuse delivery |
| Noticeably higher | Investigate address/serviceability or courier issues, not intent |
Notice how different the two tables are. That gap — a paid buyer almost never bounces a parcel, a COD buyer easily can — is the single most important fact in Indian e-commerce operations, and it drives almost every RTO strategy worth running.
What drives your number up (or down)
RTO isn’t random. It clusters around a handful of causes, each with a known fix:
- Payment mode — more COD, higher RTO. Shifting even 20-30% of COD to prepaid moves the blended rate meaningfully. See COD to prepaid conversion.
- Confirmation — unconfirmed COD orders RTO far more than confirmed ones. A quick WhatsApp/IVR confirm filters out impulse and fake orders.
- Address quality — bad pincodes and incomplete addresses fail at the door. Validate at checkout.
- Audience — broad, discount-chasing traffic RTOs more than intent-driven buyers. Your ad targeting shows up in your RTO number.
- Pincode — some zones return at multiples of your baseline. Find them in your data (see our high-RTO pincodes playbook) and treat them differently.
- Courier — delivery success varies by partner and region. Route each order to the courier with the best track record for that pincode.
See your real RTO — split, scored and trending
Kwikfy breaks RTO down by payment mode, courier and pincode, scores every COD order for return risk before you ship, confirms orders on WhatsApp, and nudges COD to prepaid — so your benchmark moves in the right direction, with the numbers to prove it.
Track & Cut RTO Free →From benchmark to action
So: measure RTO as returned-over-shipped, split COD from prepaid, and compare each against the ranges above. If your COD RTO is in the teens, you’re normal but leaving money on the table; tighten confirmation and address quality. If it’s north of 25%, treat it as an emergency and start with confirmation and audience. And never chase the blended number alone — the whole game is hiding in the COD column.