Outcome. Free-text country entries such as "USA", "U.S.", "United States", and "us" all collapse into one standardized value that reports, territory routing, and phone formatting can rely on.
Workflow mapEnrollment, branches and actions at a glance
flowchart TD
A[Country/Region known, not yet normalized] --> B[Custom code: lookup table match]
B --> C{Match found?}
C -->|yes| D[Set standardized value, status = Normalized]
C -->|no| E[Status = Needs manual review]
E --> F[Add to review list + create task]
When to use it / when not to
- Use it when the
Country/Regionproperty is, or was, free text, and existing data has many spellings for the same country. - Use it before phone formatting (data-quality-003) or territory-based routing, since both depend on a clean country value.
- Do not use it if
Country/Regionis already a native dropdown with no legacy free-text data behind it. There is nothing to normalize. - Do not use it to normalize state or province values. See data-quality-012 for that, which needs its own lookup table.



