Login / Registration

In this article you will receive useful information about the configuration of the login / registration and individual salutations. You can decide yourself, which saluation will be available in which shop and how this works.

Login / registration

Use these settings to globally configure the login and registration in your storefront.

• Minimum password length (registration): Minimum password length for new customers in the registration form.
• Standard payment method ID (registration): Default payment method ID for new customers. Please make sure that your default payment method has no restrictions, otherwise registration may fail or your customer won’t be able to place an order using their desired payment method.

You can also find ID under "Configuration > Payment methods", with the payment methods ID in parenthesis (1).

Default and fallback payment methods should never be restricted (i.e. location-based payment methods, because this may lead to cancellation). Only use unrestricted payment methods, like prepayment (ID 5).

• Standard recipient group ID for registered customers (system / Newsletter): Here you can define the default recipient group ID for your newsletter recipients.
• Generate customer numbers automatically: If set to "Yes", Shopware generates customer numbers automatically during registration.
• Deactivate AGB terms checkbox on checkout: If set to "Yes", the AGB terms checkbox will be disabled in the checkout.
• Display country and state field in shipping address forms: This shows the country and state dropdown in each shipping address form.
• Data protection conditions must be accepted via checkbox: This shows a data protection conditions checkbox in the registration, which must be checked from your customer, otherwise the registration is impossible.
• Default payment method ID: This is your fallback payment method. For instance, if risk management payment methods are blocked, Shopware uses the payment method defined here as a safety.
• Confirm customer email addresses: If active, the customer has to enter his email address 2 times for address confirmation to take place.
• Deactivate "no customer account": If set to "Yes", customers are not able to place an order without creating an account.
• Mark VAT ID number as required for company customers: If set to "Yes", company customers must fill the VAT ID number field in the registration.
• Check current password at password change requests: If set to "Yes", the customer must enter his current password while in order execute a password change.
• Treat phone field as required: If set to "Yes", the phone field (if active) is set as required.
• Show phone number field: If set to "Yes", the phone number field is displayed in the registration form.
• Password must be entered twice: If set to "Yes", the customer must confirm his password in the registration, otherwise he has to enter it only once.
• Show birthday fields: If set to "Yes", the birthday field is displayed in the registration process.
• Birthday is required: If set to "Yes", the birthday field (if active) is required.
• Show additional address line 1: If active, this shows the 1st additional address line in every address form.
• Show additional address line 2: If active, this shows the 2nd additional address line in every address form.
• Treat additional address line 1 as required: This makes the 1st additional address line (if active) required in all address forms.
• Treat additional address line 2 as required: This makes the 2nd additional address line (if active) required in all address forms.
• Show "I am" select field: If active, the registration form shows an "I am" field that can be used to define whether the user is a private customer or merchant.
• Show zip code field before city field: If set to "Yes", the zip code field is shown before the city field in every address form. Otherwise it will be shown behind the city field.
• Available salutations: This defines the salutations that can be used for the configured shop.
• Show title field: If active, this shows the title field (simple text field) in every address form.
• Use captcha in registration: If this option is activated, a captcha is used for registration. The Honeypot captcha is recommended for this.
• Create Shopware login cookie: As soon as you have activated this option, a cookie is saved by which the user can be identified again. You can find more detailed information on this in our Wiki article on the Shopware Login Token.

Defining salutations

At first you should define your desired salutations and an abbreviation for each salutation because you need this for the internal mapping.

Defining abbreviations

At first you have to define the abbreviations for the salutations you want to use.

By adding a new abbreviation in the basic settings, Shopware creates a snippet for it, which is not filled by default. If you create an abbreviation which already exists, it will be mapped on the existing snippet.

Just go to Configuration > Basic settings > Frontend > Login / registration, there you should see the option available salutations, fill it with the desired salutation for the specific shop. Please enter the abbreviations lowercased and seperated by comma and without spaces. Notice that you should do this setting for each of your language- or subshops because there is no fallback. At saving Shopware creates the needed snippets and will allocate them in the frontend.

Enter snippets

Thereby your snippets are allocated in the frontend as you want to, you have to enter the snippets first. Open the Snippet Manager in Configuration > Snippets and open Namespaces > Frontend > salutation, here you should see all your created salutation abbraviations with their empty values, just enter the desired value, so the snippet can be used in the frontend. Please Note that this must be made for every language seperately, you have to fill at least all salutations you use in the specific language!

In the frontend

In the Frontend you'll now see your configured salutations.

Usage in emails

As in any other place Shopware uses salutations, your individual salutations can be used the same way, just implement them as the other salutations e.g. in your emails.