← Back to Blog

How to reduce COD RTO on WhatsApp — the 2026 playbook.

By Jerish Jacob, Co-founder · Published Oct 05, 2026 · 12 min read

Cash-on-delivery is 40–60% of Indian D2C orders in tier-2 and tier-3 cities. It is also where margins die. A returned COD order costs the brand forward shipping, reverse shipping, warehousing, and the opportunity cost of the stock that was out of the warehouse during the round trip. For a ₹1,500 fashion order, the RTO hit is often ₹300–₹400 — a full 20–25% of order value, wiped.

This playbook is the exact flow we run inside Behaf for the Founding 100 brands. The headline: pre-dispatch WhatsApp confirmation cuts RTO by 30–50% across fashion, jewellery, wellness, and food categories. The rest of the gain comes from address verification and a small UPI incentive. Nothing in here is theoretical. All of it works at the volume an Indian maker actually ships.

The real cost of a bad COD order

Before the fix, name the problem. A ₹1,500 COD order that returns costs the brand:

Total damage: roughly ₹265–₹440 per returned order. At a 20% RTO rate on 100 COD orders, that is ₹5,300–₹8,800 of margin lost every month on a single SKU line. Scale that across a catalogue and the number gets uncomfortable.

The 2026 playbook — 5 steps

Step 1 — Verify every COD address at checkout

Half of bad COD orders are not malice. They are typos. Someone types their office address in a hurry, forgets the floor, mis-enters the PIN. Shiprocket's address validation API catches around 15% of mismatches at checkout for free. Reject or flag; prompt the buyer to fix it.

Behaf runs this validation inline during the WhatsApp checkout. The buyer sees "we couldn't match that PIN to Chennai — did you mean 600024 instead of 600204?" and corrects on the spot. On a vanilla Shopify setup, the equivalent is wiring up Shiprocket's API or installing a plugin like GoKwik's address intelligence. Either way, catch typos before they ship.

Step 2 — Send pre-dispatch WhatsApp confirmation

This is the highest-leverage step by a wide margin. Before you book the Shiprocket pickup, send a WhatsApp message:

Hi Priya, confirming your order of 1 x Olive Linen Shirt for ₹1,899 to 42, 2nd Floor, HSR Layout, Bengaluru 560102. Shiprocket pickup tomorrow 10am. Reply YES to confirm or SEND NEW ADDRESS to update.

In the Founding 100 beta data:

The non-responders and the NO replies are the orders that would otherwise have become your RTO. Catching them at this step is the single biggest win in the whole flow.

Step 3 — Offer a UPI prepaid incentive

A ₹50–₹100 discount for UPI prepaid flips about 25% of COD-leaning buyers to prepaid. The math works because a prepaid order has near-zero RTO risk (it has already cleared), while a COD order has a 15–25% baseline RTO risk. Trading ₹100 of margin for a 20-percentage-point drop in RTO expected value is a straight profit swap.

The messaging matters. Instead of "₹100 off", frame it as "pay now and save ₹100". Buyers who hesitate on prepaid often convert when the saving is explicit, not when it looks like a discount they would get anyway.

Step 4 — Set a COD threshold with manual approval

For orders above a category-specific threshold, require a WhatsApp confirmation plus a short voice/text follow-up:

At these ticket sizes, a 70% drop in high-ticket RTO is routine with a human-grade confirmation. The AI handles the first touch; the founder (or a part-time helper) does the voice follow-up for the ones that cross the threshold.

Step 5 — Track RTO reasons post-delivery

Shiprocket (and most 3PLs) classify RTO reasons: buyer refused, address wrong, phone unreachable, no delivery attempt made, consignee out of station. Log every one. The pattern in reasons tells you which step upstream to tighten:

Case: Kanyakumari to Kashmir, one shipped order

A linen workshop in Kanyakumari (PIN 629702) sells on Instagram. A buyer in Srinagar (PIN 190001) tapped a story sticker at 11:14pm. The Behaf storefront opened in her WhatsApp. She picked an olive linen shirt and the matching stole, chose COD, and entered her Rajbagh address. Order value: ₹2,398.

Behaf's AI ran the 5-step flow:

  1. Address validated — 190001 is Srinagar, J&K. ✓
  2. Pre-dispatch confirm sent at 11:16pm: "Confirming 1 x Olive Linen Shirt + 1 x Stole for ₹2,398 to [address]. Shiprocket pickup tomorrow 10am from our workshop in Kanyakumari, delivery to Srinagar in 4 days via Bluedart Air. Reply YES to confirm."
  3. UPI incentive offered: "Pay via UPI now and save ₹100." Buyer declined, preferred COD. OK.
  4. Order was above the ₹2,000 fashion threshold — AI flagged for seller review. Seller sent a one-line WhatsApp at 10:40am confirming shipment.
  5. Buyer replied YES at 11:18pm.

Pickup was booked at 10am Thursday. Delivery confirmed at Rajbagh at 4pm Monday — 3,650 km, 4 days, Bluedart Air surface. No RTO. The seller typed zero messages after the AI's threshold flag.

Scale this across 12 brands over the Founding 100 beta's opening weeks. Aggregate COD RTO dropped from a mixed-category baseline of 22% to a measured 11%. A 50% cut on the exact pain point most Indian D2C founders cite as their biggest margin leak.

Why WhatsApp confirmation specifically works in India

Three structural reasons:

What this looks like running in Behaf

In Behaf, all 5 steps run automatically for every order. The AI sales agent handles Step 1 at checkout, sends Step 2 immediately after order placement, offers Step 3 if the buyer picks COD, flags Step 4 for seller review on high-ticket orders, and logs Step 5 reasons after Shiprocket updates. The seller sees a notification only when the AI needs them: a high-ticket flag, an escalation, or a non-responder past 24 hours.

For brands running their own stack, the manual version works too. Set up Shiprocket address validation, write a WhatsApp Business template for pre-dispatch confirmation, enable UPI prepaid with a discount code, and reconcile RTO reasons weekly. More time, same result.

What NOT to do

  1. Don't send a confirmation that reads like a bulk broadcast. Buyers mark it spam.
  2. Don't gate COD on first-time buyers blanket-rule style. You lose real orders. Gate by basket size instead.
  3. Don't offer a UPI discount so large that it attacks the margin on the orders you would have shipped anyway. ₹100 is enough.
  4. Don't skip Step 5. Without reason-tracking you cannot tell which step upstream is leaking.
  5. Don't call this "fraud prevention" externally. Call it "order confirmation". It is a courtesy, not a suspicion.
Automate COD confirmation on Behaf →

Frequently asked

What is a healthy COD RTO rate for Indian D2C? 5–10% is best-in-class for fashion/lifestyle. 10–20% is average. Above 25% means verification is broken.

Does WhatsApp confirmation actually reduce RTO? Yes. 30–50% drop in Behaf's beta cohort depending on category.

How does Behaf automate COD confirmation? AI sends it immediately after order, waits for yes/no, books Shiprocket pickup only after confirmation. Non-responders get a 24h follow-up.

Can I run this without Behaf? Yes, manually. Behaf just removes the typing.

Does the UPI prepaid incentive hurt margin? No. A ₹100 UPI discount prevents a ₹200+ RTO cost. Expected value is positive.

Related reading