Login methods

Customers log in with a login code by email or SMS – or with their password, as usual. Which paths are offered, and which comes first, is controlled by two settings: Login methods offered to customers and Start email login with a login code.

Login code by email

By default, Start email login with a login code is switched on (recommended for the checkout): once the customer has entered their email address, Request login code is the primary action, with the helper line "We'll send you a login code." underneath. The customer receives a six-digit code by email and enters it into the digit boxes.

• After the customer requests a code, the form reports: "You'll receive a login code by email shortly if your email is registered."
• Switch the option off and the classic password-first flow returns: the customer clicks Continue, sees the password field and – below the "Or" divider – the Request login code button.
• The setting applies to the email path in both "Email & mobile number" and "Email only" modes; mobile numbers always use a code.

Password as a fallback

• In code-first mode, the customer switches to the password field at any time via the Or log in with password link; Forgot password? leads to the normal Shopware recovery.
• In password-first mode, the password is the starting point anyway; the login code is the alternative below the "Or" divider.
• The password login itself remains standard Shopware behaviour – QuickAuth removes nothing.

Login code by SMS

In "Email & mobile number" mode, the input field ("Your mobile number or email address") also accepts mobile numbers. If the customer enters a number, the login code is delivered by SMS: "You'll receive a login code by SMS shortly."

• The number must be a mobile number from one of the allowed countries (setting Allow login via mobile number); landline numbers and disallowed country codes are rejected with an error message.
• If the number already belongs to a customer account, the customer is logged in after entering the code.
• If the number is not yet linked to any account, a confirmation step follows the correct code: "Almost done. Please confirm your email to finish logging in." After confirmation, the number is linked to the account – from then on, the number alone is enough.
• If the SMS provider fails to send, the customer sees: "We couldn't send the login code via SMS. Please log in using your email address instead."

The two modes

• "Email & mobile number" (default): the form accepts both; the SMS path is open as soon as an SMS provider is set up.
• "Email only": the form becomes a plain email field ("Your email address"), the mobile number disappears entirely and login by SMS is disabled – it is rejected even via the Store API. QuickAuth also hides the legal notice automatically in this mode.

Blocking unregistered mobile numbers

The Block unregistered mobile numbers setting (off by default) tightens the SMS path: when enabled, login codes by SMS are sent only to mobile numbers already linked to a customer account.

• If no customer is found for the number, the customer sees: "SMS login is not available for this mobile number. Please log in with your email address." No SMS is sent.
• The linking step for new numbers described above is skipped in that case; customers store their number in the account under "Your profile" instead.