Predictive Address Lookup for WooCommerce Checkout Blocks

In 2026, WooCommerce Checkout Blocks is no longer an optional upgrade - it's the default checkout experience for new stores, and an increasing number of existing stores have made the switch. That shift has quietly broken address autocomplete for thousands of UK shops. Most address lookup plugins were built for the classic checkout, relying on DOM manipulation that simply doesn't work in a block-based environment. If your postcode lookup stopped working after enabling Checkout Blocks, you're not alone, and the fix is simpler than you might expect.

Why WooCommerce Checkout Blocks Break Most Address Plugins

Classic WooCommerce checkout renders a standard HTML form. Address plugins hook into that form by targeting specific DOM elements - finding the postcode field, injecting a dropdown, listening for changes. It's a workable approach, but it depends entirely on the DOM structure staying consistent.

Checkout Blocks works differently. It's built on React, and the form fields are controlled components managed by the WooCommerce Blocks API. Plugins that try to manipulate the DOM directly either fail silently or break the checkout entirely. The address field appears, but nothing happens when a customer types a postcode. No suggestions, no dropdown - just a blank form field and a frustrated customer.

According to Baymard Institute's cart abandonment research, the average checkout abandonment rate sits at over 70%. A broken or missing address lookup adds unnecessary friction at exactly the wrong moment. Customers who can't find their address quickly will either enter it incorrectly or leave.

If your lookup has already stopped working and you want the full diagnosis - what breaks, why DOM manipulation fails against React, and how to tell if your plugin is affected - see why your WooCommerce address plugin breaks on Checkout Blocks.

How to Add Postcode Lookup to WooCommerce Block Checkout

Adding a working postcode lookup to WooCommerce Checkout Blocks requires a plugin that integrates through the official WooCommerce Blocks API - not one that patches the DOM. The integration method matters as much as the data behind it.

SnapAddress is built specifically for this. The plugin registers with WooCommerce's block checkout API, which means it works natively with Checkout Blocks without any configuration. Installation takes about two minutes:

• Install the SnapAddress WooCommerce plugin from your WordPress dashboard
• Create a free account at snapaddress.io and copy your API key
• Paste the key into the plugin settings

That's the entire setup. The plugin auto-detects whether you're running classic or block checkout and adjusts accordingly. You don't need to choose a mode or configure anything per-checkout-type.

How to Edit WooCommerce Checkout Block Address Fields

WooCommerce Checkout Blocks address fields can be customised through the block editor (Appearance > Editor > Templates > Checkout), or programmatically via the WooCommerce Blocks API. For most stores, the block editor handles layout changes without touching code.

Where address lookup fits in is at the field-interaction level. SnapAddress adds predictive address search on top of the existing address fields - it doesn't replace them or require you to restructure the checkout layout. When a customer starts typing a postcode or address, suggestions appear in a dropdown. Selecting one fills the address fields automatically. The block structure stays intact; the lookup layer sits above it. Each of those as-you-type requests is one lookup, so a single completed search spends two to four - worth knowing when you size a credit pack.

This also means you retain full control over which fields appear and how the checkout looks. SnapAddress doesn't impose a layout - it enhances the fields already there.

The Data Behind the Lookup: Royal Mail PAF

Not all address lookup plugins use the same data. Many rely on Google Places, which is built for mapping and point-of-interest search rather than postal delivery. For UK addresses, that distinction matters.

Royal Mail's Postcode Address File (PAF) contains over 30 million UK addresses, including flat-level and unit-level detail that Google Places frequently misses. If a customer lives in Flat 3B of a converted Victorian terrace, a Google Places lookup might return the building address without the flat number. The parcel goes to the right building, then gets lost. PAF carries the granularity that postal workers actually use - because it's the same data they use to sort and deliver the post.

As Royal Mail's own AddressNow documentation states, matching against PAF gives you the most up-to-date database of UK addresses. SnapAddress is a licensed Royal Mail PAF Solutions Provider, verifiable directly with Royal Mail's Address Management Unit. The data is updated monthly.

For WooCommerce stores shipping physical goods to UK addresses, this isn't a minor technical detail. Inaccurate addresses mean failed deliveries, redelivery costs, and customer service overhead. Baymard's checkout usability research consistently identifies address entry as one of the highest-friction points in the checkout flow. Getting the address right first time - with PAF-accurate data - removes that friction at the source.

Predictive Address Search vs Postcode Lookup: Both, Not Either

WooCommerce predictive address search and postcode lookup are two different interaction patterns, and customers have preferences. Some people know their postcode and want to type it, then pick from a list. Others prefer to start typing their street name or town and see suggestions appear.

SnapAddress supports both modes through a single API and a single plugin installation. The checkout field accepts either input style - postcode search or address autocomplete - and returns suggestions from the same PAF dataset either way. You don't need to configure separate widgets or manage two different integrations.

What Happens When Credits Run Out

One concern with credit-based lookup services is what happens at the boundary. With SnapAddress, if your credits run out, the address field falls back to manual entry. Customers can still type their address by hand, and orders continue to go through. There are no HTTP 402 errors surfaced to customers, no broken checkout pages, and no lost orders. The lookup is unavailable until you top up, but the checkout itself keeps working.

How to Remove Address Fields in WooCommerce Checkout

If you need to remove specific address fields from WooCommerce Checkout Blocks - for example, removing the "Address Line 2" field or the "Company" field - you can do this using the __experimentalRegisterCheckoutFilters JavaScript API provided by WooCommerce Blocks, or via PHP using the woocommerce_checkout_fields filter for classic checkout. In Checkout Blocks, field visibility is controlled through the block settings panel in the site editor for some fields, and programmatically for others.

SnapAddress doesn't interfere with field removal. If you've hidden address fields through the blocks API, the lookup plugin respects that configuration and only populates the fields that exist.

Pricing Without the Sales Call

Most enterprise-grade UK address lookup providers - Loqate, Fetchify, and others - don't publish pricing. You request a quote, speak to a sales team, and end up on an annual commitment. For a small WooCommerce store doing a few hundred orders a month, that model is poorly suited to actual usage patterns.

SnapAddress publishes every price on the pricing page, with no subscription required. Credit packs start at £17.50 for 500 lookups (3.5p each), down to 2.5p per lookup on the Pro pack. Credits are valid for 12 months. There's no monthly fee, no overage charge, and no auto-renewal. You buy what you need, when you need it.

For comparison, a store processing 200 orders per month would use roughly 200 lookups. The Starter pack at £17.50 covers two to three months of that volume. The economics are straightforward because the pricing is straightforward.

If you're migrating from a provider that hid its pricing or locked you into an annual commitment, the UK address lookup API comparison on the SnapAddress blog breaks down what you're actually paying across providers.

Checkout Blocks Compatibility: What to Check Before Installing Any Plugin

Before installing any WooCommerce address lookup plugin, there are three questions worth asking:

• Does it use the WooCommerce Blocks API? DOM-based plugins will fail on block checkout. Ask the vendor explicitly, or check the plugin documentation for Checkout Blocks support.
• What data source does it use? Google Places is not equivalent to Royal Mail PAF for UK delivery addresses. If flat and unit-level accuracy matters for your products, PAF is the correct data source.
• What happens at the edge cases? Credits running out, API timeouts, and network errors should all degrade gracefully - not break the checkout.

SnapAddress answers all three. The plugin is built for Checkout Blocks from the ground up, uses Royal Mail PAF data exclusively, and falls back to manual entry rather than breaking when something goes wrong.

If you're ready to add a working, PAF-accurate address lookup to your WooCommerce block checkout - without a sales call, a subscription, or a lengthy integration - start free with 100 lookups at snapaddress.io. No card required.

Frequently Asked Questions

Does SnapAddress work with WooCommerce Checkout Blocks?

Yes. SnapAddress integrates through the WooCommerce Blocks API rather than DOM manipulation, which means it works natively with block-based checkout. No additional configuration is needed - the plugin auto-detects classic and block checkout and handles both. See the WooCommerce plugin documentation for full details.

How do I turn off checkout blocks in WooCommerce if I need to revert?

You can revert to classic checkout by deactivating the WooCommerce Blocks plugin or by switching your checkout page to use the classic shortcode ([woocommerce_checkout]) instead of the block. However, WooCommerce is moving toward Checkout Blocks as the default, so reverting is a short-term workaround. A plugin with native Checkout Blocks support - like SnapAddress - is a more sustainable solution than reverting the checkout type.

What's the difference between postcode lookup and predictive address search in WooCommerce?

Postcode lookup lets customers enter a postcode and select their address from a list. Predictive address search (address autocomplete) shows suggestions as they type any part of their address - street name, town, or postcode. SnapAddress supports both modes through a single plugin and API, so customers can use whichever approach they prefer without any additional configuration on your end.