A tool to track return and RTO losses across Amazon, Flipkart and Myntra should match each returned or RTO order with its settlement entries, shipping and commission charges, and warehouse receipt. It should flag mismatches against your agreed terms, such as returns never received or fees charged wrongly, and track each claim until money is recovered or written off.
What counts as a return or RTO loss
Returns and RTO (return to origin) look alike on a dashboard but behave differently in money terms. A customer return happens after delivery. An RTO happens when the shipment does not reach the customer and comes back to you. Terminology and report columns differ across Amazon, Flipkart and Myntra, so confirm definitions in each seller agreement and settlement report.
The loss usually sits in several places:
- Forward shipping or fulfilment fees that are not reversed on the returned order
- Reverse shipping or pickup fees
- Commission and other fees that are retained on returned orders, depending on your terms
- Returns marked as returned but never received in your warehouse
- Items received damaged, used or as the wrong product
- Deductions or penalties raised against the return
Not every item is recoverable. That depends on your agreement and the marketplace's current policy, so treat this list as things to check, not things to claim blindly.
Why one view across three marketplaces is hard
Each marketplace reports returns in its own format, on its own timeline. Order reports, return reports and settlement reports often live in separate files, and the same return can appear in all three with different dates and status labels.
Three problems come up repeatedly:
- Different identifiers. Order ID, return ID, shipment ID and AWB do not always line up across reports.
- Timing gaps. A return may be initiated in one month and adjusted in a settlement weeks later.
- Different claim windows and evidence rules. These are set by each marketplace. Check your seller agreement and seller portal for the current windows.
Without a common structure, finance sees net payouts while operations sees return counts, and nobody sees the loss per return.
What the tool should track
Use this as a minimum checklist when you compare options.
| Area | What to compare | Typical source |
|---|---|---|
| Return and RTO status | Marketplace status vs warehouse receipt | Return report, GRN or inward records |
| Settlement impact | Refund, reversal and deduction lines per order | Settlement report |
| Fees on returns | Shipping, commission and other fees vs agreed terms | Seller agreement, rate card |
| Product condition | Damaged, used or wrong item receipts | Warehouse QC notes, photos |
| Claims | Raised, pending, approved, rejected, recovered | Seller portal tickets |
The tool should also let you slice losses by marketplace, SKU, return reason and month. That is how you find out whether the problem is the product, the courier lane or the marketplace's fees.
How to evaluate a tool before you commit
Ask for a demo using your own files, not sample data.
- Which marketplaces and report formats are supported today? Get a clear answer on what is live and what is still planned.
- Can it check fees against your agreed terms? It should use your rate card, not generic assumptions.
- Does it match returns to settlements at order level? Summary totals are not enough for claims.
- Can it flag returns not received? This needs your warehouse data alongside marketplace data.
- Does it track claims through to recovery? A list of mismatches without status tracking leaves money on the table.
- Can finance export the output? You will need it for audits and discussions with account managers.
A recovery workflow that works
Whatever tool you use, the process is the same.
- Pull return, RTO and settlement reports for the same period.
- Match each returned order to its refund, fee and reversal lines.
- Match against warehouse receipts and QC notes.
- Flag exceptions: not received, damaged, wrong item, fee mismatch, missing reversal.
- Check each exception against your agreement and the marketplace's current claim policy and window.
- Raise claims with order-level evidence, then track each to closure.
- Review monthly which SKUs, reasons or lanes produce the most losses.
Start with the oldest exceptions, because claim windows may close on them first.
Spreadsheet or dedicated tool
Spreadsheets work when order volumes are low and you sell on one marketplace. They get fragile once you have several report formats, monthly settlements and open claims to chase.
MarketplaceMetrics by Fundle reconciles marketplace sales and settlements, checks commissions and fees against agreed terms, and tracks returns and recovery cases. Myntra Excel reports are reviewed today. Amazon, Flipkart and other marketplaces are in scope discussion, so share your report samples and ask what coverage fits your setup. Pricing is a tailored quote.
Worked example
Illustrative example only. These figures are made up to show the method, not real results or benchmarks. Suppose one month on one marketplace shows these exceptions after matching returns, settlements and warehouse receipts:
| Exception | Count | Basis (illustrative) | Potential claim |
|---|---|---|---|
| Marked returned, not received in warehouse | 30 | ₹650 landed cost each | ₹19,500 |
| Received damaged or wrong item | 12 | ₹700 landed cost each | ₹8,400 |
| Reverse shipping fee above agreed amount | 20 | ₹15 difference each | ₹300 |
| Total to review | ₹28,200 |
This ₹28,200 is only a list of items to check. What you can actually recover depends on your agreement, claim windows and the evidence you hold.
Questions and answers
What is the difference between a return and an RTO loss?
A return happens after the customer receives the product. An RTO happens when the shipment is not delivered and comes back to you. The cost components can differ, such as reverse fees or non-reversal of forward charges, so check each marketplace's report definitions and your agreement.
Can I recover all return and RTO losses from the marketplace?
No. Some losses are business costs under your agreement. Others, such as returns not received, damaged receipts or fees charged above agreed terms, may be claimable. Check your seller agreement and the marketplace's current claim policy and time windows.
Does MarketplaceMetrics support Amazon and Flipkart?
Myntra Excel reports are reviewed today. Other marketplaces, including Amazon and Flipkart, are in scope discussion. Share your sample reports and the marketplaces you sell on, and the team can tell you what coverage is possible for your setup.
What data do I need to start tracking return losses?
Collect order reports, return or RTO reports and settlement reports for the same period, plus your seller agreement or rate card and warehouse receipt records. Without warehouse data you can check fees and refunds, but you cannot reliably spot returns that never arrived.