COD isn't all-or-nothing
Turning COD off kills volume. Leaving it on everywhere invites returns. The middle path is rules: keep COD where it works, and limit it where it doesn't. A few simple rules - by cart value, category, and pincode - filter your riskiest orders while keeping the ones that pay.
Why rules beat switching COD off
The numbers explain why COD needs rules. Amazon Shipping quotes Shipway's FY25 report: about 26% of COD orders came back to origin, against under 2% of prepaid ones. That gap tempts many sellers to drop COD. But Amazon Shipping warns that removing COD shuts out high-intent buyers who simply prefer to pay cash. In Tier-2 and Tier-3 cities, that can be a large part of your market. Rules let you keep those buyers and filter only the orders most likely to fail.
Cap COD above a cart value
High-value COD orders put the most cash at risk. A ₹3,000 parcel that comes back ties up far more stock and cash than a ₹400 one. Set a ceiling. Above it, ask for prepaid or a token. Most buyers of expensive items are happy to pay online. The few who aren't are exactly the risk you want to filter out.
Restrict COD on return-prone categories
Some categories come back more than others. Fashion and footwear, where sizing is a guess, return far more than packaged goods. If a category bleeds RTO, make it prepaid-only or add a confirmation step. Let your own return data pick the categories, not a hunch.
Block COD in high-RTO pincodes
Some pincodes return COD orders again and again. You don't have to serve COD everywhere. Keep a list of pincodes where COD is switched off and only prepaid is allowed. Buyers there can still order - they just pay online. This protects your margin without a blanket block.
Set a floor as well as a ceiling
Very small COD orders can also lose money once you count the COD fee and the return risk. A minimum cart value for COD - say ₹200 - nudges tiny orders to prepaid or to add one more item. Test the floor carefully. Set it too high and you lose real orders.
Combine rules, but keep them simple
The power is in stacking a few rules, not building a maze. High value goes prepaid. Return-prone categories go prepaid. Bad pincodes go prepaid. Everything else keeps COD. A buyer should never face a confusing checkout - just the options that make sense for their order.
Review the rules with your data
Rules aren't set once. Watch your RTO by cart value, category, and pincode every month. Tighten where returns climb. Loosen where they don't. The goal is the lowest return rate that still keeps your good COD orders flowing.
Which cart values come back most
Don't assume the priciest orders fail most often. Amazon Shipping quotes Shipway's FY25 data on RTO by order value. Orders of ₹500 to ₹1,000 came back most, at 28%. Orders under ₹500 came back at 25%, and orders over ₹1,000 at 24%. It puts the peak down to impulse buying. So a cap on big carts protects the most cash per parcel, but it will not catch most returns. Pair it with a check on mid-value orders from first-time buyers. And pull the same split from your own orders before you pick any number.
A starter set of COD rules
| If the order is | Then | Why |
|---|---|---|
| COD and above your cart cap | Ask for UPI or card | Most cash at risk per parcel |
| COD from a first-time buyer | Confirm on WhatsApp before dispatch | Screens out impulse orders |
| COD above ₹1,000 | Make a confirmation call or send an OTP | Amazon Shipping's example threshold |
| COD to a flagged pincode | Prepaid only, or one extra check | High RTO in your last 30 days |
| From a buyer who refused before | Prepaid only, or a part-payment | A known refusal history |
Show the rule before the buyer pays
A COD rule should never surprise a buyer at the last step. India's Consumer Protection (E-Commerce) Rules, 2020 ask sellers to show the payment methods on offer and any fees buyers must pay. They also ask for the total price with a breakup, including delivery charges. So if you add a COD fee, show it in the price breakup before the order is placed. If a pincode is prepaid only, say so as soon as the buyer types it in. A clear line like "COD is not available here, pay by UPI" keeps the sale. A payment option that silently vanishes loses it.
A COD fee is a softer rule
Blocking COD is not your only lever. A small COD fee keeps the option open and asks the buyer to share the cost. Razorpay notes that most couriers charge a flat fee or a percentage for each COD parcel. It suggests a nominal COD fee, plus a small discount or a payment link to move buyers to prepaid. Keep your fee small and round so it feels fair. Then track two numbers each month: how many buyers switch to UPI, and how many drop off at checkout. If drop-offs climb, the fee is too high.
Block a whole area with a prefix
You don't have to list bad pincodes one at a time. Some tools let one rule cover every pincode that starts with the same digits. That helps when a whole series of codes keeps refusing parcels. But go slowly. A wide block also stops your good buyers in that area. Start with the exact pincodes in your data. Widen to a prefix only when returns spread across codes in the same series. Then look again after a month, since a new courier can fix an area that once looked hopeless.
Mistakes that make COD rules backfire
The most common mistake is adding too many rules at once. Then you can't tell which one cost you orders. Change one rule, wait a few weeks, and compare. Another mistake is hiding COD with no reason given. The buyer thinks your store is broken and leaves. A third is judging by RTO alone. A rule that cuts returns but loses twice as many good orders is a bad trade. Watch delivered orders and delivered revenue, not just the return rate.
Where your store helps
The Storemate gives you the pincode piece directly. Mark which pincodes are serviceable, set COD availability and shipping fees per area, and keep a COD-blocked list for the worst ones. Add a COD cap on cart value and a COD switch on each product, and your riskiest orders quietly move to prepaid while the rest keep converting.