Pincode-based COD blocking is the single most effective intervention for reducing Shopify RTO rates in India. It is more targeted than removing COD entirely, more scalable than manually reviewing every order, and more effective than generic cart value thresholds alone. This guide covers the complete implementation: identifying your target pincodes, configuring the blocking rules, and monitoring results.

Why pincode blocking works better than other approaches

COD fraud in India is geographically concentrated. Analysis of merchant RTO data consistently shows that 15–25 specific pincodes account for 60–70% of all returns in any given store. These high-RTO pincodes are not random — they correlate with specific market dynamics: high population density of young first-time buyers, concentrated areas of impulsive mobile shopping, or specific logistics challenges that make genuine non-delivery more common.

Blocking COD only for these specific pincodes removes the majority of your fake orders while leaving COD available for the vast majority of your customers in lower-risk locations. The surgical precision is what makes it effective — you are not penalising your entire customer base for the behaviour of a small subset.

Step 1: Identify your high-risk pincodes

You need 60–90 days of delivery outcome data. Here is how to extract it from the three most common logistics platforms:

Shiprocket: Log in → Reports → Shipments → Filter by date range → Filter status to "RTO" → Export CSV. The CSV includes the destination pincode for each returned shipment.

Delhivery: Log in → Reports → RTO Report → Set date range → Download. The report includes pincode-level breakdown.

Ekart/direct carrier: Go to your account's analytics or reports section → delivery performance → export with pincode data.

Once you have the CSV, create a pivot table in Excel or Google Sheets:

  1. Column A: Pincode
  2. Column B: Total dispatched orders to that pincode (count from your full shipment data)
  3. Column C: Total RTO orders from that pincode (count from your RTO data)
  4. Column D: RTO rate (=C/B)
  5. Column E: Total RTO cost (=C × your average per-incident cost, typically ₹300)

Sort by Column E (total RTO cost) descending. The top 20 rows are your highest-priority blocking targets. These are the pincodes costing you the most money, not just the highest percentage rates.

Step 2: Configure COD Blocker rules

Install COD Blocker from the Shopify App Store. Initial setup takes approximately 20 minutes.

Add your block list:

  1. Go to COD Blocker → Pincode Rules
  2. For up to 20 pincodes: add individually using the "Add pincode" field
  3. For 20+ pincodes: prepare a CSV file with one pincode per row, no header. Upload via the "Import CSV" button
  4. Save your rules

If you do not yet have your own 90 days of data: COD Blocker includes a built-in India high-risk pincode database compiled from aggregate merchant data. Import this as your starting point and refine over time as your own data accumulates.

Add a cart value rule (recommended):

  1. Go to COD Blocker → Cart Value Rules
  2. Set a maximum cart value for COD — ₹3,000 is a common starting point for most categories
  3. This catches high-value fake orders from pincodes not yet on your block list

Step 3: Test before going live

Before activating your rules, test the blocking from a customer perspective. Use Shopify's customer preview mode or create a test customer account:

  • Add items to cart, proceed to checkout, enter a blocked pincode → COD should not appear in payment options
  • Enter an unblocked pincode → COD should appear normally
  • Enter a cart above your value threshold → COD should not appear regardless of pincode
  • Log in as a "trusted" tagged customer → COD should appear even for a blocked pincode

If any test fails, review your configuration before activating. A misconfigured rule that blocks COD for all customers will impact your conversion rate significantly.

Step 4: Tag risky and trusted customers

Complement your pincode rules with customer history rules for maximum effectiveness:

Tag customers with RTO history: When you process a returned order in Shopify, open the customer record and add the tag rto-history. In COD Blocker settings, configure this tag to trigger COD restriction. Future orders from this customer will require prepaid regardless of their pincode.

Tag trusted customers: For your long-term, reliable customers — those who have placed 5+ orders and always accepted delivery — add the tag trusted. In COD Blocker, configure this tag as a whitelist. These customers always see COD regardless of their pincode or cart value.

Step 5: Monitor and refine monthly

COD fraud patterns evolve over time. New high-RTO pincodes emerge. Existing patterns shift. Maintain a monthly review routine:

  • Pull last 30 days of RTO data
  • Add any new pincodes above your threshold to the block list
  • Check whether your overall conversion rate has changed materially (more than 2–3% drop indicates over-blocking)
  • Review your COD/prepaid ratio — is it shifting in the right direction?

Expect to see RTO rate improvement within the first 7 days. Full impact of the configuration is usually visible within 30 days once orders from the first week have completed their delivery cycle.