Delivering to all pincodes in India is less a promise than a data question: for each six-digit PIN code, does at least one delivery partner serve it, for the service you need, from where you ship, at the weight you ship, at a price you can bear? "All India pincodes" is a common marketing claim, but couriers and aggregators quote different pincode counts and rarely say whether they mean prepaid delivery, cash on delivery, reverse pickup or all three. The only claim that matters to your business is whether the pincodes your customers live in are serviceable for the services you offer, and the only way to know is to check, store and re-check the data.
This guide explains how pincode serviceability works, from what a PIN code identifies to how couriers decide what they serve, how a store should check a pincode at each step of the journey, what to do when a customer's pincode is not served, how to keep pincode data clean for tax and delivery, how to audit coverage properly, and which metrics reveal gaps early. It describes how ShopMate's pincode check works, including its limits, and it is blunt about what "all pincodes" can and cannot mean. The numbers in the worked examples are assumed for illustration.
Quick answer: Treat serviceability as data you verify by service type, not a slogan. Check the customer's pincode on the product page and again at checkout, use more than one delivery partner so the union of their coverage reaches more pincodes, give unserved customers a clear message and an alternative, derive the state from the pincode for tax, audit coverage with a stratified sample of pincodes every quarter, and avoid claiming "all pincodes" unless you can show it.
What a PIN code identifies
The Postal Index Number is a six-digit code introduced by India Post in 1972. According to Wikipedia, the first digit identifies one of nine postal zones, the second a sub-zone, the third together with the first two a sorting district, the fourth a service route within the sorting district, and the last two the delivery office (Wikipedia, Postal Index Number). Of the nine zones, eight are regional and one, with first digit 9, is functional, for the Army Postal Service. Two facts matter for sellers:
- A PIN identifies a delivery office, not a house. One PIN can cover many streets, villages or apartment complexes, and a courier agent still has to find the door.
- A PIN is a postal unit, not a courier's unit. Private couriers build their own networks of hubs and delivery areas and decide, PIN by PIN, which they serve.
India Post publishes lists of post offices and pincodes by postal circle on its website; its pincode list page offers downloadable documents such as a list of post offices and pincodes for a circle (India Post, Pincode List, read on 3 October 2026). That is a reference for what exists, not a statement of who will deliver there.
"Serviceable" has many meanings
When a courier says a pincode is serviceable, ask: for what? A complete serviceability record has several dimensions.
| Dimension | Question | Why it matters |
|---|---|---|
| Forward delivery, prepaid | Will the courier deliver a prepaid parcel here? | The basic service |
| Cash on delivery | Will the agent collect cash here, and up to what amount? | Some pincodes are served only for prepaid parcels |
| Reverse pickup | Will the courier collect a return from here? | Often narrower than forward coverage |
| Pickup (origin) | Will the courier collect from my address? | Your own location may not be served by every courier |
| Weight and size limits | Is a heavy or bulky parcel accepted here? | Remote delivery points may have limits |
| Out-of-delivery-area surcharges | Is delivery here served at a higher rate or with extra time? | Changes your cost and promise |
| Service level | Express, surface or air? | Affects time and price |
| Special handling | Can fragile, liquid or high-value parcels go here? | Some categories are restricted |
| Time | Is the data current, and does it vary by day? | Networks change; holidays and weather affect service |
An honest claim names the dimensions. "We deliver prepaid parcels up to 5 kg to 98% of the pincodes our customers have ordered from, with cash on delivery to 92% and reverse pickup to 79%" tells a customer something. "We deliver to all pincodes" does not.
Why vendor pincode counts differ
Four aggregators we read describe their reach with different figures on their own homepages: Shiprocket states 19,000+ unique pincodes, NimbusPost 29,000+ pincodes, iThink Logistics 29,000+ serviceable pincodes and Shipway 19K+ pincodes (see our guide to Shiprocket versus other logistics aggregators; figures as read on 3 October 2026). These cannot all measure the same thing. Possible reasons include counting pincodes served by any courier versus by a particular service, counting only prepaid, counting different dates, or counting different things as a pincode. The numbers are marketing claims we have not tested, and the lesson is that no number substitutes for testing your customers' pincodes.
How a courier decides what it serves
Behind a serviceability answer is a network. A courier has origin hubs, line-haul routes, destination hubs and delivery agents who each cover a defined area. For a given origin, destination and service, the courier's system checks whether a route exists, whether a delivery agent covers the destination, whether the service is enabled there, and whether the parcel's weight and payment type are allowed. The answer is published as a list or through an API that takes the pincode, and often the weight, the origin and the payment type.
An aggregator sits on top. It holds connections to several couriers, and its answer for a pincode is usually the union: serviceable if at least one connected courier serves it, with a rate card listing the couriers that do. That is why connecting more couriers widens coverage, and why coverage can change without warning when a courier changes its network or a connection breaks.
Where a store should check a pincode
Serviceability is not a single check. A well-designed store checks at several points, each with a different purpose.
| Point | Purpose | What to show |
|---|---|---|
| Product page | Let the customer know before they invest effort | Whether the pincode can be served, and an estimated delivery window |
| Cart or checkout address step | Catch addresses entered after the product page, or changed later | The same answer, tied to the address; block or warn if unserved |
| Order confirmation | Make sure the order can actually be shipped | An internal check; flag orders that cannot be shipped |
| Shipment creation | The courier's final acceptance | Handle rejections by reassigning to another courier or contacting the customer |
The checks can disagree. A product-page check might use a default weight and your default origin, while the actual shipment uses the real weight and a different pickup address. Design for that: re-check at checkout with the real cart weight where possible, and have a manual queue for orders whose shipment creation fails, with a clear way to contact the customer and either reroute or refund.
A fail-open or fail-closed choice
When the courier's API is slow or down, a store must decide what to tell the customer. Fail-closed means saying "not serviceable" or "could not check", which protects you from promising what you cannot deliver but may turn away customers during an outage. Fail-open means assuming the pincode is serviceable and checking later, which keeps sales flowing but risks orders you cannot ship. The right choice depends on your risk tolerance, and a sensible compromise is to say "could not check, please try again" and retry, while logging the failure so you can see how often it happens.
How ShopMate's pincode check works
ShopMate's site states that its shipping covers all India pincodes through 40+ partners and includes a pincode serviceability check (ShopMate). In the product, the storefront calls a public serviceability endpoint with the customer's six-digit pincode, which returns whether the pincode is serviceable and a cash on delivery flag. The behaviour depends on how the merchant has set up shipping:
- Format check. A pincode that is not exactly six digits is rejected with an error.
- Shiprocket mode. The store asks Shiprocket for rates from the merchant's default warehouse pincode to the customer's pincode for a standard 0.5 kg parcel, and treats the pincode as serviceable if any rates are returned.
- Delhivery mode. The store asks Delhivery's pincode serviceability service and treats the pincode as serviceable if the delivery codes in the response include it.
- Both connected. A pincode is serviceable if either provider covers it.
- Manual mode. If neither provider is connected, any valid pincode is treated as serviceable as long as at least one shipping partner is active, because there is no live check.
- If a provider cannot be reached, the store reports the pincode as not serviceable, which is a fail-closed design.
Points to understand when you use it:
- The cash on delivery flag reflects the store's cash on delivery setting, not a courier-level check that cash can be collected at that pincode, so confirm pincode-level COD coverage with your courier. If you set a minimum order amount for cash on delivery, ask the team how the product-page note behaves, because the check is made without an order total.
- The check is made from the default warehouse at a standard weight, so heavy or oversized parcels and merchants who ship from more than one origin need extra checks.
- The check does not tell the customer whether reverse pickup is available at their pincode.
- The coverage you get is the coverage of the connected providers, which are Shiprocket and Delhivery; India Post is not an integrated provider.
Ask the team to demonstrate the check for a pincode you know is served, one you know is not, and one in a remote area, and to explain how the results compare with what the courier says.
Running a pincode check as a reliable service
If you build or evaluate a pincode check, think of it as a small service with its own engineering concerns. Whether you build it yourself or buy it inside a platform, ask how each is handled.
| Concern | Good practice | Why it matters |
|---|---|---|
| Speed | Respond in well under a second from the customer's point of view, using a cache for recent answers | A slow check makes the product page feel broken |
| Caching | Cache answers per pincode, origin and service for a short, defined time | Reduces load on courier APIs, but stale data can mislead; choose the time with care |
| Rate limits | Respect each courier's limits and queue or back off when you hit them | Provider throttling looks like "not serviceable" to the customer |
| Timeouts and retries | Set short timeouts and retry once, then return a clear "could not check" instead of a wrong answer | Avoids false negatives during an outage |
| Provider errors | Distinguish "not served" from "could not check" in logs and in what you tell the customer | Otherwise outages look like coverage gaps |
| Credentials | Store provider credentials securely and detect when they expire or are revoked | A broken connection should alert you, not silently turn pincodes red |
| Observability | Log each check with pincode, result, provider and latency; chart failures and slow responses | Lets you see problems before customers report them |
| Abuse protection | Rate-limit public checks per visitor | The endpoint is open to anyone and can be hammered |
| Consistency | Use the same logic in the product-page check, the checkout and the shipment creation | Prevents "served" on the page and "rejected" at dispatch |
The most common failure is the false negative: the check says "not serviceable" because of a timeout, an expired credential or a rate limit, not because the pincode is unserved. A store that cannot tell the difference will turn away real customers during every provider hiccup and never know why. Make "could not check" a separate state, log it and alert on a rising rate.
Fourteen test cases for any pincode check
Whatever platform you use, run these cases and write down what happens. They reveal most of the weaknesses.
- A pincode in a major metro that you know is served for prepaid and COD.
- A pincode in a small town that you know is served by one courier but not another.
- A pincode in a remote or hard-to-reach area.
- A pincode served for prepaid but not for cash on delivery, if you can find one.
- A pincode served for forward delivery but not for reverse pickup.
- A pincode with a valid six-digit format that does not exist.
- Five digits, seven digits, letters and spaces, to test validation and the error message.
- A pincode from the Army Postal Service zone, whose first digit is 9, to see how it is handled.
- A pincode after you change the default pickup address.
- A heavy or oversized parcel at the same pincode as a light one, if your platform lets you check by weight.
- One courier's connection switched off or its credentials removed, to see whether the check reports "could not check" or "not serviceable".
- The same pincode checked twice in a row, to see whether the answer is cached and for how long.
- A pincode entered at checkout that differs from the one checked on the product page.
- A pincode whose state does not match the state the customer selected.
Record the expected result for each, and re-run the list whenever you add a courier, change your pickup address or change your platform's shipping settings.
Pricing differences by pincode
Serviceable does not mean equally priced. Even within served pincodes, freight varies by zone and weight, and remote or hard-to-reach delivery points may carry out-of-delivery-area surcharges. Decide how you handle this:
- Absorb it. Keep a single price and average the cost, which is simple but loses margin on expensive pincodes.
- Pass it through. Charge a shipping fee that varies by zone, as in our regional playbook, which keeps contribution consistent.
- Set a minimum order value for expensive pincodes so freight is a smaller share of the sale.
- Offer prepaid only where cash on delivery returns make the economics poor.
Whichever you choose, show the cost before payment. A surprise charge at the last step is a leading reason for abandoned carts and refused parcels. Our guides to selling across all India and to pan-India shipping costs show how to model the numbers.
When coverage changes without warning
Networks are not static. A courier may close a hub, add a route, change its cash on delivery policy, suspend service after a flood or add a new area. Your own situation changes too: a new warehouse, a new product weight class, a new courier connection. Build the habit of detecting change:
- Run the fourteen test cases above each quarter, and after any change in your shipping setup.
- Watch the "could not check" and shipment-creation-failure rates for sudden jumps.
- Subscribe to your couriers' service notices and ask your account contact to flag network changes.
- Keep a second courier connected and tested, so that a failure of the first reduces coverage and does not remove it.
When the pincode is not served
An unserved pincode is a lost sale unless you offer something. Options, from cheapest to most involved:
- A clear message. Say plainly that you cannot deliver to this pincode yet, without blaming the customer. Do not leave them to discover it at payment.
- A "notify me" option. Collect an email or phone number, with consent, to tell the customer when you reach their area. This turns a lost visit into expansion data.
- A nearby collection option. Offer delivery to a neighbouring serviced pincode where the customer can collect, if that suits your product.
- A fallback carrier. Add a courier or postal service that serves the pincode, which our guide to logistics for tier 2 and tier 3 towns discusses. India Post's own page for Speed Post Parcel describes a track-and-trace service and a cash on delivery service for ecommerce and online sellers, over a network of about 165,000 post offices according to Wikipedia (India Post, Speed Post Parcel (Domestic); Wikipedia, India Post).
- Prepaid-only or surcharge options for pincodes that are served but at higher cost or lower quality.
Treat unserved checks as demand data
Every failed pincode check is a customer who wanted to buy. Log them. As an illustration with assumed numbers, suppose you receive 1,000 pincode checks a week and 8% are unserved, which is 80 checks. If the ten most-requested unserved pincodes account for 40% of those, that is 32 checks a week concentrated in ten places. Those ten are the first candidates for a new courier, a fallback or a local partner. Without logging, you would never know.
Keep your pincode data clean
Pincode data affects delivery, tax and analytics, so it deserves discipline.
- Validate format. Six digits, numeric, with spaces trimmed. Reject obvious errors at the form.
- Derive the state and city from the pincode, and show them to the customer for confirmation, instead of trusting a free-text state. This matters for tax: for goods delivered to another state, the invoice carries IGST and must show the place of supply with the name of the State (CGST Rules, 2017, Rule 46), and a wrong state means a wrong tax split. With assumed numbers, if 2% of 1,000 orders have a state that does not match the pincode, that is 20 orders a month with a questionable tax treatment.
- Maintain a master table of pincodes with state, district and source, using India Post's published lists as a reference, and record the date it was last updated.
- Handle new and changed pincodes. The postal system changes, so a valid new pincode may be missing from your table. Allow it with a flag rather than rejecting it.
- Keep the original and the normalised value, so you can see what the customer typed.
- Log and review mismatches between the pincode, the city and the state.
Our guides to GST invoices for online stores and to automated GST billing explain how the delivery state drives the CGST, SGST or IGST split.
Audit your real coverage: a stratified sample
To know how well you cover your customers, test a sample designed to reflect them, not just the easy pincodes. A method:
- Group your pincodes into strata, such as major metros, other cities, smaller towns, rural and remote or hard-to-reach areas, including the north-east, hill areas and islands.
- Sample from each, including pincodes where you have no orders yet but want to sell.
- Test every courier for every service you offer, from every pickup address you use, at representative weights.
- Record the results, including surcharges and times.
- Weight the results by your orders, not by the number of pincodes, so the coverage figure reflects your customers.
- Repeat every quarter, and after any courier change.
A worked example: pincode coverage versus customer coverage
The figures below are assumed. A seller tests 300 pincodes and finds that its combined couriers serve them for prepaid delivery as follows:
| Stratum | Pincodes tested | Served | Coverage | Share of the seller's orders |
|---|---|---|---|---|
| Major metros | 100 | 99 | 99% | 50% |
| Other cities | 100 | 95 | 95% | 30% |
| Smaller towns and rural | 60 | 51 | 85% | 15% |
| Remote and hard to reach | 40 | 24 | 60% | 5% |
| Total or weighted | 300 | 269 | 89.7% of pincodes | 93.75% of orders |
The pincode coverage is 269 of 300, which is 89.7%. Weighted by the seller's orders, it is 0.50 × 99% plus 0.30 × 95% plus 0.15 × 85% plus 0.05 × 60%, which is 49.5 + 28.5 + 12.75 + 3 = 93.75%. The two figures differ because the seller's customers are concentrated where coverage is best. Both are useful: the first shows how far the network reaches, and the second shows how many of your customers you can actually serve. Neither is "all pincodes", and an honest statement uses the numbers you can defend.
Promising "all India" honestly
Customers rely on what you say, and so do regulators. Under the Consumer Protection (E-Commerce) Rules, 2020, sellers must display specified information and honour obligations on refunds and delivery (see Trilegal's analysis), and an inaccurate claim of nationwide delivery invites complaints and refunds. A safer approach:
- Say "delivery across India" only if your own tests support it, and pair it with a pincode check so the customer can see the answer.
- State plainly any limits: cash on delivery availability, weight limits, extra charges and longer times for remote areas.
- Give an estimated delivery window for the pincode, built from your delivery history.
- Keep your policy pages consistent with what the checkout actually does.
Metrics that reveal gaps early
| Metric | How to calculate | What it tells you |
|---|---|---|
| Serviceable share of checks | Pincode checks that return serviceable ÷ all checks | How often customers hit a wall |
| Unserved demand by pincode | Count of unserved checks, by pincode | Where to add coverage |
| Check-to-order conversion | Orders ÷ pincode checks, served versus unserved | How much the check affects buying |
| Shipment creation failures | Orders whose shipment could not be created ÷ orders | Mismatch between the check and the courier |
| Reroute rate | Orders moved to another courier ÷ orders | Reliability of your first choice |
| NDRs caused by service issues | Non-delivery reports citing unserviceable or out-of-area ÷ shipped | Coverage gaps surfacing late |
| Coverage by service | Pincodes served for prepaid, COD and reverse ÷ pincodes tested | The shape of your reach |
| Data freshness | Days since the last coverage audit and master table update | Risk of stale answers |
A 30-day plan
| Days | Focus | Deliverable |
|---|---|---|
| 1 to 7 | Audit | A stratified sample of at least 300 pincodes tested across your couriers and services; coverage by pincode and weighted by orders |
| 8 to 14 | Fix the check | Pincode validation; state derived from the pincode; messages for unserved, unreachable and partially served pincodes; logging of every check |
| 15 to 21 | Close gaps | The top unserved pincodes listed; a fallback carrier or local partner piloted for them; policies updated |
| 22 to 30 | Report and repeat | A dashboard of the metrics above; a quarterly audit scheduled; website claims reviewed for accuracy |
Common mistakes
- Believing "all pincodes". Ask which services and test your customers' pincodes.
- Checking once. Re-check at checkout and at shipment creation.
- Using free-text states. Derive the state from the pincode for tax and analytics.
- Ignoring weight and origin. A check at a default weight may not hold for your real parcels.
- Not logging unserved checks. You miss your best expansion data.
- Treating COD like prepaid. Cash collection coverage is separate.
- Failing silently. Tell customers when a check cannot be completed.
- Overpromising in advertising. Use claims you can prove.
Frequently asked questions
Do couriers really deliver to all pincodes in India?
No courier can honestly promise every pincode for every service. Coverage is stated by pincode and by service type, and it varies by origin, weight and payment type. Test your customers' pincodes for prepaid, cash on delivery and reverse pickup.
What does serviceable mean?
It means a courier will handle a particular service for a pincode, such as prepaid delivery, cash on delivery or reverse pickup. A pincode can be serviceable for one service and not another, and may carry surcharges or limits.
How many pincodes are there in India?
This guide does not state a total because sources differ and the system changes. India Post publishes lists of post offices and pincodes by circle, which are a reference for what exists. Courier and aggregator counts describe what they serve, and different vendors quote different figures.
How should I handle a customer whose pincode is not served?
Tell them clearly at the product page, offer to notify them when you reach their area, consider a collection point in a nearby served pincode, add a fallback carrier where possible and log the demand to guide expansion.
How do I check pincode coverage for my business?
Build a stratified sample of pincodes that reflects your customers and your targets, test every courier for every service from your pickup addresses, weight the results by your orders and repeat each quarter.
Does the pincode decide my GST?
The delivery state does, and the pincode identifies it. Deriving the state from the pincode avoids mismatches, which matters because inter-state sales carry IGST and the invoice must show the place of supply with the name of the State.
How does ShopMate check pincodes?
The storefront calls a pincode check that uses Shiprocket's rate lookup from the merchant's default warehouse at a standard weight, or Delhivery's serviceability service, or both, and reports whether the pincode is serviceable. The cash on delivery note follows the store's COD setting. Ask the team to demonstrate it for your pincodes.
Can I deliver in areas that couriers do not serve?
Sometimes, through a postal service, a local delivery partner or a collection point, each with its own cost and risk. Pilot with small volumes, record the outcomes and decide from the data.
Sources and further reading
Postal and carrier facts come from the public references below, read on 3 October 2026, and vendor coverage figures are marketing claims we have not tested. Coverage, rules and platform features change. Sources were last checked on 3 October 2026.
- Wikipedia, Postal Index Number and India Post; India Post, Pincode List and Speed Post Parcel (Domestic).
- Aggregator homepages: Shiprocket, NimbusPost, iThink Logistics and Shipway, for the coverage figures each states.
- Central Board of Indirect Taxes and Customs, CGST Rules, 2017, Rule 46 (Tax invoice); Trilegal, Analysis: Consumer Protection (E-Commerce) Rules, 2020.
- ShopMate, home, about and pricing pages, for ShopMate shipping features and pricing.
Disclaimer: This article is for general information only and is not legal, tax or financial advice. ShopMate is the publisher of this guide and has a commercial interest in the platform it describes. Carrier, aggregator and postal names are used only to describe facts published on their own pages; this guide is independent of them. All worked examples use assumed figures for illustration. Coverage, tax rules and platform features change, and your situation may differ. Consult a qualified chartered accountant or legal professional before making decisions.
Check your own pincodes in a demo
Bring a list of your customers' pincodes. ShopMate offers a 7-day free trial and a demo call, where you can see the pincode check, courier selection for Shiprocket shipments, one-click shipments with Delhivery and the reports, and test how your toughest pincodes behave. Book a free demo, review the pricing details, or read more about ShopMate.