- or
1295 results found
-
Copying CMS content - reusable elements
It would be nice to have the option of copying elements from the shopping experiences and using them in a different place.
Example: We have the "XY" section in the start page - this should be filled and customised once and then copied in the next step and used in another page.
23 votes -
Admin Search: Search term disappears when switching search area
When using the search in Admin and you change the search area, the already entered search term disappears and needs to be re-entered.
This is a potential cause for frustration.
Imagine entering your product name, just to realise that you are in the search area "Orders", then switching to the search area "Products" and having to re-enter the same search term again.
2 votes -
Improve "Add product" UI function in orders
Shopware allows to add new products within existing orders. How ever, the way the button is currently designed is quite counter intuitiv and causes confusion.
The button consists of two parts: "Add product" and an area with an arrow, indicating further options. Users tend to interprate it as in they need to click on the arrow area in order to access all options to add a new product. How ever, there are only the option "Add custom item" or "Add credit".
This could be prevented by simply also showing the "Add product" option here as well.
2 votes -
Be able to create new Address Snippets
Currently, there is only a predefined set of snippets, that can be selected in "Settings > Shop > Countries > 'SELECT_COUNTRY' > Address Handling" for the Address Markup.
Adding new Snippets would be great for instance to add a new snippet for the street number or to customize the Address markup as you need it.
2 votes -
Tabs on the mask to create/edit products should be re-sortable
It would be helpful if the tabs in the mask for creating/editing products could be sorted or arranged individually.
Especially with regard to the extension of these tabs by plugins/apps, this makes sense, as otherwise important and frequently used tabs disappear from the display area and can only be accessed by constantly scrolling back and forth.
2 votes -
Add address validation options
It would be useful to have the ability to validate addresses inserted by customers against rules that can be defined in the Admin area for each country. Perhaps something like a regex validation.
This would allow for filtering of invalid characters, to validate the syntax in certain countries or in case of international shipping the filtering of entire character sets (i.e. Greek, Cyrillic, Chinese, Japanese). This helps with the creation of shipping labels and especially the latter use case would make it easier for shop owners to ship their products to those countries.
2 votes -
Add possibility to change shop default language
It is not possible to change the global default language of the Shopware 6 store after installation. This often leads to frustration or unexpected problems in the management of products and translations. Changing the global default language is currently only possible via a new installation or risky DB adjustments,
Please add a function that allows you to change the default store language in the settings.
2 votes -
Uninstallation via cli should delete the folder of an uninstalled extension
If an extension is uninstalled via cli, the folder in plugins is not removed. This may lead to incorrect licence warnings. The folder should therefore also be deleted when uninstalling.
2 votes -
Bitte in der Anzahl der Produktverkäufe die Produktnummer mit anzeigen (Artikelnummer)
Es wäre sehr hilfreich, die Produktnummer in der Liste der Produktverkäufe sehen zu können.
Bitte blenden Sie die Produktnummer im Analytics Plugin mit ein. (Artikelnummer)Vielen Dank
4 votes -
Delivery time display: Option to exclude specific days
It would be a nice option to have the possibility to exclude Sundays for example from the delivery time calculation. Of course, we can already cover this with the delivery time SPAN and NAME of the delivery method, saying 1-3 WORKdays or something.
But it would be a nice QoL feature, especially for customers, if the calculation took days we defined into the equation and could thus be more specific.
If we wanted to take this a step further, we could also offer a calendar where we can configure holidays and whatnot.
And if we want to take this to the extreme, we could allow those calendars to be exported and imported so shop owners and extension partners can share and/or sell them.
It would be a nice option to have the possibility to exclude Sundays for example from the delivery time calculation. Of course, we can already cover this with the delivery time SPAN and NAME of the delivery method, saying 1-3 WORKdays or something.
But it would be a nice QoL feature, especially for customers, if the calculation took days we defined into the equation and could thus be more specific.
If we wanted to take this a step further, we could also offer a calendar where we can configure holidays and whatnot.
And if we want to take this to…
19 votes -
Custom fields for property group options
Forum thread: https://forum.shopware.com/t/zusatzfelder-fur-eigenschaften/64068/7
Issue Ticket that is "solved": https://issues.shopware.com/issues/NEXT-3710We need custom fields support for property group options. That was possible in Shopware 5 according to the linked issue ticket.
Also, the issue ticket asked for property_options specifically and the ticket was marked as solved without adding custom fields to those.
Please add that missing feature.
6 votes -
Whitelist-Based Cache Key Handling for URL Parameters
Currently, Shopware allows excluding certain URL parameters from the cache key to save storage. However, this exclusion list keeps growing, making maintenance cumbersome. Instead of excluding parameters, a whitelist approach could offer more control and efficiency.
Analysis:
I tracked URL parameters in a default Shopware installation—from listing to PDP, filtering, and placing an order. These 19 parameters were captured (more possible):
cluster, keys, language, limit, locale, manufacturer, max-price, min-price, no-aggregations, order, orderId, p, paid, properties, rating, redirected, slots, timezone, searchInstead of maintaining an ever-growing exclusion list, switching to an allowlist approach would ensure that only essential parameters impact the cache key.
Proposed Solution:
- Allowlist Configuration – Define a clear set of parameters that should be part of the cache key instead of excluding specific ones.
- Event for developers – Introduce an event to allow developers to modify the allowlist dynamically.
- Control by config – Provide a config option to adjust the allowlist as needed.
This approach simplifies maintenance, optimizes cache storage, and ensures that only relevant parameters affect cache variations. 🚀
Currently, Shopware allows excluding certain URL parameters from the cache key to save storage. However, this exclusion list keeps growing, making maintenance cumbersome. Instead of excluding parameters, a whitelist approach could offer more control and efficiency.
Analysis:
I tracked URL parameters in a default Shopware installation—from listing to PDP, filtering, and placing an order. These 19 parameters were captured (more possible):
cluster, keys, language, limit, locale, manufacturer, max-price, min-price, no-aggregations, order, orderId, p, paid, properties, rating, redirected, slots, timezone, searchInstead of maintaining an ever-growing exclusion list, switching to an allowlist approach would ensure that only essential parameters impact the…
2 votes -
Mail Templates - Show Order Employee Details
It should be possible to show the first and last name of the order employee in mail templates - just like order confirmation.
1 vote -
Presets for roles
There should be fixed roles for employees. The classic roles such as customer service (read only) and SEO should be available as standard. Access to each individual setting point should be separately selectable.
1 vote -
Allow orders to be moved between customers (i.e. reassign guest order to customer account)
It would be useful to move orders from one customer account to another. Currently guest orders remain assigned to the guest account, even when a customer registers afterwards. Thus they cannot see the order status. Also for other scenarios (like duplicate accounts), moving orders would be useful.
Es wäre hilfreich, Bestellungen von einem Kundenkonto auf ein anderes verschieben zu können. Derzeit bleiben Gastbestellungen dem Gastkonto zugewiesen, auch wenn sich ein Kunde später registriert. Somit kann er den Status der Bestellung nicht sehen. Auch für andere Szenarien (z. B. doppelte Konten) wäre das Verschieben von Bestellungen nützlich.
4 votes -
Loading times of the article sliders
The article sliders currently take about one second to load properly. Until then, the first product of the slider is usually displayed briefly in large format.
An optimization of the loading time for article sliders with many products would be desirable.3 votes -
Mailer: Different SMTP data for different sales channels
More and more providers are prohibiting the sending of emails that do not come from the same domain.
However, as you can only store the access data of one domain in the mailer, this becomes a major problem as soon as you enter several sales channels with different domains.
From that moment on, not all messages can be sent or are rejected by the provider.
"mailbox unavailable\r\n 550 Sender address is not allowed.""
It should therefore be possible to configure the mailer settings for each sales channel.
24 votes -
List all assignments of a Dynamic Product Group
EN
In the Rule Builder, there is an overview with the assignments for each rule. Such an overview would also be a great addition for the dynamic product groups, because the more product groups are used in categories, product comparisons, cross-selling etc., the more difficult it becomes to determine where a particular product group is used.DE
Im Rule Builder gibt es für jede Regel eine Übersicht mit den Zuordnungen. Eine solche Übersicht wäre auch für die Dynamischen Produktgruppen eine super Ergänzung, denn je mehr Produktgruppen in Kategorien, Producktvergleichn, Cross Sellings etc. zum Einsatz kommen, um so schwieriger wird es festzustellen, an welchen Stelle eine bestimmte Produktgruppe genutzt wird.EN
In the Rule Builder, there is an overview with the assignments for each rule. Such an overview would also be a great addition for the dynamic product groups, because the more product groups are used in categories, product comparisons, cross-selling etc., the more difficult it becomes to determine where a particular product group is used.DE
Im Rule Builder gibt es für jede Regel eine Übersicht mit den Zuordnungen. Eine solche Übersicht wäre auch für die Dynamischen Produktgruppen eine super Ergänzung, denn je mehr Produktgruppen in Kategorien, Producktvergleichn, Cross Sellings etc. zum Einsatz kommen, um so schwieriger wird es…2 votes -
One page checkout
There should be an option to make a one page checkout. If you use express checkout buttons customers often do not realize that there are other payment options like purchase on account.
Showing the payment methods under the address form would make the checkout faster and more usable.
It would boost conversions. If it would not, why is Shopify using it?
4 votes -
Properly display error messages for customer-facing formfields
Currenty, Showpare (default skin) does not reliably display error messages on missing or wrong form fields when submitted by the users, e.g.
- When logging in with wrong credentials
- When registering an account (most fields)
- When using the newsletter registration form.
Shopware will highlight the fields in red and there are internal attributes (data-form-validation-required-messag) on the fields that do contain error messages, but these are not displayed reliably to the user. There seems to be something in place that will sometimes client-validate those error messages and display them, but that hardly happens / seems broken. (Not a bug accordinging to Shopware support, redirected here instead)
We would expect any error messages attached to wrongly filled or empty obligatory fields to be displayed at a sensible space (below?) the form field.
See attached Screenshots.
Currenty, Showpare (default skin) does not reliably display error messages on missing or wrong form fields when submitted by the users, e.g.
- When logging in with wrong credentials
- When registering an account (most fields)
- When using the newsletter registration form.
Shopware will highlight the fields in red and there are internal attributes (data-form-validation-required-messag) on the fields that do contain error messages, but these are not displayed reliably to the user. There seems to be something in place that will sometimes client-validate those error messages and display them, but that hardly happens / seems broken. (Not a bug accordinging to Shopware…
4 votes
- Don't see your idea?