- or
22 results found
-
Customer feedback: Improvement of e-mail dispatch in Shopware 6
Dear Shopware team,
We support the customer uba-arbeitsschutz.de (KdNr. 324128). After the customer migrated to Shopware 6 Evolve and is already online, we regularly exchange suggestions regarding the functionality of Shopware 6.
We have a few suggestions for improvement regarding the handling of sending and receiving emails.
1st example:
When a customer pays for their order in the shop via PayPal, they receive an email stating that the payment currently has the status 'unconfirmed'. As the customer is already checked during the payment process with PayPal to see whether the payment was successful, sending this information by email from Shopware 6 is unnecessary. Both the shop customer and the shop owner receive this information again by email from PayPal.2nd example:
It is currently not possible in Shopware 6 to control each individual email template in such a way that the shop owner can set the email template to active in the backend that they would like to receive as a duplicate by email. As already described in example 1, all emails that shop customers receive are also sent to the shop owner, which leads to a massive spam load, unless the shop owner leaves the recipient address field blank under Settings/System/Mailer. However, this means that the shop owner receives no emails at all.Our suggestion would be to have a checkbox field with the name "Duplicate to email recipient" in every email template. The shop owner can click on this field and thus decide for themselves whether the document is so important to them that they would like to receive a duplicate of it.
best regards Ilona Herr - HEKL Software GmbH
Dear Shopware team,
We support the customer uba-arbeitsschutz.de (KdNr. 324128). After the customer migrated to Shopware 6 Evolve and is already online, we regularly exchange suggestions regarding the functionality of Shopware 6.
We have a few suggestions for improvement regarding the handling of sending and receiving emails.
1st example:
When a customer pays for their order in the shop via PayPal, they receive an email stating that the payment currently has the status 'unconfirmed'. As the customer is already checked during the payment process with PayPal to see whether the payment was successful, sending this information by email from Shopware…1 voteNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Add user friendliness to new language handling
Since Shopware 6.7.3.0 the language pack displays a warning, that it's recommended not to use it and that it will not work with 6.8.x anymore. Unfortunately the deinstallation of the language pack removes all translations included there (test with 6.7.4.0, with selection "Remove all data it even throws an exception).
The dev docs recommend this way https://developer.shopware.com/docs/resources/references/upgrades/core/translation/language-pack-migration.html. But not every customer is feeling comfortable being forced to use the command line. It is intended to activate / deactivate a language via the language itself. So why don't you add an install / uninstall routine in settings > language to process bin/console translation:install --locales it-IT linked to the switch's setting? Perhaps in addition whether the snippets should be installed / uninstalled?Since Shopware 6.7.3.0 the language pack displays a warning, that it's recommended not to use it and that it will not work with 6.8.x anymore. Unfortunately the deinstallation of the language pack removes all translations included there (test with 6.7.4.0, with selection "Remove all data it even throws an exception).
The dev docs recommend this way https://developer.shopware.com/docs/resources/references/upgrades/core/translation/language-pack-migration.html. But not every customer is feeling comfortable being forced to use the command line. It is intended to activate / deactivate a language via the language itself. So why don't you add an install / uninstall routine in settings >…1 vote
348 results found
-
Enable export of property groups that don't have any options
Currently when I export property groups and their options, property groups that don't have any options are ignored and do not appear in the export.
It would be nice to have the possibility to include these property groups as well.
Use case: The shop owner wants to create property groups with its position numbers in a first step. In a second step, a middleware imports products with the corresponding property group options.2 votes -
B2B Components - Quotes - Show requesting employee
Show requesting employee in the quote details in the admin. Preferably also in the quote overview in an additional column. Currently we only show the B2B customer / Debtor but we are not giving any details about the employee that requested an offer / quote.
3 votes -
Fixed or Configurable Column Widths in the Order Overview
Long billing or delivery addresses in the Order Overview can cause columns to become excessively wide, making the entire order overview difficult to read. Please introduce fixed or configurable column widths, including a maximum width for address columns.
2 votes -
Admin / UX: preserve list size setting & allow custom list sizes
The Shopware Administration currently lets you pick fixed list sizes (i.e. customer list, product list) of 10, 25 (default), 50, 75 and 100.
However, the Administration does not remember the selection beyond the current session or when copying the link of the list to another session. Furthermore, it's not possible to define sizes other than the predefined ones, unless one modifies the limit-parameter in the URL.
This proposal asks:
- Make the limit customizable, perhaps with a dynamic endless scrolling option as well
- Retain the selected setting for future sessions2 votes -
Improvement proposal: Allow shoppers to dismiss and reapply automatic promotions
In Shopware 6.8, shoppers can no longer manually remove automatically applied promotions from the cart. This prevents a promotion from getting stuck after accidental removal, but it also removes the shopper’s ability to decline an optional promotion, such as a free gift.
Removing the gift product itself may work if it is a regular cart item. However, the behavior can vary when an extension adds the product.
Proposal
Allow shoppers to dismiss an applied automatic promotion without permanently blocking it. As long as the cart still meets the promotion’s conditions, the promotion should remain visible as “not applied” and be available to apply again.Shop operators should be able to choose whether shoppers can dismiss automatic promotions.
Acceptance criteria
- Shop operators can configure whether shoppers may dismiss automatic promotions.
- When enabled, shoppers can dismiss an applied promotion without emptying the cart.
- If the cart remains eligible, the dismissed promotion stays visible as “not applied” and can be applied again.
- Shopware updates the promotion’s availability when cart changes affect its eligibility.
- Removing a free gift does not leave an inconsistent promotion or unwanted product in the cart.
- The behavior remains compatible with manually entered promotion codes and extensions that add free gifts.This would prevent promotions from becoming permanently unavailable while still allowing shoppers to decline optional gifts.
In Shopware 6.8, shoppers can no longer manually remove automatically applied promotions from the cart. This prevents a promotion from getting stuck after accidental removal, but it also removes the shopper’s ability to decline an optional promotion, such as a free gift.
Removing the gift product itself may work if it is a regular cart item. However, the behavior can vary when an extension adds the product.
Proposal
Allow shoppers to dismiss an applied automatic promotion without permanently blocking it. As long as the cart still meets the promotion’s conditions, the promotion should remain visible as “not applied” and be…2 votes -
Expand Flow Builder for Advanced B2B and Logistics Workflows
The current Flow Builder is a powerful automation tool, but it does not provide sufficient coverage for many real-world B2B and logistics processes.
Merchants often need to implement custom workarounds because important triggers and actions for fulfillment, warehouse operations, and B2B workflows are not available out of the box.
Examples of commonly requested capabilities include:
- Shipment Ready trigger
- Warehouse and fulfillment process triggers/actions
- B2B-specific workflow triggers/actions
- Automated status changes based on logistics events
- More granular control over order and delivery processes
A valuable enhancement would be to significantly expand the available Flow Builder triggers and actions to better support advanced operational workflows.
Key benefits include:
- Reducing the need for custom development and workarounds
- Enabling merchants to automate complex fulfillment and logistics processes
- Supporting more sophisticated B2B business requirements
- Increasing flexibility and scalability for growing merchants
A broader set of native triggers and actions would allow businesses to automate critical operational processes directly within Shopware and unlock the full potential of the Flow Builder for enterprise and B2B use cases.
The current Flow Builder is a powerful automation tool, but it does not provide sufficient coverage for many real-world B2B and logistics processes.
Merchants often need to implement custom workarounds because important triggers and actions for fulfillment, warehouse operations, and B2B workflows are not available out of the box.
Examples of commonly requested capabilities include:
- Shipment Ready trigger
- Warehouse and fulfillment process triggers/actions
- B2B-specific workflow triggers/actions
- Automated status changes based on logistics events
- More granular control over order and delivery processes
A valuable enhancement would be to significantly expand the available Flow Builder triggers and actions to better support advanced…
3 votesGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
Shopware App for mobiles
Please note that most competitors have an app for mobile, to follow some real time KPI statistics. That would make sense for Shopware to have. what are the thoughts about that from Shopware?
13 votes -
Customize Search Results in the Admin (Quick Results)
If, for example, a company name is searched for using the search bar within the admin interface, a small window appears displaying—among other things—customer names. However, only the first and last names are displayed, not the company name itself. Since it cannot be entirely ruled out that customer names unrelated to the searched company might also be displayed, the company name should be included in this list as well.
6 votes -
Suggestion: Add a link to the Garan label
Just as warranty labels were already well implemented in Shopware version 6.7.15, I think linking warranty labels to https://europa.eu/youreurope/garantien would be a good idea. Not only from a legal standpoint, but also from the customer’s perspective.
Perhaps this has to be taken into account: https://feedback.shopware.com/forums/942607-shopware-6-product-feedback-ideas/suggestions/51682885-gew%C3%A4hrleistungs-label-%C3%BCber-link-nicht-zul%C3%A4ssig
2 votes -
Admin: Pin settings to menu
Different Shopware Admin users have different responsibilities and need to access different settings more often than others.
It would be nice, if you can pin specific settings to the navigation menu in order to customize the navigation and have faster access to regularly used settings.
3 votes -
SRT files for subtitles (videos)
With regard to video accessibility, it should also be possible to upload SRT files for subtitles.
2 votes -
Badge: based on dynamic product groups / Badge basierend auf dynamische Produktgruppe
DE:
Es sollte möglich sein anhand einer dynamische Produktgruppe das Badge selbst gestalten zu können (Farbe, Position im Bild oben rechts, oben links, unten links, unten rechts) sowie den Text
Anwendungsfall:
- Räumungsverkauf
- Werbegeschenk
- geringer Lagerbestand
usw.Forum (DE): https://forum.shopware.com/t/badge-im-listing-basierend-auf-einer-dynamischen-produktgruppe/103456
EN:
It should be possible to customize the badge itself—including its color, position (top right, top left, bottom left, or bottom right of the image), and text—based on a dynamic product group.
Use Case:
- for clearance sale
- promoting gift
- low inventory
etc3 votes -
Warning in Administration when APP_DEBUG=1 is enabled in production environment
In a productive Shopware 6 installation, APPDEBUG=1 may temporarily be enabled during troubleshooting and then unintentionally remain active afterward. Based on our findings, this causes Shopware to output a noindex directive in the storefront, even when APPENV=prod is explicitly set.
This creates a critical SEO risk because the issue can easily go unnoticed and may ultimately lead to the shop being removed from the Google index.
Problem:
Currently, there seems to be no visible warning in the Administration when a production environment is running with APP_DEBUG=1Expected Behavior:
If APPENV=prod and APPDEBUG=1 are detected at the same time, Shopware should clearly warn administrators about this potentially dangerous configuration.Possible implementations could include:
- a visible warning message in the Administration dashboard
- a dedicated system health check
- a notification explaining the potential SEO impactBenefit:
Such a warning would help prevent accidental SEO issues caused by forgotten debug configurations in production environments.In a productive Shopware 6 installation, APPDEBUG=1 may temporarily be enabled during troubleshooting and then unintentionally remain active afterward. Based on our findings, this causes Shopware to output a noindex directive in the storefront, even when APPENV=prod is explicitly set.
This creates a critical SEO risk because the issue can easily go unnoticed and may ultimately lead to the shop being removed from the Google index.
Problem:
Currently, there seems to be no visible warning in the Administration when a production environment is running with APP_DEBUG=1Expected Behavior:
If APPENV=prod and APPDEBUG=1 are detected at the…4 votes -
Add missing JSON-LD fields recommended by Google
As noted in the issue #19080 on GitHub, certain fields could not be added to Shopware's JSON-LD implementation due to core limitations. Relevant fields include: hasMerchantReturnPolicy, shippingRate, shippingDestination, vatID, legalName, PostalAddress, address and contactPoint
The implementation of these fields should be evaluated to be able to deliver more relevant data to Google and enhancing the listings of merchants using Shopware.
2 votes -
Hide legal guarantee notice for B2B customers within mixed B2B/B2C sales channels
Currently, the legal guarantee notice in the checkout can be enabled or disabled per sales channel using the option “Show legal guarantee notice on checkout page.”
For B2B customers, this notice is generally not required. However, in practice, B2B and B2C customers are not always separated into different sales channels. It is common for both customer types to use the same sales channel.
It would therefore be helpful to introduce an additional condition for controlling the visibility of the legal guarantee notice. For example, the system could check the customer’s account type (private/business) or their customer group.
This would allow merchants to hide the legal guarantee notice for B2B customers while continuing to display it to B2C customers within the same sales channel.
Currently, the legal guarantee notice in the checkout can be enabled or disabled per sales channel using the option “Show legal guarantee notice on checkout page.”
For B2B customers, this notice is generally not required. However, in practice, B2B and B2C customers are not always separated into different sales channels. It is common for both customer types to use the same sales channel.
It would therefore be helpful to introduce an additional condition for controlling the visibility of the legal guarantee notice. For example, the system could check the customer’s account type (private/business) or their customer group.
This would allow…
2 votes -
Display subscription number for each order in the Admin
In the order overview in the Admin:
when looking at the list of orders, I currently cannot see from which subscription an order was created.It would make it easier to display the subscription number in the order details, to be able to know which subscription created the new order.
2 votes -
Improvement of Extension and Update Management
The management and updating of extensions could be made more efficient and transparent, especially for shops with a larger number of installed plugins.
The following improvements would be particularly helpful:
- Display the date of the last update in addition to the installation date of an extension
- History of activation and deactivation events for an extension
- Multi-selection for extensions, allowing multiple plugins to be activated, deactivated, or updated at once
- Central overview of available plugin updates and changelogs, so changes can be reviewed before updating without having to open each plugin individually
- More meaningful error messages during Shopware updates if a specific extension prevents the update, ideally identifying the affected extension directly
- Ability to enable maintenance mode directly from the update process
- Ability to trigger a backup before an update, ideally from the same central update workflow
Background:
During an update to Shopware 6.7.14.0, the update process via the Administration was repeatedly aborted without providing any clear indication of which extension was causing the issue.To identify the cause, extensions had to be deactivated individually and the update process retried each time. The Shopware update was eventually performed via the console, after which all extensions had to be activated individually again.
Especially for shops with many installed extensions, this process is very time-consuming. Multi-selection, combined with a clear indication of which extension is blocking an update, could significantly simplify both troubleshooting and the update process itself.
Reviewing upcoming plugin updates also currently requires many individual steps. To check what has changed, each plugin needs to be opened separately, its changelog located, and the user then has to navigate back to the extension management. A central overview of all available updates showing plugin name, current version, new version, and changelog would make preparing for updates considerably easier.
In addition, it would be useful to consolidate the functions relevant to a safe update process in one central location. Maintenance mode, backups, extension compatibility checks, plugin updates, and the Shopware update itself could become part of one structured update workflow.
Benefits:
Such an improvement to extension and update management would:- Reduce the amount of manual work required during updates
- Simplify troubleshooting of incompatible or problematic extensions
- Shorten maintenance windows and potential downtime
- Make update preparation clearer and more transparent
- Provide a safer and more structured overall update process
The management and updating of extensions could be made more efficient and transparent, especially for shops with a larger number of installed plugins.
The following improvements would be particularly helpful:
- Display the date of the last update in addition to the installation date of an extension
- History of activation and deactivation events for an extension
- Multi-selection for extensions, allowing multiple plugins to be activated, deactivated, or updated at once
- Central overview of available plugin updates and changelogs, so changes can be reviewed before updating without having to open each plugin individually
- More meaningful error messages during Shopware updates if a…
2 votes -
Avoiding errors with Shopware Payments partial refund
This is a proposal of a SW Payments user:
They wanted to refund a partial amount of an order. Unfortunately the whole order was refunded.It would be helpful, if there was a "check form" which repeats the data of the refund and must be approved.
Perhaps a refund stop can be part of the resolution center.
2 votes -
Inheritance of elements in CMS pages
DE:
Aktuelle Systematik seitens Shopware:Man kann CMS-Seiten erstellen und in diesen innerhalb Sektionen verschiedene Blöcke und Elemente definieren. Nun habe ich die Möglichkeit in Kategorien entweder für jede Seite ein eigenes CMS-Layout zuzuweisen. Ebenso kann man aber auch das gleiche CMS-Layout mehreren Seiten zuweisen. Hier hat man dann die Möglichkeit die Inhalte der im Layout festgelegten Elemente zu individualisieren.
Nun entsteht dadurch folgende Problematik:
Angenommen ich habe 50 Kategorie-Seiten, welche alle das gleiche vorgegebene CMS-Layout nutzen. Dann habe ich nur die Möglichkeit die Inhalte der Blöcke/Elemente zu bearbeiten, kann aber nicht die Blöcke/Sektionen auf diverse Unterseiten vererben.
Sollte somit z.B. der Fall auftreten, dass ich von 10 dieser 50 Seiten mit dem gleichen Layout an erster Stelle keinen Slider mehr möchte (aber das restliche Layout soll beibehalten werden, bzw. der Aufbau aller darauf folgenden Elemente), so ist aktuell die einzige Möglichkeit für diese 10 Unterseiten neue Layouts anzulegen.
Diese Problematik lässt sich nun hochskalieren. Nehmen wir nun an, wir wollen von den 50 Seiten, auf 10 Seiten an erster Stelle keinen Slider und von diesen 10 Seiten soll bei 4 Seiten an letzter Stelle ein anderes Element sein, müsste ich nochmals diese 4 Seiten neu erstellen.
Obwohl von diesen 50 Seiten das Grundlayout bis auf einige Blöcke identisch ist, muss ich aktuell für jegliche Abweichung am Grundlayout neue eigene Seiten erstellen und kann nicht festlegen, dass z.B. Sektionen in einem CMS-Layout vererbbar sind.
Über eine Lösung seitens Shopware würden wir uns sehr freuen, das würde die Contentbearbeitung bei umfangreichen Inhalten mit mehr als 1000 Seiten enorm vereinfachen und wäre ein wirklicher Mehrwert.
ENG:
It is possible to create CMS pages and define different blocks and elements within sections. Categories can either be assigned their own individual CMS layout per page, or the same CMS layout can be assigned to multiple pages. In this case, the content of the elements defined in the layout can be customized individually.This leads to the following problem:
Assume there are 50 category pages that all use the same predefined CMS layout. In this scenario, it is only possible to edit the content of the blocks and elements, but it is not possible to inherit blocks or sections across different subpages.
For example, if on 10 of these 50 pages the slider should no longer appear as the first element (while the rest of the layout, including the structure of all subsequent elements, should remain the same), the only current solution is to create new layouts for these 10 subpages.
This issue can be scaled further. If, for instance, out of the 50 pages, 10 pages should not have a slider as the first element, and out of those 10 pages, 4 pages should have a different element at the last position, those 4 pages would again need to be created separately.
Although the base layout of these 50 pages is largely identical except for a few blocks, any deviation from the base layout currently requires creating entirely new pages. It is not possible to define sections within a CMS layout as inheritable.
We would greatly appreciate a solution from Shopware, as this would significantly simplify content management for large setups with more than 1,000 pages and would provide real added value.
DE:
Aktuelle Systematik seitens Shopware:Man kann CMS-Seiten erstellen und in diesen innerhalb Sektionen verschiedene Blöcke und Elemente definieren. Nun habe ich die Möglichkeit in Kategorien entweder für jede Seite ein eigenes CMS-Layout zuzuweisen. Ebenso kann man aber auch das gleiche CMS-Layout mehreren Seiten zuweisen. Hier hat man dann die Möglichkeit die Inhalte der im Layout festgelegten Elemente zu individualisieren.
Nun entsteht dadurch folgende Problematik:
Angenommen ich habe 50 Kategorie-Seiten, welche alle das gleiche vorgegebene CMS-Layout nutzen. Dann habe ich nur die Möglichkeit die Inhalte der Blöcke/Elemente zu bearbeiten, kann aber nicht die Blöcke/Sektionen auf diverse Unterseiten vererben.
Sollte somit…
12 votes -
Option for B2B Components order related mails send to customer Orga employee mail
In B2B environments, orders are often placed by employees acting on behalf of their organization. Currently, Shopware sends order confirmation emails only to the primary email address of the customer account (Main Account).
However, in many cases, it is desirable for the employee who submitted the order to also receive — or solely receive — the order confirmation email or documents.
To address this, a new configuration option should be added to the customer or organization settings, allowing administrators to define the default behavior for order confirmation emails.
Functional Proposal:
Add a setting in the B2B customer configuration:
Option A: Send order confirmation to the organization’s main (default) email address.
Option B: Send order confirmation to the email address of the employee who placed the order.
The setting should be adjustable per organization.
Optionally, allow sending to both addresses.
In B2B environments, orders are often placed by employees acting on behalf of their organization. Currently, Shopware sends order confirmation emails only to the primary email address of the customer account (Main Account).
However, in many cases, it is desirable for the employee who submitted the order to also receive — or solely receive — the order confirmation email or documents.
To address this, a new configuration option should be added to the customer or organization settings, allowing administrators to define the default behavior for order confirmation emails.
Functional Proposal:
Add a setting in the B2B customer configuration:
Option A:…
12 votes
- Don't see your idea?