
Before handing a cash-on-delivery parcel to a courier, verify two things: the customer still wants the order, and the address is usable. For Indian e-commerce stores, a short WhatsApp confirmation followed by a human call for unresolved orders is a practical way to catch avoidable returns before dispatch.
A 20% reduction is a pilot target. If 25 out of every 100 shipped COD orders return to origin today, a 20% relative reduction takes that rate from 25% to 20%. That’s five fewer returns per 100 shipments. The numbers below are illustrative.
What is RTO in Indian e-commerce?
Return to origin (RTO) happens when a shipped parcel is returned to the sender before it reaches the customer. A customer refusing a COD parcel at the door is an RTO. A customer who accepts delivery and later requests a return belongs in a separate returns report.
Start by reading the courier’s reason codes and notes. A missing flat number and a customer refusing delivery call for different fixes. Repeated delays on the same route may need a courier review, while duplicate orders and incomplete addresses can often be caught before dispatch.
A five-step WhatsApp and human verification playbook
- Pick a small COD pilot. Start with one store or dispatch location. Flag orders with incomplete addresses, duplicate checkouts, or an unusual order value against your approved rules. Set a verification deadline against the warehouse dispatch cutoff.
- Send a short confirmation. Where you have permission to message the customer, include the store name, order reference, amount due, and three clear choices: confirm, correct the address, or cancel. Use an approved template when required and respect opt-outs. Read the WhatsApp Business Messaging Policy.
- Call only the exceptions that need a person. If a flagged order remains unclear, let an authorized agent call within the agreed window. Confirm order intent, the amount due, and any delivery detail the courier needs. Avoid asking for OTPs or payment credentials. Log the outcome so the next agent can pick up the case.
- Give the warehouse one clear status. Use statuses such as Confirmed, Address Correction Pending, Follow-up Needed, and Cancelled. Release or hold orders according to store policy. A timeout should trigger your agreed review rule, since a missed message can also come from a legitimate buyer.
- Review failed deliveries quickly. When the courier reports a failed delivery attempt, check the reason, confirm whether the customer is still available, and request a reattempt when appropriate. Save the final outcome so you can see which problems survive the pre-dispatch checks.
Example confirmation: Hi [First name], this is [Store]. Your COD order #[Order ID] is ready to ship. The amount due on delivery is ₹[amount]. Please reply CONFIRM, CHANGE ADDRESS, or CANCEL.

What should your team do with each reply?
| Signal | Next action |
|---|---|
| Customer confirms | Record confirmation and release for dispatch if the address is complete. |
| Address needs correction | Verify the missing details, update the order record, and confirm the change before dispatch. |
| No reply on a flagged order | Route to the call queue or apply the agreed hold rule before the dispatch cutoff. |
| Customer cancels | Record the reason, update the store and warehouse queues, and stop dispatch if possible. |
How do you measure whether RTO fell by 20%?
COD RTO rate = COD shipments returned to origin ÷ COD shipments dispatched × 100. Give both groups enough time for final delivery outcomes to come in. Compare similar periods or use a concurrent comparison group with a similar courier, region, and product mix.
For example, 100 RTOs across 400 baseline shipments is 25%. If a comparable pilot sees 80 RTOs across 400 shipments, the rate is 20%. That’s a five-percentage-point drop, or a 20% relative reduction. Also track pre-dispatch cancellations, dispatch delays, and delivered orders as a share of all COD orders placed. You want fewer wasted shipments while still fulfilling legitimate orders.
How does this work for Shopify stores?
Shopify supports COD as a manual payment method. Start by separating COD orders in your order workflow and recording verification outcomes in tags or a shared queue. Ask your warehouse and support team to use the same dispatch rules. If you automate messages later, keep address changes, ownership disputes, and repeat delivery failures in a human review queue. Shopify’s guide to manual payment methods.
When does a COD order verification service make sense?
Consider outside help when your team has a repeat backlog of flagged orders or cannot follow up before dispatch. A useful handoff includes your approved scripts, order access, dispatch windows, escalation contacts, and rules for releasing or holding orders. SupportDeskLLP can help with confirmation, exception calls, order updates, and courier follow-up within your agreed workflow.
Start with your last month of COD dispatches, RTOs, and the top three courier reason codes. Talk to SupportDeskLLP about a COD verification pilot or explore our e-commerce support services and omnichannel customer support.


