Your growth engine is also your biggest leak
Cash on delivery is why India buys online. In smaller cities it can be more than half your orders, and switching it off would gut your volume. But COD also causes most of your returns. On COD, return-to-origin often runs 25–30%, and it can reach 35% in the riskiest areas. Prepaid comes back under 2–3%. So the goal is never to kill COD. It's to keep COD and shrink its failure rate.
The real cost of one RTO
A returned order isn't just a lost sale. You pay forward shipping, return shipping, packaging, handling, and often the product comes back unsellable. Brands doing 10,000 COD orders a month can lose ₹5.8–7.2 lakh to RTO before you even count the opportunity cost of the inventory being in transit instead of on a shelf. That's the number that decides whether you're profitable.
Where RTO actually comes from
Most RTO traces back to four causes. Amazon Shipping lists them as bad addresses, buyers who cannot be reached, COD refusals, and slow follow-up on failed deliveries. A bad address means a missing flat number, street, landmark, or pin code. Make those fields mandatory at checkout. An unreachable buyer is often just not home when the courier calls. A refusal is usually an impulse order, or the buyer found the same thing cheaper. Slow follow-up is the one cause fully in your hands. Each fix below targets one of these four, so start with the cause that shows up most in your own data.
Nudge COD to prepaid with the right incentive
Here's the counter-intuitive part: absolute discounts convert far better than percentages. A flat "₹50 off if you pay now" converts 31–38% of COD-preferring buyers, while an equivalent percentage discount converts only 18–23%. After a COD order comes in, send an automated WhatsApp offering a small prepaid discount before dispatch - many brands recover 15–25% of orders to prepaid this way, and every one you convert roughly halves its return risk.
The delivery-day WhatsApp that prevents 'not available'
A huge share of RTO is simply the customer not being home. A one-line WhatsApp on the morning of delivery - "Your order arrives today, please keep ₹X ready" - cuts customer-unavailable failures by 30–40%. It costs almost nothing and it's the single highest-ROI message in your whole flow.
Flag risky orders before you ship
Not every COD order deserves the same trust. Build a simple rule: if an order comes from a phone number or address that has failed before, route it to prepaid-only or extra verification. You're not blocking customers - you're protecting the ones who pay for the ones who don't.
Act on failed deliveries within 24 hours
When a courier cannot deliver, it raises an NDR, a non-delivery report. This is your last chance to save the order. Amazon Shipping notes that if no new attempt is set up within 24 to 48 hours, the parcel heads back as RTO. So treat NDRs as a daily task, not a weekly one. Call or message the buyer within 24 hours and fix a new delivery time. If two attempts fail, call before a third. Check the address and the buyer's plans, or decide the extra cost is not worth it.
Ship fast, because delay breeds refusals
Speed matters more than most sellers think. Shipway data, quoted by Amazon Shipping, found that orders first attempted within 1–2 days had a 22% RTO rate. Orders first attempted after five or more days hit 35%. A slow parcel gives the buyer time to change their mind, buy elsewhere, or simply be out. Pack and dispatch COD orders the same day where you can. Then tell the buyer the expected delivery date right away.
Pick couriers by pin code, not by price alone
The cheapest courier on paper can cost you the most once returns come in. Track how fast each courier makes the first delivery attempt. Then send orders to the partner that does best in each of your key pin codes. Keep a short watchlist of high-RTO pin codes from your last 30 days of data, and review it every week. Orders to those pin codes get one extra check, like a confirmation call, before they ship. Give each courier a fair trial of a few weeks before you judge it. One bad day in the monsoon is not a pattern.
Validate the address at checkout
Address problems cause 15–20% of RTO, and they're the easiest to prevent because they happen before you spend a rupee on shipping. Catching an incomplete PIN code or a missing landmark at checkout can cut address-related returns by 15–25%. Fix it at the source, not in the warehouse.
Use a token payment as a filter
For higher-value or higher-risk orders, ask for a small upfront token - ₹50 to ₹150 - with the balance collected on delivery. It barely dents conversion but it screens out impulse orders that were never going to be accepted, which are exactly the orders that become RTO.
Set a fair cancellation policy
Some sellers try to charge buyers who cancel. Be careful here. India's Consumer Protection (E-Commerce) Rules, 2020 say an online seller cannot charge a cancellation fee unless it bears similar charges when it cancels an order itself. The rules also ask you to show your return, refund, and return shipping costs clearly. So put your terms on the product page and at checkout, in plain words. A buyer who knows the rules before paying is less likely to refuse the parcel at the door.
Your weekly RTO review
- Tag every RTO with a reason: address, unreachable, refusal, or delay.
- Sort the week's returns by pin code, product, and courier.
- Move pin codes that keep failing to prepaid-only or extra checks.
- Send fewer orders to couriers with slow first attempts.
- Check that every NDR from the week got a call within 24 hours.
Track RTO like a metric, not an accident
What gets measured gets managed. Put your RTO rate on the same dashboard as revenue and watch it weekly, sliced by product, city, and courier. With orders, customers, and reports in one place on The Storemate, you can see which products and pin codes bleed returns and act on them - instead of finding out at the end of the quarter when the damage is done.