New 42-day free trial
Smarty

When to use strict vs enhanced matching in your address API

When to use strict vs enhanced matching in your address API
Andrew Townsend
Andrew Townsend
 • 
May 20, 2024
Tags

In our recent webinar, we invited Easton Gibson, one of our US Street API software engineers, to discuss key features of address validation and give insights into the functionalities of both strict and enhanced modes.

Understanding strict mode

Strict mode is precisely what it sounds like—it rigorously validates addresses against the official USPS database, ensuring that only fully accurate, postal-verified addresses are accepted. This mode is typically used for operations requiring high precision, such as legal or financial document dispatch.

For example, if you enter a known address into Smarty's address tools with strict mode, you'll see that it processes and standardizes address data, rejecting any entry that doesn't perfectly match USPS records.

However, while most people use strict mode for its reliability in confirming that an address is recognized by the USPS, its rigidity creates problems.

Introduction to enhanced mode

Enhanced mode is better than strict mode because it uses fuzzy logic, machine learning, and generally more information to provide a holistic story for each address. This mode is designed to capture and validate addresses that might not be part of the USPS database. These are known as non-postal addresses and include things such as newer developments or rural locations.

Enhanced mode’s ability to handle non-postal addresses is a significant benefit. For instance, it can identify and validate non-postal addresses and correct common address mistakes, giving you workable information instead of just an unknown result.

Enhanced mode provides everything strict mode will, but with more information about why an address does or doesn’t match. Instead of giving a “yes/no” response, it may give a “yes, if” response or “no, because.”

You can play with the enhanced mode results on the US Street API demo page.

FAQ for enhanced mode

What are the main sources for non-postal addresses in Smarty’s database?
The sources for non-postal addresses include several proprietary datasets that Smarty™ has access to, which are part of our "secret sauce." For detailed information, you can reach out to an account executive.

If I want results only from USPS addresses, should I use enhanced mode and filter out non-postal matches, or stick with strict mode?
Using enhanced mode is recommended even if you require only USPS addresses. Enhanced mode's aggressive matching strategy means it can handle typographical errors and other common discrepancies better than strict mode. Results that are non-postal will be clearly indicated, allowing easy filtering while still benefiting from enhanced mode's robust matching capabilities.

How does enhanced mode handle inputs with significant errors or typos, especially in critical components like the street name or number?
Enhanced mode is designed to be more forgiving of errors, including significant misspellings. It uses sophisticated algorithms to interpret and correct errors where possible, differentiating it from strict mode, which requires exact matches. However, there are limits; if an input is too far off from any real address data, even enhanced mode may not be able to make a correct match.

If you'd like to view the full webinar recording and the demos given, you can view that here:

 

Subscribe to our blog!
Learn more about RSS feeds here.
rss feed icon
Subscribe Now
Read our recent posts
Ecommerce shipping efficiency tools you need: Address autocomplete and verification
Arrow Icon
We know it’s not New Year's anymore, but we can still push for improvement and efficiency in our lives. Maybe you’ve lapsed on that goal to be healthier or slightly slipped on your new reading and writing regimen. No worries. Not only are we here to remind you to KEEP GOING on whatever goals you have, but we’re also here to give you an easy-to-implement solution that will create shipping efficiency and stop sending packages into the void. I mean, we’re assuming you don’t like wasting money. If you do… that’s how we’re different.
Patient form optimization: The $17.4 million problem
Arrow Icon
Let's start with a number that should make every hospital administrator do a double take: $17. 4 million. That’s how much the average hospital loses annually—just from denied claims due to patient misidentification. This isn’t from equipment costs, not from staffing shortages, and not even from insurance negotiations—just from keeping bad patient data. Surely, our forms aren’t that bad. (Yes, they are, and stop calling me Shirley. )But here’s the reality: According to the 2016 Ponemon Misidentification Report, 30% of hospital claims get denied, and over a third of those denials are caused by inaccurate or incomplete patient information.
The GPS adventures of a distracted developer
Arrow Icon
My name is Jeffrey Duncan, and at the pestering of Smarty’s editor, I’m writing a blog about the many adventures I’ve had in life and how address data has played a big part in them. I met my wife about eight years ago on a dating website. At the time, I lived in Provo, Utah, while she lived in Palmwoods, Australia, on the east coast of Queensland. On this dating app, I entered the area where I was interested in finding someone, about a 25-mile radius of Provo, Utah. I had no intention of leaving the valley, definitely not the state, and certainly not the country.

Ready to get started?