Ask a seller what an AJIO return costs and you'll usually hear the reverse-shipping number. Ask their settlement statement and you get a different answer: a reversed sale on one line, a logistics charge on another, a handling deduction two pages later, and a repack cost that never appears anywhere because it happened at your own table. AJIO return charges are not a fee — they are a stack, and the stack is why returns hurt more than the rate card suggests.
One thing before the numbers: Robnu is independent software built for AJIO sellers — not affiliated with or endorsed by AJIO — and fee specifics vary by seller agreement, category, and policy revision. Every rupee figure in this post is illustrative. The structure is what you should take away; your own rate card on the seller portal is the source of truth for the amounts.
The cost stack of one returned order
Take a ₹599 kurta, ordered, delivered, and returned by the buyer eight days later. Here is what that single return typically sets in motion:
- The revenue reverses. The ₹599 you were counting in this cycle's payout disappears. Commission treatment on reversed sales depends on your terms — but the headline number is gone either way.
- The forward logistics already happened. The parcel travelled to the buyer once, illustratively ₹70–₹90 depending on weight and zone, and that journey doesn't un-happen when the item comes back.
- The reverse leg gets charged. A pickup from the buyer and a trip back — illustratively ₹50–₹70 — with the cost treatment depending on the return reason code. Seller-fault reasons sit harder on your side than customer-preference ones.
- Handling and processing deductions where applicable — small per parcel, scattered in the statement, and easy to never notice individually.
- Your own table costs. Inspection, repack, fresh polybag, restock — ₹25–₹40 of labour and material that no statement will ever show you, plus 7–15 days of the product's selling season spent in transit.
The reason code attached to each return deserves more attention than it gets, because it often decides who carries the reverse cost. A return classed as seller fault — wrong item, defect, description mismatch — generally sits harder on your side of the table than a customer-preference return. Two practical consequences follow. First, read the codes on your returns instead of skimming them: a misclassified seller-fault code is itself worth disputing when your dispatch evidence contradicts it. Second, the codes are free product feedback — a SKU collecting “size issue” codes is asking for a better size chart, and the chart is cheaper than the returns.
The forward-plus-reverse math, done honestly
Here is the arithmetic most sellers feel but never write down. Suppose your ₹599 item carries roughly ₹150 of contribution margin after product cost, commission, and forward shipping on a successful sale. A return that costs ₹200+ in stacked fees and labour doesn't just erase one sale's margin — it erases that sale's margin and reaches into the next order's pocket. At those illustrative numbers, one return consumes the margin of one and a half delivered orders. A 25% return rate means every fourth order is quietly taxing the other three.
This is why two stores with identical sales and identical “per-order profit” on paper can have wildly different bank balances at month end. The one with the higher return rate is paying a tax that appears on no single report. The math also explains why return charges hurt low-AOV sellers disproportionately: the fee stack is roughly fixed per parcel, but the margin it eats shrinks with the price point.
The projection chart above is worth running with your own numbers because the result usually reframes priorities. A seller spending evenings shaving ₹5 off packaging cost while carrying a 30% return rate is optimising the wrong line by an order of magnitude: moving the return rate three points is worth more than every packaging negotiation combined. The leak is invisible precisely because it is distributed — no single return feels expensive, the way no single drip from a tap feels like a water bill.
Recoverable vs accept-loss: the only split that matters
Once the stack is visible, the next question is which slices can come back. The honest answer divides cleanly.
Recoverable, with evidence and a live window: a wrong item in the return flyer, an item damaged in courier custody, a tampered or empty parcel — these are claims, and they live or die on the unboxing evidence you create when the return is opened. Add fee errors to this column: logistics charged twice, a weight slab misapplied, a deduction that doesn't match any order event. Fee errors are rarer than fraud but pure profit to catch, because the dispute is arithmetic, not argument. Both kinds only surface if you reconcile per order — which is precisely what payment reconciliation exists to do.
Accept-loss, to be priced in: the reverse pickup on a genuine customer-preference return, the forward leg that already happened, your repack labour, the polybag. No claim exists for these, and pretending otherwise wastes filing time. They belong in your product pricing as a per-unit returns provision — if your category runs a 25% return rate, the surviving orders have to carry it.
Tracing AJIO return charges through a real statement
Here is what the join looks like in practice, with order AJ-77310 as the illustrative specimen. The order ships in week one and appears in that cycle's settlement as a credit: sale value minus commission, logistics, and the tax-related lines. In week three the buyer returns it. The next statement carries the reversal — but not as one tidy negative mirroring the original credit. The sale amount reverses on one line; the commission treatment adjusts on another (often as a credit back to you, since the commission was charged on a sale that no longer exists); a reverse-logistics charge appears somewhere else entirely; and a handling line may trail in the cycle after that.
Four-plus lines, two or three statements, one return. Multiply by thirty returns a month and you see why almost no seller can answer “what did returns cost you last month?” with a number. The information exists; it has simply been shredded across documents that were never designed to be read together. Reassembling it per order is tedious, mechanical, and exactly the kind of work software should be doing — including the GST side, where commission reversals and credit notes need to flow into your input-credit position rather than silently distorting it.
How to audit your own return charges this month
You can do the manual version of this once, and you should — partly for the money, mostly for the education. Pull last month's settlement files and your order list. Mark every returned order. For each one, collect every line the settlement attaches to it: the reversal, each logistics charge, each handling deduction. Add your own ₹25–₹40 of table cost. Total it. Divide by your delivered orders to get your real per-order returns tax.
Then look for the outliers: returns with two logistics charges, deductions with no matching order event, reversals where the return never physically arrived. Those outliers are your dispute list, and the window discipline from our returns playbook applies to them just as it does to fraud claims.
Expect the first audit to take an evening and to pay for itself. Sellers doing this for the first time reliably find two things: at least one systematic surprise (a fee they didn't know existed, a SKU with a 40% return rate hiding inside a healthy average) and a short list of genuine errors worth disputing. They also find the opposite — months where everything reconciles cleanly — which has its own value, because knowing the leak is structural rather than erroneous tells you to fix it with pricing and listings instead of disputes.
Where Robnu fits
Robnu is the agentic OMS for AJIO and Meesho sellers. For return charges specifically, it does the join you would otherwise do in spreadsheets at midnight: every return tied to its order, every settlement line tied to the return, your own cost assumptions layered on top — so profit tracking shows per-order and per-SKU margin with returns included, and the recoverable outliers flow into claims with evidence attached. The audit this post describes becomes a dashboard you glance at, not a weekend you lose.
The same join powers the upstream fixes: because every return carries its reason code, SKU, and pin code into the dashboard, the “which three SKUs are bleeding” question — the one that actually changes restocking decisions — is answered in one view instead of one weekend. Returns stop being weather and start being a budget line you manage.
It is free for everyone right now — every feature, every order, no card, no timer — and when paid pricing eventually launches, sellers under 25 orders/day stay free forever. Run the manual audit once this week; let software run it every day after that.