Global Address Formats: A Developer's Guide to Handling Addresses from 195 Countries
There is no universal address. Countries order fields differently, name them differently, and even structure the underlying hierarchy differently. A form that works for the US will quietly corrupt addresses from Japan, China or Germany unless you design for it.
The structural differences that break naive forms
In the US, the order is street, city, state, ZIP. In China and Japan, the hierarchy runs largest-to-smallest — province, city, district, then street and number — and Japanese addresses have no "state" at all. Germany puts the postal code before the city. A single global form with "State (required)" and "ZIP (required)" will reject or mangle a large slice of the world.
Two practical rules
First, treat the address as free-form text plus optional structured fields, and never force fields that do not exist in the target country. Second, validate per-country rather than globally — a ZIP regex for the US is meaningless in the UK, and vice versa.
Why real sample data helps
Testing with authentic, country-appropriate addresses is the fastest way to find internationalization bugs before your users do. A generator that returns real addresses per country is exactly the kind of fixture that turns a hard-to-reproduce bug into a repeatable test case.