Article7 min readUpdated
Checkout Address Form Design for Indian Online Stores
Checkout address form design for India: PIN code first, landmark field, saved addresses, delivery slot and every error state, with exact wording.
By Tithi Mondal, UI/UX Designer
A courier in a town near Bankura calls a customer three times. The address says "Near the temple, Main Road". There are four temples on that road. The parcel goes back, and the shopper loses a week. Many failed deliveries begin in the checkout address form, not on the road. A checkout address form is the screen where the shopper tells the store where to send the order. It is also called the delivery address screen. In India, addresses are long, informal and different in every town, so this screen needs more care than a standard form.
This guide covers the address screen and the delivery choice that follows it. For the payment screen, read UPI payment UX and checkout design. For field basics, read form design best practices.
What must the address step do?
The address step must collect an address the courier can find, confirm that the store can deliver there, and let the shopper move on in under a minute. These are three separate jobs, and the form should do them in that order.
If the store cannot deliver to a PIN code, the shopper should learn it on this screen at the latest. A check on the product page is better. The address step repeats it, because shoppers often skip the first check.
Keep the screen to one scroll on a phone for a returning shopper, and to two screens for a first-time shopper. Put a short progress line at the top: "Address, Payment, Done". Three steps feel finished. Six steps feel like work.
Which fields does an Indian address form need?
An Indian address form needs eight fields: name, phone, PIN code, house or flat, street or area, landmark, city and state, and an address type. The order matters as much as the list.
Use this order and these labels:
- Full name. "Name as on ID, for the courier".
- Mobile number. "10-digit mobile number" with +91 shown as a fixed prefix. Helper text: "The courier may call this number".
- PIN code. "6-digit PIN code". Numeric keypad.
- House or flat, building, company. "House no., building name".
- Road, area, village. "Road name, area, village".
- Landmark. "Landmark (optional)". Placeholder: "Near Kali Mandir, opposite SBI bank".
- Town or city and State. Filled in from the PIN code, but editable.
- Address type. Two buttons: "Home" and "Work". Add "Other" if you need it.
Do not add fields you will not use. Do not ask for email on this screen if the shopper already gave it. For work addresses, an optional note such as "Deliver between 10 am and 6 pm" helps.
Place the PIN code high. When the shopper types 6 digits, fill in the city and state at once and show them as plain text with an edit link. This saves typing on a small keyboard and avoids spelling mistakes in the city name. If the PIN code covers several villages or post offices, let the shopper choose the area from a short list.
Why does the landmark field matter in India?
The landmark field matters because many addresses in India have no reliable street number, and couriers find the house by asking people near a known place. A good landmark can be the difference between a delivery and a return.
Design the field so it gets used:
- Label it "Landmark" and add a clear example in the placeholder.
- Mark it optional but place it right under the street field, never hidden in a collapsed section.
- Allow at least 100 characters.
- Add a hint for villages: "Name of the nearest school, shop, temple or bus stop".
- Pass the landmark into the courier label and the delivery app, so it is not lost after checkout.
Do not make the landmark mandatory. Shoppers in apartment buildings in a city do not need it and will type "NA". A required field that gets junk is worse than an optional one that gets real answers.
How do saved addresses and the PIN code check work?
Saved addresses should appear as cards at the top of the step with one selected by default, and a "Add new address" button below them. The PIN code check runs on every address, saved or new, before the shopper continues.
For a returning shopper, the screen should look like this:
- A heading: "Deliver to".
- Address cards. Each shows name, full address, phone and a tag "Home" or "Work". The selected card has a clear border and a filled radio mark.
- On each card, small links: "Edit" and "Remove".
- A button: "Add new address".
- A primary button: "Deliver to this address".
Rules that save trouble:
- Select the last used address by default, not the first one in the list.
- If the saved address has a PIN code that is no longer served, mark the card "Cannot deliver here" and disable the button.
- Let the shopper edit an address inline without losing the cart.
- Let guests check out without an account. Save the address only if they create one after the order.
The PIN code check must give a plain answer. Valid and served: "Delivery to Bankura, West Bengal". Valid but not served: "We cannot deliver to 722101 yet. Try another PIN code or get an update when we start." Not a real PIN code: "Please check the PIN code. It has 6 digits."
How should delivery dates and slots be shown?
Show the expected delivery date for each delivery option as a short sentence, and offer a time slot only if your couriers can truly keep it. A slot that you cannot honour is worse than no slot.
Most small Indian stores ship through courier partners and promise a date, not a slot. For them, a single line is right: "Delivery by Wed, 25 Nov". If you have two speeds, show them as radio options:
| Option | Wording |
|---|---|
| Standard | "Standard delivery, by Wed, 25 Nov. Free above ₹999, otherwise ₹60" |
| Express | "Express delivery, by Mon, 23 Nov. ₹120" |
Those rupee amounts are examples for your own pricing. Use your real charges and show the total with shipping before payment.
Slots make sense for fresh food, grocery, flowers and cakes. A slot picker has two parts: a date strip for the next 5 to 7 days, and slot buttons such as "9 am to 12 pm", "12 pm to 4 pm", "4 pm to 8 pm". Grey out full slots and say why: "Fully booked". For festival days, mark the extra load: "Diwali week, slots fill early". For tracking after the order, see logistics and delivery tracking app design.
Give a date, not "3 to 5 days". The shopper should not have to count.
What errors and states must the address form handle?
Every field needs a default, focus, filled, error and disabled state, and the whole form needs a loading, saved and failed state. Put error text under the field, in the field's own colour, and never clear what the shopper typed.
Error wording that works:
- Name empty: "Enter your full name".
- Phone short: "Mobile number must have 10 digits".
- Phone starts with 0 or 1: "Enter a valid Indian mobile number".
- PIN code short: "PIN code has 6 digits".
- Address empty: "Enter your house number and building".
- Network lost: "No connection. Your details are saved on this screen. Try again when you are online".
On submit, scroll to the first error and move focus there. Do not show a pop-up listing all mistakes. For autofill, set correct field types so the phone's keyboard can offer the saved name, number and address.
What mistakes should you avoid in a checkout address form?
Avoid long forms, mandatory landmarks, address fields that reject real addresses, and hidden delivery costs. Most abandoned address steps come from effort or surprise.
- Using one single "Address" box. Couriers need separate house, road and area parts.
- Forcing capital letters or rejecting symbols like "/" and "-" that are normal in house numbers such as "12/B-4".
- Showing delivery charges only after the shopper has paid.
- Placing the PIN code last, so the shopper types everything before finding out the store cannot deliver.
I test address forms with real examples: a flat in Kolkata, a house in a village with no number, and an address with a slash in it. If the form fails any of the three, it will fail real customers. For help designing this step as part of a store, see my UI and UX design service or get in touch.
Frequently asked questions
Should the PIN code be the first field in an Indian address form?
Put it early, ideally right after name and phone. When the shopper types 6 digits, fill in city and state automatically and confirm delivery is possible.
Is the landmark field required?
No. Keep it optional but visible, with an example such as Near Kali Mandir. A required landmark gets filled with junk like NA.
How many saved addresses should a checkout show?
Show all saved addresses as cards if there are few, with the last used one selected. If there are many, show 3 and a link to view more.
Do online stores need delivery slots?
Only for products like fresh food, flowers and cakes where time matters. For most items, a clear delivery date is enough and a slot you cannot keep does harm.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.