Is my RTO normal? Here's what Indian sellers actually see.
Every seller group has the same anxious question: “what RTO% is normal?” The honest answer is that no single number exists — category, COD share, price point and pin-code mix all move it. This guide gives you the seller-reported ranges, then something more useful: how to compute, segment and judge your own number.
- There is no universal 'normal' RTO. Seller-reported ranges run from single digits on prepaid-heavy home catalogues to 30%+ on COD-heavy value fashion. Compare yourself against your own trend, not a forum number.
- Compute it properly: RTO orders ÷ dispatched orders, weekly, from panel or settlement data — never from memory, because RTO events land one to three weeks after their dispatches.
- The benchmark question that actually pays: which segment of your RTO is fixable? Split by product, courier, pin code and COD vs prepaid, and the ugly average usually resolves into two or three specific, addressable chunks.
Four variables move RTO more than anything you do
Two sellers on the same marketplace, dispatching the same week through the same couriers, can honestly report RTO rates ten points apart — and both be running clean operations. The spread comes from four structural variables. Category: fashion carries size doubt, colour doubt and impulse energy that home and kitchen simply do not. Payment mix: a COD buyer can refuse at the door for free; a prepaid buyer almost never does. Price point: refusing a ₹250 kurti costs the buyer nothing emotionally; a ₹2,000 order gets more consideration before checkout and at the doorstep. And pin-code mix: some lanes and localities consistently return more parcels, whatever you ship into them.
This is why chasing a forum benchmark is a trap. A number quoted without its category, COD share and pin-code context tells you nothing about your business. The seller-reported ranges above are useful for one thing only: telling you whether you are roughly in the expected band for your kind of catalogue, or so far outside it that something specific is broken. Everything after that is about your own data.
Measure your true RTO% in six steps
The goal is a weekly number you trust, split into segments you can act on. Once this is running, the “is it normal?” anxiety gets replaced by a much better question: which chunk do I fix first?
- 01
Fix the formula
RTO% = RTO orders ÷ dispatched orders. Dispatched is the base — orders cancelled before handover never had a doorstep to be refused at, so counting them flatters your number. Decide the formula once and never change it, or your trend line means nothing.
- 02
Pull from data, not memory
Use panel order exports or settlement reports, not your recollection of a bad week. RTO events land one to three weeks after their dispatches, so memory systematically undercounts. Tag each RTO event back to its dispatch week so the ratio compares like with like.
- 03
Compute weekly, not monthly
A monthly average smooths over exactly what you need to see: the week a new product started coming back, or a courier lane went bad. Weekly granularity catches a shift within days of the returns arriving instead of a month later.
- 04
Segment by product first
Sort your catalogue by RTO%. Most sellers find a hockey stick: a handful of SKUs carry a wildly disproportionate share of returns while the rest of the catalogue behaves. Those few SKUs are your first, cheapest fix — review their images, size info and price positioning.
- 05
Then by courier, pin code and payment mode
Split the same events by courier partner, destination pin code and COD vs prepaid. A courier whose lanes run several points above the others, or a cluster of pin codes that returns everything, is a pattern you can act on — and evidence you can attach to disputes.
- 06
Judge products on rupees, not percentages
For each SKU: per-order profit versus RTO% × estimated cost per RTO event (forward freight, packaging, handling, blocked stock — often ₹80-150 for a small parcel, illustratively). If the second number wins, the product is losing money at any sales volume. Fix it or delist it.
- 07
Track the trend, not the snapshot
One bad week is noise; three rising weeks are a signal. Keep the weekly numbers in one place and read direction before level. A 12% RTO falling from 18% is a business getting healthier; a 12% climbing from 7% needs attention today even though the snapshot looks fine.
A few points of RTO is real money, every month
Put illustrative numbers on it. A seller dispatching 20 orders a day is roughly 600 dispatches a month. At 15% RTO that is 90 returned parcels; at an estimated ₹100 all-in cost per RTO event, about ₹9,000 a month burned before counting the margin those 90 orders never earned and the stock locked in transit for two to three weeks. Cut RTO by five points — usually achievable by fixing the two or three worst SKUs and lanes that segmentation exposes — and roughly ₹3,000 a month comes straight back, plus faster stock turns. These are illustrative figures; run them with your own parcel costs and margins.
The second cost is quieter: wrongful deductions ride along with RTO volume. Return freight charged at the wrong weight slab, an RTO parcel marked delivered, a refund processed against a product that never left your shelf. The more RTO events you have, the more settlement lines exist to go wrong — which is why an accurate RTO count is also the base layer of payment reconciliation.
Robnu computes the benchmark you can actually use: yours
Everything in the method above is bookkeeping a two-person team rarely has time for — matching RTO events to dispatch weeks, splitting by SKU and courier and pin code, re-running it every Monday. Robnu already runs your AJIO and Meesho order pipeline, so it sees every dispatch and every return event as they happen. Your true RTO%, segmented and trended, falls out of the same data — no spreadsheet night required.
And because Robnu reconciles settlements against the same order history, the RTO events that come back with wrong charges — freight at the wrong slab, a return never credited — become claims instead of silent losses. Fully autonomous filing is rolling out; the rare claim still asks you for one approval click.
RTO benchmarks, answered
There is no single normal. Sellers publicly report anywhere from mid-single digits to well past 30% depending on category, COD share, price point and the pin codes their orders come from. Fashion and COD-heavy value segments sit at the top of the range; home, kitchen and prepaid-heavy catalogues sit near the bottom. Treat any single benchmark number you read as a rough marker, not a target — the useful comparison is your own RTO% this month against your own RTO% last month, segmented by product and pin code.
RTO% = RTO orders divided by dispatched orders, over the same window. Use dispatched as the base, not total orders — cancellations before handover are a different problem. Pull both numbers from the panel or your settlement data, never from memory, because the RTO events land one to three weeks after the dispatches they belong to. Compute it weekly, and keep the window consistent so the trend is real. A monthly number hides the week a bad product or a bad courier lane started hurting you.
Fashion combines almost every RTO driver at once: heavy COD share, impulse purchases the buyer cools on before the parcel arrives, size and colour doubt that turns into refusal at the door, and low ticket values that make refusing painless for the buyer. Home and kitchen products are bought with more intent and less ambiguity, so refusal at the door is rarer. That is why seller-reported fashion ranges run visibly higher than hardline categories on the same marketplace with the same couriers.
It is consistently the biggest single lever sellers report. A prepaid buyer has already paid, so the parcel almost always gets accepted. A COD buyer can change their mind for free any time until the doorstep, and on value-focused marketplaces most orders are COD. You usually cannot refuse COD on Meesho or AJIO, so the practical response is measurement: split your RTO% into COD and prepaid, see the gap for your own catalogue, and factor the COD-heavy reality into which products you keep pushing.
When the maths stops working, not when the percentage merely looks ugly. Each RTO typically costs you forward and sometimes return freight, packaging, handling time and days of blocked stock — sellers commonly estimate somewhere between ₹80 and ₹150 per event for a small parcel, illustratively. If a product's per-order profit is thinner than its RTO rate times that cost, every sale of it quietly loses money. Run that check per product monthly; a bestseller by order count can be a loss-maker after RTO.
Robnu already processes your AJIO and Meesho orders end to end, so it sees every dispatch and every return event in one place. That means your true RTO% is computed from real order data — weekly, segmented by product, courier and payment mode — instead of a number you assemble from panel exports at month end. When an RTO comes back, Robnu tracks the return, checks what lands in settlement against what should, and raises claims on wrongful deductions. The rare claim still asks you for one approval click while fully autonomous filing rolls out.
Where this comes from
- Public seller discussions of RTO rates by category and payment mode: Reddit r/IndiaBusiness and Indian seller Facebook/Telegram groups, 2024–2026. Ranges quoted here are compiled from these reports and are illustrative.
- Meesho and AJIO seller panel documentation on returns, RTO handling and settlement reports — check the current policy on your panel for the charges that apply to your account.
- Industry commentary on COD share and return behaviour in Indian e-commerce, 2024–2026.