You can standardize phone number formats by stripping all non-numeric characters, adding the appropriate country code prefix, and converting to E.164 format (+15551234567) — which is the international standard accepted by virtually every telephony and verification system.
Phone number standardization is one of the most straightforward — and most frequently skipped — data cleaning operations. The variety of formats that represent the same 10-digit number is genuinely surprising until you try to deduplicate on a phone field.
Why Phone Number Formats Are So Inconsistent
Users enter phone numbers in whatever format feels natural to them. Different cultures, countries, and generations have different conventions:
- (555) 123-4567 — US format with parentheses
- 555-123-4567 — US format with dashes
- 555.123.4567 — US format with dots
- 5551234567 — digits only, no formatting
- +1 555 123 4567 — international format with spaces
- +1-555-123-4567 — international format with dashes
- 1-555-123-4567 — country code without plus sign
All of these represent the same US phone number.
Sohovi profiles your datasets for quality issues in minutes — see what's broken before it breaks your pipeline — try Sohovi free.
The Three Steps to Phone Number Standardization
Step 1: Strip all non-numeric characters. Remove parentheses, dashes, dots, spaces, and any other non-digit characters. The result should be a string of digits only.
Step 2: Validate the digit count. For US/Canada numbers: should be 10 digits (without country code) or 11 digits (with country code "1"). If 11 digits starting with "1", that's the country code. If 10 digits, prepend "1". Other lengths indicate an error.
For international numbers: must be between 7 and 15 digits (ITU standard). Validate against the expected format for the country.
Sohovi lets you set up validation rules for any column and instantly see which rows fall outside them — no code or SQL required.
Step 3: Convert to E.164 format. E.164 is the international standard: "+" followed by country code followed by subscriber number, no spaces or formatting. For US numbers: +15551234567.
Handling International Phone Numbers
For datasets with contacts from multiple countries:
- Strip non-numeric characters
- Check whether the number starts with a country code
- If no country code can be inferred, flag the record for manual review or use the country field to infer the country code
- Convert to E.164
If you don't know the country and the number is ambiguous (e.g., 10 digits could be US or many other countries), flag it rather than guessing.
What to Do With Phone Numbers That Fail Standardization
- Fewer than 7 digits after stripping: almost certainly a data entry error — flag for review
- More than 15 digits: likely contains extra data (extension, PIN) — attempt to parse
- Contains letters: either a typo or a vanity number (1-800-FLOWERS) — flag for manual correction
- All zeros or repeated digits: likely a placeholder — flag as invalid
Frequently Asked Questions
Q: What is E.164 format for phone numbers? E.164 is the international standard format for phone numbers: a "+" followed by the country code and the subscriber number, with no spaces, dashes, or parentheses. For example, a US number in E.164 format is +15551234567. It's the format used by telephony systems, SMS APIs, and phone verification services.
Q: Why should I standardize to E.164 rather than another format? E.164 is unambiguous (the country code is always present), accepted by virtually every telephony API and verification service, and sortable as a string. Other formats are region-specific and ambiguous for international datasets.
Q: How do I handle phone extensions in standardization? Extensions should be stored in a separate field, not in the main phone number. If your current data has extensions embedded in the phone field ("555-123-4567 x890"), parse them out during standardization: main number to the standardized phone field, extension to an extension field.
Q: What should I do with phone numbers that contain letters? Letters in a phone number usually indicate a typo or a vanity number (like 1-800-FLOWERS, which maps to 1-800-356-9377). Vanity numbers can be converted to digits using the standard phone keypad mapping. Obvious typos need manual correction.
Q: How do I handle historical data where the country code can't be inferred? If you have a country field alongside the phone number, use the country to infer the expected country code. If the country field is also missing or wrong, flag the record as "country code unknown" and route for manual review. Don't assume a country code for ambiguous numbers.
Q: How does phone number standardization affect deduplication? Dramatically. A phone-number-based deduplication on unstandardized data misses all records where the same number is formatted differently. After standardization, identical phone numbers look identical regardless of the original format — deduplication match rates improve significantly.
Q: What's the most common mistake in phone number standardization? Assuming all phone numbers in the dataset are from one country. International datasets often have a mix of country formats. Standardizing all numbers as if they were US numbers will produce incorrect results for non-US numbers.
Q: How do I validate that a phone number is currently active after standardizing the format? Format standardization confirms the number has the right structure. Validating that it's active requires a carrier lookup or SMS/voice verification service. These services check whether the number is assigned to an active subscriber.
Q: Can spreadsheet formulas handle phone number standardization? For simple cases (standardizing US-only phone numbers to a consistent format), Excel and Google Sheets formulas can handle stripping non-numeric characters and applying consistent formatting. For international numbers or complex cases, a dedicated transformation tool or script is more reliable.
Q: How often should phone number data be re-standardized? Standardize at import for new data. For existing data, run a standardization pass whenever you notice inconsistency in phone fields or before any operation that depends on phone matching (deduplication, verification, outreach).
Phone number standardization is a one-time investment that pays returns on every deduplication, outreach, and verification operation. Strip the formatting, validate the digit count, convert to E.164 — done.
Sohovi automatically finds every duplicate in your dataset — including near-matches — and shows you exactly which rows are affected.
