Private Shopping Professional
Technical Information
Highlights
-
Exclusive login pre-page before the shop
-
Flexible login options with Shopware account or global access
-
Individual redirects after login or registration
-
Freely customisable pre-page with Shopping experiences
-
Direct customer login links with expiry dates and single-use functionality
Features
-
Activable login pre-page: No access to the shop without login
-
Choice between Shopware login or global login with shared username/password
-
Customisable header and footer on the pre-page
-
Freely customisable login page with Shopping experiences, including supplied template
-
Customised login links for customers with expiry dates, single-use functionality and centralised token management in the admin panel
-
Redirection rules via RuleBuilder: Customers can be directed to specific categories, landing pages or custom URLs
-
SEO option: Control whether the pre-page can be indexed
In the Shopware standard, the shop is immediately accessible to all visitors – regardless of whether they are logged in or not. This means that there is no central access restriction for exclusive offers, internal B2B shops or closed customer areas
We have therefore developed a plugin that offers the following advantages:
Exclusive login pre-page before the shop
No access without login – the shop only becomes visible to visitors after they have logged in. This creates an exclusive shopping experience for selected customers.
Flexible login options with Shopware account or global access
There are two options available: login with the regular Shopware account or via global access with a shared username and password – ideal for exclusive access without individual accounts.
Individual redirection
Redirects can be defined generally (e.g. home page, account, category) or defined based on rules using the Rule Builder. This allows you to set different landing pages for specific customer groups, countries or individual rules.
Freely customisable pre-page with Shopping experiences
The login page can be completely designed using Shopping experiences and adapted to your own corporate design. A template and a special Shopping experience element (‘Private Shopping Login’) with customisable texts, buttons and links are included.
Direct login links for customers
In addition, custom login links for customers can be created in the admin area. An expiry date can be set for each link, with single-use access enabled by default. The sales channel and domain are automatically pre-selected to simplify the creation process. All generated tokens are fully traceable, including status and usage information, and can be deleted at any time if required.
Additional B2B extensions
The following plugins extend key functions for B2B shops in Shopware and can be used in combination.
Discount groups - customer discount on product groups from list price
Enables flexible control of discounts and surcharges for customers based on products or product groups
B2B (debtors and contacts)
Enables the structured management of accounts receivable and associated contacts, including centralised maintenance of customer data.
Customized prices > Customer, product, time, rule and currency dependent
Offers customised pricing per customer or product, including tiered pricing, time periods, rules and currency.
Products rulebased enable / disable
Controls the visibility of products based on rules, customers or sales channels.
Customer Specific Product
Enables products to be displayed specifically to certain customers or customer groups.
Order matrix (rule-controlled and dynamic product groups)
Enables efficient ordering of variant products via a table-based matrix directly on the product detail page.
-> View all ACRIS B2B extensions
Award-winning support
In addition to the plugin’s functionality, every plugin comes with our 5-star support, which has been recognised by Shopware with the ‘Best Support Rating 2025’ award.
For us, first-class support is an essential part of our service – and our customers confirm this with over 600 5-star reviews.
Installation
- Open Plugin Manager via Settings > System > Plugins.
- Upload, install and activate the plugin.
Plugin configuration
6.7: Extensions > My Extensions > Private Shopping > Configure or Settings > Extensions > Private Shopping
Basic settings- Sales channel
Specify in which sales channels the pre-page should be active - Activate pre-page
Basic requirement for using the plugin. Activated by default after installing the plugin. - Pre-page login via
Choose between Shopware login or global login with shared username/password - Pre-page experience for customers who are not logged in
Select the Shopping experience for the login page. If none is selected, the plugin uses a default page. - Pre-page display Shopping experience
Defines how the login pre-page is displayed. Choose between a separate page or a modal window. - Loaded Shopping experience in the background (if the pre-page is displayed as a modal window)
If the pre-page is displayed as a modal window, an Shopping experience can be selected here to be displayed in the background.
- Define username and password for global access.
This requires activating global login under ‘Login via pre-page’. - Set the storage duration in the cookie so that customers do not have to log in again each time they visit.
- Header on pre-page
Display option for the header on the pre-page (standard header from the plugin, normal shop header, hide header – if this is defined in the Shopping experience) - Footer on pre-page
Display option for the footer on the pre-page (standard footer from the plugin, normal shop footer, hide footer – if this is defined in the Shopping experience)
- HTTP status code for redirect if not logged in
Choice between 302 (recommended) or 301 - Redirect after successful registration
Set destination page (account, home page or category) - Category after successful registration (if redirection to category was selected above)
Exact definition of which category page the user is redirected to. The prerequisite for this field is that a category was selected for ‘Redirection after successful registration’. - Redirect after successful login
Set destination page (account, home page or category) - Category after successful login (if redirect to category was selected above)
Precise definition of which category page the user will be redirected to. This field requires that a category has been selected under ‘Redirect after successful login’.
- Search engines are permitted to index the site
Setting to determine whether the login pre-page may be indexed by search engines
- Categories
Certain categories may be excluded from the login pre-page. These categories remain accessible to all visitors without a login. - URL whitelist
Individual URLs that should remain accessible without a login can be entered here.
Redirection rules
Targeted rules can be created under Settings > Extensions > Private Shopping > Forwarding Rules > Add Forwarding Rule:
Settings- Internal Name
Clear name of the rule - Active
If active, the rule will be applied, otherwise it will not. - Priority
Higher priority is checked first - Rule
Selection of which rule the redirection is based on. A rule can be created or edited in the Rule Builder.
- Link type
Definition of which type of page should be called up during redirection. Choice between entity or own URL. - Entity
Choice between landing page or category. Only selectable if ‘Link type’ is entity. - Category
Only selectable if ‘Link type’ is entity and ‘Category’ is selected for entity. - Landing page
Only selectable if ‘Link type’ is Entity and ‘Entity’ is set to Landing page. The landing page must also be added under Catalogue > Categories > Landing Pages. - Custom URL
Only selectable if ‘Link type’ is Custom URL. - Redirect URL
Enter with /. Only selectable if ‘Link Type’ is Custom URL. - HTTP status code for redirection
Select which status code the server should deliver to the client when accessed. Recommended code to use = 302: Found. (Options: 302: Found, 301: Moved Permanently).
Layout configuration
The pre-page can be freely designed under Content > Shopping experience > Private shopping.
The predefined element ‘Private shopping login’ can be used in the layout under Block category > Private shopping.
Element settings ‘Private shopping login’- Show heading
Switches the heading of the login area on or off. - Heading
Definition of the heading. Only displayed if ‘Show heading’ is active. - Show text between heading and login fields
Displays additional text between the heading and login fields. - Text between heading and login fields
Definition of the intermediate text. Only displayed if ‘Show intermediate text’ is active. - Show forgotten password
Activates a link to the forgotten password page. Only works if customers log in with the Shopware login (not with global login). - Forgot password link text
Label for the ‘Forgot password’ link. - Show registration link
Activates a link to the registration page. Only works if customers log in with their Shopware login (not with a global login). - Registration link text
Label for the registration link. - Custom registration URL
If registration does not take place via the standard page, a custom URL can be entered here. - Button text
Label of the login button.
Direct login links for customers
Customers > Overview > Select customer > Login links tab
- Set the expiry date of the login link
- Enable/disable single-useaktivieren/deaktivieren
- Select sales channel
- Select domain
- Create link
Videos
Frequently Asked Questions
The control can be managed via the ACRIS Private Shopping plugin and the rule-based redirection feature built in the plugin.
In the plugin, a rule can be created that is applied to a specific customer group.
Example:
- Rule: Customer group = Standard
- Action: Redirect to a category, for example "Please wait for activation".
In this context, the Shopware merchant registration is often used (can be activated under Settings → Customer Groups). Customers register via a special form for merchants. Until activation, they remain in the standard customer group to which the redirect rule is applied. Only after approval do they gain access to the protected area.
Yes, this is possible. In the plugin settings of the ACRIS Private Shopping Plugin, there is an activation switch that allows the login function to be enabled or disabled individually for each sales channel. This means you can specify separately for each channel whether a login page should be displayed or not.
| Version | Date | Compatibility | Changelog |
|---|---|---|---|
| 4.6.1 | 6 May 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 4.6.0 | 6 May 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 4.5.1 | 23 April 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 4.5.0 | 22 April 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 4.4.1 | 3 April 2026 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.4.0 | 25 March 2026 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.2.3 | 4 December 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.2.2 | 26 November 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.2.1 | 25 November 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.2.0 | 20 August 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.1.8 | 30 July 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.1.7 | 11 July 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.1.6 | 10 July 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.1.5 | 10 July 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.1.4 | 9 July 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.1.3 | 3 July 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.1.2 | 23 June 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.1.1 | 17 June 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.1.0 | 6 June 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.0.0 | 14 May 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 3.4.2 | 24 March 2026 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.4.1 | 20 August 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.3.4 | 10 July 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.3.3 | 9 July 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.3.2 | 23 June 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.3.1 | 17 June 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.3.0 | 6 June 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.2.6 | 25 March 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.2.5 | 20 March 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.2.4 | 18 March 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.2.3 | 18 March 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.2.2 | 12 February 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.2.1 | 24 January 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.2.0 | 23 January 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.1.7 | 2 December 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.1.6 | 27 November 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.1.5 | 21 October 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.1.4 | 14 October 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.1.3 | 11 October 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.1.2 | 11 October 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.1.1 | 10 October 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.1.0 | 9 October 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.0.4 | 2 August 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.0.2 | 24 April 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.0.1 | 22 March 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.0.0 | 21 March 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 2.7.1 | 17 June 2025 | >=6.5.0.0 <6.6.0.0 |
|
| 2.7.0 | 6 June 2025 | >=6.5.0.0 <6.6.0.0 |
|
| 2.6.3 | 16 April 2025 | >=6.5.0.0 <6.6.0.0 |
|
| 2.6.2 | 16 April 2025 | >=6.5.0.0 <6.6.0.0 |
|
| 2.6.1 | 12 February 2025 | >=6.5.0.0 <6.6.0.0 |
|
| 2.6.0 | 24 January 2025 | >=6.5.0.0 <6.6.0.0 |
|
| 2.5.6 | 27 November 2024 | >=6.5.0.0 <6.6.0.0 |
|
| 2.5.5 | 21 October 2024 | >=6.5.0.0 <6.6.0.0 |
|
| 2.5.4 | 14 October 2024 | >=6.5.0.0 <6.6.0.0 |
|
| 2.5.3 | 11 October 2024 | >=6.5.0.0 <6.6.0.0 |
|
| 2.5.2 | 11 October 2024 | >=6.5.0.0 <6.6.0.0 |
|
| 2.5.1 | 10 October 2024 | >=6.5.0.0 <6.6.0.0 |
|
| 2.5.0 | 9 October 2024 | >=6.5.0.0 <6.6.0.0 |
|
| 2.4.3 | 25 June 2024 | >=6.5.0.0 <6.6.0.0 |
|
| 2.4.2 | 24 April 2024 | >=6.5.0.0 <6.6.0.0 |
|
| 2.4.1 | 26 February 2024 | >=6.5.0.0 |
|
| 2.4.0 | 15 February 2024 | >=6.5.0.0 |
|
| 2.3.4 | 1 February 2024 | >=6.5.0.0 |
|
| 2.3.3 | 10 January 2024 | >=6.5.0.0 |
|
| 2.3.2 | 16 November 2023 | >=6.5.0.0 |
|
| 2.3.1 | 9 November 2023 | >=6.5.0.0 |
|
| 2.3.0 | 25 October 2023 | >=6.5.0.0 |
|
| 2.2.0 | 28 August 2023 | >=6.5.0.0 |
|
| 2.1.6 | 24 August 2023 | >=6.5.0.0 |
|
| 2.1.5 | 24 August 2023 | >=6.5.0.0 |
|
| 2.1.4 | 24 August 2023 | >=6.5.0.0 |
|
| 2.1.3 | 24 August 2023 | >=6.5.0.0 |
|
| 2.1.2 | 24 August 2023 | >=6.5.0.0 |
|
| 2.1.1 | 24 August 2023 | >=6.5.0.0 |
|
| 2.1.0 | 24 August 2023 | >=6.5.0.0 |
|
| 2.0.0 | 24 August 2023 | >=6.5.0.0 |
|
| 1.4.5 | 26 June 2024 | >=6.4.0.0 < 6.5.0.0 |
|
| 1.4.4 | 8 May 2024 | >=6.4.0.0 < 6.5.0.0 |
|
| 1.4.3 | 10 January 2024 | >=6.4.0.0 < 6.5.0.0 |
|
| 1.4.2 | 14 February 2023 | >=6.4.0.0 |
|
| 1.4.1 | 26 November 2022 | >=6.4.0.0 |
|
| 1.4.0 | 26 November 2022 | >=6.4.0.0 |
|
| 1.3.1 | 26 November 2022 | >=6.4.0.0 |
|
| 1.3.0 | 26 November 2022 | >=6.4.0.0 |
|
| 1.2.1 | 26 November 2022 | >=6.4.0.0 |
|
| 1.2.0 | 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 |
|
Login
Schnelle Reaktion & guter Service
Acris hat wie immer schnell reagiert und unseren Vorschlag zur SEO Verbesserung zeitnah umgesetzt. Vielen Dank Julian
Gute Erweiterung mit bestem Support
Für uns aktuell die beste Lösung für einen "Internen Shop". Es gibt viele Möglichkeiten der optischen Darstellung mit Hilfe von Einkaufswelten. Durch eine Überschneidung mit einer anderen Erweiterung gab es leichte, technische Probleme, die jedoch innerhalb von 24 Stunden durch ein Mini-Update gelöst wurden. Das Support- und Entwicklerteam ist sehr lösungsorientiert.