Foundation · 2 min
What you need to know
How should international phone numbers be collected?
Show a country calling-code selector, accept readable local input and normalize it for supported downstream use. Avoid teaching customers to type a particular punctuation pattern.
Should checkout show a country-code selector?
Usually, yes for international sales. Tie the default to the selected country but let customers change it, because residence, delivery and phone country may differ.
How should phone numbers be stored internationally?
Store a normalized international representation, such as an E.164-compatible value where applicable, plus any extension and the original display when operationally useful.
Should phone numbers be required at checkout?
Require it only when delivery, fraud review or support genuinely needs it. Explain the purpose and avoid collecting unnecessary contact data.
How should international customer names be stored?
Support the customer’s full name in their script and preferred order, with enough flexibility for multiple or single components. Store shipping label transformations separately.
Should checkout assume every customer has first and last names?
No. Some customers use one name, multiple family names, patronymics, or different ordering. Ask for the minimum structure required by payment and carrier systems.
A quick store check
Enter a single name, a multi-part name and three international phone formats and inspect stored and displayed values.
Foundation · 2 min
Frequently asked questions
Can a phone country code be inferred from shipping?
It can be suggested, but the customer must be able to correct it.
Should names be converted to Latin characters automatically?
Only when an operational system requires transliteration, while preserving the customer’s original name.