Outcome. Industry values imported as free text or as slightly different phrasing all collapse into one of your portal's standard industry options, so segmentation and reporting by industry are not silently split across near-duplicate values.
flowchart TD
A[Industry known, not yet standardized] --> B[Custom code: lookup table match]
B --> C{Match found?}
C -->|yes| D[Set standardized value, status = Standardized]
C -->|no| E[Status = Needs manual review]
E --> F[Add to review list + create task]

When to use it, when not to
- UseUse it when
Industryvalues arrive from imports, integrations, or enrichment tools as free text or as a different vendor's category list, rather than matching your portal's own picklist options exactly. - UseUse it right after a bulk import from a source system with its own industry taxonomy, before that data feeds segmentation or routing.
- SkipDo not use it if
Industryis already a native dropdown on your portal with no legacy or externally sourced free-text values behind it. There is nothing to normalize. - SkipDo not use it to invent an industry value for a record with none at all. This workflow maps existing values to a standard option; it does not infer industry from company name or domain.
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.





