Insight · eCommerceTOFU
The RTO cost your dashboard isn't showing you
The short answer
Ads Manager counts a purchase the moment it's placed. Your bank account counts it when the money arrives. For Indian D2C brands with a large share of COD orders, the gap between those two moments can be enormous — and most dashboards never show it.
How the gap appears
When a COD order is refused or undeliverable, you've paid for the ad that won it, the forward shipping, the reverse shipping and the handling. The platform still reports it as a conversion with full revenue. If a meaningful share of COD orders come back, your "real" ROAS can be materially lower than the one on screen.
Three changes that fix the numbers
- Report ROAS on delivered orders. Recalculate weekly using delivered revenue from your shipping partner, not placed revenue.
- Build RTO into targets. Use a break-even ROAS that includes reverse shipping and lost acquisition cost. Our calculator does this.
- Track RTO by campaign and creative. Some audiences and offers produce far more refusals than others.
And the changes that fix the problem
- WhatsApp confirmation before dispatching COD orders
- A small prepaid incentive
- COD restricted in chronically high-RTO pin codes
- Clear delivery timelines and product information
- Faster dispatch
The takeaway
If your ROAS looks healthy but cash is tight, look at RTO first. It's often the single biggest gap between reported and real performance in Indian eCommerce.
A worked example
A brand ships 3,000 orders a month, 60% of them COD, with a quarter of COD orders returned. That's 450 returned orders. If each cost ₹350 in ads to acquire and ₹150 in shipping and handling to send out and bring back, the monthly leakage is around ₹2.25 lakh — money that platform ROAS counts as revenue earned.
A delivered-order reporting template
| Campaign | Placed orders | Delivered orders | Delivery rate | Spend | Delivered ROAS |
|---|---|---|---|---|---|
| Prospecting A | |||||
| Prospecting B | |||||
| Retargeting |
Fill it weekly from your order management system to see which campaigns bring buyers who actually accept delivery. Use the RTO cost calculator to estimate the cost of refusals.
What to do next
- Report delivered revenue alongside ordered revenue
- Add COD confirmation
- Analyse RTO by pin code and source
- Recalculate break-even ROAS
Frequently asked questions
Can we send delivered-order data back to Meta?
You can send later conversion events (for example, a custom "delivered" event) through the Conversions API and use them for reporting and, with enough volume, optimisation.
Which campaigns usually have higher RTO?
It varies, but broad prospecting with heavy discounts and COD-only checkout often shows higher refusal rates. Measure by campaign.
Is RTO only a D2C problem?
It's most visible in COD-heavy eCommerce, but marketplaces and retailers face similar costs from refused deliveries.
How do we report delivered revenue to ad platforms?
By uploading delivered or cancelled order data as offline conversions or adjustments where supported.
Keep reading
Services behind this
Terms used on this page
Do the maths
Run your numbers before you spend a rupee.
Our free calculators turn margins, AOV and conversion rates into the targets that actually matter: break-even ROAS, affordable CAC and budget per stage.