Links

Visibility of address changes

When sending mail or using Address Verification through Lob, addresses can be altered to match USPS requirements. This includes performing actions such as standardization, fixing typos like wrong zip codes, etc. These changes are surfaced back up to you, and if needed you can see the changes made.

Why is this important?

Some companies may want to update their addresses to what we return when standardizing and correcting—however, some may also want to log what we changed. This could be important for compliance reasons as well as customer experience; showing your end users what was changed could be a very nice touch in your workflow.

How do we (programmatically) solve this problem?

The way to do this today is to do a string comparison and see what we altered. For example, you will need to compare the address you passed to Lob with the address we returned back. With our AV product, you can retrieve more granular information without having to split out the address data on your own. For example, if you passed in "street" and in the API response you received "ST" in the "Street Suffix" field, you would know that was the specific change. If the "Street Name" was corrected you would see that split out as well. Otherwise, you can compare the full address and pull out the changes from there.
This leaves a lot of room for customization on business logic to determine what is important to your team when classifying something as a change. Oftentimes a change like “Street” to “St '' is not something the business team wants to be surfaced. It’s these types of business rules that are important when handling these alterations.
​
Below is an example of creating a postcard and comparing the to address input with the to address response to identify changes.
TypeScript
Python
Ruby
PHP
Java

Further resources