QuickAuth – Checkout Login Without Password

The login form

QuickAuth replaces the standard storefront login form in two places. This chapter covers where the form appears, which toggles control it and which texts you can adjust.

Where the form appears

  • Account login page: the normal customer account login page. On by default.
  • Checkout registration page: the checkout page where guests register and existing customers log in. On by default – and there the form starts expanded by default, so existing customers see the login path without an extra click.

Above the form sits a short description that depends on the mode: "Quick login, no password" in code-first mode, otherwise "Log in quickly to continue".

The account login page with the QuickAuth form: mobile number or email address, Request login code
The login form on the account login page, Shopware default theme.
The QuickAuth login form on a mobile screen
The same form on a phone.
The mobile code-entry step with six login code fields and a visible Resend code link
The code-entry step after requesting a login code, with the resend link visible.

The three form toggles

All three live in the QuickAuth form card and are on by default:

  • Enable on account login page: switches the QuickAuth form on the account login page on or off. When off, the standard login applies there again.
  • Enable on checkout registration page: the same for the checkout registration page.
  • Expand on checkout registration page: when on, the login form starts expanded there; when off, it starts collapsed and the customer expands it themselves.

Adjusting the wording

Three texts of the code-first mode are editable right in the settings as snippets (card Passwordless login wording), per language:

Click the icon in a snippet field to edit its text.

  • Request-code button (default: "Request login code"): the primary button.
  • Helper line under the button (default: "We'll send you a login code."): a short note that a code is coming. In "Email & mobile number" mode, it is best to keep this channel-agnostic – the channel depends on what the customer enters.
  • "Use password" link (default: "Or log in with password"): the link to the password field.

All other form texts – field labels, messages, error texts – are snippets too and can be changed under Settings → Snippets (namespace cwkqa).

If enabled, the legal notice appears beneath the form as soon as the customer types a mobile number (card Legal Text, enabled by default). QuickAuth hides it automatically in "Email only" mode. The default text is a statement of consent to SMS/RCS messages and begins with "By proceeding, you consent to get SMS/RCS messages …".

  • Text: the notice as a snippet; the %shopName% placeholder is replaced with the shop name from your basic information.
  • Font Size (px) (default: 12) and Font colour (default: #6B6B6B).
  • Enable: switches the block off entirely if you do not need it.
The QuickAuth form with the legal notice below a mobile number
The legal notice shown after entering a mobile number.
Have the legal text reviewed

The shipped text is a starting point, not legal advice. Whether and in what form consent for SMS is required is something to clarify for your own shop.

Mobile number in the account

  • In the customer account under "Your profile" there is the field Mobile number for login (placeholder: "Include country code, e.g. +44 7400 123456"). Customers can change or remove the number there at any time.
  • A hint icon can appear at the billing address phone field (card Mobile number tooltip, on by default). The tooltip explains: "You can use your mobile number to log in without a password later. …" The text and the icon colour (default: #2B3136) are configurable.
  • A mobile number can only ever be linked to one customer account; a number already in use is rejected with an error message.
The registration phone field with the mobile-number tooltip open
The mobile-number tooltip in the registration form.