RTO, RTV, DTO — three losses, one label.
They look the same on a dashboard and cost you entirely different amounts. Tracking them as one number is why most sellers cannot say which part of their returns is actually bleeding.
- RTO = return to origin. Delivery failed; the customer never took possession.
- RTV = return to vendor. An inventory movement back to a supplier, not a consumer return.
- DTO / customer return = the buyer received the product, then sent it back.
- The claim routes differ: RTO claims are about freight accuracy, customer returns about goods condition.
- Robnu separates them automatically so you can see which one is costing you. Free while we figure out pricing.
Search interest in the difference between these terms is high for a simple reason: the words are used loosely across panels and courier systems, and getting them wrong sends your claim down the wrong route. This guide draws the lines clearly.
RTO, RTV and DTO look interchangeable on a dashboard and cost you completely different amounts. Tracking them as one number is why most sellers cannot say which part of their returns is actually bleeding. This guide draws the lines clearly, because each type needs a different claim route and different evidence.
The three types, defined
RTO means return to origin — a parcel that could not be delivered to the customer and is sent back to you. Delivery never completed. RTV means return to vendor — goods sent back to a supplier or vendor, typically in a stock or wholesale context rather than a consumer delivery one. And DTO is generally used for a customer-initiated return flow, where a buyer who has received the product initiates sending it back. The key variable across all three is possession: did the customer ever receive the goods, and did anyone open the parcel.
Why the distinction is worth money
The charges and claim rights differ sharply. An RTO is freight-heavy and rarely involves product- condition disputes, since the customer never opened it — and on Meesho a pure RTO may carry no reverse-shipping fee at all. A customer-initiated return frequently does involve condition disputes — wrong item, used item, empty box — which are claimable in ways an RTO is not, and which do attract a return fee. RTV sits outside both, as an inventory and procurement matter. Lumping them together means you never see which category is actually costing you, and you end up fixing the wrong thing. See RTO vs customer return for the delivery- versus-listing split.
How to track them apart
Tag every return with whether delivery completed before the return began, and whether the parcel was opened. Those two facts split RTO from customer returns cleanly and let you compute the loss rates independently. Most sellers keep one combined returns number, which is precisely why the underlying cause stays invisible. A high RTO rate points to address quality and cash-on-delivery exposure; a high customer-return rate points to sizing and description accuracy. The remedies share almost nothing, which is why the classification is not bureaucracy — it is what makes sure your effort lands on the lever that will actually move your number. Our return fraud guide covers the dishonest cases within customer returns.
The bigger picture for your catalogue
Whatever the specific status, charge or process, the underlying reality of selling on Indian marketplaces is the same. The platforms are built to move enormous volume, their interfaces speak in operational shorthand rather than plain language, and the money at stake hides in charges that arrive as silent settlement deductions requiring no approval from you. The sellers who stay profitable are not the ones who avoid every problem — that is impossible at scale — but the ones who understand what each event means, know which charges are genuinely owed, and reconcile every settlement so the wrong ones are caught and reclaimed while the claim window is still open.
That discipline is simple to describe and hard to sustain by hand, because it is precise, repetitive work layered on top of actually running the business. It is exactly the kind of task that a two-person team does inconsistently under volume and that software does reliably every cycle. Robnu exists to close that gap: it runs the daily operations these guides describe, reconciles the charges they represent against what you actually shipped and sold, and files the claims you are entitled to — so the vocabulary becomes something handled rather than something you have to master and police yourself. You sell; Robnu runs the rest, and makes sure every rupee is paid correctly.
Sources & further reading
Charges, policies and processes vary by marketplace and category and change over time. The details here are drawn from official documentation and reputable industry sources; always confirm current specifics against your own seller panel and settlement reports:
One question separates them
Did the customer ever take possession? That single question does most of the classification work. If delivery never completed, you are looking at an RTO. If the buyer received it and then sent it back, you are looking at a customer return. RTV sits outside both, describing stock going back to a supplier.
The reason to be strict about this is evidence. In an RTO the parcel was never opened by anyone, so condition disputes rarely arise. In a customer return the parcel has been opened, and what comes back may not be what went out — which opens an entirely different set of claims.
What each one means for you
Same outcome on the surface — stock coming back. Completely different underneath.
RTO
Customer never received it. Cost is freight in both directions plus lost margin. Claims centre on charge accuracy — weight, duplicates, parcels never returned. Fix the cause via addresses and prepaid conversion.
RTV
Goods going back to a vendor or supplier — defective stock, wrong consignment, unsold inventory under agreement. An inventory and procurement matter, not a marketplace delivery outcome.
DTO / customer return
Buyer received it, then returned it. Opens condition disputes: used goods, empty boxes, swapped items. Evidence at opening is everything.
Separating the losses automatically
The classification work is mechanical: check whether delivery completed, tag the return accordingly, apply the right claim route. Mechanical work done by a tired person at the end of a dispatch day is where errors and missed claims come from.
Robnu is an agentic OMS. It categorises every return by what actually happened, tracks the two loss rates independently so you can see which is hurting, and routes each claim down the correct path with the right evidence attached. Filing happens 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 vs RTV vs DTO, answered
RTO means return to origin — a parcel that could not be delivered to the customer and is sent back to you. RTV means return to vendor, which describes goods being sent back to a supplier or vendor, typically in a stock or wholesale context rather than a consumer delivery one. RTO is a failed sale; RTV is an inventory movement. They belong in different parts of your accounts.
DTO is generally used for a direct-to-origin or customer-initiated return flow, where a buyer who has received the product initiates sending it back. The key distinction from RTO is possession: in a DTO the customer took delivery first. That difference changes the evidence available to you and the claim routes open when something is wrong with what comes back.
Because the charges and the claim rights differ. An RTO is freight-heavy and rarely involves product condition disputes, since the customer never opened it. A customer-initiated return frequently does involve condition disputes — wrong item, used item, empty box — which are claimable in ways an RTO is not. Lumping them together means you never see which category is actually bleeding.
No. RTO claims are typically about freight accuracy: wrong weight, duplicate charge, parcel never returned. Customer-return claims are typically about goods condition and require evidence at the moment of opening — photos and unboxing video. Using the wrong claim route for a case is a common reason claims get rejected.
It depends on your category, and that is exactly why separating them matters. High-value fashion often bleeds most through customer returns with condition disputes. Low-value high-volume categories usually bleed through RTO freight. Without separate tracking you cannot tell which problem you have, and you end up fixing the wrong one.
Not entirely. Terminology varies between platforms and between courier partners, and some panels use RTO loosely for any return. Rather than trusting the label, look at the underlying facts: did the customer ever take possession, and was the parcel opened? Those two questions determine the real category regardless of what it is called.
Tag every return with whether delivery completed before the return began. That single field splits RTO from customer-initiated returns cleanly and lets you compute the two loss rates independently. Most sellers keep one combined returns number, which is why the underlying causes stay invisible.
No, and treating them the same leads to the wrong fixes. High RTO points to address quality, cash-on-delivery exposure and delivery-side failure. High customer returns point to sizing, product description accuracy and expectation mismatch. The remedies share almost nothing.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
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.
Myntra SPF (Seller Protection) Decoded: What It Covers and How to Claim
Myntra's Seller Protection Fund covers lost, damaged and fraudulent returns — but only with the right evidence, inside the right window. What SPF pays for, what proof you need, and why claims get rejected.
Amazon India SAFE-T claims: when and how to file
SAFE-T reimburses seller-fulfilled losses on returns Amazon's standard policy passed to you. What qualifies, the evidence that wins, and why most of the money is simply never claimed.
Tampered package returns: evidence that wins the claim
Broken seals, re-taped flaps, a parcel lighter than it shipped — the receive-bench routine, courier tamper annotations, and where the claim actually gets filed.
RTO deductions: why you're charged & how to claim them back
The types of RTO deduction on AJIO and Meesho, which ones are wrong and claimable, the evidence you need, and how Robnu automates recovery.
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.
Meesho QC Fail on a Return: Your Claim Window and How to Use It
When a returned Meesho parcel fails quality check, the outcome and your money are decided in a short window. What QC-fail means, the evidence that holds, and the claim path that recovers a wrongly-failed return.
Proving the Courier Never Knocked: Fake Delivery Attempts
A parcel marked 'customer unavailable' or 'premises closed' when nobody ever came is a fake delivery attempt — and it drives avoidable RTO. How to spot the pattern, gather evidence, and dispute it.