- or
No existing idea results
- ~ No ideas found ~
343 results found
-
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…8 votes -
Cloud: Storing individual files in the root directory
Cloud customers frequently need a simple way to place files in the root directory. In most cases, this is required for website authentication with Google. Currently, the available methods for customers are quite complicated (e.g., creating a custom app). A more user-friendly solution should be provided.
2 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 displayed. This is decided by Shopware in the core."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 -
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.
4 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 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.
-
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.
-
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 -
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 -
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 -
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.
- Don't see your idea?