Skip to main content
Geographic zones used by commerce configuration. Zones group geographic regions for rules such as shipping availability, tax applicability, or store configuration. Determine which geographic entities are supported by the selected release (for example, country, state/province, or postal region).

Configuration concepts

Document zone names, included regions, activation state, and the modules that consume the zone. Explain overlap/precedence behavior only when confirmed by code.

Integration guidance

Normalize country and region identifiers, validate addresses server-side, and avoid relying only on free-form country/state names. Test boundary cases such as missing region, unsupported postal code, and overlapping zones.

Verify

Search zone-related models, seed data, migrations, and services. If the zone concept is supplied by an extension or another edition, label that dependency clearly.