- or
No existing idea results
- ~ No ideas found ~
1267 results found
-
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…
2 votes -
Extend data mapping for custom fields of the manufacturer which can be linked to products.
Is it not possible to create a custom field for the manufacturer and output its content via the data mapping in a text field on the product detail page layout. I can select all standard manufacturer fields and all product custom fields but no custom fields that have been created for the manufacturer. The data mapping can only add custom fields that are directly linked to products.
Please add the function for Data Mapping of manufacturer custom fields linked to the produkt.
2 votes -
CMS block banner - extend settings
At the moment it is not possible to make any design settings for the CMS block banner (text and image with button). Please add customization options like:
Minimum height in px
Button color independent of theme settings
The possibility to display more than one button in a line.At the moment you cannot change the height of the background image or the text element to adjust the display size in the frontend.
2 votes -
Apply different discount levels depending on Shopping cart value (with one and the same code)
It would be really nice, if we could define different discount levels depending on the shopping cart value in combination with one same discount code. This is a standard usecase for promotions.
Currently this is not possible, because you can only define one shopping cart rule per promotion.
Since you cannot create multiple promotions with the same discount code, multiple promotions with different shopping cart rules are not possible at this time.Either it should be possible to create multiple promotions with the same discount code or there should be an option to apply customer-, shopping cart- and order rules for every discount created within a promotion.
It would be really nice, if we could define different discount levels depending on the shopping cart value in combination with one same discount code. This is a standard usecase for promotions.
Currently this is not possible, because you can only define one shopping cart rule per promotion.
Since you cannot create multiple promotions with the same discount code, multiple promotions with different shopping cart rules are not possible at this time.Either it should be possible to create multiple promotions with the same discount code or there should be an option to apply customer-, shopping cart- and order rules…
3 votes -
Delivery country in OffCanvas in shopping cart
The delivery country should be displayed in the offcanvas cart too or it should be an option for this.
This gives customers a better overview. In addition, this is sometimes requested by large customers without having to carry out an extra customisation.
The problem with customisation is always the ability to update.
1 vote -
Product export - Inactive items and items with no stock in CSV
In a product export, inactive items and articles with no stock that are included in the dynamic product group are not exported.
2 votes -
Reorder items in multi-select / entity-multi-select via drag'n'drop
Add possibility to reorder selected items/entities. Needed for plugin configs or smaller UI at cms elements, without the need to implement a list of items with sorting options.
'sw-entity-multi-select'
'sw-entity-multi-id-select'1 vote -
AI-generated forecasts and predictions
This technology will help to make smarter decisions, whether it’s stocking up on inventory, fine-tuning marketing strategies, or ensuring the inventory is prepared for multiple sales channels.
5 votes -
Commercial: Advanced Search - show how ranking was determined
In older versions of Shopware 6 the ranking points were shown in the advanced search preview. Currently it is not possible to estimate or optimise the search results, because the shares in the ranking can only be determined manually - if at all.
Please make the ranking more comprehensible again.
The is another feedback that seems to belong to default search (https://feedback.shopware.com/forums/942607-shopware-6-product-feedback-ideas/suggestions/45589468-understandable-search-results) maybe it's possible to find an algorithm for both.
4 votes -
Hide advanced prices
It would be nice to have the option to hide the advanced prices on the product detail page.
1 vote -
Ability to replace no results layout
It would be a great improvement if it would be possible to replace the default search results page with Shopping experience layout when there are no search results.
In the current situation, the customer leads to a dead end, which is not user friendly and most likely results in site abondenments.
2 votes -
Automatically syncing of "Pay in Advance" transaction
It would be a nice to have a feature that automatically tracks incoming "Pay in advance" payments and syncs those with the corresponding order, without manual effort.
For payments, where it's unclear, an overview for manual check up would be nice.
1 vote -
Dashboard: Feedback button leads to Github Issues
It would be great, if the Feedback button, which is shown prominently on the Dashboard of every Admin, would lead to a location, where you can actually share your generel feedback.
Currently you are forwarded to the Github Issues overview, which makes more the impression like technical bugs are reported here.
This feedback portal would be the better choice in my opinion.
1 vote -
youtube & vimeo link in product picture and in product description
At amazon it is standard to have product videos in product description and product pictures.
So Shopware should have the function:
- product picture (the last one) to us it for product video
- link youtube & vimeo videos at the end of the product description or optional as separated tabFor me: product picture (the last one) to us it for product video is very important for us, becausing using a lot of videos for using the product and describing the product.
23 votes -
Improve Export Template UX of product comparison sales channels
Currently it requires to apply changes in TWIG. This makes simpliest adjustments challenging. The UX should be improved and made adjustable for people without DEV experience.
1 vote -
Discounts in Product comparison
It should be possible for discounts from discounts & promotions to be included in the product comparison sales channel respectively in the product export.
3 votes -
Add discount as sorting option
There is currently no nice way to create a sorting option based on the discount of products in the Admin under "Settings > Shop > Products > Sorting options".
It is a common use case (especially during times like Black Friday), that consumers sort the products based on the discount. It would be valuable to have that option also for Shopware.
2 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…
1 vote -
Zusätzliche Spalte und Kommentarfeld bei SW6 Backend Bestellungen I Additional column and comment field for SW6 backend orders
Aktuell steht bei SW6 Backend Bestellungen nur ein Feld, mit Dropdown Menü für die Suche nach Artikelnummer oder Artikelname zur Verfügung. Oder die leere Positionszeile.
In SW5 gab es bei Backendbestellungen je eine Spalte für Artikelnummer und eine für Artikelname, Preis, Steuer, etc. Man konnte die Artikelnummer verwenden, den Artikelnamen, Preis, Steuer etc. bearbeiten und die Bestellung mit den überschriebenen Daten anlegen. Damit war alles geregelt und konnte sauber an Kunden, Lager, etc. übergeben werden.
Diese weitere Spalte bei den Backend Bestellungen fehlt in SW6. Damit hat man nicht mehr beide Felder zur Verfügung und kann keine Änderungen mehr vornehmen, da die Datenbank dann scheinbar nach einem nichtvorhandenen Eintrag sucht und die Eingabe nicht abgeschlossen werden kann.
Gibt es dafür eine Lösung?
Ebenfalls fehlt in dieser Ebene der Backend Bestellung noch ein Kommentarfeld, z.B. für Kundeninterne Nummern, Export-Angaben, etc… In SW5 gab es dafür die Freitextfelder.
Das Kommentarfeld steht erst im nächsten Schritt zur Verfügung. Um dahin zu gelangen, muss man die Bestellung speichern, woraufhin jedoch schon die Bestellbestätigung versendet wird. Auf der man eben gern noch ein paar Angaben gemacht hätte, bevor sie zum Kunden gesendet wird.
Gibt es dafür eine Lösung?
There is currently only one field available for SW6 backend orders, with a dropdown menu for searching by article number or article name. Or the empty item line.
In SW5 there was one column for article number and one for article name, price, tax, etc. for backend orders. You could use the article number, edit the article name, price, tax etc. and create the order with the overwritten data. This meant that everything was organised and could be transferred cleanly to customers, warehouses, etc.
This additional column in the backend orders is missing in SW6. This means that you no longer have both fields available and can no longer make any changes, as the database then appears to search for a non-existent entry and the entry cannot be finalised.
Is there a solution for this?
A comment field is also missing at this level of the backend order, e.g. for internal customer numbers, export details, etc... In SW5 there were free text fields for this purpose.
The comment field is only available in the next step. To get there, you have to save the order, after which the order confirmation is sent. You would like to have entered a few more details before it is sent to the customer.
Is there a solution for this?
Aktuell steht bei SW6 Backend Bestellungen nur ein Feld, mit Dropdown Menü für die Suche nach Artikelnummer oder Artikelname zur Verfügung. Oder die leere Positionszeile.
In SW5 gab es bei Backendbestellungen je eine Spalte für Artikelnummer und eine für Artikelname, Preis, Steuer, etc. Man konnte die Artikelnummer verwenden, den Artikelnamen, Preis, Steuer etc. bearbeiten und die Bestellung mit den überschriebenen Daten anlegen. Damit war alles geregelt und konnte sauber an Kunden, Lager, etc. übergeben werden.
Diese weitere Spalte bei den Backend Bestellungen fehlt in SW6. Damit hat man nicht mehr beide Felder zur Verfügung und kann keine Änderungen mehr vornehmen,…
2 votes -
We need repeater fields
We come from WordPress/WooCommerce and use ACF Pro there. We heavily use the repeater feature to easily add new content to things that ... well ... repeat.
We have several use cases:
Customer logos, FAQs, USPs, trust badges, a list of links, accordion items, etc.
These are all things that use the same set of fields repeated over and over. It is annoying to add new fields.
For example, we need more customer logos. I have seven image fields named image1, image2, etc. Now I need to add up to 30 for new customer logos.
So I need to manually add all those fields to the custom field and enhance the code to display those new fields in the storefront. Since you can't duplicate fields (another big issue), it takes !forever! to add all this new content.
A repeater is must-have for modern content managementm Please add this to your premium product!
We come from WordPress/WooCommerce and use ACF Pro there. We heavily use the repeater feature to easily add new content to things that ... well ... repeat.
We have several use cases:
Customer logos, FAQs, USPs, trust badges, a list of links, accordion items, etc.
These are all things that use the same set of fields repeated over and over. It is annoying to add new fields.
For example, we need more customer logos. I have seven image fields named image1, image2, etc. Now I need to add up to 30 for new customer logos.
So I need…
8 votes
- Don't see your idea?