Street normalization
Why Straße becomes Str., free of charge, and how to hide it.
You may notice corrections that look unnecessary at first glance, most commonly "Straße" being normalized to "Str." in Germany, or the Polish "ul." street prefix being added or removed. Here is what is behind them and what you can configure.
Why street normalization happens
The shipping databases of the carriers store addresses in their official format, and that includes "Str." as the correct spelling. AddressHero normalizes the entry to that format so the address is routable exactly as the sorting systems expect it. Each street can be registered under a different official form, so there is no single, fixed abbreviation rule applied everywhere, AddressHero always matches what the carrier or map database (for example Deutsche Post or Google Maps) has on file for that specific street. This normalization cannot be switched off, because deviating from the carrier format would reintroduce exactly the routing ambiguity the app is there to remove. The same goes for the Polish "ul." prefix: there is no global setting to keep it, and no way to exempt a country or an address pattern from format normalization.
What format corrections do NOT do
They cost nothing extra. Billing is per validated order (Pro plan), not per correction. A format normalization does not add anything to your bill.
They do not inflate your analytics. Pure format fixes are explicitly excluded from the error rate and the ROI numbers on your dashboard. Your ROI is calculated from real address errors only.
Hide format-only prompts from customers
What you CAN control is whether your customers ever see format-only findings. The setting "Hide Extension for Format Errors" hides the post-checkout prompt when only a format deviation is detected. The address is still normalized in the background, but the customer is not bothered with it. Most merchants switch this on for a calmer post-purchase experience.
Related: putting orders on hold for format mistakes is possible but explicitly not recommended, the address is potentially valid. See Customer emails and on-hold orders.
Still seeing corrections you disagree with?
For real content corrections (not format) that you consider wrong, see Why was an address corrected unnecessarily?, and for individual known-good addresses use the whitelist.
Related articles
Was this helpful?