Returns and RTO economics: distinguish the failure before choosing the fix

How should retail teams distinguish returns and RTO when measuring ecommerce economics?

Treat return to origin as an unsuccessful delivery journey and a customer return as a post-delivery reversal. Measure them against their own eligible shipment or delivered-order populations. Track refunds, transport, inspection, inventory condition and recovery separately. This prevents one blended return percentage from hiding whether the underlying problem is delivery, product fit, expectations or fulfilment quality.

Separate journeys, not just report labels

Return to origin, often shortened to RTO, concerns a shipment that did not complete delivery to the customer and is sent back. A customer return follows delivery and a subsequent return request. That difference matters because the available evidence, possible intervention and cost pattern are different.

Shiprocket's explanation of RTO provides the undelivered-shipment definition. Use your actual carrier and channel statuses for implementation. Do not assume a universal number of delivery attempts, a standard return charge or a guaranteed prevention rate from a general guide.

An order can also split into several shipments. One parcel might be delivered while another becomes RTO. Start at shipment or order-line level, then aggregate carefully. Labelling the entire order returned can overstate the affected value and obscure what the customer actually received.

Define the denominator before discussing performance

For an operational RTO rate, use completed RTO shipments divided by an explicitly defined dispatched-shipment cohort. Show unresolved in-transit shipments separately. For a customer-return rate, use returned delivered units or orders divided by the corresponding delivered population, with the same unit of measurement.

Young cohorts are incomplete. A parcel dispatched yesterday has had little time to be delivered or returned. Compare cohorts at equivalent maturity and show pending outcomes. Otherwise an apparent improvement may simply reflect insufficient observation time.

Track physical and financial events separately

Keep delivery, return initiation, pickup, warehouse receipt, inspection and stock disposition as separate events. Track refund approval and payment alongside them. A refund does not prove that stock was received, and receipt does not prove it is available to sell.

Shopify's reporting guidance distinguishes returns and refunds. The wider operating recommendation is to preserve both the money trail and the goods trail, then investigate where they diverge.

Use reason codes at different stages rather than one overwritten reason. A customer's stated issue, a carrier's delivery status and a warehouse's inspection finding are different observations. Retaining all three supports a better diagnosis than forcing them into one supposedly definitive explanation.

Worked hypothetical example: two problems inside one cohort

Consider a mature cohort of 1,000 single-parcel, single-unit shipments. Exactly 100 complete RTO, while 900 reach customers. Of those delivered units, 90 are subsequently returned. RTO rate is 100 / 1,000 = 10%; customer-return rate is 90 / 900 = 10%.

The two percentages have different denominators. The proportion of originally dispatched units that customers do not retain is 190 / 1,000 = 19%, not 20%. This combined figure can support a cohort overview, but it should not replace the two diagnostic measures.

Assume each RTO incurs ₹80 outbound transport, ₹70 reverse transport and ₹20 handling. Its cost is ₹170, or ₹17,000 across 100 cases. Assume each customer return incurs ₹70 reverse transport and ₹30 inspection, adding ₹9,000. Total costs shown are ₹26,000.

This simplified incremental-failure-cost view excludes normal outbound delivery costs for the 900 delivered orders, advertising, refunds and product losses. State that boundary clearly. If ten received units are unsellable at ₹400 cost each and have no recovery value, add ₹4,000, giving ₹30,000 within the expanded boundary.

Match the intervention to the evidence

For RTO, investigate address completeness, contactability, delivery timing, non-delivery responses and serviceability. Compare like-for-like lanes and service conditions. A high rate concentrated in one route suggests a different investigation from a pattern spread across products but concentrated in one checkout cohort.

For customer returns, inspect size information, product descriptions, packaging, dispatch accuracy and defects. Link reasons to variant, batch and listing version where available. A sizing problem will not be solved by a faster non-delivery follow-up process, while a failed delivery cannot establish that a product disappointed its recipient.

Avoid inferring intent from a single event. Customers can be unavailable, addresses can be incomplete and carrier records can be wrong. Use the evidence to improve the process rather than creating unsupported labels about individual shoppers.

Evaluate changes with commercial guardrails

A stricter order-confirmation step may reduce RTO among dispatched shipments while also preventing legitimate purchases. Measure eligible orders, confirmation completion, dispatches, deliveries and contribution together. Otherwise the team may optimise a narrow rate while reducing useful business.

Similarly, a restrictive return process can change reported returns without improving product quality. Track complaints, repeat behaviour and service effort alongside reverse costs. Test operational changes on appropriate populations and preserve promised customer terms.

Practical reverse-logistics checklist

Verify shipment-to-order links, mature cohort dates, unresolved statuses and consistent unit counts. Reconcile refunds to payment events, warehouse receipts to inspection outcomes and restored stock to saleable quantities. Assign owners to parcels stuck between stages, with elapsed time and the next expected event visible.

Review the largest cost categories and repeat reasons each week. Require evidence before changing customer policy, carrier allocation or product copy. A blended return total should open an investigation, not choose the action.

Bring a complete journey to the discussion

For a marketplace operations walkthrough, bring one RTO, one resellable customer return and one damaged return. Ask how a proposed Fundle Brain view would connect the events and explain the cost boundary. Evaluate the workflow with your real data availability before assuming any automated intervention is supported.

Questions from retail teams

Is a refused cash-on-delivery parcel a customer return?

If the parcel never completed delivery and is sent back, treat it as RTO within the shipment journey. A post-delivery customer return is a different event. Preserve the carrier status and customer communication because refusal, failed contact and address problems need different follow-up even when they end in the same RTO category.

Can we add the RTO rate and customer-return rate together?

Not when their denominators differ. RTO is often measured against dispatched shipments, while customer returns are measured against delivered units or orders. Calculate a combined non-retention measure directly from one common mature cohort if needed. Continue showing the separate rates so managers can distinguish delivery problems from post-delivery product or service issues.

When should returned stock become available again?

Only after the required receipt and inspection steps confirm it is suitable for sale under your operating policy. A carrier delivery scan or customer refund is insufficient evidence. Record resellable, repairable, damaged and unresolved quantities separately, and link the decision to the warehouse record so recovered value can be explained.

How can we compare courier performance fairly?

Compare similar lanes, service levels, payment types, parcel characteristics and cohort maturity. Show shipment counts and unresolved outcomes alongside rates. A courier handling a harder delivery mix can look worse in an unadjusted total. Investigate specific exceptions and response times before concluding that the carrier alone caused the difference.

Which costs belong in a return economics report?

Include the cost boundary relevant to the decision: outbound and reverse logistics where applicable, handling, inspection, unrecovered product value and related customer-service expense. Show refunds and revenue reversals separately from costs. Identify excluded advertising or overhead so users do not mistake a narrow reverse-logistics calculation for full order profitability.

Sources and further reading

• Shiprocket: Return to Origin processing and terminology — RTO definition only; dated promotional statistics, attempt counts and performance promises are not adopted.
• Shopify: Sales discrepancies in Analytics — Documented separation of return, refund, inventory and reporting effects.