What changed in the UK address database this month

What is PAF? The Postcode Address File (PAF®) is Royal Mail’s definitive database of every deliverable address and postcode in the UK.

It covers over 32 million delivery points and is updated monthly. If your business relies on accurate address data, at checkout, in your

CRM, or for deliveries, PAF is the source that keeps it current.


June 2026 in numbers


Royal Mail made 62,027 changes to PAF this month. That is not a small number. It represents new homes that need delivering to, businesses that have moved or closed, streets that have been renamed, and addresses that were simply wrong and have now been corrected.


Every one of those changes is a record in someone’s database that may now be out of date, and a delivery, a campaign, or a customer communication that could go wrong if the data hasn’t been updated.


Delivery point changes at a glance

 

Here’s the full breakdown of what changed, amended, and was removed from PAF in June:


Change type Total What it means
New properties added 24,333 New builds entering the database
Error corrections 36,204 Existing records fixed or standardised
Demolitions 955 Properties removed from the database
Name or number changes 205 Streets or properties renamed
Business name changes 187 Organisations updated
Large users moving or ceasing 137 Commercial address changes
TOTAL CHANGES 62,027 Across adds, amendments and deletes

What stands out this month


NEW PROPERTIES

24,333 new delivery points were added, the majority residential new builds. These are addresses that simply did not exist in the database last month. For businesses delivering to new developments or capturing addresses from customers who’ve recently moved into new homes, this is the data that makes those deliveries possible.


ERROR CORRECTIONS

The largest single category this month at 36,204. These are not new addresses; they are existing records that were incomplete, incorrectly formatted, or otherwise wrong. It’s a useful reminder that the address data already sitting in your database may contain errors that PAF has since corrected, but your system hasn’t picked up.


DEMOLITIONS

955 properties were removed. Sending to a demolished address is not just a wasted delivery; it can flag your account with couriers and damage the sender's reputation over time. If your database hasn’t been cleansed recently, some of those addresses may still be sitting in your records as live.


The PAF database, May 2026 snapshot


For context, here’s where the full database stands as of the May 2026 statistics release:

Metric Figure
Total delivery points 32,392,328
Total postcodes 1,810,014
Businesses on PAF 1,294,515
Vacant organisations 352,387
Postcode sectors 11,239

One figure worth noting: vacant organisations are up 1,592 on the previous month, while active businesses are down 2,260. It’s a small month-on-month shift, but it’s consistent with the wider picture of business churn, and a reminder that B2B databases decay just as fast as consumer ones.


New localities this month


Twelve new postcode sectors and localities were added to PAF in June, including new developments in Preston (PR4 7), Lymington (SO41 5), and Brough (HU15 3). These are areas where new housing developments have reached the point of receiving official postal addresses, often the moment when residents start placing orders, registering accounts, and expecting deliveries.


If you’re in eCommerce or logistics and serve customers across the UK, these are the addresses that a non-current database simply won’t recognise yet.


Why it matters for your business


Over 62,000 address changes in a single month. Annualised, that’s well over 700,000 changes to the UK address landscape every year, on top of the natural decay that comes from people moving, businesses relocating, and properties changing hands.


Fetchify pulls from Royal Mail PAF® data that is always current, so your customers are validating against the latest version of the UK address database, not a snapshot from six months ago. That matters at checkout, in your CRM, and every time you put a delivery in motion.



Data Cleansing

About Fetchify


Fetchify’s address lookup and data validation platforms cover more than 250 countries, and increases customer conversion with the fastest, most accurate customer data capture. Fetchify’s flagship products – Address Auto Complete and Postcode Lookup – reduce friction at the checkout, and also significantly increase the number of successful deliveries. Founded in 2008, Fetchify processes millions of data transactions every day for clients ranging from startups to established high-street names, and offers a full suite of data validation tools, including phone, email and bank, too.

By Fiona Paton June 18, 2026
How data decay is quietly removing your best customers before they ever decide to leave. Somewhere in your CRM right now, there is a customer you think you lost. They stopped buying about eighteen months ago. They went into a lapsed segment, got a couple of reactivation emails, did not respond, and were eventually written off. The assumption was that they moved on. What actually happened, in a surprising number of cases, is much simpler. They moved house. The reactivation emails went to an inbox they no longer check. The direct mail went to a flat that has a different tenant. The customer was not gone. They were just unreachable. And because the database had no way of flagging the difference, they were counted as churn. This is how data decay works. Not in dramatic failures, but in a steady accumulation of records that have quietly stopped being accurate. Around 30% of customer data goes stale every year, not because anything went wrong, but because people move, change jobs, switch email addresses, or get married. Left unaddressed, that figure compounds. A database that has not been properly maintained for three years may have a third of its records either partially or wholly unreachable. The problem is that it is almost invisible until it is already significant. A handful of bounced emails does not raise an alarm. Neither does a slightly elevated returns rate. The metrics look broadly normal because the volume of bad data is not yet high enough to distort them. By the time it is, the damage is done. The churn you cannot account for Most businesses have a reasonable handle on the customers they actively lose. Cancellations are tracked. Lapsed accounts are flagged. Retention programmes exist precisely to address the customers who stop buying. What those programmes cannot reach is the customer who never formally left. They sit in the CRM as a lapsed record. They count toward the database size. They get included in reactivation segments. They cannot receive the communication because the address on their record is no longer valid. The downstream effect is real. A repeat customer whose address changed after a house move never receives the offer that would have brought them back. A lapsed member does not see the renewal reminder and lets the subscription quietly expire. In both cases, the organisation records an attrition event. In neither case did the customer actually decide to leave. A customer who moved house is not the same as a customer who left. That distinction tends to matter quite a lot when you are trying to work out where your retention budget should go. Why reactivation campaigns underperform When a win-back campaign comes back with poor results, the instinct is to interrogate the campaign. The subject line gets tested. The offer gets more aggressive. The timing gets adjusted. All of that is reasonable. None of it helps if a meaningful share of the list cannot receive the email in the first place. A lapsed customer segment typically contains three types of contact: people who genuinely disengaged and are unlikely to respond, regardless, people who might respond to the right message, and people who would respond, but the email never arrives because the address has changed. The frustrating thing is that you cannot easily tell these groups apart from the outside. Low open rates and low click-through rates look the same whether the cause is disengagement or data decay. Email is only part of it. Physical address decay affects direct mail and delivery. Phone number decay affects SMS and outbound calling. Each channel erodes at its own rate, and most organisations are not tracking the accuracy of their data across all of them. 30% of customer database records become inaccurate within 12 months, without any action by the customer. What changes when the data is clean A data cleanse does not just improve deliverability, though it does that. It changes what the numbers actually mean. When ghost records are removed from a lapsed segment, the remaining file is smaller but more meaningful. Reactivation revenue from that cleaned list is real revenue, not a percentage improvement calculated against contacts who were never going to respond. The churn figure, once recalculated without the unreachable records, is often more positive than expected. Some of what looked like permanent attrition turns out to be recoverable. There is a GDPR dimension too. Article 5(1)(d) requires that personal data be kept accurate and, where necessary, up to date. The ICO can issue fines of up to £17.5 million for data accuracy failures. Most organisations are not at serious risk of enforcement, but most organisations also have not checked how their database holds up against a standard they are legally required to meet. The more common consequence is commercial rather than regulatory. Marketing budgets applied to an inaccurate list simply do less than they should. The same spend, against a validated file, produces measurably better results. Not because the campaigns improved, but because the contacts can actually receive them. The practical starting point Addressing data decay does not require a significant IT project. For most organisations, the starting point is a cleanse of the existing CRM: matching records against current address databases, identifying email addresses with persistent bounce history, removing duplicates, and flagging phone numbers that are no longer in service. Done once, it resets the foundation. Done regularly, and combined with validation at the point of data capture, it prevents the drift from accumulating again. The customers in those unreachable records did not all decide to leave. Some of them are still out there, still buying in your category. They just moved. Improve your data health and protect your business today. Reach out to our team below for a free data health check.
By Fiona Paton June 15, 2026
Jay’s career has never followed a straight line. Electronics engineering. Automotive systems. A social app for hostels that was about to launch just as COVID closed every hostel in the world. A pivot into web development. And eventually, Fetchify - where he now leads the team building the technology that keeps millions of data lookups running accurately every day. Looking back, the route makes perfect sense. Jay has always been drawn to what’s next. To faster feedback. To building things that work and seeing them work quickly. Software gave him all of that in a way that automotive engineering, for all its complexity, eventually stopped doing. The long way round Jay studied electronics engineering and came out of university specialising in embedded systems. By 2015, he was working on automated parking systems - the kind built on sensors and split-second decisions - and for a while, he found it genuinely interesting. But something was missing. “I wanted to see results faster,” he says. “With embedded systems and automotive work, the feedback loops are long. I wanted to build something and see it working.” So, he pivoted. He taught himself mobile development and from there, a startup building a social app for hostels and hotels - a platform that matched guests by shared interests, so someone travelling alone could find other guests up for the same activities. It was a genuinely good idea, with a handful of places trialling the beta version. Then 2020 arrived, the hospitality industry stopped overnight, and the timing simply couldn’t have been worse. Most people would have counted it as a setback. Jay counts it as part of the story. Finding something that fits He joined ClearCourse, initially working on the membership CRM side of the business. When a role came up at Fetchify, he knew it was the one. Tech Lead. A team to run. Real scope to build, improve and innovate - and enough space to do it properly. “What I love most about my job is the chance to be innovative and improve the quality of the software - and the opportunity to keep learning. There’s always something new.” His approach to leading the team reflects the same values. He talks about trust a lot - giving people the space to do things the way they think makes sense, rather than prescribing the path. The team checks in daily, whether that’s to swap ideas, talk through a problem, or join a scrum call. It’s not just his immediate team either: the wider Fetchify team, and within the ClearCourse group, there’s a culture of helping out. Of people being willing to lend a hand when it’s needed. “Software development can feel like a solo job, but actually the team here is solid, and we enjoy working together.” The thing he's most excited about Ask Jay what he’s most passionate about right now, and the answer is immediate: AI. Not in an abstract, trend-chasing way - but with a specific and considered view of what it actually means for software developers and the organisations they build for. “AI is raising the bar for what developers can produce. But I see it as a two-way collaboration - a helping hand to do the grunt work, while the ideas, the creativity, the innovation still come from people. It should help people achieve more in less time. Not replace the thinking.” His long-term goal is to help other ClearCourse businesses integrate AI into their products - starting, naturally, with Fetchify. For a company built on data accuracy, the intersection of clean data and AI capability is not an abstract future conversation. It’s already the direction of travel. Beyond the screen Jay grew up in Egypt, and travel is still one of the things he values most. He heads home to family a couple of times a year, and fits in city breaks wherever he can - somewhere new, with good food and different people and things to explore. His ideal off-duty scenario involves a beach, good conversation, and absolutely no particular agenda. The gym, friends and music round it off - time away from the screen that, for someone whose working life involves building technology that processes millions of data points a day, seems like a fairly sensible skill. When he imagines the distant future - the looking-back version - he pictures a career of creation, innovation and the willingness to embrace whatever comes next. That, and a beach somewhere warm. We’re very glad the winding road brought him to Fetchify.
By Fiona Paton May 28, 2026
“Fetchify turned what felt like a crisis into a straightforward fix - and in just a couple of days. We went from not being able to contact anyone to generating four new client applications from a single send. The data cleanse didn't just fix a problem - it opened the door again.” – Marcel Stirling, Phoenix Insolvency
By Fiona Paton May 26, 2026
There is a lot of enthusiasm right now about what AI can do for ecommerce and CRM teams. Personalisation at scale. Predictive analytics. Automated outreach that learns and adapts. The pitch is compelling, and much of it is real. But there is a foundational question that almost nobody is asking loudly enough: what happens when you run AI on bad data? The answer is not that the AI fails gracefully. The answer is that it fails at scale, confidently, and in ways that are harder to trace than a simple spreadsheet error. This is not a theoretical risk. It is already happening inside the organisations that have moved fastest to adopt AI-driven tools without first addressing the quality of the data those tools run on The assumption nobody questions Most organisations treat AI as a layer that sits on top of their existing data. Feed in the CRM, connect the customer database, and point the model at the transaction history. The assumption is that AI is smart enough to work around imperfections. It is not. AI systems are pattern recognition engines. They find what is consistent in the data and treat it as a signal. If your data consistently contains errors - outdated addresses, duplicate records, lapsed contacts still marked as active - the AI learns those patterns as the truth. It bases its predictions, segments, and recommendations on a foundation that does not reflect reality. B2B contact data decays at 30% per year. For a database of 100,000 records, that means 30,000 entries become inaccurate every 12 months. When an AI personalisation engine is drawing on that data to decide who to target, when to contact them, and what to offer, it is working with a picture of your customer base that is one-third wrong AI doesn't fix bad data. It amplifies it. What this looks like in practice The problems that emerge are not dramatic. They are quiet and cumulative, which makes them harder to catch. Automated email sequences reach the wrong people or the wrong addresses, generating hard bounces that damage your sender reputation and, in serious cases, trigger blocks from email service providers. Personalisation that references a customer's last purchase or location draws on a record that has not been updated in two years. Predictive models identify high-value customers to target for retention campaigns - but a portion of those customers moved, changed roles, or lapsed long ago. Each of these is a cost. Collectively, they represent a significant drag on the performance of tools that were supposed to be driving efficiency. The irony is that AI makes these problems less visible, not more. A human reviewing a list might notice that an address looks wrong. An AI processes it at speed and acts on it. A case study: what happens when AI meets dirty data A professional services firm recently experienced this directly, who work with our sister company FLG for lead management. The team began bulk emailing an existing database through their email marketing system - a reasonable use of automation for a business trying to re-engage contacts at scale. The data, however, was old. Hard bounces accumulated quickly, and their account was flagged and blocked from sending. Fetchify cleansed the data. Contact information was standardised, and inactive or undeliverable entries were identified and removed. When they resumed outreach, the results were immediate - higher engagement, no delivery issues, and the kind of performance the automation was always supposed to deliver. The AI-driven outreach did not fail because of the tools. It failed because the data had not been maintained. Once the data was clean, everything else worked as intended. The AI readiness question organisations should be asking As AI becomes a standard component of ecommerce and CRM operations, the conversation around data quality needs to change. It is no longer just a compliance issue or an operational nicety. It is a prerequisite for AI to function as intended. Before deploying any AI-driven personalisation, automated outreach, or predictive analytics tool, the right question is not 'which AI platform should we use?' It is 'is our data clean enough for AI to learn from?' For most organisations, the honest answer is no - not without first running a data cleanse. The good news is that this is not a complex or expensive process. It is a one-time exercise that resets the foundation, followed by ongoing validation to prevent decay from accumulating again. What clean data actually enables Organisations that address data quality before deploying AI achieve fundamentally different outcomes. Personalisation engines draw on accurate records and produce recommendations that reflect the real customer base. Automated outreach reaches real inboxes and generates real responses. Predictive models identify genuine opportunities rather than ghost records. The regulatory dimension is worth noting, too. The ICO can issue fines of up to £17.5 million or four per cent of global annual turnover under UK GDPR for data governance failures. AI that acts on inaccurate or out-of-date data does not protect organisations from that exposure - it amplifies it, at speed and scale. Clean data is not an enhancer of an AI strategy. It is the essential prerequisite that makes an AI strategy viable. The organisations seeing the best results from AI aren't necessarily the ones with the best tools. They're the ones with the cleanest data. Start with a free data health check and find out where you stand.
Show More