20 years of online shopping and a whole industry excited to collect data and autofill and address checking functions STILL mess up apartments.

The system is set up to work well with houses, but there is no consensus on if "apartment/suite" should be a separate field or not... and it's also still often rendered wrong, and makes bad suggestions such as "correcting"

123ABC to 123Abc

Granted when I worked in database design this was my "thing" so I'm hypercritical ... but still.

I get personally offended because I suspect that it's some kind of American suburban-centric mentality that makes apartments an afterthought.

The correct answer is that "apartment suite" should be a separate field NOT tacked on to the street address, but in most renderings it should be on the same line with a comma.

And you need to deftly separate this information if the user tries to enter it in the address line.

ANYWAY.

Every now and then I STILL encounter a system that just can't handle the existence of apartments. There is no way to enter the information because they use an address checker that strips it away... but don't have their own field to store the data.
@futurebird
I have to pay a particular vendor every quarter, but I can't pay them via QuickBooks because their address checker puts them in the wrong village with the wrong ZIP code, and won't permit a manual override.