eg

Address form patterns

The address form is the heaviest data-entry moment in checkout. The pattern depends on which markets you ship to, what lookup services are available, and how willing the brand is to depend on a third-party autocomplete provider.

Shopify default

Autocomplete-driven entry

A single address field that surfaces Google Places or Loqate suggestions as the shopper types. Manual entry is a secondary link below the field. The default in modern hosted checkouts.

Example of a Shopify-style autocomplete-driven address form with Google Places suggestionssearchShipping addressCountry/regionUnited States ▾Address221 Bake221 Baker StreetLondon, NW1 6XE, UK221 Baker AvenueAtlanta, GA 30309, USA2210 Baker DriveAustin, TX 78701, USA221B Baker LaneBrooklyn, NY 11201, USAEnter address manuallyContinue to shippingecommerceguide.com

> what's good

  • +One field replaces six, dramatic reduction in keystrokes on mobile.
  • +Validated addresses upstream means fewer failed deliveries downstream.
  • +International coverage handled by the provider, no per-country logic.

> what's risky

  • ·Autocomplete fails on rural, new-build, and PO box addresses, fallback must be visible.
  • ·Provider outages stall the entire checkout if not handled gracefully.
  • ·Privacy-conscious shoppers may distrust auto-suggest pulling from a third party.
Amazon

Manual field grid

Country, name, phone, two address lines, then a city/state/zip row. The traditional pattern, still dominant on marketplaces and any retailer that ships to addresses outside autocomplete coverage.

Example of an Amazon-style manual address form grid with traditional fieldssearchAdd a new addressCountryFull namePhone numberAddress line 1Address line 2 (optional)CityStateZIP codeMake this my default addressUse this addressecommerceguide.com

> what's good

  • +Works for every address type, no autocomplete edge cases to handle.
  • +Familiar layout, shoppers know exactly what to expect.
  • +Easy to validate field-by-field with clear inline error messaging.

> what's risky

  • ·High keystroke count on mobile, the slowest path through checkout.
  • ·Field labels and order vary by country, easy to ship a US-only form by accident.
  • ·Shoppers skip optional fields, missing apartment numbers cause delivery issues.
UK Loqate-style

Postcode-first minimal

A hero postcode input, then a single dropdown of matching addresses. Common on UK retailers using Loqate or PCA Predict, where postcode-to-address lookup is highly reliable.

Example of a UK Loqate-style postcode-first minimal address formsearchdelivery addressWhere shall we send it?PostcodeSW1A 2AAFindSelect your address10 Downing Street, London ▾12 resultsaddress preview10 Downing StreetLondonSW1A 2AAedit manuallyContinueecommerceguide.com

> what's good

  • +Two interactions to a complete address, the fastest path on UK checkouts.
  • +Bold single-field layout reduces visual weight, feels modern.
  • +Address preview confirms the match before the shopper commits.

> what's risky

  • ·Only viable in markets with reliable postcode-to-address services.
  • ·New-builds and recent moves may not yet appear in the lookup database.
  • ·Shoppers who mistype the postcode can hit a confusing empty state.

More cart & checkout patterns