RTO Benchmarks for Indian D2C

Every Indian D2C founder eventually asks the same question: is my RTO rate normal? It is a reasonable question and a surprisingly hard one to answer well, because the benchmark numbers in circulation are a mix of credible aggregate reporting and figures that have been repeated so often their origin has been lost.

What the credible public figures say

A few numbers are reported consistently enough by organisations with access to real transaction volume to be worth anchoring on.

COD share of orders. Payment processor Cashfree puts Cash on Delivery at roughly 60 to 65 percent of Indian online orders. Other payment and logistics providers report figures in the same band. This one is well established.

RTO rate on COD orders. Cashfree has reported that RTO on COD can reach 25 to 30 percent. Logistics platform Shipway has reported a figure of around 26 percent of Indian COD orders ending as RTO. These are aggregate figures across many merchants and categories, so they describe the market rather than any particular store.

Those two numbers together explain why COD management is a category at all. They are also about as far as reliable public data goes.

Why the category-level numbers deserve scepticism

You will find articles presenting neat tables of RTO rates by category — apparel at one figure, electronics at another, beauty at a third. Treat these carefully, for several reasons.

Most are not sourced. A number appears in one article, gets cited by a second, and by the fifth citation it has the authority of a statistic without ever having had a dataset behind it. If you cannot trace a benchmark to an organisation that would plausibly have the data, it is not a benchmark.

Those that are sourced usually come from a single platform’s book of business, which is not a random sample of Indian ecommerce. A logistics aggregator serving mostly large brands and one serving mostly new Shopify stores will report very different averages, and both will be accurate about their own customers.

And definitions vary more than you would expect. Some providers count only parcels refused at the door. Others include undelivered parcels returned for address failures, parcels returned after repeated failed attempts, and customer-initiated cancellations in transit. A 15 percent rate under a narrow definition and a 26 percent rate under a broad one can describe the same operation.

The practical consequence: an external benchmark can tell you whether you are in a different league from the market, but it cannot tell you whether your apparel line is underperforming. Only your own data does that.

Build your own benchmark instead

A blended store-wide RTO percentage is nearly useless for decisions, because it averages across populations that behave completely differently. The useful exercise is to break your own history into segments and compare segments against each other.

Export twelve months of orders and calculate RTO rate across these cuts:

By payment method. Prepaid, partial payment, full COD. This is the most important split and the one that shows you what COD is actually costing you. If you take nothing else from this article, take this one.

By order-value band. Group into four or five bands. Most brands find a band where refusals spike — often where the amount becomes large enough for a customer to reconsider at the door. That threshold is where your partial-payment or prepaid-only rules belong.

By category and by SKU. Category tells you where fit and expectation problems live. SKU-level data tells you something more actionable: if refusals concentrate in a handful of products rather than spreading across a category, the problem is those listings, not COD.

By pincode and state. Aggregate to state for signal and look at pincode for action. Expect concentration — a minority of pincodes usually accounts for a disproportionate share of failures, and the list is often not the one you would have guessed.

By acquisition source. Cold social traffic, search, direct, email. Intent varies sharply by source, and this cut frequently explains more variance than category does.

By dispatch speed. Bucket orders by hours from placement to courier pickup and calculate RTO for each bucket. If the slow buckets fail more, you have quantified the cost of your dispatch delay — and that is usually the most persuasive internal argument available for fixing it.

By new versus returning customer. First orders behave differently from repeat orders. If your returning-customer RTO is low, blanket restrictions are taxing your best customers for a problem they are not causing.

Reading the result

The point of segmenting is not to find your average. It is to find your spread.

If one segment’s RTO is several times another’s, that gap is your opportunity, and it is specific enough to act on. A brand with 22 percent blended RTO that turns out to be 6 percent on prepaid and 31 percent on COD above ₹3,000 does not have an RTO problem — it has a high-value COD problem, which is a narrower and far more tractable thing.

Set your internal targets per segment rather than store-wide. Then the next question stops being “is 22 percent normal?” and becomes “why is this segment four times that one?” — which is a question with an answer.

Recalculate quarterly

RTO patterns move with your product mix, your ad channels, your courier performance, and the season. A segmentation done once and filed away describes a business you no longer run. Quarterly is frequent enough to catch drift and infrequent enough that the volumes stay meaningful.

Watch in particular for pincode lists going stale, new SKUs entering the high-refusal group, and courier lanes degrading — all three change quietly and none of them announce themselves in a blended average.

COD King’s analytics break RTO down by payment method, order value, pincode, and category, which covers most of the cuts above. The dispatch-speed and acquisition-source cuts need your Shopify and ad data alongside it — and they are often the two that reveal the most.