- or
21 results found
-
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
329 results found
-
Digital Sales Room - Live Queue & Direct Call Functionality
Enhance the Digital Sales Room by introducing a real-time interaction feature (Button Frontend) that allows customers to directly request live consultations with available presenters, including a queue system for managing demand.
Use Case Example:
A customer browsing the Onlineshop has a question about a product or offering. Instead of waiting for a scheduled session, they can immediately request a consultation. If no presenter is available, they are placed in a queue and connected as soon as possible.
This feature would significantly enhance the flexibility and usability of the Digital Sales Room, turning it into a hybrid tool that supports both events and real-time customer engagement.
Enhance the Digital Sales Room by introducing a real-time interaction feature (Button Frontend) that allows customers to directly request live consultations with available presenters, including a queue system for managing demand.
Use Case Example:
A customer browsing the Onlineshop has a question about a product or offering. Instead of waiting for a scheduled session, they can immediately request a consultation. If no presenter is available, they are placed in a queue and connected as soon as possible.
This feature would significantly enhance the flexibility and usability of the Digital Sales Room, turning it into a hybrid tool that supports both…
5 votes -
Artikelübersichtstabelle (Kataloge|Produkte) | Improve product lists
Es wäre sehr hilfreich, wenn im Backend bei der Artikelübersicht weitere Spalten zur Ansicht ein-/ausgeblendet werden könnten, so wie in SW5. Wenn man eine schnelle Übersicht haben will, welche Artikel z.B. eine bestimmte Eigenschaft haben.
Filterbar sind Eigenschaften auch nicht. Dies wäre eine hilfreiche alternative Funktion.
So ist eine Pflege mehrerer Artikel sehr umständlich. Da war SW5 deutlich besser.
Diese Funktionalität wäre für mich eigentlich eine Standardfunktion. Wann wird hier nachgebessert?
–
It would be very helpful if additional columns could be toggled on or off in the backend product overview, just like in SW5—for instance, to get a quick overview of which products have a specific property.
Properties cannot be filtered either; that would be a useful alternative feature.
As it stands, managing multiple products is very cumbersome. SW5 was significantly better in this regard.
To me, this is essentially a standard feature. When will this be improved?
Es wäre sehr hilfreich, wenn im Backend bei der Artikelübersicht weitere Spalten zur Ansicht ein-/ausgeblendet werden könnten, so wie in SW5. Wenn man eine schnelle Übersicht haben will, welche Artikel z.B. eine bestimmte Eigenschaft haben.
Filterbar sind Eigenschaften auch nicht. Dies wäre eine hilfreiche alternative Funktion.
So ist eine Pflege mehrerer Artikel sehr umständlich. Da war SW5 deutlich besser.
Diese Funktionalität wäre für mich eigentlich eine Standardfunktion. Wann wird hier nachgebessert?
–
It would be very helpful if additional columns could be toggled on or off in the backend product overview, just like in SW5—for instance, to get a quick…
2 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.
-
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 -
Admin: ability to display all products of category including subcategories
Currently, one cannot display all products from a category including subcategories in the administration. Both the filter on the product page and the assigned products page of the category will only display directly assigned products.
It would be helpful to have a filter option to display products of subcategories as well. Otherwise, one would need to use workarounds via dynamic product groups, the API, or Import/Export.
5 votes -
Import/Export Cheapest price (last 30 days)
There should be a way to import/export the cheapest price (last 30 days).
There is a regulationPrice in the price field for this purpose, but it cannot currently be mapped.
12 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.
2 votes -
wish list: sending the whole wish list to cart
It would be nice to send the whole wish list to cart at once via one click.
2 votes -
Enhanced Pricing Flexibility for Subscriptions
Current Limitation
At the moment, the same base product price is used for both one-time purchases and subscription purchases. This limits flexibility in commercial models and pricing strategies.Requested Enhancements
Option to Hide the One-Time Purchase Price
It should be possible to hide the one-time purchase option entirely for products that are primarily intended to be sold as subscriptions. This would allow merchants to position certain products as “subscription-only” without displaying a regular purchase alternative.Individual Pricing per Subscription Interval
If the one-time purchase price remains visible, merchants should have the ability to define separate prices per subscription interval (e.g., monthly, quarterly, yearly).
Currently, the same product price is used as the calculation basis for both one-time and subscription models, regardless of the selected interval.Example Use Case
One-time purchase: €25.000
Monthly subscription: €480
Quarterly subscription: €985
Annual subscription: €2.500In addition to pricing flexibility, we require enhanced control over how shipping costs are calculated for subscription products.
Requested Options
Merchants should be able to configure whether shipping costs are:
Charged for every subscription delivery,
Charged only once (e.g., for the initial order), or
Charged upfront for the minimum subscription interval (e.g., calculated once for the full minimum term).
Currently, there is no flexible configuration for subscription-specific shipping logic.
Current Limitation
At the moment, the same base product price is used for both one-time purchases and subscription purchases. This limits flexibility in commercial models and pricing strategies.Requested Enhancements
Option to Hide the One-Time Purchase Price
It should be possible to hide the one-time purchase option entirely for products that are primarily intended to be sold as subscriptions. This would allow merchants to position certain products as “subscription-only” without displaying a regular purchase alternative.Individual Pricing per Subscription Interval
If the one-time purchase price remains visible, merchants should have the ability to define separate prices per subscription interval (e.g.,…7 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…7 votes -
Newsletter Conformation Page
As a merchant, I want to be able to set up and define a newsletter confirmation page that shows up as soon as the customer clicked the confirm link in the DOI mail.
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…3 votes -
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 -
Automated Calculation of Fees (Customs & Taxes) in Checkout for International Orders
Currently, Shopware 6 does not provide a native feature for automatically calculating variable fees such as customs duties, import taxes, or country-specific charges during checkout.
However, this functionality is increasingly important for international merchants to ensure a legally compliant and transparent order process.Competing platforms (e.g., Shopify) already offer this functionality as a built-in feature. It enables automated calculation and display of additional fees (e.g., customs duties, import VAT, service fees) based on product value, shipping destination, product category, or customs tariff number (HS code).
In Shopware, this can currently only be achieved through manual configuration using the shipping method price matrix, which is not dynamic and cannot handle complex calculation logic (e.g., article-based or country-based variations). Additionally, surcharges added via the price matrix are included in the cart subtotal, leading to incorrect tax and duty calculations when these are applied again on top.
Use Cases:
International Shipping: Merchants shipping outside the EU (e.g., to the US, UK, Canada, or Switzerland) need to automatically calculate and display customs and import duties.
Legal Compliance & Transparency: Customers should be informed of all applicable fees during checkout to prevent unexpected costs or returns.
Automation & Efficiency: Merchants want to automate fee calculation via integrations with external tax or logistics services (e.g., Avalara, Zonos, FedEx API, etc.) rather than maintaining manual tables.
Competitive Edge: Competing eCommerce systems like Shopify or BigCommerce already include this capability, putting Shopware at a disadvantage, especially for international merchants.
Suggested Implementation:
-
Introduce a dynamic fee calculation module within checkout, based on:
- Shipping destination
- Product item data (including tariff/HS code)
- Total cart value
- Potentially also carrier or fulfillment method
Provide API endpoints and plugin interfaces for integrating external tax or customs calculation services.
-
Add configurable admin settings to define:
- Which fee types should be calculated (customs, taxes, service fees, etc.)
- Whether the fees should be shown in the cart or added during checkout only.
The technical foundation could be a core-level extensibility module that third-party providers can build upon.
Benefits:
Increased legal compliance for international trade.
Transparent cost display for customers.
Reduced cart abandonment rates due to unexpected delivery charges.
Improved competitiveness and attractiveness for global and enterprise merchants.
Currently, Shopware 6 does not provide a native feature for automatically calculating variable fees such as customs duties, import taxes, or country-specific charges during checkout.
However, this functionality is increasingly important for international merchants to ensure a legally compliant and transparent order process.Competing platforms (e.g., Shopify) already offer this functionality as a built-in feature. It enables automated calculation and display of additional fees (e.g., customs duties, import VAT, service fees) based on product value, shipping destination, product category, or customs tariff number (HS code).
In Shopware, this can currently only be achieved through manual configuration using the shipping method…
16 votes -
Badge : Product bought on / Produkt gekauft am
EN:
It should be a badge for already purchased products and tha last purchased date.
Naming: "Product purchased on" or "Item bought on". Like Amazon.DE:
Es sollte ein Badge geben um Produkte zu kennzeichnen, die bereits gekauft wurden sind und hier das Datum des letzten Kaufs anzeigen. So macht es beispielsweise auch Amazon.2 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.
-
Reintroduce CLI commands (functionality) for Migrations
CLI commands for migrations have been removed from release 16 (see https://github.com/shopware/shopware/issues/10825) without proper replacement.
As a result it is currently not possible to migrate with a finer selection via the CLI. One has to select an entire data category (i.e. all products) to migrate, making it more difficult and time-consuming in larger shops to debug issues.
2 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.
-
Allow saving changes by pressing Enter in the Admin
Allow saving changes by pressing Enter in the Admin
Description:
In Shopware 5, it was possible to save many changes simply by pressing the Enter key after editing a field. This made product maintenance much faster because users did not have to move their hand from the keyboard to the mouse to click Save or the checkmark.In Shopware 6, after editing fields such as prices, users always have to click the save/checkmark button with the mouse.
For merchants maintaining hundreds or thousands of products every day, this results in many unnecessary mouse clicks and slows down the workflow.
Expected behavior
After editing a field (for example a price), pressing Enter should:
Confirm the edited value.
Save or apply the change (depending on the context).
Allow the user to continue working without using the mouse.This should work consistently throughout the Shopware Admin where appropriate.
Benefits
Faster product maintenance.
Better keyboard workflow.
Fewer mouse movements.
Increased productivity for power users.
Similar workflow to Shopware 5, making migration easier.Allow saving changes by pressing Enter in the Admin
Description:
In Shopware 5, it was possible to save many changes simply by pressing the Enter key after editing a field. This made product maintenance much faster because users did not have to move their hand from the keyboard to the mouse to click Save or the checkmark.In Shopware 6, after editing fields such as prices, users always have to click the save/checkmark button with the mouse.
For merchants maintaining hundreds or thousands of products every day, this results in many unnecessary mouse clicks and slows down the workflow.
Expected…
2 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.
-
Passwortfelder in Storefront mit "Passwort anzeigen"-Funktion ausstatten
In der Shopware-Storefront wäre es hilfreich, Passwortfelder standardmäßig mit einer Möglichkeit zum Ein- und Ausblenden des eingegebenen Passworts auszustatten, z. B. über ein Auge-Icon.
Das betrifft insbesondere:
Passwort-Wiederherstellung
Login / RegistrierungAus UX-Sicht ist das inzwischen ein verbreitetes Pattern und hilft Kunden, Tippfehler zu vermeiden. Gerade bei der Passwort-Wiederherstellung müssen Nutzer neue Passwörter oft mehrfach eingeben, wodurch eine Sichtbarkeitsoption die Bedienbarkeit verbessern würde.
Wichtig wäre, dass dies nur eine reine Frontend-Funktion ist und keine Änderung an Passwortlogik, Validierung, Sicherheit oder Speicherung vornimmt.
EN: In the Shopware Storefront, it would be helpful if password fields included an option to show and hide the entered password by default, for example via an eye icon.
This applies in particular to:
Password recovery
Login / registrationFrom a UX perspective, this has become a common pattern and helps customers avoid typos. Especially during password recovery, users often have to enter new passwords multiple times, so a visibility toggle would improve usability.
It would be important that this remains a purely frontend feature and does not change any password logic, validation, security, or storage.
In der Shopware-Storefront wäre es hilfreich, Passwortfelder standardmäßig mit einer Möglichkeit zum Ein- und Ausblenden des eingegebenen Passworts auszustatten, z. B. über ein Auge-Icon.
Das betrifft insbesondere:
Passwort-Wiederherstellung
Login / RegistrierungAus UX-Sicht ist das inzwischen ein verbreitetes Pattern und hilft Kunden, Tippfehler zu vermeiden. Gerade bei der Passwort-Wiederherstellung müssen Nutzer neue Passwörter oft mehrfach eingeben, wodurch eine Sichtbarkeitsoption die Bedienbarkeit verbessern würde.
Wichtig wäre, dass dies nur eine reine Frontend-Funktion ist und keine Änderung an Passwortlogik, Validierung, Sicherheit oder Speicherung vornimmt.
EN: In the Shopware Storefront, it would be helpful if password fields included an option to show and…
2 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.
-
Commercial: improve organization units for shopping lists
Currently, the organization unit field on shopping lists is purely an informational indicator from which unit the list was originally created.
The following improvements should be added to give this more utility:
- The OU field should be definable during creation (i.e. by admins or the customer account) and changeable / re-assignable afterwards when needed.
- Role permissions should be added that define which lists from which OU an employee can see - this allows better separation between units which should not see lists from other departments.
3 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.
8 votes -
Maximum amount of products or maximum sum for the cart
Currently, there is no elegant way to set order limits with product amounts or the total sum per order.
One can create rules via the rule builder and use them to hide shipping methods once the limit is surpassed, but there is no transparent message for the customer that there are limits or that they have been reached.
Analogous to the “Maximum quantity” in the cart settings it would be useful to set order limits similarly, perhaps on a per sales channel basis or even on a customer group basis. Once the limit has been reached, the storefront could hinder the user from adding more items to the cart with a clear error message.
Currently, there is no elegant way to set order limits with product amounts or the total sum per order.
One can create rules via the rule builder and use them to hide shipping methods once the limit is surpassed, but there is no transparent message for the customer that there are limits or that they have been reached.
Analogous to the “Maximum quantity” in the cart settings it would be useful to set order limits similarly, perhaps on a per sales channel basis or even on a customer group basis. Once the limit has been reached, the storefront could hinder…
2 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.
- Don't see your idea?