RTO shipping charges: who pays what when the parcel comes back?
An RTO order is the only order that bills you twice for freight and pays you nothing. This guide breaks down the forward leg and the reverse leg, shows where each one lands on your AJIO and Meesho settlements, and walks through the situations where an RTO charge is not just painful but disputable.
- An RTO order carries two freight legs — forward and reverse — and in most cases both are charged to you, on an order that earned nothing. The two legs usually land in different settlement cycles, which is why the full cost hides so well.
- Not every RTO charge is legitimate. Charged but never shipped back, charged RTO and delivered on the same sub-order, reverse leg billed at a fatter weight slab, or freight billed for a return that never physically arrived — each one is disputable with tracking evidence.
- Run an expected-return log: every RTO the panel records, with AWB and an arrival window. A parcel that never turns up is not bad luck, it is a claim — and the log is the evidence trail that wins it.
One order, two freight bills, zero revenue
When an order delivers, the freight story is simple: one forward leg, priced into your unit economics, recovered by the sale. When an order RTOs, the same parcel travels the route twice. The forward leg is already spent by the time delivery fails, and the reverse leg — bringing the parcel back to you — is generally billed to the seller too, depending on your marketplace's current policy and the recorded RTO reason. Two freight charges now sit against an order that produced no sale, no margin, and a parcel that needs inspection before it can be sold again.
On the settlement sheet this rarely looks like one clean “RTO charge.” The forward leg hides inside the normal shipping deduction for the order. The reverse leg appears as a separate return-shipping entry — and because the reverse journey finishes weeks after dispatch, it often lands in a later payout cycle than the forward charge. Sellers who read payouts file by file see two unremarkable deductions. Sellers who match both legs to the same sub-order see what one failed delivery actually cost.
Seven checks that find the disputable RTO charges
Work through these against your settlement files and tracking records. Most RTO freight is legitimate; the point of the audit is to find the entries that are not.
- 01
Find both legs of every RTO
For each sub-order marked RTO, locate the forward freight in the original settlement and the reverse freight wherever it landed — often a later cycle. AJIO and Meesho name these lines differently, so match by sub-order number, not by label.
- 02
Compare the reverse slab to the forward slab
Same parcel, same weight, same route in reverse. If the forward leg billed one weight slab and the reverse leg billed a higher one, something was re-measured or defaulted on the return journey — that mismatch is a dispute with its evidence built in.
- 03
Confirm the parcel actually shipped back
Sellers report cases where the panel records an RTO and bills reverse freight, but the tracking history shows no reverse movement at all. Freight for a journey that never happened is disputable — attach the tracking record showing the last scan.
- 04
Catch double-status contradictions
An order cannot be both delivered and returned. If a sub-order carries a delivery record and an RTO shipping charge, one of them is wrong — and the settlement should not hold both. Screenshot both statuses and raise the contradiction as a single ticket.
- 05
Match expected returns to arrivals
Every RTO on the panel goes into an expected-return log: sub-order, AWB, date recorded, arrival window. Charged for the return but the stock never reached you means you paid freight and lost inventory — a double loss that becomes a claim only if the log exists.
- 06
Check the RTO reason recorded
The recorded reason — customer refused, address issue, undeliverable — can affect how charges apply under the marketplace's current policy. A reason that does not match reality (a buyer who says no attempt was made, for instance) is worth contesting alongside the charge.
- 07
Dispute inside the window
Marketplaces accept settlement disputes for a limited period after payout, and the window differs by platform and changes over time — check the current policy on your panel. An airtight case raised late is worth nothing; audit each payout as it lands.
On thin margins, RTO freight is a multiplier, not a fee
Run the illustrative numbers on a ₹500 order that clears ₹120 after product cost, commission, and forward freight. A single RTO takes the ₹120 that never materialised, the forward freight already spent, a reverse charge of similar size, and the labour of receiving, inspecting, and repacking a parcel that may come back shopworn. Stack it up and one failed delivery can absorb the profit of three or four delivered orders. A product with a high RTO rate is not a slightly less profitable product — it can be a loss-making one that looks fine on the sales report.
The missing-RTO-parcel makes the math worse. If the return is charged but never arrives, you also lose the stock — cost price gone on top of two freight legs. The evidence trail that recovers this is boring and mechanical: the expected-return log, a ticket raised when the arrival window lapses, follow-ups on a schedule, and the tracking history attached to each one. Sellers who keep that trail recover missing parcels or reimbursements; sellers who rely on memory pay for returns they never received.
Robnu matches every RTO charge to what actually happened
Auditing RTO freight by hand means matching sub-orders across settlement files from different cycles, cross-checking tracking histories, and keeping a return log that never skips a day. Robnu does this as a pipeline: every settlement line is reconciled against the order's real journey on AJIO and Meesho, forward and reverse legs are paired to the same sub-order automatically, and the exceptions — freight without reverse movement, RTO plus delivered, a fatter slab on the return leg, a return that never arrived — surface as flagged items with the evidence already attached.
When a flagged charge becomes a claim, Robnu prepares and files it. Fully autonomous filing is rolling out — the rare claim still asks you for one approval click, and the rest run end to end while you pack orders.
RTO shipping charges, answered
In most cases, you do — on both legs. The forward freight was spent getting the parcel to the buyer, and when delivery fails the reverse freight for bringing it back is typically charged to the seller as well, depending on the marketplace, your rate card, and the RTO reason. Policies differ between AJIO and Meesho and change over time, so check the current shipping-charge policy on your seller panel rather than assuming — but plan your unit economics as if a full RTO costs you two freight legs and earns you nothing.
Rarely as one obvious line called RTO. The forward leg usually sits inside the regular shipping or logistics deduction for the order, and the reverse leg appears as a separate return-shipping or RTO-shipping entry — sometimes in a different settlement cycle from the forward charge, because the return completes weeks after dispatch. That timing gap is why RTO freight is so easy to miss: you have to match both legs back to the same sub-order across two payout files to see the full cost of one failed delivery.
Three situations show up repeatedly in seller reports. First, the order never actually shipped back — an RTO was recorded but tracking shows no reverse movement. Second, you were charged both an RTO fee and delivery on the same sub-order, which is a status contradiction. Third, the reverse leg was billed at a higher weight slab than the forward leg for the same parcel. In each case the settlement entry contradicts the tracking record, and that contradiction is your dispute. Raise it inside the marketplace's dispute window — check the current window on your panel.
This is the missing-RTO-parcel problem, and it is a double loss: you paid reverse freight for a return, and the stock never reached you — so the inventory is gone too. The defence is an expected-return log: every RTO the panel records goes into a list with its sub-order number, AWB, and expected arrival window. Anything that does not arrive within a reasonable period becomes a ticket with the tracking history attached, and a follow-up on a schedule until it is resolved as a refund, a reimbursement, or a delivered parcel.
Take an illustrative ₹500 order with roughly ₹120 of margin after product cost, commission, and forward freight. If it RTOs, the margin never materialises, the forward freight is already spent, reverse freight adds a second charge of a similar size, and the product comes back needing inspection and repacking — if it comes back saleable at all. One RTO can quietly consume the profit of several delivered orders. That multiplier, not the individual charge, is why RTO freight deserves a line in your per-product costing.
Robnu reconciles every settlement line against what actually happened to the order. It matches forward and reverse freight to the same sub-order across payout cycles, flags RTO charges where tracking shows no reverse movement, catches double-status contradictions like RTO plus delivered, and keeps the expected-return list so a parcel that never arrives becomes a claim instead of a silent write-off. When a claim needs filing, Robnu prepares and files it — fully autonomous filing is rolling out, and the rare claim still asks you for one approval click.
Where this comes from
- AJIO and Meesho seller-panel documentation on shipping charges, returns, and settlement statements (policies vary by seller agreement — verify on your panel).
- Recurring seller reports of double-billed freight, RTO-without-reverse-movement, and missing RTO parcels: public seller community threads (Reddit r/IndiaBusiness, seller Facebook and Telegram groups), 2024–2026.
- Standard courier billing conventions for forward and reverse legs and weight-slab rating, including the common /5000 volumetric divisor.