Shopify merchants using Checkout Blocks Address Blocker should move their shipping-address rules to Shopify’s native address format validation before Address Blocker sunsets on August 31, 2026. Compatible settings were scheduled for automatic migration, but the safe response is to open Settings > Checkout > Checkout rules, confirm every rule, test it in the intended markets and verify that legitimate customers can still complete checkout.
Native address format validation can block several problematic address types, enforce field requirements, limit character counts, allow or block ZIP or postal-code patterns and run custom regular expressions. It validates shipping addresses, not billing addresses. Some legacy Address Blocker rules are not supported, so a store that relies on non-ASCII blocking or a required street number needs a different operational control.
Last reviewed: August 30, 2026. The Address Blocker sunset is scheduled for August 31, 2026. Check the current rule status in your own Shopify Admin because migrated behavior depends on the legacy configuration and market targeting.
What Is Changing on August 31, 2026?
Shopify has deprecated the Address Blocker feature in Checkout Blocks and set its sunset for August 31, 2026. The replacement is native address format validation, managed as a checkout rule in Shopify Admin. Shopify’s changelog says compatible Address Blocker settings are automatically migrated.
Automatic migration reduces manual work, but it does not prove that the new rule produces the same business outcome. A legacy rule may be unsupported, mapped differently or targeted at a market whose address formats vary more than expected. A rule can also be technically correct and still create conversion loss by rejecting valid customers.
| Area | Before | After migration |
|---|---|---|
| Management location | Checkout Blocks Address Blocker | Settings > Checkout > Checkout rules |
| Rule engine | Checkout Blocks app feature | Native Shopify address format validation |
| Compatible settings | Configured in Address Blocker | Scheduled for automatic migration |
| Unsupported settings | Could exist in the legacy feature | Require another control or process |
| Validation scope | Shipping-address workflow | Shipping addresses, not billing addresses |
Treat the sunset as a checkout change, not just an app cleanup. It belongs in the same release calendar as payment, shipping and extension changes. If the store is also replacing legacy checkout customizations, use our Shopify Checkout Scripts migration guide to keep the projects separate and testable.
Where to Find Shopify Address Format Validation
In Shopify Admin, go to Settings > Checkout and locate Checkout rules. Address format validation is available from that section. Review the rule’s status, targeted markets, configured checks and customer-facing error messages.
Do not infer that a rule is active because Checkout Blocks is installed. The native rule must exist in Checkout rules and be enabled for the intended scope. Record the rule name and settings in the store’s change log.
Who should own the rule?
Address validation touches several teams:
- operations knows which address types carriers or warehouses cannot serve;
- customer support knows which addresses trigger real complaints;
- ecommerce owns checkout completion and customer messaging;
- developers or technical partners review patterns and regular expressions;
- legal or compliance may advise on market-specific restrictions.
Assign one owner who can approve changes and one person who reviews conversion and support signals after release.
Which Address Rules Does Shopify Support?
Shopify’s current documentation lists several native validation options. Availability can depend on the exact address format and market, so verify the controls presented in your store.
Block selected address types
The rule can block supported categories such as:
- PO boxes;
- diplomatic or military addresses;
- parcel lockers;
- gopost addresses.
Only block an address type when the actual fulfillment service cannot deliver to it. A broad PO-box ban can be unnecessary if one carrier supports the route and another does not. Where possible, align the restriction with shipping methods, markets and fulfillment capabilities.
Allow or block ZIP and postal codes
You can define allowed or blocked postal-code patterns, including wildcard patterns. This is useful for genuine service-area restrictions, remote regions or controlled delivery zones. Keep the source list and effective date with the rule so that it can be updated when carrier coverage changes.
Limit address-field length
Character limits can protect carrier labels, warehouse systems and integrations that reject oversized fields. Base the limit on the narrowest verified downstream system, not an arbitrary aesthetic preference. Test accented letters, spaces, hyphens and apartment information.
Require selected fields
Required-field rules can ensure that operationally necessary information is provided. Avoid requiring data simply because the field exists. Every additional obstacle can reduce checkout completion and create support contacts.
Use custom regular expressions
Regular expressions can enforce a format that Shopify’s standard controls do not cover. They are powerful and risky: a small pattern mistake can block an entire market. Use them only with written examples of valid, invalid and edge-case addresses.
Which Legacy Address Blocker Rules Are Not Supported?
Shopify’s help documentation identifies legacy options that are not supported by native address format validation:
- blocking non-ASCII characters;
- requiring a street number.
Do not replace non-ASCII blocking with an English-only pattern
Names and addresses legitimately contain accented and non-Latin characters. A broad ASCII-only regular expression can reject valid customers, corrupt address meaning and create unnecessary manual work. First verify whether the carrier, label system or fulfillment platform still has the original limitation. If it does, solve the data-handling problem as close to that system as possible.
Street numbers are not universal
Many valid addresses do not fit a simple “number followed by street” structure. Some use named properties, rural routes, building identifiers or market-specific ordering. If fulfillment frequently fails because a street number is missing, improve the customer prompt and operational review instead of deploying an untested global regex.
Document every unsupported rule, the business reason behind it and the replacement control. “Not migrated” must not become “forgotten.”
Step-by-Step Address Blocker Migration Checklist
Step 1: Capture the legacy configuration
Before the sunset, record every Address Blocker rule, targeted market, pattern, error message and exception. Screenshots are useful, but also write the logic in plain language so it remains understandable after the old interface disappears.
Step 2: Confirm the native rule exists
Open Settings > Checkout > Checkout rules. Locate the migrated address format validation rule. Verify that its status is active and that its purpose is obvious from the name.
Step 3: Compare settings line by line
Create a simple matrix with legacy rule, native equivalent, market scope, expected customer message and migration status. Mark unsupported rules explicitly rather than forcing them into a weak approximation.
Step 4: Review real failed addresses
Use support cases and failed-fulfillment examples to learn which restrictions solve a real problem. Remove obsolete rules created for a carrier, warehouse or app that is no longer used.
Step 5: Prepare test cases
For each rule, create at least one address that should pass, one that should fail and one boundary case. Include every targeted market and language. Test guest and returning-customer flows where applicable.
Step 6: Release and monitor
Do not combine the migration with unrelated checkout, theme, shipping-rate or payment changes. Note the release time and watch checkout completion, errors, customer contacts and fulfillment exceptions.
Market Targeting and Customer Error Messages
Address formats are local. A rule that works in one country can be wrong in another. Target only the Shopify Markets for which the restriction is valid and tested.
| Question | What to verify |
|---|---|
| Where is delivery unavailable? | Carrier and fulfillment coverage by country or postal region |
| Which address structure is normal? | Local postal guidance and real customer data |
| Which language should appear? | Checkout language and market localization |
| Can the customer fix the issue? | The message explains the specific field and accepted alternative |
| Is there another delivery method? | Offer a supported address or fulfillment path where possible |
Write actionable messages
“Invalid address” tells a customer nothing. A useful message states what failed and what to do next: for example, “We cannot ship this method to a PO box. Enter a street address or choose an eligible alternative.” Keep it concise and avoid exposing internal pattern syntax.
Coordinate validation with shipping profiles and rates. If a store already produces confusing split shipments or duplicated rates, address those issues separately with our guide to fixing multiple Shopify shipping charges.
How to Use ZIP Patterns and Regular Expressions Safely
Start with Shopify’s standard rule options. Use a custom regular expression only when the requirement cannot be expressed safely with the built-in controls.
Define the requirement before the pattern
Write: “Block postal codes beginning with X in Market Y because Carrier Z does not serve them.” Do not start with a copied expression from a forum. The business statement lets another person review whether the pattern matches the real restriction.
Build a test table
Include:
- valid codes with and without spaces;
- lowercase and uppercase input where applicable;
- leading zeros;
- the shortest and longest valid forms;
- near-matches that must fail;
- codes from neighboring regions;
- empty or incomplete input.
Avoid catastrophic scope
A misplaced anchor, wildcard or character class can match far more than intended. Have a second person review the expression and run the full market test set before activation. Keep a plain-language rollback instruction beside the rule.
Shopify Checkout Address Validation Test Plan
- Confirm the storefront and market. Use the correct currency, language and shipping destination.
- Add a shippable product. Include a product assigned to the relevant shipping profile and location.
- Test a valid address. The customer must be able to proceed and see appropriate rates.
- Test every blocked category. Confirm the rule stops the intended address and shows an actionable message.
- Test boundaries. Check character limits, wildcard edges, postal-code formatting and apartment details.
- Test multiple markets. Ensure a rule for one market does not leak into another.
- Test accelerated and returning flows. Check saved addresses and available accelerated checkout paths.
- Complete a test order where appropriate. Confirm the normalized address reaches order admin and downstream fulfillment correctly.
If the store has multiple checkout configurations or controlled releases, document this rule alongside the process described in our Shopify Rollouts guide. Address validation should remain consistent between control and treatment unless it is the deliberate test variable.
Monitoring, Support and Rollback
For at least the first business cycle after activation, monitor:
- checkout completion by targeted market;
- shipping-address error reports;
- customer support contacts mentioning rejected addresses;
- manual order edits and carrier corrections;
- failed fulfillment or label creation;
- unexpected changes in shipping-method selection.
If valid customers are blocked, disable or narrow the specific rule rather than turning off every checkout control blindly. Record the affected market and address example without exposing personal customer data in shared logs.
B2B stores need additional testing because company locations, purchasing staff and delivery workflows can differ from consumer checkout. Review the relevant constraints in our Shopify B2B plans and catalogs guide.
For a focused review of checkout rules, shipping behavior and migration risks, contact SmallDeskApps for Shopify support.
Frequently Asked Questions
When does Shopify Address Blocker sunset?
Shopify has scheduled the Checkout Blocks Address Blocker sunset for August 31, 2026.
Where is the replacement address validation rule?
Go to Shopify Admin, then Settings > Checkout > Checkout rules. Review the address format validation rule and its active market scope.
Will Shopify migrate Address Blocker rules automatically?
Shopify says compatible settings are automatically migrated. Merchants should still compare the native rule with the legacy configuration and test every important market.
Does address format validation check billing addresses?
No. Shopify’s documentation states that address format validation applies to shipping addresses, not billing addresses.
Can Shopify block PO boxes and parcel lockers?
The native rule supports blocking selected address types, including PO boxes and parcel lockers, where those options apply.
Can I require a street number?
Requiring a street number is listed as an unsupported legacy Address Blocker rule. Avoid a global workaround until you have tested valid address formats in each market.
