A customer in Bengaluru types "Bangalore" in the city field at your Shopify checkout. The order goes to Shiprocket. The waybill says Bangalore. Your carrier's sorting facility has the zone indexed as Bengaluru. The package gets held at the hub while the system tries to resolve the mismatch. Delivery is delayed 2–3 days. The customer emails you asking where their order is. You spend 20 minutes investigating a problem that should never have existed.
This happens thousands of times every day on Indian Shopify stores. It is one of the most common causes of avoidable delivery failures — and Shopify's default checkout does nothing to prevent it.
The scale of India's city spelling problem
India has over 6,000 cities and towns. Most major cities have multiple accepted spellings across different courier systems:
- Bengaluru / Bangalore
- Mumbai / Bombay
- Chennai / Madras
- Kolkata / Calcutta
- Thiruvananthapuram / Trivandrum
- Kozhikode / Calicut
- Visakhapatnam / Vizag / Vishakhapatnam
- Gurugram / Gurgaon
Smaller towns and tier-2 cities have even more variation. And different courier companies use different spellings in their internal databases — what Delhivery accepts, Bluedart may reject.
Your customers do not know which spelling their courier requires. They should not have to.
Three ways wrong city names cost your store money
Automatic waybill rejection
Most courier APIs run automatic address validation when a waybill is created. If the city name does not match an entry in their database, the waybill is flagged or rejected. Your team has to manually intervene, rebook the shipment, and update the address. At 10–20 incidents per day on a high-volume store, this consumes significant operations time.
Hub holds and delayed delivery
Even if the waybill is accepted, mismatched city names can cause the package to be held at a sorting hub while the address is verified manually. A next-day delivery becomes a 3–4 day delivery. The customer calls your support team. You issue a partial refund as goodwill. Every step is a preventable cost.
Undeliverable returns
In the worst case the package is returned as undeliverable because the address cannot be matched to a valid delivery zone. You pay return shipping. The customer is frustrated. You lose the sale and potentially the customer relationship permanently.
Why Shopify cannot fix this on its own
Shopify's checkout city field is a free-text input with no validation layer. The platform has no database of Indian cities or courier-compatible spellings. This is not a bug — it is a design decision made for Western markets where address validation works at the postcode level.
In India, pincodes do not map cleanly to single cities. The same pincode can serve multiple towns and neighbourhoods. City-level validation is the only reliable solution.
City Dropdown: the fix
City Dropdown replaces Shopify's city text field with a validated dropdown of cities matched to your logistics providers' address databases. Customers pick their city from a list — no spelling variations, no rejected waybills, no address-related delivery holds.
When a customer selects their pincode, City Dropdown auto-fills the city name in the exact format your logistics provider expects. For UAE and Gulf customers, the same system works for emirates and major delivery zones.
The app installs in under 5 minutes with no theme code changes. It adds no load time to your checkout — the dropdown loads asynchronously alongside the standard checkout flow.
What merchants see after installing City Dropdown
- Address-related RTO incidents drop to near zero
- Fewer manual waybill corrections (saves 30–60 min/day for high-volume stores)
- Reduction in support tickets about delayed delivery
- Cleaner address data in Shopify analytics and CRM exports
At $7.99/year — approximately ₹670 — City Dropdown pays for itself the first time it prevents a single address-related return. For most stores it prevents 5–20 per month.