COD/RTO guide

How to Reduce COD RTO

A practical COD ecommerce checklist to reduce RTO by improving confirmation, address quality, payment intent, courier review, offer quality, and break-even CPA.

COD marketsUpdated May 31, 2026
Check COD/RTO ProfitView Sample Report

Short answer

To reduce COD RTO, do not start with a generic trick.

Start by finding where the COD funnel leaks:

placed orders
-> confirmed orders
-> shipped orders
-> delivered and paid orders
-> RTO / failed delivery

Then fix the highest-cost stage first: weak confirmation, low-intent COD orders, address issues, poor courier-zone performance, high CPA, low AOV, unclear offer, or high failed-delivery cost.

Step 1: Separate RTO from cancellations

Do not mix all failed orders together.

Separate:

  • unconfirmed orders
  • cancelled before shipping
  • shipped and delivered
  • shipped and RTO
  • delivered and returned later
  • pending shipments

RTO reduction starts after you know which stage is failing. A confirmation issue needs a different fix from a courier-zone issue.

Step 2: Confirm COD intent before shipping

COD orders can be low intent because the customer has not paid upfront.

Improve confirmation with:

  • phone or WhatsApp confirmation
  • clear order total
  • clear delivery time expectation
  • address confirmation
  • duplicate order checks
  • fake number checks
  • high-risk order review
  • partial-prepaid option where appropriate

The goal is not to reject every risky order. The goal is to avoid shipping orders that are unlikely to become delivered paid revenue.

Step 3: Clean address and contact data

RTO often starts with poor delivery information.

Review:

  • phone number validity
  • complete street address
  • city or zone
  • postal code or local equivalent
  • landmark
  • customer availability notes
  • duplicate addresses with different names or phones

If a courier marks many parcels as unreachable or incomplete address, fix order capture before blaming ad targeting.

Step 4: Review RTO by city, courier, and product

Do not look only at total RTO rate.

Segment RTO by:

  • city or delivery zone
  • courier
  • product
  • SKU weight or size
  • traffic source
  • campaign
  • offer
  • customer type
  • order value

A few combinations may create most of the RTO loss. For example, one city, one courier lane, one low-ticket product, or one ad angle may be the main leak.

Step 5: Use COD rules carefully

COD controls can reduce bad orders, but they can also reduce legitimate demand.

Review rules such as:

  • COD disabled for very low order value
  • COD disabled for risky zones
  • COD allowed for repeat buyers
  • COD available only after confirmation
  • partial prepaid deposit for risky or high-cost items
  • shipping fee or COD fee shown clearly

Do not make a rule just because another seller uses it. Check whether the rule improves collected profit, not only RTO percentage.

Step 6: Fix offer and product mismatch

Some RTO is caused before checkout.

Review:

  • misleading ad promises
  • unclear product size or variant
  • weak product page trust
  • price shock at delivery
  • long delivery promise
  • poor expectation setting
  • low-quality leads from broad targeting
  • COD impulse buyers with low intent

If customers refuse because the product or price did not match expectations, confirmation scripts alone may not fix the leak.

Step 7: Check break-even CPA before scaling

Even after reducing RTO, COD ads can still lose money if CPA is too high.

Calculate:

break-even CPA =
expected collected contribution after COD/RTO costs / placed COD orders

Then compare:

current CPA vs break-even CPA

If current CPA is above break-even CPA, reduce ad cost, improve margin, raise AOV, or reduce failed-delivery cost before scaling.

Step 8: Track collected COD ROAS

Do not use placed-order ROAS alone.

Track:

placed-order ROAS = placed COD order value / ad spend

and:

collected COD ROAS = delivered and paid COD revenue / ad spend

If collected COD ROAS is much lower, the funnel leak is still large even if ads look good.

Source notes

Shiprocket support lists address issues, customer unavailability, refusal, COD issues, and remote delivery areas as RTO causes. Delhivery's rate-card language separates forward, RTO, reverse/DTO, and COD cash-handling concepts. These references support the operational checklist, but your own delivery data should decide the first fix.

Use SellMira to pick the first fix

SellMira helps you avoid guessing by showing:

FAQ

What is the fastest way to reduce COD RTO?

Start by separating confirmation failure, delivery failure, and post-delivery returns. Then fix the stage with the highest cost impact.

Should I remove COD to reduce RTO?

Removing COD can reduce COD RTO, but it may also reduce demand. Check collected profit, not only RTO percentage, before changing payment options.

Does prepaid conversion reduce RTO?

Prepaid or partial-prepaid flow can improve intent for some sellers, but it should be tested against conversion rate, collected revenue, and profit after ads.

What should I measure after reducing RTO?

Measure collected COD ROAS, break-even CPA, RTO loss, delivered order rate, net profit, and margin status.