Shopware 6 - Product Feedback & Ideas: Hot (1501 ideas)

What idea would you like to share with us?

Enter your idea here

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

Change product detail page layout for more than 25 items

EN

If a separate layout has been designed for some products, for example because these products have a special property for which there should be an explanation, then I can select the products under Content > Experience worlds > Layout assignment > Assign layout. However, the selection list is limited to 25 elements. To do this, we have added a filter to filter the selection for additional products. However, this only works as long as the search terms are different.

If I have 80 products with, for example, ‘variant’ in the name, I can only select 25, after which further products could only be selected if there was another unique criteria with which further products could be selected. The only other alternative is to select each product individually and then change the layout manually.

It is not possible to link the products to the layout via a dynamic product group and it is also not possible to set a new layout in the additional change.

DE

Wenn für einige Produkte ein eigenes Layout entworfen wurde, beispielsweise weil diese Produkte eine spezielle Eigenschaft haben, zur der es eine Erläuterung geben soll, dann kann ich unter Inhalte > Erlebniswelten > Layout-Zuweisung > Layout zuweisen die Produkte auswählen. Jedoch ist die Auswahlliste auf 25 Elemente beschränkt. Dafür haben wir den Filter eingebaut, mit dem die Auswahl auf weitere Produkte gefiltert wird. Das funktioniert aber nur so lange, wie die Suchbegriffe unterschiedlich ausfallen.

Haben ich 80 Produkte mit zum Beispiel "Variante" im Namen kann ich nur 25 auswählen, danach gingen weitere nur noch, wenn es ein weiteres eindeutiges Kriterium gäbe, mit dem weitere Produkte ausgewählt werden können. Die einzige andere Alternative jedes Produkt einzeln auszuwählen und dann das Layout manuell zu ändern.

Es ist nicht möglich die Produkte über eine Dynamische Produktgruppe mit dem Layout zu verbinden und auch in der Mehränderung kann kein neues Layout gesetzt werden.

EN

If a separate layout has been designed for some products, for example because these products have a special property for which there should be an explanation, then I can select the products under Content > Experience worlds > Layout assignment > Assign layout. However, the selection list is limited to 25 elements. To do this, we have added a filter to filter the selection for additional products. However, this only works as long as the search terms are different.

If I have 80 products with, for example, ‘variant’ in the name, I can only select 25, after which…

4 votes

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · User Experience · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
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,…

3 votes

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · Orders & Customers · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
Retail Media Capabilities

Challenge/Problem:
What is Retail Media: https://www.criteo.com/blog/wtf-is-retail-media-guide/

Selling paid content within a shop. Currently, it would involve a lot of custom & manual effort to create & maintain paid content in SW6.

Possible Constraints for retail media:
* Different methods how to defining prices such as KPI based (by CR, by Traffic, by Clicks, etc.) or fixed prices
* Time limitation of active content (fixed period, max. number of Klicks/CR/Traffic, etc.)
* Legal requirements (paid content and product position must be clearly indicated as an advertisement)
* Integration of third-party system
* Integration of external admin users (e.g. paid influencer who writes a blogpost and pushes it to SW6)

Possible use cases for retail media:
* Teaser and Banner (PLP, PDP, Homepage, Navigation, Blogposts, LPs)
* Paid rankings (Search, search results, PLP sorting, Recos)
* Paid blog posts
* Paid brand category pages
* Paid LPs

Solution/Approach:
Some sort of management for marketing to create, maintain and automate paid content within admin.

Target Group:
Beyond
Retail media requires a certain size and reach of an online shop within its industry in order to be attractive for brands so that their paid content would lead to significant higher sales of their products in the corresponding onlineshop.

Challenge/Problem:
What is Retail Media: https://www.criteo.com/blog/wtf-is-retail-media-guide/

Selling paid content within a shop. Currently, it would involve a lot of custom & manual effort to create & maintain paid content in SW6.

Possible Constraints for retail media:
* Different methods how to defining prices such as KPI based (by CR, by Traffic, by Clicks, etc.) or fixed prices
* Time limitation of active content (fixed period, max. number of Klicks/CR/Traffic, etc.)
* Legal requirements (paid content and product position must be clearly indicated as an advertisement)
* Integration of third-party system
* Integration of external admin users (e.g. paid influencer who…

2 votes

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · Content management · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

DECLINED · AdminJonas Fuchs (Product Manager Data & Services, shopware AG) responded

Thank you for sharing this idea with us and for your patience while it’s been on the portal. After reviewing it again, we’ve decided not to move forward—There is not enough interest. Please keep the feedback coming; your insights continue to shape what we build next!
I am trying to customize SEO URL slugs and encountered an issue

When I use variable meta-title in the url template, it works only for main products, not for variants, even if there is meta title inheritance enabled. But even when I check html of the variant page, meta title is not there. I don't know if you made it on purpose or it is a bug, but it means: I cannot use meta title variable for variants when creating a url.

This lead to my other thought: let's turn Use single canonical URL for all variants - because of course we do not want google to mark it as duplicates when we are using inheritance for all the descriptions and stuff. But when I turn it on, you force me to pick one of the variants. But I don't logically want it to be one of the variants, i want it to be main product. That leads me to another problem that I tried to solve with you: main product cant have the same product number as variant. So I cannot create variant as main product - so I cannot use it as main product for canonical URL. BUT! I think you would tell me: change storefront presentation, lets go to Product-Variants-Storefront presentation-Product lsitings and instead of Main product you could pick one variant and go with it. But I don't want to do it, because if I choose it as "Main product" in the storefront it is more beneficial since it shows, that there are more variants and price starts at.... You know what I mean? I don't want the specific size of the product be as main variant, you actually told me not to, since you require variant and main product to have different product number.

This is actually really frustrating. Because I want it (as it should be):
- main product - main URL - it is main product page that I want to be crawled by search engines
- variants - url with whatever slug added to the main product URL, but I don't want Google to crawl it.
Sounds pretty easy, right? And it even works like that, just not in case if I want to use MetaTitle as a slug.

You give me these:
- main product - main URL (i want to use meta title for that and you allow it since it is in the list of supported variants)
- variant - can't use meta title - it makes it different url, which is ugly and not practical
- seo canonical - can use only variant, not meta title, so basically I have many duplicate pages and it takes us down from Google.

When I use variable meta-title in the url template, it works only for main products, not for variants, even if there is meta title inheritance enabled. But even when I check html of the variant page, meta title is not there. I don't know if you made it on purpose or it is a bug, but it means: I cannot use meta title variable for variants when creating a url.

This lead to my other thought: let's turn Use single canonical URL for all variants - because of course we do not want google to mark it as duplicates when…

3 votes

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · SEO · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
Social Shopping / Product comparison: Media URL with sales channel domain

EN
We often receive enquiries about how image links in product comparisons or social shopping can be adjusted to use the domain of the exporting sales channel. There were already tickets for this in the old issue tracker: e.g. https://issues.shopware.com/issues/NEXT-17674.

However, this ticket was then created last year https://github.com/shopware/shopware/issues/4807, reporting that CDN media were receiving the wrong domain.

Programme request:
Please adjust the URL determination for media so that the handling of media links follows the same pattern as the product links within a product comparison. Of course, it must be possible to resolve the link. CDNs must also be taken into account, whereby the request was also made that it should be possible to resolve the domains per sales channel.

According to tests in Shopware 6.7.4.2, the domain from APP_URL is used during export; no adjustment to other sales channels is made. Neither AI nor humans can find any information in the (dev) documentation as to whether and, if so, how it is possible to change this behaviour. If there are already settings options for the media link, it would be necessary to document these clearly and display them in the search.

DE
Es kommt öfter die Nachfrage, wie in Produktvergleichen oder Social Shopping die Bildlinks so angepasst werden können, dass sie die Domäne des exportierenden Verkaufskanals nutzen. Da zu gab es im alten Issuetracker bereits Tickets: z.B. https://issues.shopware.com/issues/NEXT-17674.

Jedoch wurde im letzten Jahr dann dieses Ticket erstellt https://github.com/shopware/shopware/issues/4807, worin gemeldet wurde, dass CDN Medien die falsche Domain erhielten.

Programmwunsch:
Bitte die URL Ermittlung für Medien so anpassen, dass die Behandlung von Medienlinks dem gleichen Schema folgt wie die Produktlinks innerhalb eines Produktvergleichs. Natürlich muss der Link aufgelöst werden können. Außerdem berücksichtigt werden müssen naturlich CDNs, wobei hier auch der Wunsch geäußert wurde, dass es ebenfalls möglich sein soll die Domänen pro Verkaufskanal aufzulösen.

Gemäß Versuchen in Shopware 6.7.4.2 wird beim Export die Domäne aus der APP_URL verwendet, eine Anpassung an andere Verkaufskanäle erfolgt nicht. Weder KI noch Mensch finden in der (Dev-)Dokumentation Hinweise, ob und wenn ja wie, eine Änderung des Verhaltens möglich ist. Falls es bereits Einstellmöglichkeiten für den Medienlink gibt, wäre es notwendig diese verständlich zu dokumentieren und in der Suche anzuzeigen.

EN
We often receive enquiries about how image links in product comparisons or social shopping can be adjusted to use the domain of the exporting sales channel. There were already tickets for this in the old issue tracker: e.g. https://issues.shopware.com/issues/NEXT-17674.

However, this ticket was then created last year https://github.com/shopware/shopware/issues/4807, reporting that CDN media were receiving the wrong domain.

Programme request:
Please adjust the URL determination for media so that the handling of media links follows the same pattern as the product links within a product comparison. Of course, it must be possible to resolve the link. CDNs must…

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · System & Settings · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
Optimization of plugin management and configuration in Shopware 6 Admin

We are having difficulties finding and managing the apps and plugins installed in Shopware 6 within the admin area. Since many standard features from SW5 have been removed and must now be replaced by apps, there is no central overview for these extensions. The apps are spread out across different sections, without a clear indication of which plugin provides which functionality. This leads to issues with managing and identifying extensions.

Note from Shopware Support:
We think it's a very good idea. For many colleagues in support, it is often very difficult to find out which plugin inserts which functions and where these are configured.

Main Issues:

Scattered Apps: Apps are spread out across various sections of the admin area (e.g., Marketing, System, Settings), making them difficult to find.

No Clear Function Assignment: After installation, it is often unclear which plugin is responsible for which function. Only after disabling a plugin does it become apparent what it was doing.

Challenges with CMS Plugins: With multiple CMS plugins active at the same time, it’s almost impossible to figure out which plugin is being used in which Shopping Experience without manually testing each one.

Shopify Example:
We find that Shopify has a clear structure where all apps are centrally located under one "Apps" section, with direct access to configuration, making it super easy to manage.

Use Cases for Clarification:

1 - Finding an App:
If i want to configure a recently installed plugin. However, it is scattered across the admin area (e.g., partly under Marketing, partly under System), and there is no central overview. The user wastes time searching for the app.

Use Case 2 - Unclear Function Assignment:
As a shop owner, i noticed a functionality in our shop (e.g., "Products in saved shopping carts" under Marketing) but does not know whether it’s part of the core system or added by a plugin. Suggestion: Clearly indicate which function is provided by which plugin.

Wanted improvements:

Introduce a central "Plugin" section where all installed extensions are listed and can be configured.

Clearly label in the admin area which functions belong to which plugins. Maybe with an Icon and text on hover.

Improve the identification of CMS plugins within Shopping Experiences.

We are having difficulties finding and managing the apps and plugins installed in Shopware 6 within the admin area. Since many standard features from SW5 have been removed and must now be replaced by apps, there is no central overview for these extensions. The apps are spread out across different sections, without a clear indication of which plugin provides which functionality. This leads to issues with managing and identifying extensions.

Note from Shopware Support:
We think it's a very good idea. For many colleagues in support, it is often very difficult to find out which plugin inserts which functions and…

3 votes

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · System & Settings · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
"not specified" salutation handling

This is handled rather inconsistently in Shopware. In some but not all places, if you leave out the salutation, Shopware searches the database for the "not_specified" entry that comes with the installation and inserts it if found. If also sometimes inserts it just for display in the Administration if the real salutation reference is null, so you wouldn't even know the real value without looking directly into the database, but again, not always.

Crucially, that "not_specified" entry can be changed and deleted at will, so there's no guaranteed meaning behind it.

Also, sometimes like in the contact form the salutation is randomly required. You can delete it for addresses and the database has a default value of null, but then there is a non-configurable validator that won't let you through the checkout process if no salutation is given. And again, "given" can just mean that you set the "not_specified" salutation, which can have any meaning you assign to it.

This is an intransparent mess and should be changed. The very legality of requiring a salutation is now even in question. Just allow null values for all salutations in the application, it's already allowed in the DB structure, stop enforcing it in random places without a way to turn it off, and make the display name of a "null" salutation translatable via config.

This is handled rather inconsistently in Shopware. In some but not all places, if you leave out the salutation, Shopware searches the database for the "not_specified" entry that comes with the installation and inserts it if found. If also sometimes inserts it just for display in the Administration if the real salutation reference is null, so you wouldn't even know the real value without looking directly into the database, but again, not always.

Crucially, that "not_specified" entry can be changed and deleted at will, so there's no guaranteed meaning behind it.

Also, sometimes like in the contact form the…

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · Content management · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

← Previous 1 2 3 4 5 6 Next →

Placeholder system for properties & custom fields

The desired function allows the use of placeholders such as

{{ product.properties.<name> }} or

{{ product.customFields.<fieldName> }}

in various product fields. These should then be automatically replaced with the respective values.

✅ Potential benefits for retailers:
- Reduced manual maintenance effort
- Consistent and accurate product data
- Particularly helpful with many variants or large catalogs
- Works in the cloud without individual template adjustments

2 votes

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · Products, Prices & Properties · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
B2B Components: Approval Rules: Add organization unit option

Currently you can only create approval rules that are active for all organization units. It would be great if we could also create approval rules specifically for an organization unit, in case I want different conditions to be applied for different org units.

2 votes

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

IN RESEARCH · 0 comments · B2B · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
Allow setting time zone for logs

Add the possibility to modify the time zone for the log files. This would make it easier to parse them, both by reading and via scripts or other means.

2 votes

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · System & Settings · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
blog Kommentare

Hallo liebes Team,

ich habe fassungslos festgestellt, dass man nicht auf Blog Kommentare antworten kann. Das ist für mich eine absolute Standardfunktion. Wozu sollte es Blogkommentare geben, wenn man nicht darauf antworten kann.

Bitte in einem zukünftigen SW Update einplanen.
Dabei auch die standardmäßige Benachrichtigung, wenn ein neuer Blogkommentar aufgegeben wurde.
Danke.

Viele Grüße
Magdalena

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · Marketing & Promotions · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

DECLINED · AdminTim Jurchen (Product Manager Shopware Core, shopware AG) responded

Hallo und danke für das Feedback. Soweit ich das richtig sehe sind Sie mit Ihrem Shop noch auf der Version 5 von Shopware. Diese wurde bereits durch Shopware 6 ersetzt unserem zukunftsicheren Shopsystem, welches stätig weiterentwickelt wird. Shopware 5 wird somit nicht mehr weiterentwickelt.
VAT ID of guest accounts can't be changed via the shipping address.

If a commercial customer has an item delivered to another company in Austria and the invoice is sent to Germany, then the corresponding VAT ID should be taken from the delivery address - and not from the billing address.
The delivery address is the basis for which tax rate is used for the order.

The VAT ID. field is not available under “Change delivery address”.

Registered customers change the VAT ID in the profile settings and cannot change it at all via the billing address, as guest customers do it.

The behavior should be the same for both account types and ideally you should also be able to store multiple VAT IDs.

If a commercial customer has an item delivered to another company in Austria and the invoice is sent to Germany, then the corresponding VAT ID should be taken from the delivery address - and not from the billing address.
The delivery address is the basis for which tax rate is used for the order.

The VAT ID. field is not available under “Change delivery address”.

Registered customers change the VAT ID in the profile settings and cannot change it at all via the billing address, as guest customers do it.

The behavior should be the same for both account types…

8 votes

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

2 comments · Orders & Customers · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
Blog with Custom Entities

Blogs are an excellent way for businesses to tell stories and generate more traffic around their products. Currently, running a blog requires external setups, which often need coding skills, manual workflows and are disconnected from the shop system. Therefore we will provide an integrated blog functionality as a first example of using custom entities. This will enable merchants to write content, design and publish blog posts without coding skills.

70 votes

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

11 comments · Content management · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
Search Result - Show Cheapest Variant

Currently, when searching for the parent product number, the next available variant based on the product number suffix (12345.1) is displayed in the search results.

It would be good if we could influence the search results via settings and, for example, always display the cheapest (available) variant within the search results.

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · System & Settings · Edit… · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
Admin order creation: Allow guests

Currently, it is not possible to create an order via our Admin unless the customer is registered. This presents an annoyance because it is still somewhat customary in some industries to place orders by calling a customer support hotline or something along those lines.

As it is now, when calling a merchant running a Shopware 6 shop, we first have to enter the customer menu, register a new customer (and ask our customer all their data) and THEN do the same thing after switching menus to orders again.

It would be a neat QoL feature to be able to do both in one step. Allow us to place a guest order via our Admin which only includes the absolute bare minimum of required information when it comes to customer data with the rest being optional.

Currently, it is not possible to create an order via our Admin unless the customer is registered. This presents an annoyance because it is still somewhat customary in some industries to place orders by calling a customer support hotline or something along those lines.

As it is now, when calling a merchant running a Shopware 6 shop, we first have to enter the customer menu, register a new customer (and ask our customer all their data) and THEN do the same thing after switching menus to orders again.

It would be a neat QoL feature to be able to do…

2 votes

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · Orders & Customers · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
Improve export of products - better handling of variant data

The current situation is, that inherited field stay empty when a product export is done. This makes it more difficult to exchange data with other software or just to use spreadsheets to gain special information.

It's a topic that currently needs a workaround for many customers. Perhaps it could be possible to create several export profiles: one for exchange and editing data just for Shopware and one for external exchange.

3 votes

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · Migration & Im-/Export · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
Show cms layout "source"

When I assign a layout to a category/product, all settings from the “global” layout are initially applied. However, this only applies until I make changes within the category/product via the “Layout” tab—which therefore only apply to this entity.

This often leads to confusion if changes are made to the “global” layout at a later date and these no longer affect the specific category or product. If the above scenario occurs, I still have to make the changes at the category/product level for them to be visible.

At this point, we need a note in the “Layout” tab that indicates that changes have already been made at the category/product level and that any changes to settings (filters, etc.) at the global layout level will no longer automatically apply to these.

When I assign a layout to a category/product, all settings from the “global” layout are initially applied. However, this only applies until I make changes within the category/product via the “Layout” tab—which therefore only apply to this entity.

This often leads to confusion if changes are made to the “global” layout at a later date and these no longer affect the specific category or product. If the above scenario occurs, I still have to make the changes at the category/product level for them to be visible.

At this point, we need a note in the “Layout” tab that indicates that…

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · Content management · Edit… · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
The chosen delivery country of shopping basket should be preselected for customer registration

As a new customer, it would be nice if the delivery country selected in the shopping basket was also preselected on the customer registration page.

Currently, I go to the shop, add an item to my shopping basket, select France as the delivery country (also to see the shipping costs for that country), then click on "Checkout" and am taken to the "Login/Registration page". There, Germany is set as the country again and I have to select "France" once more.

Not really user-friendly!

Als neuer Kunde wäre es schön, wenn das im Warenkorb ausgewählte Lieferland auf der Kundenregistrierungsseite auch vorausgewählt ist.

Aktuell komme ich in den Shop, lege einen Artikel in den Warenkorb, wähle dort z.B. Frankreich als Lieferland aus (auch um mir die für dieses Land gültigen Versandkosten anzeigen zu lassen), klicke dann auf "Zur Kasse" und lande auf der "Anmelde / Registrierungsseite". Dort ist dann wieder Deutschland als Land eingestellt und ich muss erneut "Frankreich" auswählen.

Nicht wirklich user-friendly!

As a new customer, it would be nice if the delivery country selected in the shopping basket was also preselected on the customer registration page.

Currently, I go to the shop, add an item to my shopping basket, select France as the delivery country (also to see the shipping costs for that country), then click on "Checkout" and am taken to the "Login/Registration page". There, Germany is set as the country again and I have to select "France" once more.

Not really user-friendly!

Als neuer Kunde wäre es schön, wenn das im Warenkorb ausgewählte Lieferland auf der Kundenregistrierungsseite auch vorausgewählt…

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · User Experience · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
Import / Export Profiles - technical names make identification more difficult

Since Shopware 6.7 (?) the import / export profiles use technical names. The customer's labelling has been totally erased, although it's still available in the translation table.

Of course the customer can now overwrite the new name default_product-copy-1762844593373 for duplicated profiles. But usually these profiles were marked like "Import prices manufacturer1", "Import prices manufacturer2" and so on.
Means the customer has to check all their profiles correct the technical name, which seems to be the same for any administration language. Please add the labeling again.

2 votes

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · Migration & Im-/Export · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
Display multiple stocks on shop frontend

The ability to display multiple inventory stock level quantities per product in the shop frontend.

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · Inventory · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
Additional section for CMS pages

A CMS Page contains of sections, blocks and elements. Shopware offers only 2 different sections (sidebar/content and content).
Blocks can easily be moved between sections and within sections - making editing a breeze.

Sections only with 2 columns sidebar/content and 1 column content are not enough.
Many plugins add columns to blocks, but moving content between blocks is not possible. We loose the strong feature of moving blocks with text or images between sections.

Solution: add at least one additional section with 3 equal columns.

Thus making moving blocks and editing much easier.

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · Content management · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
Improve discount handling and transparency in quotes

Discount handling during quote creation and editing is currently very limited and not compatible with external ERP systems such as SAGE. In addition, discounts are not sufficiently transparent for customers.

At the moment, absolute or relative discounts can only be applied to the entire cart and are represented as an additional line item in the resulting order document. Defining discounts on a per-line-item level is not supported.

While it is possible to manually adjust the unit price of individual quote items, these adjustments are not recognized or displayed as discounts. As a result, customers cannot clearly see that a discount has been applied.

Furthermore, the quote functionality does not provide a clear comparison between the original product price (shop base price) and the quoted price. Displaying a “before” (regular price) and “after” (quoted price) would significantly improve transparency and customer understanding.

Enhanced discount capabilities and clearer price representation would improve usability, customer trust, and compatibility with ERP-driven pricing and discount logic.

Discount handling during quote creation and editing is currently very limited and not compatible with external ERP systems such as SAGE. In addition, discounts are not sufficiently transparent for customers.

At the moment, absolute or relative discounts can only be applied to the entire cart and are represented as an additional line item in the resulting order document. Defining discounts on a per-line-item level is not supported.

While it is possible to manually adjust the unit price of individual quote items, these adjustments are not recognized or displayed as discounts. As a result, customers cannot clearly see that a discount…

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · B2B · Edit… · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
Allow multiple orders to be created from a single quote

Currently, only a single order can be created from a quote.
It should be possible to allow multiple orders to be generated from the same quote.

Ideally, this behavior should be configurable on a per-quote basis during the creation or editing of a quote. For example, it should be possible to define whether only one order or multiple orders are allowed, and optionally to limit the maximum number of orders that can be created from a quote.

This would provide greater flexibility for B2B use cases where a single quote may be fulfilled through multiple partial or separate orders.

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · B2B · Edit… · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
Indication of orders created from quotes

It should be clearly visible whether an order was created from a quote.

Ideally, this information should be displayed directly within the order overview to allow quick identification.
If displaying this information in the order overview is not feasible, it should alternatively be available within the order details, for example via a dedicated field or a custom field.

This improves transparency and makes it easier for users to distinguish regular orders from those originating from quotes, especially in B2B workflows.

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · B2B · Edit… · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
Cannot respond to comments if quote has been expired

While the customer who did set up a quote is still able to add new comments to a quote that already has been expired, the shop owner / admin cannot respond to these comments accordingly.

Either remove the possibility to add new comments (for the customer) on expired quotes or the shopw owner / admin should have the possibility to respond to those comments accordingly.

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · B2B · Edit… · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
Add notifications for new comments on quotes

Currently, new customer comments on offers are not actively communicated. An email or in-administration notification would ensure timely awareness and faster responses.

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · B2B · Edit… · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close
Enable configuration of ratings
The product reviews section needs to be further expanded. It's so rudimentary that almost nothing can be configured.

Possible optimizations:

You can't set whether a comment (text) is mandatory (i.e., required) or optional. It's currently mandatory.

The minimum number of characters that can be written as a comment can't be set either. This is currently 40 characters.

You can set whether only customers who have purchased the product can leave a review, or whether all customers who haven't purchased it can leave a review.

What would be ideal for us: an optional comment, with only 10 characters for the comment instead of 40.
The product reviews section needs to be further expanded. It's so rudimentary that almost nothing can be configured.

Possible optimizations:

You can't set whether a comment (text) is mandatory (i.e., required) or optional. It's currently mandatory.

The minimum number of characters that can be written as a comment can't be set either. This is currently 40 characters.

You can set whether only customers who have purchased the product can leave a review, or whether all customers who haven't purchased it can leave a review.

What would be ideal for us: an optional comment, with only 10 characters for the comment…
4 votes

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

0 comments · Orders & Customers · Delete… · Admin →

How important is this to you?

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

← Previous 1 2 3 4 5 6 7 8 … 75 76 Next →

Don't see your idea?

Shopware 6 - Product Feedback & Ideas

Categories

Searching…

What idea would you like to share with us?

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

Not really user-friendly!

Not really user-friendly!

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here

We're glad you're here