RTO (return to origin) is the COD parcel that goes out, gets refused or can't be delivered, and comes back. You pay shipping both ways and make no sale. To reduce COD RTO on WhatsApp, catch the bad orders before the courier picks them up: check the address, confirm every COD order with the buyer on WhatsApp, cancel the ones nobody confirms, and nudge buyers to pay now by UPI.
This playbook works for any brand that takes COD orders on WhatsApp, with or without Behaf. Start by putting a number on the problem.
The real cost of a bad COD order
Before the fix, name the problem. A COD order that comes back costs the brand:
- Forward shipping, to the buyer
- Reverse shipping, the RTO leg back to you
- Handling and restocking
- Stock that sits in transit instead of being on sale
- Cash you counted on that never came in
Put your own shipping rates against that list and multiply by last month's returned COD orders. That number is what this playbook goes after.
How to reduce RTO on COD orders: 5 steps
Step 1: Verify every COD address at checkout
Many bad COD orders are not malice. They are typos. Someone types their office address in a hurry, forgets the floor, mis-enters the PIN. Catch it before you confirm the order and ask the buyer to fix it.
In a WhatsApp checkout, ask for the house or flat number, a landmark and the PIN, and check that the PIN matches the city before you confirm. On your own website checkout, add an address check there too. Either way, catch typos before they ship.
Step 2: Send pre-dispatch WhatsApp confirmation
Before you book the Shiprocket pickup, message the buyer on WhatsApp with the product, the amount and the address. Ask them to reply YES or send a new address. YES ships. A corrected address ships to the new address. NO does not ship. No reply gets one reminder before your courier cut-off; if the buyer is still silent, cancel before pickup. In Behaf, an unconfirmed COD order is cancelled automatically before pickup.
The silent orders and the NOs are the ones most likely to come back. For the exact wording, use our copy-ready COD confirmation templates in English and Hinglish.
Step 3: Offer a prepaid discount for paying by UPI
A small discount for paying now moves some COD-leaning buyers to prepaid. A prepaid order is already paid, so the buyer has already decided. Compare the discount with what one returned COD order costs you.
Some sellers also take a small advance on COD orders they see as high-risk, and collect the rest on delivery.
The wording matters. Instead of "₹100 off", say "pay now and save ₹100, or choose cash on delivery". The buyer sees both options, and the saving is explicit.
In Behaf, you set the discount for paying now, and Aria offers it at checkout: pay now and save the % you set, or choose cash on delivery.
Step 4: Set a COD threshold with manual approval
Set your own threshold from your RTO data: find the order values and PIN codes where your returned COD orders cluster. Above that line, the WhatsApp confirmation handles the first touch, and you, or someone on your team, call the buyer before you ship. A higher-value return costs more, so the call is worth it.
Step 5: Track RTO reasons post-delivery
Note why each returned order came back: buyer refused, address wrong, phone unreachable, no delivery attempt made, buyer out of station. Log every one. The pattern in reasons tells you which step upstream to tighten:
- Lots of "address wrong" → tighten Step 1 verification
- Lots of "phone unreachable" → add a 2nd-number field at checkout
- Lots of "buyer refused" → tighten Step 2 confirmation copy, or gate COD by basket size
- Lots of "consignee out of station" → push weekend scheduling or let buyer pick a delivery date
Worked example: Kanyakumari to Kashmir, one COD order
An illustration of the flow, not a customer record.
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 sales agent handled the COD steps:
- Pre-dispatch confirm sent on WhatsApp: "Confirming 1 x Olive Linen Shirt + 1 x Stole for ₹2,398 to [address]. Reply YES to confirm."
- Buyer replied YES.
- Shiprocket pickup booked automatically; tracking sent to her in the same chat.
Had she not replied, the order would have been cancelled before pickup instead of travelling the length of India only to come back. The seller did not have to send a single message.
Why WhatsApp confirmation specifically works in India
Three structural reasons:
- WhatsApp is where buyers already are. It is where family and friends live, so a message there gets seen. An SMS sits between OTPs and offers. An email lands in promotions.
- The confirmation is bidirectional, not transactional. If the buyer wants to change the address, they type it. If they want to cancel, they say so. You get the answer in writing, without a phone call.
- WhatsApp confirmation feels like a human asking. Even when it's Aria, the tone matches a seller who cares about the order.
What this looks like running in Behaf
Behaf is AI sales for D2C brands. Aria, our AI salesperson, sells to your buyers inside WhatsApp: she helps the buyer pick, takes the address in the chat while she closes the sale, and offers your pay-now discount at checkout. Behaf is built to cut RTO. Every COD order is confirmed with the buyer on WhatsApp before dispatch, and an unconfirmed COD order is cancelled automatically before pickup. Once it is confirmed, the pickup is booked on your own Shiprocket account and tracking goes to the buyer in the same chat. Want to talk to the brand? Buyers can raise a request, and you connect with them on your own WhatsApp or by email. See how a WhatsApp store for D2C brands works.
For brands running their own stack, the manual version works too. Add an address check at checkout, write a WhatsApp Business template for pre-dispatch confirmation, enable UPI prepaid with a discount code, and reconcile RTO reasons weekly. More typing, same idea.
What NOT to do
- Don't send a confirmation that reads like a bulk broadcast. Buyers mark it spam.
- Don't gate COD on first-time buyers blanket-rule style. You lose real orders. Gate by basket size instead.
- Don't offer a UPI discount so large that it attacks the margin on the orders you would have shipped anyway. Keep it small.
- Don't skip Step 5. Without reason-tracking you cannot tell which step upstream is leaking.
- Don't call this "fraud prevention" externally. Call it "order confirmation". It is a courtesy, not a suspicion.
Frequently asked
What is a healthy COD RTO rate for Indian D2C? It depends on category, city mix and how much of your volume is COD. Track it monthly by SKU line; if it keeps climbing, your verification is broken. Jewellery and electronics should aim lower than apparel because a returned high-ticket order costs more.
Does WhatsApp confirmation actually reduce RTO? It catches the orders most likely to come back before they ship: wrong addresses, buyers who were never sure, and buyers who never reply. It also gives the serious ones a second nudge.
How does Behaf automate COD confirmation? Behaf's AI sales agent sends the confirmation message automatically after a COD order is placed, waits for the yes/no reply, and only books the Shiprocket pickup if the buyer confirms. If the buyer does not confirm, the COD order is cancelled automatically before pickup, so it never ships.
Can I run this without Behaf? Yes. The manual version is: send a WhatsApp message with 'Confirming your order to <address>, reply YES to ship' before booking Shiprocket. Behaf sends it for you, so you don't type each one. The manual version works too if you have the hands for it at your volume.
Does the UPI prepaid incentive hurt margin? It costs you a little on every prepaid order, so compare it with what one returned COD order costs you: two shipping legs and stock stuck in transit. Keep the discount small.