Description
Preconditions and environment
Magento 2 versions tested:
- 2.4.6-p4 (with the default Blank theme).
- 2.4.7 (also tested with the default Blank theme).
Configuration:
- Stores > Configuration > Customers > Customer Configuration > Show Telephone: Set to Required.
Issue observed in both environments and themes.
Steps to reproduce
- Go to My Account as a logged-in customer.
- Attempt to Add or Edit the telephone field under account details.
- Enter invalid input, such as text or symbols (e.g., "abc123" or "!@#").
- Save the changes.
Expected result
- The telephone field in the My Account section should validate input to ensure it is a valid phone number (e.g., digits only, proper phone format).
- Invalid input should trigger an error message and prevent saving.
Actual result
- The telephone field in My Account allows invalid input (e.g., text or symbols) without validation.
- In the checkout, when retrieving customer details from the account, the invalid phone number causes errors during the shipping process.
- For example, UPS shipping fails to process the order due to incorrect phone number format.
Additional information
- Video evidence of the issue is attached for reference.
- The issue occurs regardless of the Magento version (tested on 2.4.6-p4 and 2.4.7) or theme used (Blank theme).
- This inconsistency between the My Account section and Checkout makes it critical, as incorrect phone numbers lead to shipping failures.
phone_validation.mp4
Release note
No response
Triage and priority
- Severity: S0 - Affects critical data or functionality and leaves users without workaround.Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
Metadata
Metadata
Assignees
Labels
Gate 3 Passed. Manual verification of the issue completed. Issue is confirmedA defect with this priority could have functionality issues which are not to expectations.Indicates original Magento version for the Issue report.Indicates original Magento version for the Issue report.Indicates original Magento version for the Issue report.The issue has been reproduced on latest 2.4-develop branch
Activity
m2-assistant commentedon Nov 22, 2024
Hi @marctbb. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.
@magento I am working on this
Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.
m2-assistant commentedon Nov 22, 2024
Hi @engcom-Delta. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branchDetails
- If the issue is reproducible on2.4-develop
branch, please, add the labelReproduced on 2.4.x
.- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
Issue: Confirmed
once verification is complete.engcom-Delta commentedon Nov 22, 2024
Hi @marctbb ,
Thanks for your reporting and collaboration.
We have verified the issue in Latest 2.4 develop instance, but we are unable to reproduce the issue. Kindly refer the screenshots.
Steps to reproduce

Stores > Configuration > Customers > Customer Configuration > Show Telephone: Set to Required.
Observe Error displays when user fill invalid phone number
Can you please re-verify and confirm if you are still facing the issue.
Thanks.
marctbb commentedon Nov 25, 2024
Hi,
Thank you for your response and for verifying the issue.
I have re-tested this scenario using a freshly installed Magento 2.4.7-p3 instance, and I can confirm that the issue still occurs in this version. I have attached a video recording demonstrating the exact steps and the error encountered when entering invalid input in the telephone field.
Key details of the environment:
Steps followed are identical to those mentioned in the ticket.
The error persists when saving invalid phone numbers like abc123 or !@# in the customer account details. It does not trigger the expected validation message.
Attached Evidence:
Video of the issue reproduction in my environment
Could you kindly verify this on a Magento 2.4.7-p3 environment or provide any additional steps for us to align?
Looking forward to your feedback.
Best regards,
engcom-Delta commentedon Nov 26, 2024
Hi @marctbb ,
Thanks for your reporting and collaboration.
We have verified the issue in 2.4.7-p3 instance and the issue is reproducible. Kindly refer the screenshots.
Steps to reproduce
Thanks.
45 remaining items
github-jira-sync-bot commentedon Jan 20, 2025
❌ Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-13418
magento#39395 Telephone field in customer account does not validate
ajay2108 commentedon Feb 28, 2025
@magento run all tests
magento#39395 fixes for automation checks failure
ajay2108 commentedon Mar 6, 2025
@magento run all tests
engcom-Hotel commentedon Mar 7, 2025
Hello @ajay2108,
Just want clarify you, the command which you have tried to run above will work only on the PRs, not in issues. As I can see you have created this PR #39688, please run this command there to run all the tests.
Thanks
marctbb commentedon Jun 16, 2025
Hello, any update about this?
Thank you