'We deliver to 29,000 pincodes' is a marketing number — the operational truth is three different maps per carrier: where prepaid delivers, where COD works, and where reverse pickup runs. Your customer's pincode might exist on one and not the others.

The three coverage maps

Prepaid delivery reaches furthest — nearly every claimable pincode. COD coverage is narrower — collecting cash needs agent infrastructure. Reverse pickup is narrowest — sending a rider out for returns is cost-heavy. A 'served' pincode might be prepaid-only, which matters enormously to a COD-heavy seller.

How to check before you promise

Carrier serviceability checkers exist on their sites and inside aggregators — test the pincode for the service you intend (COD, prepaid, reverse). For your top destination pincodes, maintain a per-carrier serviceability list — it changes quarterly.

The checkout-side fix

The right place is the checkout itself — COD option hidden on non-COD pincodes, 'delivery not available' on unserved ones. A declined order at checkout is a customer saved; an impossible order shipped is an RTO.

The fallback plan

Unserved doesn't mean unshippable — a different carrier may cover it, India Post reaches everywhere, or the customer might accept a pickup-point delivery. The answer exists; it just isn't the first courier you tried.

Pakka Parcel automates exactly this — the pipeline from order to AWB without the manual steps.

See how →

The playbook

1

Map your top pincodes

Per carrier, per service type — the coverage matrix.

2

Check COD serviceability separately

The narrower map is the one that matters.

3

Filter at checkout

Unserved pincodes get prepaid-only or a polite decline.

4

Keep a fallback carrier

Unserved to one is often served to another.