284 results found
-
Modern, accessible email templates should be built into Shopware by default — just like Shopify
Right now, the standard templates are plain and outdated:
• Not fully responsive on all devices
• No real focus on accessibility (screen readers, contrasts, alt-texts)
• Hard to adapt to a shop’s corporate identityIn 2025, merchants expect more. Platforms like Shopify already provide beautiful, responsive, accessible templates out of the box — Shopware should do the same.
👉 Having this built in would save time, improve customer experience, and make Shopware more competitive. Please vote if you agree!
5 votes -
Add Sha512 as legacyEncoder
Currently, only Sha256 and Md5 are supported as legacyEncoders for customer passwords. Please extend this to Sha512.
5 votes -
Make the GMV extension more transparent
As can be read in the forum and tickets, many customers are skeptical about the GMV extensions and what happens in the background.
Customers would install the extension if, for example, there was a preview function of the transfer and a log of exactly when what was transferred.
This transparency would enable Shopware to reach more customers.
5 votes -
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.
5 votes -
Improve loading times (for example by using correct values for the sizes attribute of thumbnails)
Shopware uses wrong values for the sizes attribute of thumbnails. Therefore bigger images are downloaded than shown. This increases the loading times.
It is not useful to download a thumbnail of 400 x 400 pixels if you show an image with 200 x 200 pixels.
If this is fixed you no longer need https://store.shopware.com/en/frosh56163799233f/lazysizes-and-lazyloading-for-suitable-image-sizes.html.
Shopware shows images of 430 x 430 pixels on product detail pages by default. Therefore thumbnails with 430 x 430 pixels should be created. On product detail pages the 400 x 400 pixels big thumbnails are not used for the normal product images and way…
5 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…4 votes -
Custom fields from apps cannot be repositioned.
Custom fields from apps cannot be repositioned. This means that, for example, such fields end up in product locations that are potentially completely unsuitable and irrelevant.
According to the software vendor, this is due to the Shopware core. This should be adjusted.
Feedback from the manufacturer:
"If you create custom fields within an app, these cannot be edited in the Shopware admin panel. This is a limitation of Shopware, and unfortunately, we cannot change it. Within an app, custom fields are only 'defined' in an XML file. No programming is done here to determine how and where the field is…4 votes -
Inheritable category and menu visibility in organizational units (B2B)
Currently, category and product visibility settings can only be explicitly configured per category within organizational units.
When a parent category is selected, the subcategories beneath it are not automatically included.
This leads to the following problems with extensive category structures (several hundred subcategories):
- very high manual maintenance effort
- increased susceptibility to errors
- poor maintainability when structural changes are made
- limited scalability in a B2B contextIn addition, the main menu must be controlled indirectly via individual assignments to the contained categories, as a blanket menu activation is not possible.
Target Image:
- Selecting a parent category…4 votes -
Improve checkout message performance
The AI-generated checkout message sometimes takes 10 seconds to generate if there are many products in the shopping cart.
Many customers close the page during this time. It would be better if the messages were generated in the background beforehand or if a faster AI model were used.
4 votes -
ZIP code validation only takes effect once all other mandatory fields have been filled in during checkout.
While testing the checkout process, I noticed inconsistent behavior when validating the postal code.
Steps to reproduce:
Go to checkout.
Select country.
Enter an invalid value in the “Postal code” field (e.g., asdasd or asd123).
Leave at least one other required field blank.
Click “Continue.”
Result:
All required fields are marked as incorrect except for country and zip code.
The zip code is not displayed as invalid in this state.Further behavior:
As soon as the previously missing required field is filled in, the zip code validation takes effect retrospectively and the field is then marked as incorrect.Expected behavior:…
4 votes -
B2B Components: Include divergent mail addresses in search results
Shop owners sometimes report having difficulties finding B2B root accounts when provided with little more than a mail address of an employee in case it is not conforming to the companies' mail structure.
For example:
Our B2B root account is company@example.com.
Our employee's mail address is employee@shopware.com.Since the mail addresses don't match, when searching for employee@shopware.com, we will find no results for customers. This is sometimes the case where entire departments have separate mail addresses like a purchase department.
So the request is to have an option to index employee mail addresses and associate them with…
4 votes -
Force customers to assign a new password after creation via the administration
There should be an option to force customers - that have been set up through the administration - to change their password after the initial login.
4 votes -
returns management: Add additional items
Currently, no additional new items can be added to a return. It would be great if this option were available, for example, to add return costs that cannot be processed via the shipping costs.
4 votes -
Add express buttons for google/apple pay
Please add Apple/Google Pay Express buttons to Shopware Payments & PayPal Extension
This is a follow-up of https://feedback.shopware.com/forums/942607-shopware-6-product-feedback-ideas/suggestions/48554927-add-express-buttons-for-google-apple-pay
3 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 -
Improve Admin search for properties
Bei der Suche nach Artikeleigenschaften ist uns aufgefallen, dass vollständige Ausprägungen mit Leerzeichen offenbar nicht gezielt gesucht werden können.
Ein Beispiel:
Eigenschaft: «Masse / Grösse»
Gesuchte Ausprägung: «14 x 14 x 38 cm»Idealerweise möchten wir im Feld «Ausprägungen durchsuchen» den vollständigen Wert «14 x 14 x 38 cm» eingeben und direkt die passende Ausprägung angezeigt erhalten.
Aktuell scheint die Suche jedoch nur einzelne Bestandteile wie «14» oder «38» zu berücksichtigen. Dadurch werden sehr viele Treffer angezeigt und die gewünschte Ausprägung muss manuell gesucht werden.
Könnt ihr bitte prüfen, ob die Suche nach vollständigen Ausprägungen inklusive Leerzeichen und Sonderzeichen irgendwie…
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.
-
Product visibility options in dynamic product group
EN
If a product’s visibility is set to ‘Hide in product lists and search’, the product will not be displayed in the storefront. If a dynamic product group is to be used for a product comparison or product export that includes these products, then
- the shop operator has no way of querying the product visibility settings
- the products are exported in a feed and are therefore visible (externally) after all.DE
Wenn in einem Produkt die Produktsichtbarkeit auf in Produklisten und Suche ausblenden gestellt ist, werden die Produkt in der Storefront entsprechend nicht angezeigt. Wenn eine Dynamische Produktgruppe…3 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…
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.
-
Custom coupon codes as variables
It should be possible to automatically send individual coupon codes via email, for example, as a variable in email templates.
3 votes -
Central Management and Exclusion of Image Keywords in Shopware
Problem:
The Shopware Image Keyword Assistant generated irrelevant and misleading keywords for a product image. In this specific case, keywords such as “Kanalisation,” “Kanalschacht,” and “Loch” were detected or generated — likely based on a small detail within the image — and do not accurately represent the product. These terms are inappropriate and not acceptable from a merchant’s perspective.
Example of generated keywords:
“Loch, Abtropfen lassen, Kanalisation, Kanalschacht, Loch, Abtropfen lassen, Kanalisation, Kanalschacht, Bodenmatte, Gepäckmatte, Autoabdeckung, Kofferraummatte, Rutschfeste Matte, matte de, tappetino auto, sotto-pavimento?, antiscivolo, tappeto auto”
The terms “Kanalisation,” “Kanalschacht,” and “Loch” are clearly not relevant and do not…
3 votes
- Don't see your idea?