- or
No existing idea results
- ~ No ideas found ~
1561 results found
-
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…3 votes -
Checkbox für AGB entfernen, weil rechtlich unnötig
Laut https://www.heise.de/hintergrund/Warum-im-Netz-Checkboxen-fuer-AGB-und-Datenschutz-meist-ueberfluessig-sind-10449542.html braucht man keine Checkboxen für Datenschutzerklärung und AGB.
Durch das Entfernen der Checkbox für die AGB im Checkout ist der Checkout viel schneller und einfacher.
Bei der verlinkten Seite sind Formulierungen für den Text angegeben. Ohne Checkbox muss der Text angepasst werden.
Viele Besucher übersehen die Checkbox, klicken auf den Kaufen-Button und bekommen dann eine Fehlermeldung, dass sie erst einen Haken setzen müssen.
25 votes -
B2B: allow defining and using of multiple VAT IDs per customer account
Currently, only one VAT ID can be defined for a customer. This may be undesirable for some companies that are tightly related to other legal entities or have sub-companies they want to create orders for. In that case, multiple customer accounts would need to be created for proper invoicing.
The database structure already has a field to store a VAT ID with an address, so it would be useful to allow saving different VAT IDs depending on the address, so that customer can choose them during checkout.
7 votes -
Offline/Developer mode for the commercial plugin in local development environments
Partners and agencies often work on multiple client projects simultaneously. Consequently, a local development environment may contain extensions for various clients, even though those extensions are neither actively used nor tested there.
The commercial plugin currently checks installed extensions and their license status but cannot distinguish between an extension that is merely part of the local development environment and one that is actually in use. In development environments, this can lead to unexpected license checks or subsequent actions.
An optional offline or developer mode for local development environments—intended exclusively for non-production systems—would be beneficial. Alternatively, a way to clearly designate local development environments as such would help, allowing license checks to be adjusted accordingly.
Added value:
- Better support for agencies and partners managing multiple client projects.
- Fewer unintended license conflicts in local development environments.
- Improved developer experience with no impact on production systems.Partners and agencies often work on multiple client projects simultaneously. Consequently, a local development environment may contain extensions for various clients, even though those extensions are neither actively used nor tested there.
The commercial plugin currently checks installed extensions and their license status but cannot distinguish between an extension that is merely part of the local development environment and one that is actually in use. In development environments, this can lead to unexpected license checks or subsequent actions.
An optional offline or developer mode for local development environments—intended exclusively for non-production systems—would be beneficial. Alternatively, a way to clearly designate…
2 votes -
Allow approvers to edit orders in B2B-Approval-Workflows
Problem Description:
In the current B2B approval workflow, users with an Approver can only approve or reject orders that are subject to approval rules.
Even if the role permissions are explicitly set to allow order-related actions, the approver cannot make any changes to the order before approving it.
This is a limitation for real-world B2B processes, where ordering mistakes are common and must be corrected by the approver instead of rejecting and recreating the order.
Current Behavior:
When an order requires approval:
- The approver can only approve or reject the order
- The approver cannot:
- Change product quantities
- Remove order positions
- Change payment method
- Change shipping method
- Edit billing or shipping addresses
- Write a comment on the order, regardless of approvalThis behavior applies even if the corresponding permissions are assigned to the approver role.
Expected Behavior:
Approvers should be able to edit an order before approval, according to the permissions defined for their role.
If the role permissions allow it, an approver should be able to:
- Remove order line items
- Adjust product quantities
- Change payment method
- Change shipping method
- Edit billing and shipping addresses
- Regardless of approval or rejection, write a comment on the orderThe approval decision (approve/reject) should then apply to the modified order.
Business Impact:
In B2B commerce, approval workflows are meant to:
- Correct ordering mistakes
- Ensure compliance with company rules
- Avoid unnecessary rejections and re-ordersRestricting approvers to only approve or reject orders leads to:
- Inefficient workflows
- Increased manual effort
- Poor user experience for B2B customersThis behavior does not reflect common B2B purchasing processes, where approvers are expected to correct errors rather than reject orders entirely.
Problem Description:
In the current B2B approval workflow, users with an Approver can only approve or reject orders that are subject to approval rules.
Even if the role permissions are explicitly set to allow order-related actions, the approver cannot make any changes to the order before approving it.
This is a limitation for real-world B2B processes, where ordering mistakes are common and must be corrected by the approver instead of rejecting and recreating the order.
Current Behavior:
When an order requires approval:
- The approver can only approve or reject the order
- The approver cannot:
- Change product quantities…6 votes -
Structured data for AI readability
I recently stumbled upon this press release by one of our partners - basically an ad for their plugin: https://www.openpr.de/news/1299320/Shopware-Shops-werden-KI-sichtbar-mitho-veroeffentlicht-KI-Agentic-Commerce-Plugin.html
However, as Shopware wants to go ahead with AI massively, the proposed features seem to be basic when it comes towards being prepared for AI readability:
- structured product and category feeds in JSON format
- llms.txt and other manifests for AI
- precise microdata and JSON descriptions of variants, prices, shipping etc.
7 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 meet expected quality standards.
Current Limitation:
At present, Shopware does not provide a way for merchants to centrally exclude or remove unwanted keywords. The only option is to manually edit keywords per media item in the media library. This becomes highly inefficient when the issue affects multiple assets (e.g., 50 images all containing the same incorrect keyword like “Kanalisation”).
Proposed Solution:
Introduce a centralized/global keyword management feature that allows merchants to:
- Define a list of excluded keywords (blacklist)
- Automatically prevent these keywords from being generated in the future
- Remove these keywords across all existing media assets in bulk
- Optionally trigger an update of affected metadata (e.g., alt texts) when keywords are removed
This would significantly improve efficiency, ensure higher data quality, and give merchants better control over automatically generated content.
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 -
Shopware Account Plugin License List Update
The current license list overview of the shop in the account.shopware.com is sadly not really handy for customers / agencies.
When updating to later Shopware Versions, you need mostly plugin updates to get back from a broken to a working state (e.g. 6.6 > 6.7, php bin/console fails as well):
- Therefore I have to go to said website, search for the plugin name (somehow over name / description mixed, because names are handled differently in the search)
- Then click on the plugin (when i finally found it) and get the update version.
- Another plugin must be found the same way again.
A better solution would be:
- Make the search icon search over all tab categories (rent + free + archived..)
-> faster search of single plugins
- Show the technicalName in the license list table to make it "searchable" and or via CMD/STRG+F
-> Plugin Descriptions are different in store than in plugin composer.json -> always hard to find (especially with german/english translations)
- Add function to shopware-cli that you can update / migrate plugins from custom/plugins structure to composer.json
-> handy one command to select a list of plugins to update the latest version / migrate to composerThe current license list overview of the shop in the account.shopware.com is sadly not really handy for customers / agencies.
When updating to later Shopware Versions, you need mostly plugin updates to get back from a broken to a working state (e.g. 6.6 > 6.7, php bin/console fails as well):
- Therefore I have to go to said website, search for the plugin name (somehow over name / description mixed, because names are handled differently in the search)
- Then click on the plugin (when i finally found it) and get the update version.
- Another plugin must be found the same way…
2 votes -
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 für einen Produktvergleicht / Produktexport genutzt werden soll, in dem diese Produkte enthalten sind, dann
- gibt es für den Shopbetreiber keine Möglichkeit die Optionen der Produktsichtbarkeit abzufragen
- die Produkte werden in einem Feed exportiert und somit dann doch (extern) sichtbar.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…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…
2 votes -
Automatic Country Restrictions Based on Manufacturer
Many merchants need to restrict the sale of specific brands or manufacturers in certain countries due to contractual, legal, or distribution agreements.
Currently, country restrictions must be assigned manually on a product-by-product basis. This becomes error-prone and difficult to maintain, especially for large product catalogs and when new products are added regularly.
A valuable enhancement would be the ability to define country restrictions at the manufacturer level and automatically apply them to all associated products.
Key benefits include:
- Automatically inheriting country restrictions for newly created products of a manufacturer
- Reducing manual maintenance and the risk of human error
- Ensuring compliance with brand-specific distribution agreements
- Improving scalability for merchants managing large product catalogs
This would provide a more efficient and reliable way to manage international sales restrictions while significantly reducing administrative effort.
Many merchants need to restrict the sale of specific brands or manufacturers in certain countries due to contractual, legal, or distribution agreements.
Currently, country restrictions must be assigned manually on a product-by-product basis. This becomes error-prone and difficult to maintain, especially for large product catalogs and when new products are added regularly.
A valuable enhancement would be the ability to define country restrictions at the manufacturer level and automatically apply them to all associated products.
Key benefits include:
- Automatically inheriting country restrictions for newly created products of a manufacturer
- Reducing manual maintenance and the risk of human error
- Ensuring compliance…
2 votes -
Packaging Unit Recommendation for B2B Products
Many B2B merchants sell products that are physically supplied in packaging units (e.g., 20 pieces per carton) while still allowing customers to order any quantity on a per-piece basis.
Currently, Shopware provides features such as tier pricing, minimum order quantities, and quantity steps. However, there is no native way to define a packaging unit for a product and use it as a recommendation rather than a restriction.
A valuable addition would be the ability to:
- Define a packaging unit size per product (e.g., 20 pieces)
- Display a recommendation in the buy box suggesting the next full packaging multiple based on the selected quantity
- Optionally provide convenience actions such as “+1 packaging unit”
- Encourage ordering full packaging units without enforcing quantity restrictions
The underlying product and inventory logic should remain unchanged:
- No product variants are required
- No separate products for packaging units are required
- Inventory should continue to be managed on the regular product level
- The cart should continue to process only the actual ordered piece quantity
This would help B2B merchants optimize logistics and packaging efficiency while maintaining maximum flexibility for customers.
Many B2B merchants sell products that are physically supplied in packaging units (e.g., 20 pieces per carton) while still allowing customers to order any quantity on a per-piece basis.
Currently, Shopware provides features such as tier pricing, minimum order quantities, and quantity steps. However, there is no native way to define a packaging unit for a product and use it as a recommendation rather than a restriction.
A valuable addition would be the ability to:
- Define a packaging unit size per product (e.g., 20 pieces)
- Display a recommendation in the buy box suggesting the next full packaging multiple based on…
2 votes -
Revocation button for Online-Shops
The revocation button for online stores will become mandatory in the near future. You should therefore keep an eye on this now.
https://www.versandhandelsrecht.de/2024/03/27/widerrufsbutton/
https://www.golem.de/news/neuerungen-bei-onlinekaeufen-der-widerrufs-button-kommt-2507-197913.html
https://www.bmjv.de/SharedDocs/Gesetzgebungsverfahren/DE/2025_GAendVVVR.html?nn=110490
21 votes -
Easier customization of email templates
Customizing email templates is usually quite complex and hardly feasible for the average customer. For example, adding the manufacturer's name for each item in the order confirmation.
The entire process of customizing email templates should be significantly simplified and made much more intuitive. We also receive a large number of support requests regarding this.
4 votes -
Custom Products: Add weight to option values and include it in shipping weight calculation
In some cases the shipping weight may change substantially depending on product configuration using the Custom Products extension. However, merchants cannot define additional properties such as weight for custom products options at the moment. This makes it more difficult to calculate appropriate shipping costs.
2 votes -
Allow copying and moving banner elements within Shopping Experiences without losing links
In Shopware 5, it was possible to move individual banners within a landing page using clipboard functionality without losing the assigned links.
In Shopware 6, this is currently not possible. Images have to be reselected from the media library, text has to be rewritten, and links have to be reassigned manually.
Especially for homepages and landing pages with multiple banners, it would be highly beneficial to allow copying and repositioning content within a Shopping Experience while keeping all existing configurations (images, text, links) intact.
3 votes -
Hide buy button for specific products on sales channel level
Implement an option that allows hiding the buy button for specific products. Moreover, it should be possible to hide the buy button for specific sales channels while it continues to be displayed in other sales channels.
6 votes -
Shopware Analytics - Beta Phase
Following the launch of the first iteration of Shopware Analytics, we are continuing to develop the next iterations, which will further enhance functionalities. Additionally, we will steadily introduce a series of new dashboards featuring more metric visualizations. These updates will be rolled out independently of Shopware minor releases, leveraging the flexibility of our App-based service.
We invite you to explore the new features of Shopware Analytics and share your feedback. Your insights and feedback will be considered during development to ensure continuous improvement.
Here you can find the original feedback, which was the base of the first iteration: https://feedback.shopware.com/forums/942607/suggestions/45651289
96 votesWe already started the further development and already added new statistics:
Added a new KPI “Promotion codes”
Added a new KPI “Sales by manufacturer”
Added a new KPI Sales by country
Added a new KPI Best selling products
UI enhancements and technical improvements
-
Mark quotes with message in the quote listing
EN
When requesting quotes via B2B Components, shop customers have the option to send a message. Unfortunately, there is no indication in the quote list that a message has been sent. No additional fields are available either. Our client’s request is as follows: please mark quotes that include a message directly in the listing, for example using a speech bubble icon or similar.
DE
Wenn über B2B Components Angebote angefragt werden, hat der Shopkunde die Möglichkeit dabei eine Nachricht zu schicken. Leider ist in der Angebotsliste kein Hinweis darauf zu finden, dass es eine Nachricht gibt. Weitere Felder stehen ebenfalls nicht zur Verfügung, Der Wunsch unseres Kunden lautet: Bitte Angebote mit Nachricht bereits im Listing markieren, zum Beispiel durch ein Sprechblasensymbol oder ähnliches.EN
When requesting quotes via B2B Components, shop customers have the option to send a message. Unfortunately, there is no indication in the quote list that a message has been sent. No additional fields are available either. Our client’s request is as follows: please mark quotes that include a message directly in the listing, for example using a speech bubble icon or similar.
DE
Wenn über B2B Components Angebote angefragt werden, hat der Shopkunde die Möglichkeit dabei eine Nachricht zu schicken. Leider ist in der Angebotsliste kein Hinweis darauf zu finden, dass es eine Nachricht gibt. Weitere Felder stehen ebenfalls…2 votes -
Warenkorb Spalte "Produktnummer" auch für Angebote
Im Backend besteht derzeit im Warenkorb von Angeboten keine Möglichkeit, die Spalte „Produktnummer“ einzublenden, um die Artikelnummern der hinzugefügten Produkte direkt sehen zu können.
Da diese Funktion bei Aufträgen bereits verfügbar ist, wäre es sinnvoll und hilfreich, die Anzeige der Produktnummer auch für Angebote zu ermöglichen.
___EN below_______
Shopping cart column "Product number" also for offers: Currently, in the backend, there is no option to display the "Product number" column in the shopping cart for offers, so that the article numbers of the added products can be viewed directly. Since this function is already available for orders, it would be useful and helpful to enable the display of the product number for offers as well.
Im Backend besteht derzeit im Warenkorb von Angeboten keine Möglichkeit, die Spalte „Produktnummer“ einzublenden, um die Artikelnummern der hinzugefügten Produkte direkt sehen zu können.
Da diese Funktion bei Aufträgen bereits verfügbar ist, wäre es sinnvoll und hilfreich, die Anzeige der Produktnummer auch für Angebote zu ermöglichen.
___EN below_______
Shopping cart column "Product number" also for offers: Currently, in the backend, there is no option to display the "Product number" column in the shopping cart for offers, so that the article numbers of the added products can be viewed directly. Since this function is already available for orders, it…
2 votes
- Don't see your idea?