Shipping method / Payment method Preselection
Technical Information
Highlights
-
Automated preselection of shipping & payment method
-
Prioritization of shipping and payment methods
-
Additional field for storing a preferred payment method per customer
-
Avoid unwanted messages
-
Suppress saving of the last selected payment/shipping method
Features
-
Prioritization of shipping and payment methods via additional field
-
Automatic preselection of payment & shipping method in the storefront via prioritization
-
Taking into account a customer-specific payment method stored in the system during pre-selection
-
Hide unwanted messages
-
Suppress saving of the last selected payment/shipping method in order to reprioritize afterwards
It often happens that preselected shipping or payment methods are not available for certain products. In such cases, an error message is displayed by default. Such error messages are undesirable and reduce usability.
We have therefore developed a plugin that offers the following features:
Automated preselection of shipping & payment methods
To prevent error messages when certain delivery or payment methods are unavailable for products, the plugin ensures an automated selection. This is achieved through prioritisation in the backend. A custom order can be set via additional fields in the administration settings, whereby the valid delivery or payment method with the highest priority is automatically selected. This not only prevents error messages but also gives you greater control over your own shop.
In addition, a preferred payment method can be stored for each customer via an additional field. This is taken into account during automatic pre-selection, provided it is available for the current shopping basket. Which payment method is ultimately selected depends on the plugin configuration: depending on the settings, either the most recently used payment method, the one stored for the customer, or the global prioritisation scheme is used. If the preferred payment method is not available, a suitable alternative is automatically selected based on the defined prioritisation scheme.
Hide notification of automatic change of shipping or payment method
Automatically changed settings also trigger push notifications in the storefront. Therefore, a solution has been implemented to hide these messages as well.
Suppress storage of the last selected shipping/payment method
To ensure that the automatic storage of user inputs does not override the shop owner's prioritization, this can be disabled via the plugin configuration.
Installation
- Open Plugin Manager via Settings > System > Plugins
- Upload, install, and activate the plugin
Plugin Configuration:
6.7: Extensions > My Extensions > Checkout Shipping Payment Preselection > Configure
Configuration options:Hide notification of an automatic change of shipping or payment method
Select "Hide" and the standard Shopware notifications about automatic changes will be suppressed.
Use stored payment method of the customer (when logged in)
- Use the last payment method used by the customer (Priority 1). Fallback 1: Standard payment method from the custom field in the customer profile (Priority 2)
The customer’s last used payment method will be applied when logged in. If this function is deactivated, the payment method defined in the custom field in the admin for this customer will be used. - Ignore and use selection made before login or based on defined prioritization
The input in the custom field will be ignored. The preselection will then be made based on the manual input of the customer before login or according to the defined prioritization. - Use the customer’s standard payment method from the custom field added by the plugin (Priority 1).
With this setting, the input in the custom field will have the highest priority.
When this setting is activated, the customer’s entries will not be saved after placing the order.
Frequently Asked Questions
Es wurden keine Fragen gefunden. Kontaktieren Sie uns, wenn Sie konkrete Fragen haben!| Version | Date | Compatibility | Changelog |
|---|---|---|---|
| 8.1.14 | 9 July 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 8.1.13 | 21 April 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 8.1.12 | 26 March 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 8.1.11 | 9 March 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 8.1.10 | 9 December 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 8.1.9 | 27 November 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 8.1.8 | 27 November 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 8.1.7 | 24 November 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 8.1.6 | 21 November 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 8.1.5 | 17 November 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 8.1.4 | 3 September 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 8.1.3 | 11 July 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 8.1.2 | 3 July 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 8.1.1 | 27 May 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 8.1.0 | 27 May 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 8.0.3 | 23 May 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 8.0.2 | 19 May 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 8.0.1 | 19 May 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 8.0.0 | 14 May 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 7.3.3 | 22 June 2026 | >=6.6.3.0 <6.7.0.0 |
|
| 7.3.2 | 22 June 2026 | >=6.6.3.0 <6.7.0.0 |
|
| 7.3.1 | 25 March 2026 | >=6.6.3.0 <6.7.0.0 |
|
| 7.3.0 | 27 January 2026 | >=6.6.3.0 <6.7.0.0 |
|
| 7.2.8 | 27 January 2026 | >=6.6.0.0 <6.7.0.0 |
|
| 7.2.7 | 9 December 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 7.2.6 | 27 November 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 7.2.5 | 24 November 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 7.2.4 | 24 November 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 7.2.3 | 21 November 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 7.2.2 | 17 November 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 7.2.1 | 3 September 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 7.2.0 | 27 May 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 7.1.8 | 23 May 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 7.1.7 | 23 May 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 7.1.6 | 19 May 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 7.1.5 | 13 May 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 7.1.4 | 6 May 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 7.1.3 | 29 April 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 7.1.2 | 29 April 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 7.1.1 | 23 April 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 7.1.0 | 1 April 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 7.0.10 | 19 December 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 7.0.9 | 18 December 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 7.0.8 | 12 December 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 7.0.7 | 9 December 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 7.0.6 | 6 December 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 7.0.5 | 2 December 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 7.0.4 | 28 November 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 7.0.3 | 28 October 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 7.0.2 | 16 August 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 7.0.1 | 25 March 2024 | >=6.6.0.0 |
|
| 7.0.0 | 21 March 2024 | >=6.6.0.0 |
|
| 6.1.8 | 19 December 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 6.1.7 | 9 December 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 6.1.6 | 6 December 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 6.1.5 | 2 December 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 6.1.4 | 28 November 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 6.1.3 | 28 November 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 6.1.2 | 28 October 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 6.1.1 | 19 March 2024 | >=6.5.0.0 |
|
| 6.1.0 | 9 February 2024 | >=6.5.0.0 |
|
| 6.0.3 | 16 January 2024 | >=6.5.0.0 |
|
| 6.0.2 | 12 January 2024 | >=6.5.0.0 |
|
| 6.0.1 | 13 September 2023 | >=6.5.0.0 |
|
| 6.0.0 | 24 April 2023 | >=6.5.0.0 |
|
| 5.2.0 | 20 April 2023 | >=6.4.10.0 |
|
| 5.1.3 | 28 October 2024 | >=6.4.10.0 |
|
| 5.1.2 | 14 February 2023 | >=6.4.10.0 |
|
| 5.1.1 | 10 February 2023 | >=6.4.10.0 |
|
| 5.1.0 | 1 February 2023 | >=6.4.10.0 |
|
| 5.0.2 | 26 November 2022 | >=6.4.10.0 |
|
| 5.0.1 | 26 November 2022 | >=6.4.10.0 |
|
| 5.0.0 | 26 November 2022 | >=6.4.10.0 |
|
| 4.0.0 | 26 November 2022 | >=6.4.9.0 |
|
| 3.0.5 | 26 November 2022 | >=6.4.1.0 |
|
| 3.0.4 | 26 November 2022 | >=6.4.1.0 |
|
| 3.0.3 | 26 November 2022 | >=6.4.1.0 |
|
| 3.0.2 | 26 November 2022 | >=6.4.1.0 |
|
| 3.0.1 | 26 November 2022 | >=6.4.1.0 |
|
| 3.0.0 | 26 November 2022 | >=6.4.1.0 |
|
| 2.0.2 | 26 November 2022 | >=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.2.2 | 26 November 2022 | >=6.3.4.0 |
|
| 1.2.1 | 26 November 2022 | >=6.3.4.0 |
|
| 1.2.0 | 26 November 2022 | >=6.3.4.0 |
|
Login
Sehr nützliches Plugin mit Top-Support
Das Plugin macht es soll und ist in Verbindung mit dem Plugin Verbesserter Versandkostenrechner eine unschlagbare Kombination. Der Support hier ist hervorragend, daher meine uneingeschränkte Empfehlung für diesen Anbieter.
Plugin und Support sehr gut
Ich kann dieses Plugin und den Support von Acris gerne weiterempfehlen, meine Erfahrungen sind ausgesprochen gut.
Sehr gutes Plugin mit perfektem Support
Das Plugin ist super für unseren Einsatzzweck.
Der Support von ACRIS reagiert sehr schnell und kompetent auf Anfragen.
Es gibt nichts auszusetzen, eine absolute Empfehlung!
Klasse Support - Vielen Dank!
Nach dem Update auf Shopware 6.4.10.1 wurden die Plugin-Einstellungen im Backend nicht mehr angezeigt. Daher haben wir uns an den Support gewendet. Nach nicht einmal 1,5 Stunden wurde ein Update (Version 5.0.1) zur Verfügung gestellt und das Plugin funktioniert wieder. Wir sind begeistert - Vielen Dank :)
Essentielle Extension! Super Support
Für unsere Konfiguration wichtige Extension. Der Support hat bei einem kleinen Problem extrem schnell geholfen - besser gehts nicht!