Postal codes are where address forms break. A field that accepts 94103 will happily reject M15 4FN, 75008 and 810-0001, and you usually find out from a support ticket. Each address here is built to its own country's format, including the postal pattern.
What you can control
- Postal codes follow the real shape for each country — five digits in the US and France, alphanumeric in the UK, hyphenated in Japan and Brazil.
- Add a secondary line (apartment, suite, unit) to check that your form and your label printer both survive it.
- Coordinates land within a few kilometres of the named city, so map pins cluster where they should.
- Switch between separate columns and a single formatted line depending on whether you are seeding a database or filling a text field.
Testing ideas
- Postal code formats. Generate UK and US addresses together. A ZIP-only regex rejects
SW1A 1AA, and a numeric column drops the leading zero from02134. - Unit lines. Turn on the unit or suite line. Shipping labels and address forms that assume one street line truncate it.
- Single-line shape. Switch to one formatted line to test parsers and geocoders that receive an address as free text.
- Coordinates. Include latitude and longitude to seed a map view and check marker clustering without calling a geocoding API.
What this is not
Street numbers and names are generated, so the addresses are structurally valid but not deliverable. Cities, regions and coordinates are real places; the buildings are not.