Playbooks

Pincode serviceability and RTO: which areas to flag

The same product sells cleanly in one pin code and comes straight back from another. Here's how to tell which areas are worth shipping COD to, which need a prepaid-only rule, and how to set it up without turning good customers away.

Illustration: pincode serviceability and RTO across India
Vikram Iyer
Logistics & Ops
8 Jul 2026 · 7 min read

Why one pin code delivers and another bounces

Not all delivery areas behave the same way. A pin code has its own courier coverage, its own delivery reliability, and its own history of orders that stick versus orders that come back. Two customers can order the same product on the same day, and the one in a high-RTO pin code is far more likely to become a return — for reasons that have nothing to do with your product. Once you can see delivery at the pin-code level, you can stop guessing and start setting rules.

First question: can the courier even deliver here?

Serviceability comes before everything else. For any pin code, you want to know three things: will a courier deliver there at all, is COD allowed, and how long will it take. Some pin codes are prepaid-only by the courier's own rules. Some add two or three days to the ETA. Showing a realistic delivery date at checkout — instead of a hopeful one — sets the right expectation and cuts the cancellations that turn into returns.

Serviceable isn't the same as safe

A pin code can be fully serviceable and still bleed you dry. The courier reaches it, but a large share of COD orders there come back — wrong addresses, buyers not home, or areas where COD refusal is simply common. These are the pin codes worth flagging. You're not looking for places you can't ship to; you're looking for places where shipping COD, specifically, is a bad bet.

How to find your high-RTO pin codes

Pull your last few months of orders and group returns by pin code. Ignore any pin code with only a handful of orders — the numbers are too small to trust. For the rest, compare each pin code's RTO rate against your store average. The ones sitting well above it, month after month, are your flag list. This is a pattern you watch over time, not a one-off snapshot.

What to do with a risky pin code — don't just block it

Blocking a pin code throws away good customers to stop the bad ones. There are gentler tools. Make the risky pin code prepaid-only, so buyers can still order — just not on COD. Or keep COD but ask for a small advance token. Or raise the minimum cart value for COD there. Each of these keeps the door open for the customers who pay, while filtering out the orders that were never going to be accepted.

Catch address problems at checkout

A lot of pin-code trouble is really address trouble, and it's cheapest to fix before you ship. Validate the 6-digit PIN so it matches a real serviceable area. Ask for a landmark in areas where addresses are hard to find. A checkout that quietly rejects an impossible PIN or a blank landmark stops the return at the source, before you've spent a rupee on shipping.

Turn your findings into standing rules

The goal is that this runs without you thinking about it. Your flag list becomes a set of rules: these pin codes are prepaid-only, these carry a COD fee, these get a longer ETA. New orders then follow the rules automatically, and you revisit the list every month or two as areas improve or slip. The work is in setting it up once; after that it protects your margin on every order.

Where a store platform helps

You can track this by hand, but pin-code rules are much easier when your store already knows them. The Storemate has pin-code serviceability built in — per-area ETA, COD availability and fees, plus a list of pin codes where you'd rather block COD. Set your rules once and every checkout respects them, so the risky areas stop quietly draining your returns budget.