Short answer: A US address is a system, not a sentence. The carrier checks that the city, state, and ZIP agree before it accepts the label. When they don't — wrong city for the ZIP, a moved customer, a PO box in a city field — the address is flagged inconsistent, the label may be rejected, or the parcel is misrouted. The fix is a consistency check at the ZIP + city + state level, run before you ship.
A US ZIP code is not an arbitrary number — it maps to a delivery route, and the USPS binds a specific city and state to each ZIP (and to each ZIP+4 segment). So an address is internally consistent only when:
street + house number → resolves to a delivery point
city + state → matches the ZIP
ZIP → matches the city + state
A validator that only checks "does the street exist" misses the most common failure: the street is fine, the ZIP is wrong for that city.
| Cause | What happens | Why it slips through |
|---|---|---|
| Customer moved recently | City they remember ≠ city bound to new ZIP | Autocomplete filled the old city |
| Town spans multiple ZIPs | Entered the "main" city name, not the ZIP's bound city | Humans use the familiar name, not the postal one |
| PO box typed in street field | Carrier expects a street or a PO box format | Mixed up the two input boxes |
| Wrong state abbreviation | CA vs a different "C*" state | Typo in the dropdown or free text |
| Military APO/FPO/DPO | Treated as civilian, falsely flagged | Validator doesn't recognize the military format |
None of these are "the customer lied." They are format/consistency errors — exactly the class an automated check is built to catch.
A mismatch caught at label time costs you nothing: you standardize the address (or ask the customer) and reprint. The same mismatch caught after the parcel is moving becomes a misroute, a return, or a "delivered to the wrong city" dispute — each one more expensive than the last.
This is also where AddressGuard earns its keep: it runs the ZIP–city–state consistency check on the free data main path, so the bulk of your orders are validated at zero cost, and only addresses the free path cannot confidently resolve escalate to the paid official backstop.
You do not need to force customers to type ZIP+4 — the carrier and your validator can derive it — but you must not ship an address whose 5-digit ZIP disagrees with the city/state.
Disclaimer: This is operational guidance for US shipping, not official USPS or carrier advice. ZIP bindings, APO/FPO handling, and carrier validation rules change; confirm current behavior with your carrier before relying on any specific rule.