Configuration for customer data¶
User Groups for private and business customers¶
To separate business and private users in one installation, there are two User Groups in the "Shop user" group.
You can configure those groups using
Timeout for ERP updates¶
The shop checks the age of the customer data that is stored in the session. If it is too old (past timeout) the shop fetches the data from the ERP again.
The default timeout is configured in
Default handling for VAT¶
You can define VAT handling rules in configuration.
isPriceInclVat is set to
true, the customer always sees prices including VAT.
For B2B shops, the handling can be changed.
You can override the setting per customer if required (e.g. if the ERP provides this information per customer).
In some cases the customer does not have to pay VAT at all (for example, for shopping abroad).
1 2 3
Working with contact data¶
Fetching of the customer contact data¶
You can configure when customer contact data is fetched:
onPreEvent: contact is requested before requesting customer data
onPostEvent: contact is requested after requesting customer data
disabled: disable selecting contact before/after requesting customer data
Set up the contact number¶
Set the contact number in the Back Office, in the
contact_number Field of a User Content item,
Contact number: KT100210
Connecting to the events¶
To take advantage of existing events, for example to modify customer contact data,
EventService must listen to the
1 2 3 4
You also have to implement appropriate methods:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
User edit interface configuration for backend¶
You can add new form fields for buyer address and delivery addresses in the Back Office.
The additional fields are stored in
ses_extension of the address.
If the configured
ses_extension field does not exist, it is created.