No universal RTO percentage is good for all COD orders in India. It depends on category, price band, pincode mix and courier. Calculate RTO as RTO orders divided by shipped orders, track COD and prepaid separately, and set your target from your own trend and break-even cost per RTO. Treat any published benchmark with caution unless you know how it was measured.
Why there is no single good RTO percentage
Most articles quote a neat range and call it healthy. We will not, because a number without context misleads. A brand selling low-priced accessories to tier 3 pincodes will see very different RTO from one selling premium footwear in metros, even with identical operations.
What moves RTO more than anything is your mix: payment mode, category, order value, delivery pincodes, courier performance and how you run discounts and promotions. A figure that is acceptable for one brand can be a margin leak for another.
So the useful question is not "what is the industry number?" but "what is my number, how does it split, and at what level does RTO start hurting my contribution margin?"
How to calculate your COD RTO percentage
The basic formula is simple. The errors come from the denominator and from mixing cohorts.
- COD RTO % = COD orders returned to origin ÷ COD orders shipped × 100.
- Use shipped orders, not placed orders. Cancelled-before-dispatch orders are a different problem.
- Count by ship date cohort. Orders shipped in the last few days may not have reached a final status, so recent weeks look better than they are.
- Keep RTO separate from customer returns. RTO happens before or at delivery; a customer return happens after the customer accepts the parcel.
Wait until the cohort has closed (delivered or RTO received) before you compare weeks. Otherwise you will celebrate an improvement that is just pending shipments.
Split RTO before you judge it
One blended percentage hides the real story. Cut the same data along these lines:
- Payment mode: COD versus prepaid. COD RTO is usually the bigger problem, but measure it rather than assume.
- Pincode or region: a few pincodes often drive a disproportionate share.
- Category and price band: high-value COD orders cost more per failed delivery.
- Courier or delivery partner: compare on the same pincodes only.
- Reason code: customer refused, not reachable, address issue, delivery attempts exhausted, or damaged in transit.
Reason codes matter because they point to different fixes. Unreachable customers suggest verification gaps. Address issues point to data quality. "Delivery attempts exhausted" may point to a courier problem you can raise.
How to set a target for your brand
Build your target from your own numbers in this order:
- Baseline: take at least a few months of closed cohorts, COD and prepaid separately.
- Break-even: work out the cost of one RTO (forward freight, return freight, packaging, handling, any non-resalable stock, and any marketplace charges per your terms).
- Contribution check: at what COD RTO percentage does a COD order stop earning more than it costs?
- Target by segment: set a different goal for each pincode cluster or category rather than one brand-wide figure.
- Trend, not a point: aim for steady month-on-month reduction, and review it after sales events, when RTO usually spikes.
If an outside benchmark is quoted to you, ask how it was calculated, which categories it covers and whether it includes marketplace orders. If those answers are missing, do not anchor your target to it.
What RTO really costs on marketplaces
On marketplaces, an RTO is not just a logistics event. Depending on your seller agreement, it can affect fees, reversals, shipping charges and penalties. Do not assume how a particular charge behaves; read your agreement and rate card, and confirm the latest terms with the marketplace.
Then check the settlement report line by line. Look for whether commission was reversed on RTO orders, whether forward and reverse shipping were charged as agreed, and whether any penalty or deduction appears against the order.
Parcels that come back damaged, with missing items, or never reach you are a separate recovery question. Keep order IDs, return status, receiving evidence and the claim timeline in one place so a case can be raised within the window your terms allow. MarketplaceMetrics by Fundle reconciles sales and settlements, checks fees against agreed terms and tracks returns and recovery cases, so these items do not sit in scattered spreadsheets.
Practical ways to bring COD RTO down
- Verify risky orders: confirm by call or message for high-value or high-risk pincode orders before dispatch.
- Fix address quality: flag incomplete addresses and landmarks at order stage.
- Nudge to prepaid: where you control the checkout, offer a clear incentive for prepaid payment.
- Manage delivery follow-ups: act on failed-delivery notifications quickly, within the courier's reattempt window.
- Review courier allocation: shift weak pincodes to a better performing partner.
- Review COD availability: restrict or limit COD in consistently poor pincodes, if the channel allows.
Change one lever at a time and compare cohorts, so you know what actually worked.
Worked example
Illustrative example only. These figures are not benchmarks.
| Segment | Shipped | RTO | RTO % |
|---|---|---|---|
| Prepaid | 600 | 48 | 8% |
| COD | 400 | 88 | 22% |
| Total | 1,000 | 136 | 13.6% |
The blended 13.6% hides that COD RTO is 22%. Suppose the illustrative cost per RTO is ₹160 (₹80 forward freight, ₹70 return freight, ₹10 packaging). Then the 88 COD RTOs cost about ₹14,080 (88 × ₹160) before counting any stock damage or marketplace charges. If, after a pincode review, COD RTO falls to 18% on the same 400 shipments, RTOs drop to 72 and the freight and packaging cost to ₹11,520, a saving of ₹2,560 in that cohort.
Questions and answers
Is 20% RTO on COD orders too high?
It depends on your category, order value and margins. Instead of judging 20% in isolation, calculate your cost per RTO and your contribution margin per COD order. If RTO costs wipe out the margin, it is too high for you, whatever others report.
Should I include cancelled orders in RTO percentage?
No. Count only orders that were shipped. Orders cancelled before dispatch never left your warehouse, so they point to different issues such as stock or customer changes of mind. Mixing them with RTO makes the percentage unreliable.
Is RTO the same as a customer return?
No. RTO means the shipment goes back to you because delivery failed or was refused. A customer return happens after the customer receives and accepts the parcel. Track them separately, since causes, costs and fixes differ, and marketplace treatment may differ too.
How often should I review my COD RTO percentage?
Review weekly for operations and monthly for target setting, using closed ship-date cohorts. Check again after sales events and campaigns, because discount-led COD orders often behave differently from regular demand and can distort your average.
