The RTO deduction, line by line.
It looks like one charge. It is usually several stacked together — and at least one of them is frequently wrong. Here is how to read it and how to claim back the difference.
- An RTO deduction is what the marketplace subtracts to cover a return to origin.
- It is often several components stacked: reverse freight, sometimes forward freight, plus handling.
- Four things commonly go wrong: inflated weight, duplicate charge, unexpected forward leg, phantom return.
- Genuine freight stands. Inflated, duplicated and phantom charges are claimable.
- Robnu reconciles every RTO line against the shipment it should have been. Free while we figure out pricing.
Of all the deductions on a marketplace settlement, RTO is the one sellers examine least and pay most. It arrives as a subtraction rather than an invoice, which means nobody has to approve it — and in a busy month, nobody checks it either.
Of all the deductions on a marketplace settlement, the RTO line is the one sellers examine least and pay most. It arrives as a subtraction rather than an invoice, so nobody has to approve it — and in a busy month, nobody checks it either. This guide takes the number apart so you can see what is inside it and reclaim the part you should never have paid.
What is inside the number
A single RTO deduction typically bundles several things: the reverse freight to bring the parcel home, possibly the forward freight you already bore, and sometimes handling or lane surcharges for remote destinations. Because it appears as one figure, the components are invisible — and so are the errors inside them. The first job is simply to understand that the line is composite, not atomic, because you cannot audit what you assume is a single correct charge.
The RTO-versus-return question comes first
Before auditing the components, establish what kind of event this was. On Meesho, a pure never-delivered RTO often carries no reverse-shipping fee, while a customer return after delivery does — commonly ₹140 to ₹170 by weight. So a reverse charge on a pure RTO is itself the anomaly, before you even look at the weight. See RTO vs customer return to classify the event correctly, because the whole audit depends on it.
The four errors worth reclaiming
Four errors recur, and each is checkable. An inflated weight basis — the charge computed on a weight above what you dispatched — is the most common, and a classic weight discrepancy. A duplicate charge deducts the same shipment twice, often across two cycles so it hides from a totals check. An unexpected forward leg appears when forward shipping is absorbed inconsistently with comparable orders. And a phantom return charges you for a parcel that never arrived, losing you stock, sale and freight at once.
How to audit it in practice
Reconcile per order, not per total. A total within your expected range can hide an overcharge on one order offset by a missing deduction on another — both wrong, neither visible. For each RTO line, retrieve your dispatch weight, confirm the shipment appears once, and check the parcel actually returned against your inward record. Where the numbers do not reconcile, raise the claim inside the window with the evidence attached. Our reconciliation method lays out the full per-order routine.
The reason this is left undone is purely time. Verifying RTO deductions by hand means opening the settlement, matching each line to an order, retrieving the weight and confirming the return — five minutes per order, a full job across a month. The individual charges are small enough that chasing them by hand rarely feels worth it, which is exactly how the aggregate quietly grows. Automating the check reverses that economics: the charge stays small, the effort goes to zero, and the recovered rupees add up.
Reducing the charges at source
Alongside recovery, reduce the volume. A lower RTO rate through prepaid conversion and address quality means fewer charges to audit in the first place, and tighter packaging lowers the weight basis on the reverse charges that do occur. Prevention and recovery are two halves of the same job; working only one leaves money on the table.
What one month of unchecked deductions looks like
Consider a seller doing twenty orders a day with a fifteen-percent return-and-RTO rate. That is roughly ninety returns a month, each carrying a deduction. If even a small fraction of those deductions are wrong — a reverse charge on a pure RTO, a weight billed higher than the parcel was, an occasional duplicate — the recoverable amount across ninety events is not trivial. Yet almost none of it gets reclaimed, because no single charge is large enough to justify the manual effort of chasing it, and the claim windows close before a monthly review ever gets around to them.
This is the quiet economics of settlement leakage. The charges are individually small and collectively significant, they arrive as deductions that need no approval, and they expire faster than a busy seller can review them. Every one of those three factors pushes toward the same outcome — money lost by default. Reversing it does not require heroics; it requires a reconciliation that runs every cycle whether or not anyone remembers to do it, which is precisely the case for automating the check rather than relying on discipline that inevitably lapses under volume.
Sources & further reading
Charge figures reflect Meesho’s published policy as summarised by independent logistics sources; rates vary by category and change. Confirm against your settlement and the official documentation:
What is inside the number
A single RTO deduction typically bundles the reverse freight to bring the parcel home, possibly the forward freight you already bore, and sometimes handling or lane surcharges for remote destinations. Because it appears as one figure, the components are invisible — and so are the errors inside them.
The single most useful habit is recording your actual dispatch weight. Almost every disputable RTO charge comes down to a mismatch between what your parcel weighed and what you were billed for, and without your own record there is nothing to compare against.
The four recoverable errors
Each is checkable against records you already have, and each has a claim window that closes fast.
Inflated weight basis
The charge was calculated on a weight higher than your parcel actually was. Compare against your dispatch record — this is the classic weight discrepancy case.
Duplicate charge
The same shipment deducted twice, sometimes across two settlement periods. Invisible unless you reconcile per-order rather than per-total.
Unexpected forward leg
Forward shipping absorbed into the RTO charge when comparable orders were treated differently. Inconsistency across similar cases is the flag.
Phantom return
Charged for a return that never arrived. You lose the sale, the stock and the freight. Check every RTO Delivered against your inward record.
Checking what nobody has time to check
Verifying RTO deductions by hand means opening a settlement report, matching each RTO line to an order, retrieving the dispatch weight, and confirming the parcel actually came back. For one order that is five minutes. For a month of orders it is a job.
Robnu is an agentic OMS. It reads your settlement automatically, matches every RTO deduction against the shipment’s real weight and lane, catches duplicates, and flags returns you were billed for but never received. Where the numbers do not reconcile it prepares the claim and files it — with a rare approval click while fully-autonomous filing rolls out.
You sell. Robnu runs the rest — and makes sure every rupee is paid correctly.
RTO deductions, answered
It is the amount a marketplace subtracts from your settlement to cover the cost of a return to origin. At minimum it covers reverse freight — bringing the undelivered parcel back to you. Depending on the marketplace and the order type it can also absorb the forward shipping you were charged, plus handling components. It appears as a deduction rather than a bill, which is why it is easy to miss.
Usually one of four reasons: the charge was calculated on a higher weight than your parcel actually was, the forward leg was included as well as the reverse, a handling or ODA component was added for a remote lane, or the same shipment was charged twice. The first and last of those are straightforwardly claimable if you catch them in the window.
It depends on the marketplace's policy for that order type, and it is one of the least-understood parts of the deduction. What matters practically is consistency: if comparable RTOs are treated differently across your settlements, that inconsistency is worth querying. Erratic treatment of the same scenario is often an error rather than a policy.
Compare three numbers: the weight you recorded when dispatching, the weight the charge was calculated on, and the lane the parcel travelled. If the billed weight exceeds your dispatch weight, you have a weight discrepancy case. Also check the shipment appears only once — duplicate deductions for a single RTO are more common than sellers assume.
The genuine freight for a real return generally stands. What is recoverable is the incorrect portion: an inflated weight basis, a duplicate charge, or a deduction for a parcel that never physically came back to you. Each has a defined claim window, and missing it forfeits the money regardless of the strength of your case.
It scales directly with your RTO rate and your average order value, so there is no single figure. The useful way to think about it is proportionally: on a category with a high return rate, RTO deductions frequently exceed marketplace commission as a line item. Sellers are usually surprised by this when they total it for the first time.
It varies by marketplace and report format. Some show a discrete RTO line, others fold reverse logistics into a broader shipping or adjustment column. Where it is bundled, reconciling per-order rather than per-total is the only reliable way to see what you actually paid on each return.
Two independent levers. Reduce the RTO rate itself through address quality, prepaid conversion and accurate listings. Then verify every RTO charge that does occur, because a meaningful share are wrong. Most sellers work only on the first lever and leave the second entirely unexamined.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
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.
Amazon India settlement reports explained
Referral fees, closing fees, shipping, refund reversals — reconcile order by order, spot the wrong-rate and duplicate errors, and find the refund reversals worth a SAFE-T claim.
Flipkart Settlement Reports Explained: Read Yours Line by Line
Every Flipkart settlement is order value minus a stack of deductions. Here is what each line means, which fees are wrong often enough to check, and how to reconcile a payout to the rupee.
Decode your AJIO settlement statement line by line
Reconcile order by order, never by totals. What each section covers, the discrepancies that hide inside a plausible-looking total, and which mismatches to raise.
Meesho RTO charges: exactly what you are billed
There is no flat rate — weight and lane drive the number. What determines your RTO charge, why similar orders differ, and the three checks that catch errors.
Marketplace deductions glossary: every settlement term decoded
Every deduction on an AJIO or Meesho settlement in plain English — commission, GST on fees, RTO, weight adjustments, TCS, TDS, negative balance — with the disputable lines flagged.
“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.
The 30-minute monthly shipping-deductions audit
Pull the settlement lines, bucket every freight and RTO charge, compare against expected slabs, flag wrong slabs and phantom reverse charges, file disputes, log recoveries.