- or
354 results found
-
Shorten the Order Number Column Header in the Order Overview
The current "Order number" column in the Order Overview header takes up unnecessary horizontal space in the order overview. Please consider shortening it to "No." or "Order No." to make the table more compact and improve readability, especially when working with many orders. Or that you can adjust the width of the columns yourself.
1 vote -
Separate sales quota across all sales channels
Standard functionality for a separate sales quota across all sales channels, which is decremented independently of the imported stock level. This would allow better control of limited-quantity sales campaigns for specific products.
1 vote -
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.
9 votes -
Create test environments securely and easily
Initial Situation:
Over the past few months, more than 100 support tickets have been received regarding test environments where the live shop and the test shop share the same shop ID. This can negatively impact apps and connected services.The current documentation outlines several manual approaches—such as copying files and databases, modifying environment variables and sales channel domains, or setting up a local environment—and also mentions the "staging mode" available from Shopware version 6.6.1.0 onwards. Consequently, it is not always clear to customers which method is appropriate for their specific use case or which steps are strictly necessary. Furthermore, the currently official documentation often leads to the aforementioned conflicts, resulting in a significant additional workload for all parties involved.
Proposal:
Shopware should offer a guided process for creating a test environment. This could take the form of a wizard within the administration interface, an official service, or a Shopware extension that leads customers through the setup and automatically handles critical steps.Specifically, the process should:
- ensure a unique, distinct Shop ID for the test environment,
- correctly configure the necessary settings and domains,
- highlight potential implications for apps, services, and licenses,
- verify that the live and test environments are properly separated before completion,
- provide steps tailored to the specific hosting and installation type.Benefits:
A standardized process would simplify setup for customers and reduce common sources of error associated with manual copying. At the same time, it could lead to a decrease in support requests and recurring issues related to duplicate Shop IDs.As a first step, it should be investigated whether the existing procedure is indeed the root cause of duplicate Shop IDs and which types of setups are most frequently affected. Based on these findings, a secure, essential process could be defined and subsequently implemented as a guided solution.
Initial Situation:
Over the past few months, more than 100 support tickets have been received regarding test environments where the live shop and the test shop share the same shop ID. This can negatively impact apps and connected services.The current documentation outlines several manual approaches—such as copying files and databases, modifying environment variables and sales channel domains, or setting up a local environment—and also mentions the "staging mode" available from Shopware version 6.6.1.0 onwards. Consequently, it is not always clear to customers which method is appropriate for their specific use case or which steps are strictly necessary. Furthermore, the…
1 vote -
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 -
Make “Show matching variants grouped” disabled by default or configurable
When creating a new dynamic product group in Shopware 6, the option “Show matching variants grouped” is currently enabled by default.
It should either be disabled by default or there should be a global configuration option to define whether this setting is enabled or disabled by default for newly created dynamic product groups.
This would prevent repetitive manual adjustments and allow merchants to control the default behavior according to their needs.
1 vote -
Länderauswahl im Checkout für digitale und physische Produkte getrennt steuern
aktuell lassen sich die im Checkout verfügbaren Länder pro Verkaufskanal festlegen. Wäre es möglich, diese Einstellung für digitale und physische Produkte getrennt zu steuern?
Physische Waren können oft nicht in alle Länder geliefert werden oder verursachen hohe Versandkosten. Digitale Produkte hingegen lassen sich weltweit verkaufen.
At present, it is possible to specify which countries are available at checkout for each sales channel. Would it be possible to control this setting separately for digital and physical products?
Physical goods often cannot be delivered to all countries or incur high delivery costs. Digital products, on the other hand, can be sold worldwide.
1 vote -
Kundenspezifische Preise im admin / Customer specific pricing in admin
DE:
Kundenspezifische Preise sollte in Kunden > Übersicht > Kunde > neuer Reiter > Kundenspezifische Preise
einsehbar sein.Felder:
Suchfeld, welches nach Name und SKU suchen kann
SKU | Produktname | Nettopreis | Bruttopreis
Docu
https://docs.shopware.com/de/shopware-6-de/erweiterungen/kundenspezifische-preiseHinweis: es geht um die Preise die per API bei der Beyond Edition eingespielt werden und nicht B2B component individual-pricing
https://docs.shopware.com/en/shopware-6-en/commercial-features/b2b-components?category=shopware-6-en/features/commercial#individual-pricingEN:
Customer-specific prices should be visible under Customers > Overview > Customer > New Tab > Customer-specific prices.
Fields:
Search field (searching by name and SKU)
SKU | Product Name | Net Price | Gross Price
Documentation
https://docs.shopware.com/en/shopware-6-en/extensions/customer-specific-pricingNote: This refers to the prices imported via API for the Beyond Edition, not the B2B component for individual pricing.
https://docs.shopware.com/en/shopware-6-en/commercial-features/b2b-components?category=shopware-6-en/features/commercial#individual-pricingDE:
Kundenspezifische Preise sollte in Kunden > Übersicht > Kunde > neuer Reiter > Kundenspezifische Preise
einsehbar sein.Felder:
Suchfeld, welches nach Name und SKU suchen kann
SKU | Produktname | Nettopreis | Bruttopreis
Docu
https://docs.shopware.com/de/shopware-6-de/erweiterungen/kundenspezifische-preiseHinweis: es geht um die Preise die per API bei der Beyond Edition eingespielt werden und nicht B2B component individual-pricing
https://docs.shopware.com/en/shopware-6-en/commercial-features/b2b-components?category=shopware-6-en/features/commercial#individual-pricingEN:
Customer-specific prices should be visible under Customers > Overview > Customer > New Tab > Customer-specific prices.
Fields:
Search field (searching by name and SKU)
SKU | Product Name | Net Price | Gross Price
Documentation
https://docs.shopware.com/en/shopware-6-en/extensions/customer-specific-pricingNote: This refers to the…
2 votes -
Show attributes and properties in Quick Search for items without variants
In Quick Search, attributes and properties are already displayed on the right for items with variants. This information is currently unavailable for items without variants.
Please enable attributes and properties to be displayed on the right for items without variants as well, following the same presentation used for items with variants.
Benefit:
This additional information would make it easier to distinguish between similar items and find the right item more quickly.Suggested implementation:
Display the existing attributes and properties of items without variants in the results view, preferably using the same format as for items with variants.1 vote -
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 -
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…
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.
-
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.
-
Make inherited objects scrollable/inspectable
In Categories > Layout:
eventhough a layout-section (for example a text) might be inherited from the assigned layout, make it scrollable so i can look through the text and dont need to go into the category itself.1 vote -
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.
-
Agentic Commerce - Beta Release
The Agentic Commerce plugin enables merchants to distribute products through OpenAI and Google product feeds while supporting emerging standards such as UCP (Universal Commerce Protocol). It provides a dedicated sales channel for AI-driven commerce and helps merchants prepare for the next generation of product discovery and purchasing experiences.
-> Help Shape the Future of Agentic Commerce
AI-powered commerce is evolving rapidly, and we're continuously expanding the capabilities of Agentic Commerce.
Do you have ideas, feature requests, or suggestions for improvement? We'd love to hear your feedback. Share your thoughts on UserVoice and help us shape the future of AI-powered commerce in Shopware.
The Agentic Commerce plugin enables merchants to distribute products through OpenAI and Google product feeds while supporting emerging standards such as UCP (Universal Commerce Protocol). It provides a dedicated sales channel for AI-driven commerce and helps merchants prepare for the next generation of product discovery and purchasing experiences.
-> Help Shape the Future of Agentic Commerce
AI-powered commerce is evolving rapidly, and we're continuously expanding the capabilities of Agentic Commerce.
Do you have ideas, feature requests, or suggestions for improvement? We'd love to hear your feedback. Share your thoughts on UserVoice and help us shape the future of AI-powered commerce…
2 votes -
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.
-
Typographically correct quotation marks in product description
The quotation marks around the product name in the product description are typographically incorrect.
Since these are hard-coded in the TWIG file component/product/description.html.twig, one suggestion would be to insert a new snippet here that renders the name with the appropriate quotation marks depending on the language.For example:
<h2 class="product-detail-description-title">
{{ 'detail.descriptionTitle'|trans|sw_sanitize }} {{ "custom.quotedName"|trans({'%name%': product.translated.name}) }}
</h2>Snippet custom.quotedName
e.g. DE: „%name%“ EN: “%name%” FR: «%name%»1 vote
- Don't see your idea?