Returns and undelivered orders are usually tracked as a logistics problem. They are a merchandising problem, a product-page problem and a payments problem too — and most dashboards hide the connection.
Return to origin is the order that was shipped, travelled, failed to be delivered, and travelled back. You paid forward freight, reverse freight and handling, the stock was out of circulation for a week or more, and there is no revenue against any of it. For brands with a meaningful cash-on-delivery share, RTO is often the single largest controllable drain on contribution margin.
It gets under-managed because it lands in the logistics report, where it looks like a courier problem. Much of it is decided long before the parcel moves.
Separate the three things people call 'returns'
- RTO — never delivered. The customer refused it, was unreachable, or the address failed. Costs two legs of freight and zero revenue.
- Return — delivered, then sent back. The customer saw the product and did not keep it. Costs a leg of freight plus handling, refurbishment and often a refund.
- Exchange — delivered, then swapped, usually for size or colour. Costs freight but keeps the revenue, and frequently keeps the customer.
These have different causes and different fixes. A dashboard that adds them into one percentage tells you almost nothing about what to do next.
Ask why, at the level where the decision was made
Returns of a delivered product are usually an expectation gap: the product was not what the page implied. Size, colour under real light, material weight, scale relative to a body or a room. Every one of those is a product-page decision, not a courier decision.
RTO is usually an intent gap: the order was placed with less commitment than a prepaid order carries, or the customer's situation changed during the days in transit. That is a payments and confirmation problem.
The merchandising angle nobody runs
Here is the connection most stores miss. Your collection pages decide which products get seen, and therefore which products get ordered, and therefore what your return rate is. If the products that surface first are the ones that come back most often, your merchandising is actively buying you returns.
Most sorting tools cannot express this, because they rank on gross demand — views, orders, revenue. What you want is to rank on outcomes that survive delivery. Two products with identical revenue are not equally valuable if one of them comes back a third of the time.
This is the same argument as sorting by profit rather than sales, one step further. SellRank ranks by profit and margin where cost price is recorded, so a high-revenue, low-margin product stops crowding out a quieter product that actually pays the bills. Ranking on delivered, kept revenue is the natural extension of that thinking, and it starts with measuring returns per product rather than per month.
A practical sequence
- Measure returns and RTO per product, not just per store. The distribution is almost never even; a handful of SKUs usually carry it.
- Fix the worst offenders' product pages first — real-scale photography, measured dimensions, material weight, a size guide built from your own returns data rather than a generic chart.
- Address intent at checkout: partial prepayment, order confirmation before dispatch, and address validation at the point of entry rather than at the warehouse.
- Then change what your collection pages promote, so the products that reliably stay sold get the positions that matter.
Measure it in your own store
Deliberately, this article quotes no industry benchmark. Published RTO and return figures vary enormously by category, price band, geography and payment mix, and a number from someone else's catalogue will mislead you about your own. Your own per-product numbers over the last ninety days are the only benchmark that can change a decision.
If you want help wiring that measurement into something you look at weekly rather than dig for quarterly, that is the kind of work we do at LeelaRam Technologies.
