Customer sign-in
Sign-in requirements depend on your store configuration. Stores without a login requirement retain their existing try-on journey. Ask support to confirm which sign-in method is available for your store before changing an existing setup.
Phone verification
Section titled “Phone verification”Where Aabhas phone verification is enabled, customers enter a phone number with its country code and the six-digit SMS code in the try-on dialog. The code expires after five minutes. Sending and verification attempts are limited to protect customers from unwanted messages.
This verifies access to that phone. It does not sign the customer into Shopify checkout or grant merchant administration access. An existing account may need additional confirmation before it can be linked; do not create a replacement account or change permissions to bypass a linking error.
Session behavior
Section titled “Session behavior”The current theme-widget phone session is held in page memory. Refreshing or navigating to another product can require verification again. Do not promise that customers stay signed in across product pages. Repeated requests can reach the sending limit; wait rather than repeatedly requesting codes.
An optional Aabhas profile link can be available after verification. It is short-lived and single-use; reopening an expired link requires a new authorized handoff. Access to a customer profile does not grant merchant permissions.
Troubleshooting
Section titled “Troubleshooting”- Check the international phone format and use the newest code after requesting a replacement.
- For an expired code, use the dialog’s resend action when available.
- After a timeout or uncertain verification result, do not repeatedly submit the same request. Follow the dialog instructions or contact support.
- If account confirmation is requested, complete the authorized confirmation flow or contact support. Never share OTPs, passwords or account-linking codes.
- Send support the store URL, approximate time, affected step and displayed error, without customer photos or credentials.
Before enabling a login requirement for customers, test receipt of an SMS, wrong and expired codes, cancellation, a successful try-on, navigation to another product, and your custom modal if used. Keep a known working configuration until those checks pass.