Address Lookup Pricing Without Subscription: One-Off Credit Packs vs Recurring Fees
In 2026, UK store owners are paying more than they should for address lookup. Most providers hide their pricing behind sales calls, lock you into annual commitments, and auto-renew before you've noticed. If you've just opened an invoice from Loqate or Fetchify and felt that sinking feeling, you're not alone - and you're right to start looking for a better model. This guide breaks down exactly how address lookup pricing works, what Royal Mail PAF (Postcode Address File) licensing actually requires, and how to calculate the real cost of each model for a typical WooCommerce store.
How UK Address Lookup Pricing Models Actually Work
There are two dominant pricing models in the UK address lookup market: subscriptions and credit packs. They sound simple, but the details matter enormously when you're a small or mid-sized store owner rather than an enterprise with a dedicated procurement team.
Subscription models charge you a recurring monthly or annual fee - sometimes with a lookup allowance, sometimes with per-lookup overages on top. The fee applies whether you use the service or not. Seasonal stores, new sites, and low-volume shops end up subsidising enterprise infrastructure they don't need.
Credit pack models work differently. You buy a block of lookups upfront, use them as you go, and top up when you're ready. There's no monthly minimum, no auto-renewal, and no commitment beyond what you've purchased. The trade-off - and it's worth being honest about this - is that credits expire. For SnapAddress, credits are valid for 12 months from purchase. That's not arbitrary: it's a requirement of the Royal Mail PAF licensing framework that every licensed provider operates under. A 500-credit Starter pack costs £17.50 and lasts a low-volume store a couple of months, well within that window; busier stores size up to a larger pack.
What Does a UK Address Lookup API Actually Cost?
This is where things get murky with most providers. Loqate and Fetchify don't publish pricing publicly - you have to request a quote, sit through a discovery call, and wait for a proposal. That process exists to anchor you to a contract before you've compared alternatives.
Ideal Postcodes publishes its pricing and, like us, sells pay-as-you-go credits with no subscription - as of July 2026 their bundles work out at roughly 4.5p per lookup at entry size down to about 2.8p at volume. GoAddress offers pay-as-you-go credits too, but their per-lookup rates and data sourcing aren't always clearly documented.
SnapAddress publishes every price on the pricing page, with no registration required to see it. Here's how the credit packs break down:
| Pack | Lookups | Price | Per Lookup |
|---|---|---|---|
| Free | 100 | £0 | - |
| Starter | 500 | £17.50 | 3.5p |
| Standard | 2,000 | £60 | 3p |
| Business | 5,000 | £140 | 2.8p |
| Pro | 15,000 | £375 | 2.5p |
No overage charges. No monthly fee. If you run out of credits, your checkout falls back to manual address entry - orders still go through, no HTTP errors, no broken experience for your customers.
Why Subscription Address APIs Lock You In
The subscription model isn't inherently dishonest, but the way it's sold often is. Annual commitments are presented as discounts. Auto-renewal clauses are buried in terms. And when you want to leave, you're told your contract runs until the next renewal date - which could be eleven months away.
The practical effect: you're paying for address lookup API capacity whether your store is busy or not. A store that does 80% of its volume in Q4 is still paying the same monthly fee in February. That's a structural mismatch between how subscription pricing works and how e-commerce revenue actually flows.
There's also the question of what happens when your needs change. If you migrate from WooCommerce classic checkout to Checkout Blocks, you might discover your existing plugin breaks entirely - and you're still paying for it. Most UK address lookup plugins were built using DOM manipulation against the classic checkout structure. Checkout Blocks renders differently, and those plugins simply don't fire. You're left paying a subscription for a broken integration.
Is Pay-As-You-Go Address Lookup Right for Your Store?
Pay-as-you-go address lookup - credit packs, no subscription - suits most WooCommerce stores better than a recurring plan. Here's a simple way to calculate whether it fits your situation.
Estimating Your Monthly Lookup Volume
First, a definition worth being precise about: a lookup is one API request, not one checkout. Because the checkout field searches as the customer types, a completed address search uses two to four lookups - a few suggestions as they type, then one retrieval when they pick. Not every order triggers a search either - some customers type manually, and returning customers often skip it - so a reasonable estimate is that half to two-thirds of orders use the lookup. So a store processing 200 orders a month runs roughly 120-140 searches, or around 300-500 lookups. At 3p per lookup on the Standard pack, that's roughly £10-15 per month, and a single 2,000-lookup pack still lasts several months.
Compare that to a subscription plan with a £30-50 monthly minimum. The maths isn't close for most small stores.
When a Subscription Might Make Sense
Very high-volume stores - processing thousands of orders daily - may find subscription pricing competitive once they've negotiated enterprise rates. But that negotiation requires a sales relationship, a procurement process, and ongoing account management. For the vast majority of WooCommerce store owners, that overhead isn't worth it.
Does Address Lookup Quality Differ Between Providers?
Yes, and the difference matters for your delivery rate. Every licensed UK address lookup provider uses Royal Mail's Postcode Address File - the same underlying dataset. But how that data is accessed and what layer sits on top of it varies.
Some plugins use Google Places API rather than Royal Mail PAF directly. Google Places works well for finding towns, streets, and landmarks, but it frequently misses the flat and unit-level detail that PAF carries. A customer at Flat 3, 12 High Street might get "12 High Street" autocompleted - close enough to submit, wrong enough to cause a failed delivery. According to Baymard Institute's checkout usability research (April 2023), 28% of mobile sites still require users to manually enter city and state fields, creating exactly this kind of friction and error.
SnapAddress uses Royal Mail PAF data directly - over 30 million UK addresses, updated monthly. We're a licensed Royal Mail PAF Solutions Provider, which you can verify directly with Royal Mail's Address Management Unit. That's the same data standard that postal workers use to sort and deliver the post.
What Is Royal Mail PAF Licensing and Why Does It Affect Pricing?
PAF - the Postcode Address File - is Royal Mail's database of UK delivery addresses. To use it commercially, providers must hold a licence from Royal Mail and pay licensing fees based on usage. Those fees are real costs that flow through to the pricing you see.
This is why the credit expiry exists. Royal Mail's PAF licensing framework requires licensed providers to track and report usage within defined periods. The 12-month credit validity on SnapAddress packs isn't a commercial tactic - it's a licensing constraint that every PAF-licensed provider operates under, including Loqate, Ideal Postcodes, and Fetchify.
It also explains why some cheaper-looking alternatives use Google Places or unlicensed data instead. In October 2025, the High Court of England and Wales ruled that getAddress.io's address data infringed Royal Mail's and IDDQD Limited's database rights. Thousands of stores were left with broken address lookup overnight. Proper PAF licensing isn't a nice-to-have - it's what keeps your integration legally sound and operationally stable.
How SnapAddress Compares to Loqate, Fetchify, and Ideal Postcodes
The honest comparison across providers comes down to four variables: data source, pricing transparency, contract terms, and integration complexity.
- Loqate: Enterprise-grade, PAF-licensed, but pricing requires a sales call and contracts typically involve annual minimums. Strong for global address lookup; expensive for UK-only WooCommerce stores.
- Fetchify: UK-focused, subscription-based, pricing not publicly listed. Auto-renewal has caught store owners out.
- Ideal Postcodes: Publishes its pricing, pay-as-you-go credits with 12-month validity, PAF-licensed, no recurring commitment - the closest model to ours. The honest difference is price per lookup (roughly 4.5p-2.8p as of July 2026, against our 3.5p-2.5p) and WooCommerce integration depth.
- GoAddress: Pay-as-you-go credits available, but data sourcing and per-lookup rates vary by plan and aren't always clearly documented.
- SnapAddress: Published pricing, credit packs, no subscription, Royal Mail PAF licensed, WooCommerce Checkout Blocks support built in. Integration takes minutes, not days.
If you're migrating from Loqate specifically, our API supports Loqate's request format. Change the endpoint, swap the key, and your existing integration keeps working. The Loqate migration guide walks through each step.
How to Calculate the Real Cost of Address Lookup for Your Store
Subscription providers quote monthly fees. Credit pack providers quote per-lookup rates. To compare them fairly, you need a common unit: cost per completed order.
Take your monthly order volume. Multiply by 0.65 (a conservative share of orders that use the lookup field) to get your monthly address searches. Multiply by 3 - the typical lookups per search, since the field searches as the customer types - to get your lookup volume. Multiply by the per-lookup rate. That's your monthly address lookup cost on a credit pack model.
For a store doing 300 orders per month: 300 × 0.65 = about 195 searches, then × 3 = roughly 585 lookups × 3p = about £18 per month on the Standard pack. A typical subscription plan for the same volume would cost £25-40 per month. The credit-pack model still comes out ahead for most stores, and you only pay for the lookups you actually use.
The ONS e-commerce survey documents how deeply embedded electronic trading is across UK businesses - address accuracy at checkout feeds directly into fulfilment costs, return rates, and customer satisfaction. Every failed delivery costs you the delivery fee, the redelivery, and potentially the customer relationship.
If you're ready to see exactly what address lookup would cost for your store - with no sales call and no commitment - start with 100 free lookups on SnapAddress. No card required. You'll have a working integration before the free credits run out.
Frequently Asked Questions
Do address lookup credits really expire, and is there any way around it?
Yes, credits expire at 12 months. This applies to every Royal Mail PAF-licensed provider - it's a licensing requirement, not a commercial choice. There's no way around it under a properly licensed service. For most stores, a single credit pack lasts well within that window. If you're buying the Pro pack (15,000 lookups) and won't use them within 12 months, buy a smaller pack instead and top up as needed.
What's the difference between address lookup pricing from SnapAddress vs Loqate for a small WooCommerce store?
Loqate targets enterprise clients and prices accordingly - you won't see a number without a sales conversation, and contracts typically involve annual minimums. SnapAddress publishes every price on the website, sells one-off credit packs from £17.50, and requires no commitment beyond what you buy. For a store doing a few hundred orders per month, the cost difference is significant: SnapAddress credit pack pricing typically works out at £10-20 per month versus £30-50+ on enterprise subscription plans.
Does a no-subscription address API mean worse reliability or support?
Not with a properly licensed, purpose-built service. SnapAddress runs its own licensed infrastructure - it's not a reseller layered on top of another provider's API. If your credits run out, your checkout falls back to manual entry rather than throwing errors. And because we're built specifically for WooCommerce, including native Checkout Blocks support, there's no fragile DOM manipulation that breaks when WordPress updates. Transparent pricing and reliable infrastructure aren't in conflict - they're both just design choices.