- or
354 results found
-
Placeholder system for properties & custom fields
The desired function allows the use of placeholders such as
{{ product.properties.<name> }} or
{{ product.customFields.<fieldName> }}
in various product fields. These should then be automatically replaced with the respective values.
✅ Potential benefits for retailers:
- Reduced manual maintenance effort
- Consistent and accurate product data
- Particularly helpful with many variants or large catalogs
- Works in the cloud without individual template adjustments2 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.
-
B2B Components: Approval Rules: Add organization unit option
Currently you can only create approval rules that are active for all organization units. It would be great if we could also create approval rules specifically for an organization unit, in case I want different conditions to be applied for different org units.
2 votes -
Allow setting time zone for logs
Add the possibility to modify the time zone for the log files. This would make it easier to parse them, both by reading and via scripts or other means.
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.
-
Search Result - Show Cheapest Variant
Currently, when searching for the parent product number, the next available variant based on the product number suffix (12345.1) is displayed in the search results.
It would be good if we could influence the search results via settings and, for example, always display the cheapest (available) variant within the search results.
1 voteGathering 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 order creation: Allow guests
Currently, it is not possible to create an order via our Admin unless the customer is registered. This presents an annoyance because it is still somewhat customary in some industries to place orders by calling a customer support hotline or something along those lines.
As it is now, when calling a merchant running a Shopware 6 shop, we first have to enter the customer menu, register a new customer (and ask our customer all their data) and THEN do the same thing after switching menus to orders again.
It would be a neat QoL feature to be able to do both in one step. Allow us to place a guest order via our Admin which only includes the absolute bare minimum of required information when it comes to customer data with the rest being optional.
Currently, it is not possible to create an order via our Admin unless the customer is registered. This presents an annoyance because it is still somewhat customary in some industries to place orders by calling a customer support hotline or something along those lines.
As it is now, when calling a merchant running a Shopware 6 shop, we first have to enter the customer menu, register a new customer (and ask our customer all their data) and THEN do the same thing after switching menus to orders again.
It would be a neat QoL feature to be able to do…
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.
-
Improve export of products - better handling of variant data
The current situation is, that inherited field stay empty when a product export is done. This makes it more difficult to exchange data with other software or just to use spreadsheets to gain special information.
It's a topic that currently needs a workaround for many customers. Perhaps it could be possible to create several export profiles: one for exchange and editing data just for Shopware and one for external exchange.
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.
-
Show cms layout "source"
When I assign a layout to a category/product, all settings from the “global” layout are initially applied. However, this only applies until I make changes within the category/product via the “Layout” tab—which therefore only apply to this entity.
This often leads to confusion if changes are made to the “global” layout at a later date and these no longer affect the specific category or product. If the above scenario occurs, I still have to make the changes at the category/product level for them to be visible.
At this point, we need a note in the “Layout” tab that indicates that changes have already been made at the category/product level and that any changes to settings (filters, etc.) at the global layout level will no longer automatically apply to these.
When I assign a layout to a category/product, all settings from the “global” layout are initially applied. However, this only applies until I make changes within the category/product via the “Layout” tab—which therefore only apply to this entity.
This often leads to confusion if changes are made to the “global” layout at a later date and these no longer affect the specific category or product. If the above scenario occurs, I still have to make the changes at the category/product level for them to be visible.
At this point, we need a note in the “Layout” tab that indicates that…
1 voteGathering 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.
-
The chosen delivery country of shopping basket should be preselected for customer registration
As a new customer, it would be nice if the delivery country selected in the shopping basket was also preselected on the customer registration page.
Currently, I go to the shop, add an item to my shopping basket, select France as the delivery country (also to see the shipping costs for that country), then click on "Checkout" and am taken to the "Login/Registration page". There, Germany is set as the country again and I have to select "France" once more.
Not really user-friendly!
Als neuer Kunde wäre es schön, wenn das im Warenkorb ausgewählte Lieferland auf der Kundenregistrierungsseite auch vorausgewählt ist.
Aktuell komme ich in den Shop, lege einen Artikel in den Warenkorb, wähle dort z.B. Frankreich als Lieferland aus (auch um mir die für dieses Land gültigen Versandkosten anzeigen zu lassen), klicke dann auf "Zur Kasse" und lande auf der "Anmelde / Registrierungsseite". Dort ist dann wieder Deutschland als Land eingestellt und ich muss erneut "Frankreich" auswählen.
Nicht wirklich user-friendly!
As a new customer, it would be nice if the delivery country selected in the shopping basket was also preselected on the customer registration page.
Currently, I go to the shop, add an item to my shopping basket, select France as the delivery country (also to see the shipping costs for that country), then click on "Checkout" and am taken to the "Login/Registration page". There, Germany is set as the country again and I have to select "France" once more.
Not really user-friendly!
Als neuer Kunde wäre es schön, wenn das im Warenkorb ausgewählte Lieferland auf der Kundenregistrierungsseite auch vorausgewählt…
1 voteGathering 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.
-
Import / Export Profiles - technical names make identification more difficult
Since Shopware 6.7 (?) the import / export profiles use technical names. The customer's labelling has been totally erased, although it's still available in the translation table.
Of course the customer can now overwrite the new name default_product-copy-1762844593373 for duplicated profiles. But usually these profiles were marked like "Import prices manufacturer1", "Import prices manufacturer2" and so on.
Means the customer has to check all their profiles correct the technical name, which seems to be the same for any administration language. Please add the labeling again.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.
-
Display multiple stocks on shop frontend
The ability to display multiple inventory stock level quantities per product in the shop frontend.
1 voteGathering 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 multiple orders to be created from a single quote
Currently, only a single order can be created from a quote.
It should be possible to allow multiple orders to be generated from the same quote.Ideally, this behavior should be configurable on a per-quote basis during the creation or editing of a quote. For example, it should be possible to define whether only one order or multiple orders are allowed, and optionally to limit the maximum number of orders that can be created from a quote.
This would provide greater flexibility for B2B use cases where a single quote may be fulfilled through multiple partial or separate orders.
1 voteGathering 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.
-
Indication of orders created from quotes
It should be clearly visible whether an order was created from a quote.
Ideally, this information should be displayed directly within the order overview to allow quick identification.
If displaying this information in the order overview is not feasible, it should alternatively be available within the order details, for example via a dedicated field or a custom field.This improves transparency and makes it easier for users to distinguish regular orders from those originating from quotes, especially in B2B workflows.
1 voteGathering 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.
-
Add notifications for new comments on quotes
Currently, new customer comments on offers are not actively communicated. An email or in-administration notification would ensure timely awareness and faster responses.
1 voteGathering 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.
-
Replacing the sw-text-editor editor
It would be a great Idea to schedule the replacement of the sw-text-editor by a better editor like Tiptap as it is mentioned in the architectural desicion report: https://developer.shopware.com/docs/resources/references/adr/2023-03-27-admin-text-editor-evaluation.html
75 votes -
Cloud: Enabling the editing of template files via the admin panel
In cloud environments, customers are increasingly reaching their limits because manually customizing template files (e.g., forms) is not possible. Therefore, the admin panel should offer the ability to edit template files.
Extensions in the Shopware Store demonstrate that this is technically feasible.
Such a feature would significantly reduce the limitations within the cloud and further increase user adoption.
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.
-
Possibility to negate promotion combination exclusion or add a seperate inclusion
Currently I only have 2 options: "Prevent combination with other promotions" or "Do not combine with".
When I have e.g. 2 promotions which should work together but not with other promotions I would have to add all other promotions to the "Do not combine with" field which can be tediuos when having a lot of individual promotions.I would be nice to have either an option to negate the "Do not combine with" condition making it an inclusion or having a seperate inclusion field where both, exclusion and inclusion can be combined.
1 voteGathering 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.
-
Output the favicon of the sales channel for Google as well
Although other favicons are stored in the theme, Google seems to favour the favicon.ico in the public folder that displays your logo.
In fact, I have noticed this in several Shopware 6 shops in Google search results.
If you only have one public sales channel, you can simply replace the favicon.png with your own, but we have four sales channels with different favicons.
In this case, you have to set up redirects.
It would be better if the corresponding favicons of the respective shops were actually used and displayed.
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.
-
Product delivery time vs. shipping method delivery time
The delivery time of a product overwrites the delivery time of the shipping method. However, this is not helpful if the delivery time of the shipping method exceeds the delivery time of the product, as a delivery time that is not possible is then displayed.
It would be helpful if the higher delivery time is used in each case.14 votes -
Filters for Flow Builder
For bigger lists of any entity, it is super important to have filters in order to find efficiently what you are looking for. We have filters for the Products, Customers, Rule Builder overviews and probably in many other menus as well.
There for we should most definitely also have this kind of filtering also for the Flow Builder overview.
Finding the flow you are looking for only with the search is a pain. Try to search for the flow "Order placed". Since the string "order" is part in 90% of all flows out of the box, you will not be able to find it but will need to filter manually through the list of flows again.
For bigger lists of any entity, it is super important to have filters in order to find efficiently what you are looking for. We have filters for the Products, Customers, Rule Builder overviews and probably in many other menus as well.
There for we should most definitely also have this kind of filtering also for the Flow Builder overview.
Finding the flow you are looking for only with the search is a pain. Try to search for the flow "Order placed". Since the string "order" is part in 90% of all flows out of the box, you will not be…
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.
-
Improved coupon code generation: Reuse of patterns & exclusion of certain characters
Problem:
Currently, coupon templates (e.g., SHOP-{random}) can only be used once. If the same template is used in a subsequent campaign, Shopware prevents its creation with a message indicating that the template already exists.Furthermore, it is not possible to exclude specific characters from the random code, which can lead to potential confusion (e.g., I vs. l or 0 vs. O).
Solution/Request:
A pattern may be used multiple times as long as no duplicates are created in the generated codes.During generation, the system only checks whether a code already exists, not whether the pattern has already been used.
Optional configurable exclusion list for specific characters.
Relevance increases with the growing number of parallel voucher campaigns (marketing, promotion, campaign management). Customers with f.e. 400+ promotions are having a very difficult time due to the current situation.
Problem:
Currently, coupon templates (e.g., SHOP-{random}) can only be used once. If the same template is used in a subsequent campaign, Shopware prevents its creation with a message indicating that the template already exists.Furthermore, it is not possible to exclude specific characters from the random code, which can lead to potential confusion (e.g., I vs. l or 0 vs. O).
Solution/Request:
A pattern may be used multiple times as long as no duplicates are created in the generated codes.During generation, the system only checks whether a code already exists, not whether the pattern has already been used.
Optional…
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?