Adoment
All posts
Guide1 July 20268 min read

COD return to origin: what it actually costs, and how to fix it

RTO gets treated as an annoying line item. It's usually one of the largest hidden costs in a COD-heavy business — and almost nobody has an accurate number for it. Here's how to actually calculate it, and what to do next.

Cash-on-delivery is why a lot of Indian e-commerce exists at all — it removes the trust barrier that stops first-time online buyers from paying upfront. It's also why return-to-origin, RTO, is a cost almost every COD-heavy brand carries and almost none has actually measured properly.

"Return to origin" means exactly what it sounds like: the courier couldn't deliver the order, so it comes back to your warehouse. For COD specifically, this happens for a cluster of reasons — the customer wasn't home, they changed their mind before cash was due, the address was wrong, or the order was never a serious purchase intent to begin with.

Why RTO is so expensive, order for order

The mistake most founders make is pricing RTO as "the cost of a return." It's worse than that, because unlike a normal e-commerce return, you pay for the shipping in both directions on an order that generated zero revenue.

  • Forward freight — paid the moment the courier picks up the order, regardless of whether it's ever delivered.
  • Reverse freight — paid again to bring the undelivered order back to your warehouse.
  • Packaging — consumed and unrecoverable the moment the order was packed.
  • Handling — inbound QC, restocking, and the labour of processing a returned shipment.
  • Working capital — cash tied up in inventory that's now sitting in transit twice instead of on a shelf or in a customer's hands.

Add it up and a single RTO'd order typically bleeds somewhere between ₹100 and ₹250, purely in logistics and handling — before you even count the opportunity cost of the inventory or the customer acquisition spend that won it in the first place.

The calculation almost nobody does

Here's the arithmetic that turns RTO from a vague annoyance into a number that shows up on your P&L: take your monthly order volume, multiply by your COD share, multiply by your RTO rate on those COD orders, and multiply that by your average cost per RTO'd order.

1,000 orders/month × 60% COD × 30% RTO × ₹175/order ≈ ₹31,500 lost every single month — and that's a conservative, mid-range estimate for a completely average D2C store.

Most brands have never run this calculation cleanly, because the inputs live in two different systems — order data in Shopify or their storefront, delivery status in the courier's dashboard — and nobody's stitched them together into one number. Which means the RTO bleed sits there, invisible, month after month, while everyone treats it as a rounding error.

The three things that actually reduce it

  • Confirm intent before you ship — a WhatsApp confirmation on risky orders catches the impulse buys and typo'd addresses before you've paid forward freight.
  • Score risk instead of treating every order the same — most RTO risk concentrates in a minority of orders; find them and act only there.
  • Recover failed delivery attempts — a failed attempt isn't a return yet; a timely nudge on WhatsApp turns a lot of these back into completed deliveries.

None of this requires switching couriers or changing your business model. It requires seeing the number clearly and acting on the highest-risk slice of orders — which is precisely what RTO Shield does, starting with a free, read-only baseline of your actual RTO cost.

Written by Rishabh Gupta

Ready to put your operations on autopilot?

Book a 30-minute walkthrough and we'll wire up your first workflow with you.

Book a demo