An RTO analytics tool for ecommerce sellers in India should do more than show an RTO percentage. It should split RTO by pincode, courier, payment mode and SKU, separate RTO from customer returns, estimate the cost of each undelivered shipment, and connect to settlement data so you can check charges and follow up on damaged or missing stock.
What an RTO analytics tool should actually do
RTO (return to origin) happens when a shipment cannot be delivered and goes back to the seller. Many sellers see it as one percentage on a dashboard. That number tells you something is wrong but not where, why or how much it costs.
When you compare tools, look for these capabilities:
- Clear definitions. RTO (never delivered) should be separate from customer returns (delivered, then sent back) and from cancellations before dispatch.
- Useful cuts. You should be able to slice RTO by pincode, courier or logistics partner, payment mode, category, SKU, channel and order value band.
- Cost visibility. The tool should estimate forward freight, reverse freight, handling and any fees applied to RTO orders.
- Stock outcome. It should show whether returned units were received, received damaged, or never arrived.
- Follow-through. Cases that need a claim or a dispute should have an owner, a status and an age.
Metrics worth tracking
Start with a short list. Each metric should lead to an action, not just a chart.
| Metric | What it tells you | Typical data source |
|---|---|---|
| RTO rate (orders and value) | Overall health of delivery outcomes | Order and shipment reports |
| RTO by pincode and courier | Where to restrict serviceability or change partners | Logistics or courier reports |
| RTO by payment mode | Whether cash-on-delivery orders behave differently | Order reports |
| Cost per RTO order | The real financial hit, beyond lost sales | Settlement and logistics charges |
| Expected vs received units | Stock that was meant to return but did not | Warehouse receiving records |
| Open claim ageing | Recoveries at risk of missing a deadline | Recovery case log |
Keep customer return rate as a separate metric. The causes (size, quality, expectation mismatch) differ from RTO causes (address, reachability, refusal at the door).
Why RTO analytics must connect to settlements
RTO is an operations problem and a money problem. Depending on the marketplace, your agreement and who handles logistics, an RTO order may carry forward shipping, reverse shipping or other deductions, and the original payment may be reversed. These rules vary and change, so confirm the current position in your seller agreement, rate card and settlement report rather than relying on assumptions.
A tool that only reads order data can tell you the RTO rate. It cannot tell you whether the amount deducted for those RTO orders matched what you agreed. For that you need shipment-level data and settlement data in one place, so each RTO order can be traced to the charge applied against it.
This also helps with recovery. If a unit was marked returned but never reached your warehouse, you need the order ID, the dates and the amount ready before you raise the case.
Questions to ask before you pick a tool
- Which marketplaces and report formats are supported today? Ask the vendor to run a sample using your own files, not a demo dataset.
- Does it separate RTO, customer returns and cancellations? Blended numbers lead to wrong decisions.
- Can it compare charges with your agreed terms? Dashboards that only display what the marketplace deducted do not catch errors.
- Does it track recovery cases to closure? Look for status, owner, evidence and ageing.
- Can your finance team trace every number back to a source row? If not, audits will be painful.
- How is pricing structured, and what does setup involve? Ask what you need to provide and who maintains the mappings.
Spreadsheet or dedicated tool?
A spreadsheet is reasonable if you sell on one marketplace, ship modest volumes and have one person who understands the report layouts. It starts to fail when you add channels, when SKU-level analysis is needed, when report formats change, or when recovery follow-ups depend on someone remembering to check.
A practical trigger: if your team spends more time assembling the data than acting on it, or if disputes are being missed because nobody owns the follow-up, it is time to look at a dedicated tool.
Where MarketplaceMetrics fits
MarketplaceMetrics by Fundle reconciles marketplace sales and settlements for Indian brands, checks commissions and fees against agreed terms, and tracks returns and recovery cases. Myntra Excel reports are reviewed today; other marketplaces are in scope discussion, so confirm your channel mix during evaluation. Pricing is a tailored quote based on your setup.
Worked example
Illustrative example only. All figures are assumptions, not benchmarks or real rates.
A brand ships 2,000 orders in a month and 240 become RTO, so the RTO rate is 12%. Assume forward freight of ₹80 and reverse handling of ₹70 per RTO order (illustrative).
- Forward freight: 240 × ₹80 = ₹19,200
- Reverse handling: 240 × ₹70 = ₹16,800
- Total direct cost: ₹36,000, before counting lost sales
Now the stock check: warehouse receiving shows 40 of the 240 units never arrived. At an assumed landed cost of ₹600 each, that is ₹24,000 of stock to investigate. Separately, the settlement report shows a reverse charge on 15 orders where the agreed terms do not apply one. At ₹70 each, that is ₹1,050 to dispute. Without order-level linking, neither issue would be visible from the 12% figure alone.
Questions and answers
What is the difference between RTO and a customer return?
RTO means the shipment was never delivered and came back to you, usually due to refusal, an unreachable customer or an address problem. A customer return happens after successful delivery. They have different causes, costs and fixes, so track them separately.
Which RTO metrics matter most for a marketplace seller?
Start with RTO rate by orders and value, then cut it by pincode, courier, payment mode and SKU. Add cost per RTO order, units expected versus received, and the age of open claims. These point to specific actions you can take.
Can an RTO analytics tool reduce my RTO rate by itself?
No. It shows where RTO concentrates and what it costs. Reducing it still needs action, such as address verification, changing courier partners, restricting risky pincodes or fixing product listings. The tool makes those decisions better informed and measurable.
Do I need settlement data for RTO analysis?
Yes, if you want to know the financial impact. Order data gives the rate, but settlement data shows what was charged or reversed against each RTO order. Comparing it with your seller agreement helps you spot incorrect deductions and raise recovery cases.