For small and medium businesses (SMBs) selling online in India, shipping a product does not guarantee revenue. A significant share of orders never reaches the customer — they come back. This is called RTO, or Return to Origin, and it is a major driver of avoidable costs in Indian e-commerce.
Unlike a customer return, an RTO occurs before the customer receives the product. The package comes back to you. You pay for forward shipping; you pay for reverse logistics and recover no revenue. For an SMB managing tight margins, even a 20% RTO rate can materially reduce profitability.
Understanding what causes RTO — and how to reduce it systematically — is critical to building a sustainable e-commerce business in India.
TL;DR
- RTO (Return to Origin) is when a shipped order fails to reach the customer and is returned to the seller.
- In India, Shipway’s ShipNotes FY25 analysis reports about 26% RTO on COD/non-prepaid orders overall, with under 2% for prepaid orders; in some cohorts/cities, RTO is reported to be as high as ~35% (Shipway ShipNotes Report, FY25).
- One industry estimate puts the logistics-only cost per RTO at ₹180–₹240 (forward + reverse + handling), often with no revenue recovered on that shipment.
- The primary drivers of RTO are incorrect addresses, customer unavailability, COD refusal, and poor NDR follow-up.
- To reduce RTO, focus on: address verification at checkout, WhatsApp/SMS confirmation before dispatch, risk-based COD screening, and acting on NDRs within 24 hours of a failed delivery attempt.
Glossary
- COD (Cash on Delivery): The customer pays at the time of delivery, which also makes refusal at the doorstep possible.
- NDR (Non-Delivery Report): A courier-raised delivery-failure status that needs quick follow-up to schedule re-attempts and prevent RTO.
- OTP (One-Time Password): A verification code used at delivery as proof-of-delivery and to reduce fraud/false handoffs.
- AOV (Average Order Value): The average value (₹) per order, used to set risk-based verification thresholds for COD orders.
Why RTO Is a Disproportionate Problem in India
India’s e-commerce market is growing rapidly. India’s online shoppers grew from 140 million in 2020 to 260 million in 2024 and are expected to hit 700 million by 2035, driven mainly by tier‑2 and tier‑3 cities.
But this growth comes with a structural challenge: Cash on Delivery (COD) dominates. Approximately 60–65% of e-commerce orders in India are placed via COD (ET Prime Research, via Dazeinfo). COD gives customers the option to refuse delivery at the door.
For an SMB processing 500 orders a month at an average order value of ₹800, a 25% RTO rate means 125 orders come back every month. At ₹200 per RTO in logistics costs alone, that is ₹25,000 per month in direct logistics cost — before accounting for inventory handling or repackaging.
The True Cost of an RTO
Most sellers calculate RTO cost as just the reverse shipping fee. The actual cost is broader:
Cost Component |
Typical Range (per RTO) |
Forward shipping charge (non-refundable) |
₹60 – ₹100 |
Reverse logistics charge |
₹50 – ₹80 |
Repackaging / quality check |
₹20 – ₹40 |
Inventory holding during transit |
₹10 – ₹20 |
Opportunity cost (capital blocked) |
Variable |
Total estimated cost per RTO (illustrative; varies by weight, lane, and courier) |
₹180 – ₹240 |
Source (illustrative estimate): bepragma.ai Industry Data, 2025
This does not include the impact on customer acquisition cost. If you spent ₹450–₹680 acquiring a customer who then refuses the order at the door, the total unit economics can quickly become unsustainable.
Common Causes of RTO in India
Understanding why RTOs happen is the first step to preventing them. The causes fall into three categories:
1. Address and Contact Issues
- Incomplete or incorrect delivery address
- Outdated phone number on the order
- No response when the courier calls for directions
As per industry estimates, address errors contribute 18–24% of total RTOs in India (bepragma.ai, 2025).
2. Customer Unavailability
- Customer not at home during delivery hours
- No authorized person available to receive and pay for COD
- Courier makes a single attempt and closes the NDR
3. COD Refusal
- Impulse purchases where the customer has reconsidered
- Customer found the same product cheaper elsewhere after ordering
- Order placed for price comparison without genuine purchase intent
4. Poor NDR Management
When a delivery attempt fails, the courier raises an NDR. If no re-attempt is coordinated within 24–48 hours, the shipment escalates to RTO. Research shows that delivery speed is directly correlated with RTO rates: orders attempted within 1–2 days had a 22% RTO rate, rising to 35% when attempted after 5+ days (Shipway ShipNotes FY25).
The If–Then Framework: When to Intervene
Stage |
If… |
Then… |
Diagnosis (weekly) |
RTO is spiking in specific pin codes or products |
Segment RTO by pin code/product/courier and apply targeted verification + routing changes |
Delivery execution |
First delivery attempt is slow or inconsistent |
Prioritize faster first-attempt SLAs and tighter dispatch windows to reduce reconsideration and “customer unavailable” cases |
NDR operations |
NDR volume is rising |
Treat NDR follow-up as an ops SLA and run a daily queue until cases are resolved |
RTO Reduction Playbook
The 7-step RTO reduction playbook
- Fix address quality at checkout. Make flat/house number, street/locality, landmark, and pin code mandatory.
- Confirm first-time COD orders before dispatch. Use WhatsApp/SMS to confirm or OTP confirmation for high-risk segments.
- Use risk-based COD rules. Tighten COD on first-time buyers, high-RTO pin codes, and high-value orders.
- Set clear delivery expectations at dispatch. Share tracking immediately and communicate an expected delivery window.
- Operate NDR as a 24-hour SLA. The moment an NDR is raised, contact the customer and lock a re-attempt time.
- Escalate after the second failed attempt. If two attempts fail, call before a third attempt; confirm address and availability, or proactively limit incremental cost.
- Close the loop weekly. Tag every RTO with a reason code (address, unreachable, refusal, delay) and review by pin code, product, and courier to update your rules.
Decision rules
If (condition) |
Then (action) |
COD + first-time customer |
Require WhatsApp/SMS confirmation before dispatch |
COD + high AOV (e.g., > ₹1,000) |
Do a confirmation call or OTP before dispatch |
Address missing flat/house number/landmark |
Hold shipment until corrected |
Pin code is flagged “high RTO” in your last 30-day data |
Add one extra verification step (confirmation + shorter dispatch window) |
NDR raised |
Contact the customer within 24 hours and schedule a re-attempt |
2 delivery attempts fail |
Call + reconfirm address; decide whether a 3rd attempt is worth the incremental cost |
Customer has prior RTO/refusal history |
Switch to prepaid-only or offer COD with part-payment/fee |
KPIs to track (simple and actionable)
- Overall RTO rate = RTO orders ÷ shipped orders (trend down month-over-month).
- COD RTO rate vs prepaid RTO rate (your COD gap shows where to focus).
- Address defect rate = orders needing address correction ÷ total orders (trend down as checkout improves).
- NDR response time = median time from NDR to first customer contact (aim for < 24 hours).
- Re-attempt success rate = successful deliveries after NDR ÷ NDR cases (trend up with better follow-up).
- RTO by pin code and product (top 10 drivers should shrink over time).
The RTO Reduction Checklist for Indian SMBs
Before Dispatch
- Ensure checkout captures complete address and a reachable phone number
- Define which orders require manual review (e.g., high AOV > ₹1,000, unusually high quantity, repeat refusal/RTO history)
- Maintain a simple “high-RTO pin code” watchlist based on your last 30 days of data and review it weekly
At Dispatch
- Confirm shipment data quality: correct phone number, complete address, and COD amount on the label/manifest
- Monitor first-attempt delivery speed by courier and route orders to partners that perform best for your key pin codes
After a Failed Delivery Attempt (NDR Management)
- Run a daily NDR queue, so cases don’t auto-escalate to RTO
- Capture the reason for each NDR (unreachable, address issue, customer unavailable) and fix the root cause before re-attempt..
Post-RTO Analysis
- Standardize RTO reason codes (address, unreachable, refusal, delay) and make them mandatory in your ops sheet
- Review your “top 10” RTO drivers (pin codes, products, couriers) and change one rule/process each week
Misconceptions About RTO
“RTO is a logistics problem.”
RTO is typically driven by a mix of logistics execution and buyer/seller-side factors. Faster, more responsive delivery can reduce unavailability-related RTOs, but address errors and COD refusal also require seller-side process improvements.
“Removing COD will fix my RTO rate.”
Blanket COD removal eliminates high-intent buyers who simply prefer COD. In Tier-2 and Tier-3 cities, this can mean losing large portions of your reachable market. The goal is smarter COD screening, not COD elimination.
“Low-value orders are the biggest RTO risk.”
Actually, orders in the ₹500–₹1,000 range see the highest RTO rates (28%), likely driven by impulse purchases. Orders below ₹500 and above ₹1,000 see lower RTO rates of 25% and 24% respectively (Shipway ShipNotes FY25).
“Zone 1 (local) shipments are always safe.”
Some datasets report that intra-city shipments can have lower RTO than longer-distance lanes, but “local” is not guaranteed delivery—address quality, reachability, and COD intent still matter.
Once you have the right SOP in place (address quality, COD verification, and an NDR response SLA), execution comes down to logistics capabilities: reliable first-attempt delivery, strong pin-code coverage, real-time tracking, and proof-of-delivery controls like OTP. The right shipping partner makes these controls easier to run consistently at scale.
Ship Smarter with Amazon Shipping
Reducing RTO is easier when your shipping partner supports fast first-attempt delivery, end-to-end tracking, and responsive exception handling. Amazon Shipping supports last-mile deliveries across 14,000+ pin codes and offers real-time tracking; it also supports OTP-secured delivery for eligible shipments to help confirm handoff to the intended recipient.
RTO is when a shipped order cannot be delivered to the customer and is sent back to the seller’s address. It can occur due to reasons such as incorrect addresses, customer unavailability, COD refusal, or unresolved delivery exceptions. The seller bears both the forward and reverse shipping cost and typically recovers no revenue from the transaction.
Benchmarks vary by category, price band, lane mix, and COD share. As a reference point, Shipway’s ShipNotes FY25 reports 26% RTO on COD/non-prepaid orders overall and <2% for prepaid; some segments/cities are reported at 35% (Shipway ShipNotes FY25). Operationally, if your overall RTO is persistently high (for example, ~20%+), it is a strong signal to review checkout/address quality, pre-dispatch verification, courier first-attempt performance, and NDR follow-ups.
COD allows customers to decide at the door whether to accept the order, creating a built-in refusal option. Impulse purchases, price-comparison behavior, and the absence of upfront financial commitment all contribute to higher cancellation rates. In India, COD represents 60–65% of all e-commerce orders but drives the overwhelming majority of RTO volume.
An NDR is raised by the courier when a delivery attempt fails. If the NDR is not acted on quickly — typically within 24–48 hours — the shipment is escalated to RTO. Proactive NDR management, where the seller contacts the customer and reschedules delivery, is a highly effective lever to prevent RTOs.
A practical approach is risk-based screening: verify orders from first-time buyers, flag high-risk pin codes, use WhatsApp or SMS for address confirmation before dispatch, and require OTP for high-value COD orders. This reduces refusals and address errors without blocking genuine customers who prefer COD.
Yes, in many cases. According to FY25 data from Shipway, orders delivered within 1–2 days had a 22% RTO rate. This rose to 35% for orders with delivery attempted after 5 or more days. Faster delivery can mean less time for the customer to reconsider or become unavailable.
In the Shipway ShipNotes FY25 dataset referenced above, cities including Patna, Srinagar, Jaipur, Varanasi, Ranchi, Jammu, Meerut, Guwahati, Visakhapatnam, and Nashik were reported among the higher RTO rates. Vadodara recorded the lowest RTO rate at 18%. (Shipway ShipNotes FY25)
Some brands introduce a nominal COD fee or require part-payment to reduce low-intent orders. This can lower RTO volume but may also reduce conversion rates. A more targeted approach is to apply these restrictions selectively to first-time buyers or high-risk pin codes rather than universally.
Disclaimer:
The information provided on this blog is for general informational purposes only. While we strive to keep the information up-to-date and accurate, we make no representations or warranties of any kind, about the completeness, accuracy, suitability or availability of the information contained on this blog. All content on this blog is protected by copyright law. Unauthorized use of this material without express written permission is strictly prohibited.
