Critical Checkout Validation & UX Issues

Shahjahan Jewel / Ripon Sarkar 

I am reporting several critical bugs and usability issues observed on the standard Checkout Page. These issues impact data integrity and user experience and should be prioritized.

1. Input Validation and Missing Indicators

A. Full Name Field

• Problem A (Missing Indicator): The placeholder is missing the required asterisk (*) indicating it is a mandatory field.
• Problem B (Validation): The system allows me to enter only a single name (e.g., rafael), not enforcing a full first/last name.
• Expected Behavior: The field must show the required asterisk (*) and validate for at least a first and last name.

B. Email Address Field

• Problem: The system accepts invalid email formats (e.g., missing a proper TLD extension like .com or .net).
• Expected Behavior: Must enforce strict validation for standard email format (user@domain.tld).

C. Phone Number Field

• Problem A (Invalid Characters): It accepts letters and random text (e.g., dksodksodsdkdskdoskdo).
• Problem B (Country Code): It lacks a mechanism for inputting or selecting the country code, which is essential for international orders.
• Expected Behavior: Accept only valid phone characters, and include a Country/Region selector.

2. User Experience (UX) Issues

The current error display method is hurting the user experience:

• Notification Duration: The time a notification stays on the screen is too short. Users cannot reliably read or process the information before it disappears.
• Error Message Location: The pop-up in the top right is not the best UX. Inline error messages (displayed directly below the field that failed validation) would provide much better clarity and feedback.

Steps to Reproduce

These issues can be verified by navigating to the checkout page and attempting to place an order after entering the incomplete or invalid data described above.

Thanks for your prompt attention to these issues!