Should you build or buy Address Verification & Geocoding?
Address verification and geocoding software checks that a mailing address is real and deliverable, standardizes its format, and converts it to map coordinates. E-commerce checkouts, shipping platforms, and CRM systems buy it to cut failed deliveries, catch typos at signup, and power location search and mapping features.
Buy certified address verification; self-host geocoding only for high, predictable volume without deliverability needs.
Build it, buy it, or bridge?
When building makes sense
Building makes sense when the job is geocoding, not verification, and the query volume is high and geographically bounded. OpenStreetMap's Nominatim serves 30 million queries a day on a single server at openstreetmap.org, which shows self-hosting can handle serious volume without per-query fees. Pelias is another open option with the same trade-off. What neither gives you is deliverability: OpenStreetMap data is community-maintained and doesn't know whether the postal service will actually deliver to a given address. If your use case is plotting locations on a map, routing, or search, a self-hosted geocoder covers it well once you accept the setup and maintenance cost. If your use case is confirming a customer's shipping address before you ship, geocoding alone won't tell you that, and you're back to a licensed data source regardless of how you built the rest of the stack.
When buying makes sense
Buying is the right call whenever deliverability matters, which is most commercial use of this category. Smarty says plainly that it charges per address lookup performed, with no setup fees or long-term commitments, and Loqate and Melissa price similarly. That per-lookup model is what you're actually paying for: a live license to USPS or Royal Mail reference data that tells you whether a given address will actually receive mail, something no open dataset can certify. Geocoding alone, plotting a point on a map, is a solved problem you could self-host. Confirming an address is real and deliverable is a regulated data relationship a vendor maintains for you. For most e-commerce, shipping, and CRM use cases, the cost of a failed delivery or a returned shipment outweighs the per-lookup fee many times over.
The desk read
Build-versus-buy analysis for Address Verification & Geocoding is being written. In the meantime, the framework that drives every B4 call is on the B4 Index page.
Frequently asked
What's the difference between address verification and geocoding?
Verification confirms an address is real and can receive mail, matching it against postal databases like USPS or Royal Mail. Geocoding converts an address into map coordinates for plotting, routing, or distance calculations. Many vendors bundle both, but they solve different problems and only one needs a postal license.
Can I geocode addresses for free?
Yes. Nominatim, built on OpenStreetMap data, powers openstreetmap.org itself and handles 30 million queries a day on one server. It's free to self-host, though the usage policy on the public instance caps casual use at one request a second.
Why do address verification vendors charge per lookup instead of a flat rate?
The licensed postal data behind each check has its own per-record cost, so vendors pass that through as a per-lookup fee rather than a flat subscription. Volume plans exist, but pricing stays usage-based because the underlying data license is usage-based too.
Does address verification stop typos at signup?
Yes, that's one of its most common uses. Real-time verification during checkout or account creation catches a misspelled street name or a nonexistent unit number before an order ships, which is often the fastest payback for the subscription cost.