- or
No existing idea results
- ~ No ideas found ~
1341 results found
-
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 -
Delete extensions from the "My extension" overview in the Admin
Extensions, which are added via our Extension Shop are shown permanently in the "My extension" overview in the Admin. These Extensions can only disappear from the overview, if customers archive the license in their Shopware Account.
This is not really selfexplanatory and creates confusion and frustration.
Either the documentation musst be clearer (tool tips, docs, etc.) or a function to perform the archiving in the Admin would be highly appreciated.
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 -
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 -
If the shopping basket contains several tax rates, each tax rate should be managed individually as an item for discounts.
If the shopping basket contains several tax rates, each tax rate should be managed individually as an item for discounts.
Currently, if the shopping basket contains several tax rates, a discount item is created which contains the discount for both tax rates.
However, this can lead to problems for some merchandise management systems.
1 vote -
Change sorting of product slider
- I added a product slider via Content > Experience Worlds (???) > Landing Pages.
- I added products to the slider.
- I cannot change the order of the products in the slider but need to delete all products and start over again.
Solution: It should be easily possible to change the sort order of products listed in the product slider without starting over again.
27 votes -
Bulk translation editor for CMS element config in Layout tab
Currently, when managing translations for CMS configurations (such as a text block, images, ...) within product or category pages, the process is quite time-consuming. We need to manually switch languages and update the field one-by-one for each language. For stores with multiple languages, this creates a lot of overhead for even small content updates like updating a photo.
I’d like to propose a bulk translation editor that allows us to edit the config of a CMS element across multiple languages in one view, similar to how snippet management already works at this moment. This would greatly improve usability and efficiency for content managers working in multilingual shops.
Ideally, this editor could be opened from the CMS config card in the Layout tab and show a table or structured form where we can input translations for each language side-by-side.
Additionally, bonus points for a way to copy a translated config for a certain element to all other languages would be great. An image for example is often not translated, thus does not need a specific config for each language.
Currently, when managing translations for CMS configurations (such as a text block, images, ...) within product or category pages, the process is quite time-consuming. We need to manually switch languages and update the field one-by-one for each language. For stores with multiple languages, this creates a lot of overhead for even small content updates like updating a photo.
I’d like to propose a bulk translation editor that allows us to edit the config of a CMS element across multiple languages in one view, similar to how snippet management already works at this moment. This would greatly improve usability and efficiency…
1 vote -
gallery slider is not compatible with different sizes
When the pictures are very different in size or ratio, the gallery slider pops out downside or shrinks back upside, which is not very nice
an option to choose a certain height so that the pictures scale to it would be nice
1 vote -
Display of variants in product-sliders and cross sellings if assigned via dynamic product group
The display of variants within product sliders - if assigned via dynamic product groups - is based on the configuration from the storefront presentation. Even if individual variant options are explicitly assigned to the dynamic product group, it is still possible that the main product or a different variant will be displayed, unless it has been specified that the variants should be fanned out.
If I want to ensure that only certain variants are displayed in a product slider, the individual variants must currently be manually assigned to the product slider. This is because changes to the storefront display always have a direct effect on the listing at the same time, even though this may not be desired and the configuration should only relate to the slider.
The display of variants within product sliders - if assigned via dynamic product groups - is based on the configuration from the storefront presentation. Even if individual variant options are explicitly assigned to the dynamic product group, it is still possible that the main product or a different variant will be displayed, unless it has been specified that the variants should be fanned out.
If I want to ensure that only certain variants are displayed in a product slider, the individual variants must currently be manually assigned to the product slider. This is because changes to the storefront display always…
3 votes -
Add search for blocks and elements at cms page editing
Add a search bar to block sidebar and element selection to get blocks and elements quicker.
Important when more elements/blocks are added with plugins/apps.2 votes -
predefined periods for products / add an expiration date
In Shopware 6 it would be very useful if it were possible to activate products for a set period of time.
Since there is already a “release date”, it would be very useful to add an end to it.
In certain sectors, products may only be offered for a period of time x, e.g. for pesticides as these have approvals with an end date.
2 votes -
Different flows for different forms
It is currently not possible to send different actions, for example different e-mail templates, if different forms are sent.
A differentiation through a rule in the Rule Builder or different flow triggers would be helpful here.2 votes -
Product overview with additional filter options on variant level
The filtering at the product level under "Catalog > Products" unfortunately only works at the master/parent product level. This option is not conducive for the following reason:
All of our products have variants and we maintain the images only at the variant level. The same applies to the product status active/inactive. Text, on the other hand, is always maintained at the master/parent product level.
This approach is deliberately chosen because variants can have different images or individual variants can be inactive.It is now important for us to be able to locate the following at the variant level:
- Product active, has image, has NO text, has stock
- Product active, has NO image, has text, has stock
- Product active, has neither image nor text, has stock
- Product inactive, has image, has NO text, has stock
- Product inactive, has NO image, has text, has stock
- Product inactive, has neither image nor text, has stock
The filtering at the product level under "Catalog > Products" unfortunately only works at the master/parent product level. This option is not conducive for the following reason:
All of our products have variants and we maintain the images only at the variant level. The same applies to the product status active/inactive. Text, on the other hand, is always maintained at the master/parent product level.
This approach is deliberately chosen because variants can have different images or individual variants can be inactive.It is now important for us to be able to locate the following at the variant level:
- Product active,…
10 votes -
Order details - Show customer group, company name etc.
Add information just like "customer group", "company name" and "vat id" to the order details. To get those kind of information you currently need to open the customer record itself.
4 votes
- Don't see your idea?