How to reduce RTO on COD orders: the India playbook

Updated July 5, 2026 · ACOD (E-TRADE PARTNER)

RTO (return to origin) on Indian COD orders is fought at two layers. At checkout, you filter the orders most likely to bounce: charge a COD fee so the order carries a small commitment, offer COD only for pin codes your courier serves reliably, cap COD order values, and move repeat refusers to prepaid with customer tags. After checkout, you confirm and deliver better: NDR follow-up, address quality, and courier selection. ACOD handles the entire checkout layer in one app, on every Shopify plan.

Why RTO is a COD problem

A prepaid order that fails delivery still leaves the money with you while you re-attempt or refund. A COD order that fails delivery costs you twice: forward shipping and return shipping, plus weeks of inventory stuck in transit, plus the courier's COD handling charge on a sale that never happened. In India, where COD still carries a large share of D2C volume outside the metros, an unmanaged RTO rate quietly decides whether the store makes money at all. The good news: a large share of RTO is predictable from what happens at checkout, and Shopify lets you act on it there.

Where Indian RTO actually comes from

• Impulse orders with zero commitment. COD with no fee and no confirmation costs the buyer nothing to place and nothing to refuse at the door.
• Fake and prank orders. Wrong numbers, joke orders, competitor mischief. Nothing was ever going to be delivered.
• Serviceability gaps. The order was placed for a pin code where your courier's COD delivery is slow or unreliable; by the time the parcel arrives, the buyer has moved on.
• High-ticket regret. A ₹6,000 COD order placed at midnight looks different to the buyer three days later when the doorbell rings.
• Address and phone quality. Incomplete addresses and unreachable phones turn into failed delivery attempts, and every failed attempt raises the refusal odds.

Checkout layer 1: a COD fee that filters intent

The single highest-leverage change is making COD carry a small, visible cost while prepaid stays free. A ₹49–149 fee does two things at once: it covers your courier's cash-handling charge, and it makes the zero-commitment impulse order slightly less free, which is exactly the order most likely to bounce. Set it up as a dedicated shipping rate linked to the COD payment method so nobody dodges it by switching shipping options, and read the fee-to-prepaid conversion playbook for how to frame the choice at checkout. Buyers who switch to UPI or card to avoid the fee have effectively pre-verified their own order.

Checkout layer 2: pin-code serviceability rules

Every Indian courier publishes which pin codes it serves for COD, and RTO concentrates heavily in the weak ones. Mirror that list at checkout: offer COD only where delivery actually works. Indian PIN codes are hierarchical (first digit = zone, first three digits = sorting district), so prefix rules cover whole belts without pasting thousands of codes; setup steps here. Everyone else still checks out, just prepaid.

Checkout layer 3: order-value caps

Refusal pain scales with ticket size, and most couriers cap per-parcel cash collection anyway. Set a maximum order value for COD (₹5,000 is a common ceiling; use your courier's cap if lower) so high-ticket orders go prepaid, and optionally a minimum (around ₹300) below which the COD handling charge eats the margin. How to choose the numbers.

Checkout layer 4: block repeat refusers

A small group of customers generates a disproportionate share of refusals. Tag them (manually after a refusal, or automatically with Shopify Flow) and hide COD for that tag. They can still buy from you, just prepaid, which converts their refusal risk to zero. The inverse also works: a COD allowlist tag for wholesale or repeat customers you trust.

The ops layer: what stacks on top

Checkout rules prevent the bad order from existing; operations rescue the good order that still wobbles. The proven ops levers: NDR (non-delivery report) follow-up the same day a delivery attempt fails, address prompts that catch incomplete addresses before dispatch, calling or messaging to confirm large COD orders before shipping, and courier selection based on your own RTO data by region. Several apps specialize in OTP or IVR order confirmation; ACOD deliberately focuses on the checkout rules, and the two approaches stack without conflict.

Measure it or it didn't happen

Track your COD share of orders, RTO rate on COD vs prepaid, and RTO rate by region, before and after each change. Most courier dashboards and aggregators (Shiprocket, NimbusPost and similar) report RTO by pin code; feed the worst performers back into your ACOD pin rules monthly. Stores usually find that a fee plus serviceability rules cuts RTO meaningfully within the first cycle, and the remaining refusals cluster in patterns the tag blocklist handles.

Frequently asked questions