Display personal contact + rule-based + grouped
Technical Information
Highlights
-
Creation and management of any number of contact persons
-
Grouping of contact persons
-
Rule-based display via RuleBuilder
-
Display in the ‘My Account’ area or directly on landing pages/category pages
Features
-
Personal contact person with photo, contact details and additional information
-
Creation of contact person groups (e.g. sales, support, accounting)
-
Included experience world element/block for easy integration on landing pages/category pages
-
Assignment via RuleBuilder (e.g. country, postcode) and/or directly to customers
-
Order can be controlled via priorities (for groups and contact persons)
In the standard Shopware version, there is no option to display personal contact persons with photos and contact details directly to customers in the ‘My Account’ area or on landing pages/category pages. This means that important functions for direct customer service are missing, especially in the B2B sector.
We have therefore developed a plugin that offers the following advantages:
Personal contact person for customers
One or more individual contact persons can be assigned to each customer. In addition to their name, you can also store their photo, telephone number, email address and other information.
Contact person groups
To make organisation easier, contact persons can be grouped together in categories such as sales, support or accounting and displayed collectively.
Rule-based display
The visibility of contact persons is flexibly controlled via the RuleBuilder. For example, contact persons can be assigned by country, postcode, customer group or even 1:1 for an individual customer.
Flexible display
Contact persons appear directly in the ‘My Account’ area or can be integrated into categories and landing pages using a supplied experience world element.
Order by priority
Contact persons and groups can be assigned priorities. This allows you to specify which contact persons or groups are displayed first in the front end.
Installation
- Open Plugin Manager via Settings > System > Plugins.
- Upload, install and activate the plugin.
Plugin configuration
6.7: Extensions > My extensions > Contact persons > Configure
- Sales channel
Activation for all or only certain sales channels. - Display in customer account
Setting to determine whether personal contact persons are displayed in the ‘My Account’ area. - Personal contact persons in customer account (rule-based)
Contact persons are only displayed if at least one rule applies or no rule is stored. The option to display in the customer account must be activated. - Personal contact persons in customer account (experience world)
Assign an experience world for display in the customer account. If no selection is made, the default page is used. - If no contact person is available
Display menu item (default) or hide - Label for the menu item in the customer area
Individual name for the tab in the customer area (e.g. ‘My contact persons’). - Menu item positioning
Set the order in the ‘My Account’ area (e.g. at the top or at the bottom). - Text if no personal contact persons are available
Individual message if no contact person is available. - Contact person heading
Custom heading above the contact details - Image - text positioning
Specifies whether the image is displayed on the left, right, top or bottom. - Image corners
Images can be displayed as round, oval, rounded or rectangular. - Frame
Option to choose whether a frame should be visible around the contact. - Block width
Adjust the display for each device (desktop, tablet, mobile)
Contact groups
Groups can be created or edited under Settings > Extensions > Contacts > Groups.
- Internal name
Used for display in the administration. - Name
The name is displayed on the website. - Show group name
If active, the name appears once above the group. - Priority
Determines the order of the groups in the display. - Display settings
Here you can define whether only the first contact person of a group is displayed and which data (heading, name, image, email, telephone number, additional line) should be visible.
Contact persons
Under Settings > Extensions > Contact persons > Contact persons, you can create as many contacts as you like.
- Internal name
Used for display in the administration. - Active
Controls whether the contact person is displayed or not. - Assigned rules
Here you can select previously created RuleBuilder rules (e.g. country, customer group). The contact person is displayed if one or more of the rules apply. - and/or assigned customers
The contact person can also be assigned directly to individual customers – by name or customer number. - Priority
Determines the order when several contact persons apply. The higher the priority, the higher the contact person is ranked. - Contact person group
Assigns the contact person to a previously created group (e.g. sales, support). - Contact person data
Name, picture, heading, telephone number, email and an additional contact line (HTML possible). Which fields are visible depends on the group settings.
Frequently Asked Questions
Yes, this is possible in the current Shopware version of the RuleBuilder a wildcard * can be used, e.g. 0*.
Yes, example calls: Retrieve personal contacts (Admin API): POST https://www.my-shop.com/api/search/acris-personal-contact?limit=50 and update or insert personal contacts (Sync API): POST https://www.my-shop.com/api/_action/sync (Entity name in JSON: acris_personal_contact)
| Version | Date | Compatibility | Changelog |
|---|---|---|---|
| 5.2.2 | 10 March 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 5.2.1 | 4 March 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 5.2.0 | 24 February 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 5.1.0 | 19 February 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 5.0.5 | 4 December 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 5.0.4 | 30 July 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 5.0.3 | 11 July 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 5.0.2 | 3 July 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 5.0.1 | 28 May 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 5.0.0 | 11 May 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 4.4.3 | 10 March 2026 | >=6.6.0.0 <6.7.0.0 |
|
| 4.4.2 | 4 March 2026 | >=6.6.0.0 <6.7.0.0 |
|
| 4.4.1 | 24 February 2026 | >=6.6.0.0 <6.7.0.0 |
|
| 4.4.0 | 24 February 2026 | >=6.6.0.0 <6.7.0.0 |
|
| 4.3.0 | 20 February 2026 | >=6.6.0.0 <6.7.0.0 |
|
| 4.2.6 | 4 December 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 4.2.5 | 28 May 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 4.2.4 | 19 March 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 4.2.3 | 18 March 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 4.2.2 | 18 March 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 4.2.1 | 20 August 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 4.2.0 | 20 August 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 4.1.0 | 25 July 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 4.0.0 | 19 March 2024 | >=6.6.0.0 |
|
| 3.4.1 | 20 August 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 3.4.0 | 25 July 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 3.3.1 | 29 May 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 3.3.0 | 29 May 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 3.2.0 | 23 May 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 3.1.3 | 6 December 2023 | >=6.5.0.0 |
|
| 3.1.2 | 9 November 2023 | >=6.5.0.0 |
|
| 3.1.1 | 9 November 2023 | >=6.5.0.0 |
|
| 3.1.0 | 8 November 2023 | >=6.5.0.0 |
|
| 3.0.2 | 8 September 2023 | >=6.5.0.0 |
|
| 3.0.1 | 7 August 2023 | >=6.5.0.0 |
|
| 3.0.0 | 5 May 2023 | >=6.5.0.0 |
|
| 2.2.2 | 10 February 2023 | >=6.4.0.0 |
|
| 2.2.1 | 1 February 2023 | >=6.4.0.0 |
|
| 2.2.0 | 31 January 2023 | >=6.4.0.0 |
|
| 2.1.1 | 27 January 2023 | >=6.4.0.0 |
|
| 2.1.0 | 27 January 2023 | >=6.4.0.0 |
|
| 2.0.1 | 26 November 2022 | >=6.4.0.0 |
|
| 2.0.0 | 26 November 2022 | >=6.4.0.0 |
|
| 1.0.5 | 26 November 2022 | >=6.4.0.0 |
|
| 1.0.4 | 26 November 2022 | >=6.4.0.0 |
|
| 1.0.3 | 26 November 2022 | >=6.4.0.0 |
|
| 1.0.2 | 26 November 2022 | >=6.4.0.0 |
|
| 1.0.1 | 26 November 2022 | >=6.4.0.0 |
|
| 1.0.0 | 26 November 2022 | >=6.4.0.0 |
|