Outcome. Street addresses land in one consistent format, title case with standard abbreviations for street, avenue, suite, and similar terms, so mailing labels, exports, and address-based matching all read the same value.
flowchart TD
A[Street address known or changed] --> B[Custom code: title case + whole-word abbreviation mapping]
B --> C[Set Street address to standardized value]

When to use it, when not to
- UseUse it when addresses arrive from multiple sources, forms, imports, manual entry, with inconsistent abbreviations and casing: "123 MAIN ST", "123 main street", "123 Main St.".
- UseUse it as a light normalization pass; it standardizes format, not accuracy. It does not verify the address exists or correct a wrong street name.
- SkipDo not use it expecting full address validation or geocoding. That needs a dedicated address-verification service called from custom code with its own API key and cost, which is out of scope for this fiche.
- SkipDo not use it on portals where the address field is rarely used or not relied on for anything operational; the cleanup effort is not worth it there.
or the data quality pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.





