Operator Notes · 3 min read

What Our Own COD Data Showed About Returns

Return-to-origin is not one number. Segmenting our own COD orders by traffic source and pincode changed what we did about it.

The short answer

Treating return-to-origin as a single blended rate hides where the losses actually come from. Segment COD orders by acquisition channel first, because impulse-led social traffic consistently fails at a higher rate than search intent, then by pincode using your own delivery history rather than a purchased list. The remedies that follow are targeted and cheap. A blanket response, such as switching COD off entirely, usually costs more than it saves.

The blended number tells you nothing useful

A single COD failure rate across the whole store is an average of several very different behaviours. Returning customers and branded search traffic barely fail at all. Cold prospecting from social fails at a materially higher rate, because the order was placed on impulse with no payment behind it.

Reporting one number means the campaign generating most of your losses looks the same as the one generating none of them.

Segment by channel first

Channel is the cut that usually produces the largest difference, and it is the one you can act on immediately, because COD rules can be applied differently by campaign.

A store can reasonably offer COD freely to returning customers and branded search, while requiring confirmation or restricting it above a value threshold on cold prospecting traffic. That is not a customer experience compromise. It is applying friction where the risk is.

Then segment by pincode, using your own history

Purchased pincode blocklists are built from someone else's customers buying someone else's products. Your own delivery history is a far better predictor, and after a few hundred orders you will have enough to identify the pincodes where failure is consistent rather than incidental.

The important distinction is consistency. One failed delivery in a pincode is noise. Repeated failures across different orders and different months is a pattern worth acting on.

What actually moved the number

Each of these moves the rate by a few percentage points. None of them is dramatic alone. Together they are the difference between COD being survivable and not.

  • A prepaid incentive, framed as a saving rather than a COD penalty
  • Confirmation before dispatch, with WhatsApp getting noticeably better response than SMS
  • An order value ceiling on COD, since high-value failures hurt most
  • Address quality validation at checkout, which catches a share of undeliverable orders before they ship

Key takeaways

  • Segment RTO by channel before doing anything else
  • Use your own delivery history rather than a purchased pincode list
  • Report revenue on delivered orders, or your ROAS is fiction

Reading these regularly? Make Rangblaze a preferred source on Google and our posts surface higher in your own results.

FAQ

Questions that follow this one

  • Rarely. Removing it usually costs more in lost orders than it saves in returns, because a large share of Indian buyers still will not prepay to an unfamiliar brand. Restrict it selectively instead.

  • Slightly, and it removes disproportionately more of the orders that would have failed anyway. Most brands find the trade clearly worthwhile.

Your Brand Could Be Next

Your brand could be next

Send a few details and we will reply on WhatsApp with a first read on what we would do, before any talk of fees.

No cold calls and no email sequences, so you set the pace.