How Indian Sellers Can Reduce COD RTO

What is COD RTO?

RTO (return to origin) means a shipped order never reaches the buyer and comes back to the seller. On COD (cash on delivery), the buyer typically has not paid the full amount online, so when delivery fails you often absorb reverse logistics with little or no revenue from that order.

A simple COD RTO path:

1. Customer places a COD order.
2. Seller packs and dispatches it.
3. Delivery does not complete — for example because of refusal, unavailability, address failure, or failed reattempts.
4. The parcel returns to the seller.

RTO is not the same as a post-delivery return. RTO is a pre-receipt failure: the customer never successfully took delivery.

Common consequences for sellers include:

• forward shipping cost
• reverse shipping cost
• inventory locked in transit
• delayed resale
• extra operational workload such as support, packing, and reconciliation

Exact rupee cost per RTO varies by weight, lane, and courier. Measure it using your own orders rather than treating any single published figure as a national average.

Why is COD RTO often higher than prepaid?

Prepaid buyers have already paid online, so doorstep refusal for payment reasons is rarer. Logistics and commerce datasets commonly show a large gap between COD or non-prepaid and prepaid outcomes, but those figures are dataset-specific, not a single national RTO rate for all of India.

In Shipway's FY25 ShipNotes analysis of millions of D2C shipments, reported via MediaBrief in July 2025, non-prepaid or COD orders saw about 26% RTO versus under 2% for prepaid.

Unicommerce's FY23 dataset, reported by Hindu BusinessLine in August 2023, showed COD returns around 20.9% versus prepaid around 5.8%. Treat that as a historical dataset observation, not a current national benchmark.

Other providers publish their own ranges. Always attribute the source and year, and split your own KPIs into:

• COD RTO %
• prepaid RTO %
• blended RTO %

Why do COD orders become RTO? Seven common causes

COD RTO is driven by several failure modes.

Do not treat fake orders as the primary national cause.

Cashfree's published internal cause mix is a useful attributed illustration rather than a universal rule. It groups causes across customer intent, address and cart quality, delivery experience, and seller-side issues.

1. Buyer intent

Examples include:

• low-intent or impulse COD orders
• accidental or duplicate orders
• buyer changing their mind before delivery
• fraudulent or fake orders

Fake or low-intent orders matter, but they are only one cause among several.

2. Address and contact quality

Examples include:

• incomplete address
• incorrect pincode
• missing landmark
• unreachable phone number
• typing errors in contact details

Simple validation can help without introducing invasive identity checks.

3. Fulfilment

Examples include:

• wrong SKU
• wrong size or colour
• dispatch delay
• incorrect packing
• missing items

4. Delivery and logistics

Examples include:

• long delivery time
• failed attempts
• weak courier performance on a particular lane
• poor NDR recovery

In Shipway's FY25 sample, COD RTO was associated with attempt speed: roughly 22% when the first attempt happened within 1–2 days versus about 35% when the first attempt took more than five days.

That is a dataset correlation, not a universal maximum-delivery-time rule.

5. Product expectation

Examples include:

• product does not match listing expectation
• unclear size or variant information
• misleading imagery
• incomplete product descriptions

6. Communication

Examples include:

• buyer forgets the order
• no order confirmation
• unclear amount due at delivery
• no delivery expectation set
• customer does not recognise the courier or order

7. Payment commitment

Full COD involves no upfront payment commitment.

Possible ways to introduce some commitment include:

• prepaid nudges
• Partial COD / advance collection

These may help filter some low-intent orders, but they do not automatically reduce RTO and do not solve address, fulfilment, product, or courier problems.

Before dispatch: reduce avoidable COD RTO

1. Validate address and contact details

This step addresses the address and contact quality problem, not fake orders in general.

Before dispatch, check:

• complete delivery address
• correct pincode
• landmark where useful
• reachable mobile number
• obvious data-entry errors

Keep validation practical. Do not treat every COD buyer as suspicious.

2. Confirm the order before dispatch

WhatsApp, SMS, or a phone call can help re-check an order before handover to the courier, especially for new customers or higher-value COD orders.

Confirm:

• product and variant
• size and colour where applicable
• amount due at delivery
• expected delivery timing where known

Order confirmation can help validate buyer intent and reduce forgotten or misunderstood orders.

It does not guarantee delivery, and WhatsApp confirmation does not prevent RTO on its own.

For WhatsApp-led selling workflows, see how to sell on WhatsApp in India.

3. Use Partial COD where appropriate

Partial COD means collecting part of the order value in advance and collecting the remaining amount at delivery.

It introduces some upfront payment commitment and may filter some low-intent COD orders.

It does not fix:

• logistics delays
• bad addresses
• fulfilment mistakes
• product mismatch
• customer unavailability

Shiprocket's Partial COD guidance also notes that Partial COD does not eliminate RTO.

For the full workflow, see how Partial COD works for Indian sellers.

4. Encourage prepaid where it makes sense

Where commercially appropriate, sellers can test:

• prepaid incentives
• free shipping for prepaid orders
• COD convenience fees
• other nudges toward online payment

Measure the economics yourself.

A discount that reduces margin may or may not save enough RTO cost to make sense.

Do not assume prepaid always improves profitability, that every COD buyer should be pushed to prepaid, or that discounts always pay for themselves.

5. Fulfil accurately and dispatch quickly

Before handing the order to the courier, check:

• correct SKU
• size
• colour
• quantity
• secure packaging
• dispatch without unnecessary delay

This directly addresses fulfilment and product-expectation problems.

Do not try to solve weak fulfilment only by adding payment restrictions.

After dispatch: delivery and NDR recovery

Why delivery speed matters

In Shipway's FY25 dataset, COD RTO was associated with first-attempt speed:

• roughly 22% RTO when the first attempt was within 1–2 days
• roughly 35% RTO when the first attempt took more than five days

Treat this as a dataset correlation, not a universal delivery-time threshold.

Seller results vary by:

• courier
• lane
• category
• location
• customer mix

Use your own delivery data when choosing courier and service levels.

What is NDR?

A Non-Delivery Report (NDR) means a delivery attempt failed and needs action before the parcel becomes RTO.

Think of it as a recovery window.

A simple NDR workflow is:

1. NDR received
2. Check the recorded reason
3. Contact the customer quickly
4. Correct address, landmark, or delivery instructions where necessary
5. Request or reschedule another delivery attempt
6. Monitor the next attempt
7. Stop retrying and close or return the shipment when recovery is no longer practical

Amazon Shipping's RTO guidance emphasises responding to NDRs quickly, including guidance around a 24-hour window.

Treat that as Amazon Shipping's recommendation, not a universal rule for every courier.

Some courier products also report client-observed RTO improvements from NDR automation. Those are vendor claims, not guaranteed industry outcomes.

Compare courier performance using your own data

Measure at least:

• delivery success rate
• first-attempt success
• average delivery time
• NDR rate
• NDR recovery rate
• RTO rate

Where useful, segment by:

• courier
• pincode
• city or region
• product/category

If one courier performs better on a particular lane, that can be useful operational information.

This guide does not claim ShopSynq currently provides automated courier intelligence.

Measure RTO by segment — not only one store-wide number

A single blended RTO rate can hide important patterns.

Review RTO by:

• payment method
• pincode or city
• AOV band
• new versus repeat customer
• product or category
• courier
• delivery time
• confirmation status
• Partial COD, full COD, or prepaid

In Shipway's FY25 sample, the ₹500–₹1,000 AOV band showed higher RTO than some neighbouring bands.

That is useful context for analysing your own data, not a reason to automatically restrict every order in that price range.

Correlation does not automatically prove causation.

Use these segments to find hypotheses to test, not to automatically label customers as risky.

COD RTO diagnostic table

Use this table diagnostically, not as a universal rulebook.

What sellers should not do

Don't treat every COD buyer as fraud

COD remains important for many Indian buyers.

A payment preference alone is not evidence of fraud.

Don't publish blanket "bad pincode" lists

Use your own order history to understand performance and test proportionate controls.

Avoid broad rules that unnecessarily block legitimate buyers.

Don't copy another brand's Partial COD percentage

Their AOV, margins, buyers, and logistics may be completely different.

Don't present vendor case studies as guaranteed outcomes

Provider case studies are useful signals, not universal forecasts.

Don't use payment restrictions to hide fulfilment problems

A wrong product or slow dispatch remains a problem whether the customer paid prepaid, Partial COD, or full COD.

Don't ignore NDRs

A failed first delivery attempt may still be recoverable.

Don't hide refund or payment conditions

Customers should understand payment and cancellation terms before they commit.

Don't assume one courier is best everywhere

Performance can vary by city, pincode, service level, and lane.

How ShopSynq supports COD workflows

ShopSynq supports two useful pre-dispatch workflows for COD sellers:

• Partial COD / advance collection
• automatic WhatsApp order confirmation

Both are live ShopSynq capabilities.

Partial COD can be used where payment commitment is useful.

Automatic WhatsApp confirmation can be used to communicate and confirm order details before dispatch.

These tools should be combined with good fulfilment and delivery operations rather than treated as automatic RTO-reduction systems.

You can explore the wider ShopSynq setup through:

• ShopSynq features
• WhatsApp selling workflows
• online and counter inventory
• store and billing workflows

This guide does not claim that ShopSynq currently provides:

• RTO prediction
• fraud scoring
• pincode scoring
• customer risk scoring
• automated courier selection
• automated NDR recovery
• guaranteed RTO reduction

When you are ready to try confirmation and advance collection alongside storefront and order ops, see Pricing or create a store from the CTA below.

You can also read the detailed guide on Partial COD for Indian sellers.

Educational note

This guide is educational content for Indian sellers. Percentages are attributed to named datasets or vendors. Results vary by category, location, buyer mix, and fulfilment. This guide does not provide legal advice.