UPRN vs postcode: what to key your property data on
A postcode names a group of addresses; a UPRN names one. Join sales, energy certificates, council tax bands and listings on the right key and trust the result.
Most property spreadsheets are keyed on the postcode because the postcode is what people know. It works until it does not: two datasets disagree on how to write "Flat 2, 12 Lordship Lane", a block of forty flats shares one postcode with a shop, a new development gets a postcode months after its first sale. The fix is not a better postcode. It is a different key.
What a postcode is for
A postcode is a delivery unit. It groups the addresses a postal worker walks between, typically a street or part of one, often a dozen or more homes, sometimes a single large building. It was never meant to identify a property, and it does not: the same postcode covers the ground-floor shop and the flats above it. For area statistics it is fine and useful; the postcode district, the "SE23" part, is the grain MarketCode publishes its indices and volumes at. For a property it is a lookup key with dozens of collisions.
What a UPRN is
The Unique Property Reference Number is a twelve-digit identifier the local authority assigns when an address is created, published through Ordnance Survey AddressBase. Every addressable location in England, Scotland and Wales has one: each flat in a block, each house, the shop, the substation. It never changes when the address is rewritten, and public datasets increasingly carry it. The glossary entry has the short definition; this is the case for using it.
Why the join changes everything
Take one flat and five things you want to know about it: its registered sales, its energy certificate, its council tax band, whether it is listed for sale, and who owns the title. Five datasets, five ways of writing the address. Join on text and you match some, miss some and, worse, match a few wrongly. Join on the UPRN and the only question is whether each dataset has been resolved to it: a yes-or-no you can measure.
MarketCode does that resolution once, upstream, and keeps the answer. A property summary is one call because everything behind it was already joined at the front door. Where a record could not be placed on a UPRN with confidence, it is reported as not found rather than guessed, and the full record carries a source and a confidence score beside every field.
Where the UPRN is weakest
Flats in subdivided buildings. Some datasets record the building rather than the unit: an older energy certificate, a listing that gives the building address. A per-unit count over those over-reports, and a building-level record attached to one flat can be wrong for its neighbour. The floor area is the field most often affected, which matters because it is what turns a price into a price per square metre.
And coverage: AddressBase covers England, Scotland and Wales, so a Northern Ireland address has no UPRN here. HM Land Registry, by contrast, is England and Wales, so a Scottish address resolves to a UPRN and then has no sale history to attach.
Resolving an address, and what it costs
Autocomplete is free: type part of an address or a postcode and get ranked candidates. Pick one and resolve it to the canonical record and its UPRN. Through the API or an assistant that costs 2 credits (2p), because it returns a licensed Ordnance Survey record; inside MarketCode itself it is free. Then carry the UPRN through everything else. Autocomplete on every keystroke, resolve once: that is the order to ask an assistant to work in. The postcode lookup returns every address at a postcode for 2 credits (2p). How often the first suggestion is the right property, by typing style and region, is measured in the 5,000-query benchmark.
Keep the postcode for what it is good at
Area questions. The house price index, the monthly sale counts and the asking-price index are all published by postcode district, and the market pages for a district, such as SE23 in Lewisham, are built on it. Property questions want the UPRN. Most real work needs both, in that order: resolve the property, then read its area.
Do it today
With MarketCode connected to your assistant, ask: "Resolve 12 Lordship Lane, SE22 8HN to its UPRN, then give me its sale history and energy certificate." Watch it autocomplete, resolve once and reuse the identifier. That is the whole idea, for two credits (2p). To see the same property with its valuation and evidence in the workspace, start with valuation.
Keep reading: We measured our address search on 5,000 real queries. Here is every number., Land Registry Price Paid Data, explained and How to find out who owns land or a building in England and Wales.
Related guides
- Connect your AI assistant to MarketCode and value a propertyTen minutes from nothing to a valuation with its comparables, in Claude, ChatGPT, Codex or Cursor. One URL, one sign-in, no API key.
- Pull a house price index into a spreadsheet with the REST APIOne key, one free call, and the monthly index for any UK district or authority is in Excel or Sheets. The response marks which months are still forecast.
- Comparable evidence in property valuationHow valuers rank, adjust and weigh comparable sales in England and Wales, with a worked two-bed flat example and the traps in Price Paid and listing data.