Master data

Master data is stored in the system both for an organisation and for a personal user account.

Personal user master data

Users are maintained independently of an organisation – they can equally be associated with different organisations.

Although master data can be stored on the user (in the administration area), users in B2B mode only use a reduced subset of their master data. Instead they inherit this data automatically from the organisation.

In B2C mode, by contrast, the master data is used from the user entity.

The following settings and data are used in B2B mode; all others are defined by the organisation:

• Last name
• First name
• Email address
• Account status
• Email address status
• Language
• Date of birth

All addresses and available terms (prices, shipping, payment methods, etc.) are likewise taken over from the organisation.

In the context of an organisation, organisation-specific master data can be set for each user.

Organisation-specific data of a user

In the context of an organisation, additional information can be stored on each associated user.

These fields are predefined by the system. They are only used in the context of the specific organisation. A user can therefore have different values stored in this area per associated organisation.

The fields are:

• Role
• CC email
• Cost centre
• Department

TIP

Additional fields can be added by IT where required. The fields can also be linked to functional flows.

Billing address

TIP

Note: In B2C mode, the user's own billing address is used. The following description therefore does not apply and the normal Shopware 6 behaviour applies.

The billing address is part of the address management as an address and is defined in the organisation itself.

The billing address is inherited equally by all users of the company account and individual customisation is not possible.

Only one address can be defined as a valid billing address.

Data entered into the form by the user during registration (or registration request) is taken directly into this record.

The data must therefore, if necessary, be checked by the agent during the approval process and reconciled with other storage locations.

If an ERP is used as the leading system at this point, the data can also be defined as non-editable in the shop backend (see here).

(List of organisations → organisation view → tab "Addresses")

Make billing address non-editable by the user

It is possible, as a matter of principle, not to allow users to change their billing address in the customer account of the shop. This approach is appropriate when changes cannot or should not be propagated directly via an ERP connection, for example if a change should be reviewed by customer service in advance.

• Billing address must not be changed (default: users may change the address)
• Show a link to a change form when changes are disabled (default: no)

Delivery address (ship-to)

In principle, the delivery address follows the behaviour of the billing addresses. The organisation can store several delivery addresses in the system. Delivery addresses can be edited at any time.

The delivery addresses are inherited equally by all users of the company account. There is currently no way for the shop operator to restrict the organisation to a fixed (non-editable) delivery address.

It is, however, possible via role management within the customer account that this option is granted to or taken from certain organisation users. For a given user role it can therefore be defined that the role can only use those addresses which the company admin has predefined.

See here → Roles and rights in the customer account XXXX

Customer number

The records are linked via the customer number (debtor number).