Address Fields in Online Forms Explained

An address form is a conversation: it asks for the minimum needed to place a parcel in the right hands. The fields below form a sensible baseline for a worldwide audience.

The core fields

• Country: ask first, because the rest of the form depends on it.
• Recipient name: the person or organisation.
• Address line 1: building number and street, or whatever the destination uses. See address line 1 and address line 2.
• Address line 2: unit, floor, building name or extra detail.
• City or town.
• Region: state, province or county, shown only where relevant.
• Postal code: shown only where the country uses one.
• Phone number: so the carrier can reach the recipient.

Optional but useful

• Locality or district: for places where it is a normal part of the address.
• Delivery notes: gate codes, landmarks, preferred time.
• A map pin or location code: to identify the exact spot where the written address is ambiguous.

Fields that should adapt to country

Labels, order and requirements change with the country. A form that always asks for "State" and "ZIP" will confuse users elsewhere. Labels such as "County", "Province", "Postcode" or "Postal code" should follow the country selection. See postal code format vs address format.

Technical considerations

• Store postal codes as text so leading zeros and letters survive.
• Allow Unicode characters and sufficient length.
• Avoid forcing capitals or stripping punctuation.
• Keep fields separate in the database so you can reformat later.

Common mistakes in forms

1. Requiring a house number where none exists.
2. Limiting field length too tightly.
3. Rejecting valid postal codes through an overly strict pattern.
4. Asking for a region in countries without one.

See good address form design for how to avoid these.

Summary

Ask for country first, show only relevant fields, label them in local terms and store them separately. A short form that adapts is better than a long one that does not.