RTO deductions: why marketplaces charge you — and how to get it back.
Every RTO costs you freight twice. What most sellers don't know is that a meaningful share of those charges are wrong — wrong weight, wrong lane rate, or billed for a parcel that never came back. This guide explains the deduction types, which are claimable, and what evidence you need to win.
- RTO deductions appear on every marketplace settlement when a shipment returns — forward freight is already lost, and the marketplace deducts reverse freight and handling on top.
- 8–15% of RTO deduction lines have errors: wrong weight tier, wrong lane rate, or charged for a parcel that was never returned. All are claimable within the claim window.
- Robnu detects wrong charges automatically, builds the evidence bundle, and files the claim — you see recovered rupees in the next settlement without manual effort.
The RTO line on your Meesho settlement is rarely a single charge. It is often several components stacked together, and at least one of them is frequently wrong. This guide reads the RTO deduction apart, separates the charges you genuinely owe from the ones you can claim back, and shows you how to audit them before the claim window closes.
What an RTO deduction is
An RTO deduction is the amount a marketplace subtracts from your settlement to cover a return to origin. It appears as a subtraction rather than an invoice, which is precisely why it is easy to miss — nobody has to approve a deduction; it simply reduces what arrives. At minimum it can cover reverse logistics, and depending on the marketplace and order type it may fold in other components. Understanding what is inside the number is the first step to knowing whether it is correct.
The crucial RTO-versus-return distinction
Here precision saves money. On Meesho, a pure RTO — where the parcel was never delivered — often does not attract a separate reverse-shipping fee to the seller. A customer return after delivery, by contrast, is charged a return-shipping fee based on shipment weight, commonly in the ₹140–₹170 range including taxes. That means a reverse charge appearing against a genuine, never-delivered RTO is exactly the kind of line worth questioning. Always check whether the order was a true RTO or a customer return before accepting the deduction — see RTO vs customer return for the full comparison.
The four recoverable errors
Beyond the RTO-versus-return question, four specific errors recur and each is checkable against records you already have. The first is an inflated weight basis — the charge computed on a weight higher than your parcel actually was, which is the classic weight discrepancy. The second is a duplicate charge, where the same shipment is deducted twice, sometimes split across two settlement periods so it is invisible unless you reconcile per order.
The third is an unexpected forward leg, where forward shipping is absorbed into the RTO charge inconsistently with how comparable orders were treated. The fourth, and worst, is a phantom return — being charged for a parcel that never physically came back, so you lose the stock, the sale and the freight together. Every one of these is claimable inside a window, and every one is missed by a seller who only checks totals. Our RTO order deduction guide walks through the anatomy line by line.
How to audit an RTO deduction
The method is simple and the discipline is everything. For each RTO charge, compare three numbers: the weight you recorded at dispatch, the weight the charge was calculated on, and the lane the parcel travelled. If the billed weight exceeds your dispatch weight, you have a discrepancy. Confirm the shipment appears only once. And check the parcel actually came back by matching against your inward record — a “delivered” RTO that never arrived is the costliest error of all. This is the reconciliation half of the job, and it is where our payment reconciliation earns its place.
The reason most sellers never do this is time, not ability. Opening a settlement, matching each RTO line to an order, retrieving the dispatch weight and confirming the return is five minutes for one order and an entire evening for a month of them. That is exactly the kind of precise, repetitive work that software does perfectly and tired humans do badly — which is the whole case for automating it.
Sources & further reading
Charge figures reflect Meesho’s published policy as summarised by independent logistics sources; rates vary by category and change over time. Confirm against your own settlement and the official documentation:
What an RTO deduction looks like on your settlement
When a shipment cannot be delivered and is returned, the marketplace recovers its reverse-logistics cost from your payout. The deduction shows as a negative line item on your settlement statement — typically labeled "RTO charges", "return freight", "reverse logistics fee", or similar.
The amount is calculated by the courier using the parcel's weight (at their scan, not your dispatch weight) and the lane (local, regional, national). Both figures are frequently wrong — either intentionally or because of scan errors — and that is the recoverable part.
The four types of RTO deduction — and which are claimable
Not all RTO deductions are wrong, but not all are correct either. Knowing the difference is what separates sellers who silently absorb losses from sellers who claim them back.
Reverse freight
Claimable: PartiallyThe courier charges to ship the parcel back to you. This is legitimate. What is claimable is when the weight used to calculate freight is higher than your actual dispatch weight — scan errors are common.
RTO handling charge
Claimable: PartiallyA fixed processing fee layered on top of reverse freight. Usually legitimate, but sometimes applied twice on the same RTO or at the wrong rate tier.
Weight discrepancy charge
Claimable: YesWhen the courier scans a higher weight than you dispatched, the extra weight is charged at the applicable rate. This is claimable with evidence — your dispatch slip + scan weight from the tracking log.
Non-returned RTO charge
Claimable: Yes — fullyCharged for an RTO but the package was never actually returned to your warehouse. This is rare but real. Claimable with delivery-attempt proof and warehouse receipt logs.
Where RTO charges go wrong — and why it's hard to catch manually
The core problem is volume. If you ship 20 orders a day with a 15% RTO rate, that's 3 RTO deductions every day — 90 a month. Checking each one against the correct weight and lane manually is genuinely not feasible.
The courier's scan weight is recorded at their facility, often with equipment that adds 50–100g. Over a large volume, even a consistent 50g over-scan turns into thousands of rupees in overcharges per year that most sellers never recover because they never see the individual discrepancies.
Wrong lane rates are even harder to catch — you need to know the origin–destination pair for every RTO and what rate should have applied. Without a system doing this automatically, it's an invisible leak.
How to claim a wrong RTO deduction — manually
If you want to do this yourself, here is what the process looks like. It is how Robnu does it too — the difference is Robnu does it for every deduction, automatically.
- 01
Download your settlement
Export the settlement CSV from the marketplace. Filter for 'RTO', 'reverse freight', or 'return' line items.
- 02
Compare against dispatch weight
For each RTO deduction, look up the original order's dispatch slip. Check the weight the courier used vs what you dispatched.
- 03
Build the evidence bundle
Screenshot the settlement line + attach the dispatch slip + add courier tracking events showing the RTO. Structure to the marketplace's claim format.
- 04
File within the claim window
Submit through the marketplace's seller portal (AJIO: Seller Hub > Claims; Meesho: Supplier Panel > Disputes). Track the status.
Robnu detects, prepares, and files — you just see the recovery
Robnu reads your settlement statement the moment it lands, matches every RTO deduction against the correct weight tier and lane, and flags discrepancies automatically. No spreadsheet comparison. No manual export.
For every flagged deduction, Robnu builds the evidence bundle in the format the marketplace expects — settlement screenshot, dispatch weight reference, tracking event log. Then it files the claim. You see the recovered rupees land in your next settlement.
The window is tracked from the moment the deduction appears. You will never miss a deadline because you were busy running orders.
RTO deductions, answered
An RTO deduction is a charge a marketplace (AJIO, Meesho, etc.) deducts from your payout to recover the reverse freight and handling cost when a shipment cannot be delivered and is returned to you. It appears as a line item on your settlement statement, usually labeled 'RTO charges', 'reverse logistics', or 'return freight'.
Yes — but only in specific cases. You can dispute if the weight used to calculate freight was higher than the actual shipment weight, if you were charged for an RTO but the package was never returned to you, if the lane rate applied was wrong (e.g. metro rate applied to a local delivery), or if the same RTO was deducted twice. You cannot dispute the deduction itself just because you disagree with the policy.
Claim windows vary. On Meesho, most deduction disputes must be raised within 30 days of the settlement date. AJIO allows a similar window but applies different rules by deduction type. Missing the window almost always means the claim is rejected — even if you are right. Robnu tracks windows automatically and raises claims before they expire.
Typically: the original dispatch slip (showing actual weight), a screenshot of the settlement deduction, and the RTO tracking event log. For weight discrepancy claims, a photo of the sealed parcel on a scale at the time of pickup is the strongest evidence — Robnu's video-proof capture does this automatically for sellers who use it.
Based on typical seller data we see through Robnu, 8–15% of RTO deduction line items have at least one error — wrong weight tier, wrong lane, or a charge for a non-returned parcel. The rupee value is small per incident but adds up fast at any meaningful order volume.
Robnu detects wrong RTO charges automatically and prepares the claim with the required evidence. Filing is largely autonomous — a rare approval click is needed in some cases while fully-autonomous claim filing rolls out. You see the recovered amount land in your next settlement.
Rejection usually means insufficient evidence or a missed window. Robnu structures claims to match each marketplace's evidence format, which reduces rejection rates significantly compared to manually filed claims. If a claim is rejected, Robnu flags it so you can escalate through the seller support channel with the full evidence bundle.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
RTO in Meesho, every status decoded
What RTO Initiated, In Transit, RTO Locked and RTO Delivered mean for a Meesho seller — the charges behind each, and how to claim the wrong ones back.
Meesho seller charges & deductions: every line on your payout
Commission, shipping, SLA penalties, cancellation charges, return and RTO reversals, TCS and TDS — every charge on a Meesho payout, what each means, and which ones you can claim back.
“RTO Initiated” meaning: what just happened to your order
Delivery failed and your parcel is heading back. What triggered it, what the double freight hit costs, and which part of the bill you can claim back.
RTO OFD meaning: out for delivery, then back to you
"RTO OFD" means your returned parcel is out for delivery back to your own pickup address. What the status means, the timeline to expect, and what to watch so you are not charged for a parcel that never arrives.
AJIO return disputes: process, timelines and evidence
When a fashion return comes back wrong, used or short, you have a claim — but only inside a window that runs from receipt and only with evidence captured on arrival.
RTO vs customer return: different problems, different fixes
One is a delivery problem, the other a listing problem. They need opposite remedies and different claim routes — yet most sellers track them as a single number.
RTO order deduction: the line item that eats your margin
One number, several charges stacked inside it. How to read the RTO line on your settlement and find the inflated, duplicated or phantom portion you can claim back.
RTO vs RTV vs DTO: three returns, three different losses
They look identical on a dashboard and cost completely different amounts. One question separates them, and each needs a different claim route and different evidence.