Capturing flat-level addresses at UK checkout
Flat-level address checkout: how Royal Mail PAF lookup captures exact flat addresses at UK checkout, and what to do when a flat won't match.
- Written by
- Mark Salvin
- Published
- Updated
- Reading time
- 8 minutes
If you sell to customers in flats, maisonettes or converted houses, you already know the problem: a basic postcode lookup gets you to the building, but not to the door. In 2026, with UK e-commerce running on tighter margins and customers expecting checkout to take seconds, getting the full flat-level address at the point of order matters. This guide walks through how flat-level address lookup works at checkout, and what happens in the two cases where a match genuinely won't come back - so you can handle both without losing the sale.
Flat-level address capture works by searching UK postcode data down to sub-premise level, so a customer typing a postcode sees "Flat 3, 14 Acacia Road" as a selectable option, not just "14 Acacia Road". When the data source holds that level of detail, the customer picks their exact address in one click. When it doesn't, you need a manual fallback ready, because forcing a customer to retype an address they can't find is how you lose the order entirely.
Why Flat-Level Address Checkout Depends on the Data Source
Not every UK address dataset goes down to flat level, and that's the first thing worth checking before you build or buy anything. Royal Mail PAF (the Postcode Address File) is the definitive database of UK postal addresses, maintained by Royal Mail and used by postal workers to deliver mail. It holds over 32 million UK delivery points, many at sub-premise level, which is why a PAF-powered lookup can return a flat number rather than stopping at the building.
In our own experience comparing address lookup options, general-purpose location APIs such as Google Places are built for mapping and navigation rather than postal delivery, and we've found they often don't carry the same flat and unit-level detail that PAF does for UK addresses. If you're comparing address autocomplete options for WooCommerce, this is the core difference worth understanding before you pick one - we cover it in more depth in our comparison of free address autocomplete options versus properly licensed PAF data.
How to Set Up Flat-Level Lookup at WooCommerce Checkout
The fastest way to get flat-level address capture working on a WooCommerce store is to add address lookup directly to the checkout page, on both the billing and shipping sections. The SnapAddress plugin does exactly this, and it works on both Checkout Blocks (the newer, block-based WooCommerce checkout) and classic checkout - which matters, because many older UK address plugins were built using DOM manipulation against classic checkout fields and break when a store upgrades to blocks.
In practice, the setup looks like this:
- The customer types their postcode into the address field at checkout.
- The plugin returns a list of addresses at that postcode, including individual flats and units where PAF holds them as separate delivery points.
- The customer selects their exact address, and the flat number, building name and street populate automatically.
If you want the full technical walkthrough of how this behaves specifically on Checkout Blocks, including what the plugin does and doesn't touch on the page, see our guide to predictive address lookup for WooCommerce Checkout Blocks. Worth noting: since plugin version 1.2.0 the same lookup also covers My Account address editing and the admin order screen, so addresses captured over the phone or updated later are as precise as the ones taken at checkout. Both are off until you tick them in the plugin settings, so updating the plugin changes nothing on its own. It doesn't extend to the cart shipping calculator or registration forms, neither of which asks for a street address.
Why a Flat Address Is Not Found at Checkout
When a customer can't find their flat in the lookup, it's usually one of two things: the unit sits in Multiple Residence data rather than standard PAF, or the building is a new-build not yet in the database. Neither means the address doesn't exist - it means the lookup query didn't match the licensed dataset, which is a different thing entirely from a wrong or undeliverable address.
Case One: Multiple Residence Units Outside the Licensed Dataset
Royal Mail maintains two separate address datasets. PAF lists every deliverable point in the UK - buildings and flats that each have their own publicly accessible delivery point, such as an individual letterbox. Multiple Residence is a separately licensed file covering sub-premises that share a single delivery point, such as bedsits or rooms in a house split into multiple occupancy, as our data and licensing documentation explains.
Per Ideal Postcodes' guide to Multiple Residence data, around 180,000 PAF premises (roughly 0.6%) have multiple dwellings attached to a single delivery point, with an average of four additional dwellings each - covering roughly 850,000 addresses nationally that sit in Multiple Residence rather than standard PAF.
SnapAddress serves standard PAF only - it does not include Multiple Residence data. So if a customer lives in a shared-entry flat that only has a parent building address on PAF, the lookup will return that building, but not their individual flat or room as a separate selectable result. This isn't a fault in the lookup. It's a reflection of which dataset the address sits in.
Case Two: New-Build Addresses Not Yet in the Database
Royal Mail updates PAF daily, and we refresh our copy monthly in line with Royal Mail's release cycle, so new postcodes appear shortly after Royal Mail activates them. A newly built flat or development that hasn't yet been through that activation process won't appear in a lookup yet: a brand-new postcode returns no matches ("No addresses found" in the plugin) rather than an error, and new flats in an existing building are simply missing from that postcode's list. This is a timing gap, not a data error - the address will typically appear in a future monthly refresh once Royal Mail has processed it.
Capturing the Flat Number When the Lookup Doesn't Match
In both of the cases above, the practical fix is the same: give the customer a manual entry path where the flat or unit number has its own line, alongside the rest of the address, so they can complete their own details when the lookup can't. This should sit as a visible fallback option on the checkout form itself, not a dead end. In the SnapAddress plugin, that's the "Enter address manually" link under the search field, which reveals WooCommerce's standard address fields - including the second address line for a flat or unit.
Illustratively, imagine a checkout where 1,000 customers use postcode lookup in a month, and half live in flats. Of that group, suppose a handful hit a Multiple Residence unit or a very recent new-build that PAF hasn't yet indexed. For that small number, a flat or unit field with manual entry means the order still captures a complete, customer-confirmed address - rather than an incomplete one submitted because the customer couldn't find their flat and gave up trying. We have no measured data on how often this occurs across stores generally; this is an illustrative scenario only, built to show the shape of the fallback, not a reported outcome.
Address capture removes one cause of delivery problems: mistyped or incomplete addresses entered by hand. Royal Mail PAF data is the same dataset UK postal workers use, according to our data and licensing documentation, which is why matching against it at checkout gives customers their real, deliverable address rather than an approximation. We don't hold separate figures on how parcel delivery problems affect small traders' costs generally, since the plugin never sees order or delivery outcomes.
What This Means for Your Checkout Build
If you're an agency or technical founder evaluating address lookup options for a WooCommerce store, flat-level coverage and a sensible manual fallback are two separate design decisions, and both matter. The lookup handles the common case in one click. The fallback field handles the Multiple Residence and new-build edge cases without blocking the order.
Integration itself is quick: the plugin installs directly into WooCommerce checkout, and you don't need a Google Maps billing account or any sales call to get a working setup. Pricing is published in full, with one-off credit packs rather than a subscription - starting from £18.50 excluding VAT for 500 lookups, with no monthly fee and no overage charges, as detailed on our pricing page. For a side-by-side look at how that compares to subscription-based providers, read our breakdown of address lookup pricing without a subscription. If you're evaluating options as an agency across multiple client builds, our agency guide to evaluating and trialling an address lookup plugin walks through what to test before committing.
Start with 100 free lookups and no credit card required at snapaddress.io/pricing, and you can have flat-level address lookup running on your checkout the same day.
Frequently Asked Questions
Why is my customer's flat not showing up in the address lookup?
It's usually one of two reasons: the flat sits in Royal Mail's Multiple Residence dataset rather than standard PAF (common in shared-entry buildings with one letterbox), or it's a new-build that hasn't yet appeared in the monthly PAF refresh. Neither is an error: a Multiple Residence flat shows only its shared building address, and a brand-new postcode returns no matches.
Does SnapAddress support Multiple Residence addresses like bedsits or shared-entry flats?
No. SnapAddress serves standard Royal Mail PAF data only. Multiple Residence is a separately licensed Royal Mail file covering sub-premises that share a single delivery point, and it isn't part of the current SnapAddress dataset, as stated in our data and licensing documentation.
What should customers do if their flat address isn't found at checkout?
Give them a manual entry option where the flat or unit number has its own line alongside the standard address fields. With the SnapAddress plugin, the "Enter address manually" link reveals WooCommerce's address fields, and the flat or unit goes in the second address line. This lets them complete an accurate, customer-confirmed address even when the automated lookup can't return a match for their specific unit.
More on making checkout work
- Why your WooCommerce address plugin breaks on Checkout BlocksWooCommerce address plugin broken after checkout block update? Learn why DOM manipulation fails and how to fix incomplete address issues fast.9 min read
- Predictive address lookup for WooCommerce Checkout BlocksWhy WooCommerce Checkout Blocks break DOM-based address plugins, and how to add PAF-accurate UK postcode lookup that works natively on block checkout.9 min read
- WooCommerce address autocomplete: free options vs properly licensed PAFWooCommerce address autocomplete free options vs licensed PAF: discover which solution cuts delivery failures and saves UK stores money long-term.9 min read