- or
334 results found
-
Improve Safety and Flexibility for Promotion Code Configuration
Context
In the current version of Shopware 6, when creating a new promotion, the field “Promotion code type” is automatically set to “No promotion code required”.
This UX choice was made intentionally to simplify creation of general cart-level discounts, which are the most common use case.However, this default selection can lead to unintended activation of promotions when a user forgets to change the option to “Fixed” or “Individual promotion code.”
In such cases, discounts may be applied to all customers instead of a limited target group, which can cause serious financial and operational issues.Problem
Users may overlook that a promotion is configured without a code, because “No code required” is preselected
This can unintentionally trigger discounts for all customers
Currently, there is no system-level control or "safeguard" to prevent this
Proposed Solutions
We suggest adding configurability or safety mechanisms for the “Promotion code type” field to reduce user errors and increase administrative control.
There are three possible options that could be implemented independently or in combination:
Require explicit selection (no default preselection)
Remove the preselected value “No promotion code required.”System-wide default configuration
Add a configuration setting in system or admin preferences allowing administrators to define the default for new promotionsOptional warning before activation
Display a confirmation or warning when activating a promotion that has no promotion code set.
Example message:
“This promotion will be applied to all customers because no promotion code is required. Are you sure you want to activate it?”
Expected Benefits
Prevents accidental large-scale discount activations
Improves administrative control and safety
Reduces support incidents and potential financial losses
Aligns the promotion workflow with enterprise-level requirements
Context
In the current version of Shopware 6, when creating a new promotion, the field “Promotion code type” is automatically set to “No promotion code required”.
This UX choice was made intentionally to simplify creation of general cart-level discounts, which are the most common use case.However, this default selection can lead to unintended activation of promotions when a user forgets to change the option to “Fixed” or “Individual promotion code.”
In such cases, discounts may be applied to all customers instead of a limited target group, which can cause serious financial and operational issues.Problem
Users may overlook 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.
-
Optionally, the net prices should remain the same, even if there are other taxes in other countries.
Currently, the net price changes if you offer products in other countries with different taxes. The gross price remains the same.
There should be an option to decide for yourself whether the net price remains the same with a variable gross price, or whether the gross price remains the same with a variable net price.
90 votes -
Revision of list prices
The implementation of strikethrough prices has been poorly and even incompletely implemented. In the ITA shop, we don't have a proper way to display a sale category, as the default function here also goes to the first tab.
And independently, the in-house solution/rule for discounted items in the dynamic product groups is incredibly slow.
The host once sent me the Slow Query. If printed out, I could wallpaper at least half the room (high ceilings in an old Berlin building).
So please take a look at the topic. Anyone who has multiple sales channels and different prices within them will wish they were back in Shopware 5. It was all easy peasy and performant.
The implementation of strikethrough prices has been poorly and even incompletely implemented. In the ITA shop, we don't have a proper way to display a sale category, as the default function here also goes to the first tab.
And independently, the in-house solution/rule for discounted items in the dynamic product groups is incredibly slow.
The host once sent me the Slow Query. If printed out, I could wallpaper at least half the room (high ceilings in an old Berlin building).
So please take a look at the topic. Anyone who has multiple sales channels and different prices within them will…
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.
-
Backend: Product Filtering and Customization - Filter Value
The product filters section needs more customization and can be optimized.
Here is an example of the main shortcomings:
1 - Allow the addition of custom fields and properties.
2 - Allow the use of operators such as: "Like," "=", "And," "Or," "Starts with," etc.
3 - Allow filtering by entering multiple values in a search field.8 votes -
"not specified" salutation handling
This is handled rather inconsistently in Shopware. In some but not all places, if you leave out the salutation, Shopware searches the database for the "not_specified" entry that comes with the installation and inserts it if found. If also sometimes inserts it just for display in the Administration if the real salutation reference is null, so you wouldn't even know the real value without looking directly into the database, but again, not always.
Crucially, that "not_specified" entry can be changed and deleted at will, so there's no guaranteed meaning behind it.
Also, sometimes like in the contact form the salutation is randomly required. You can delete it for addresses and the database has a default value of null, but then there is a non-configurable validator that won't let you through the checkout process if no salutation is given. And again, "given" can just mean that you set the "not_specified" salutation, which can have any meaning you assign to it.
This is an intransparent mess and should be changed. The very legality of requiring a salutation is now even in question. Just allow null values for all salutations in the application, it's already allowed in the DB structure, stop enforcing it in random places without a way to turn it off, and make the display name of a "null" salutation translatable via config.
This is handled rather inconsistently in Shopware. In some but not all places, if you leave out the salutation, Shopware searches the database for the "not_specified" entry that comes with the installation and inserts it if found. If also sometimes inserts it just for display in the Administration if the real salutation reference is null, so you wouldn't even know the real value without looking directly into the database, but again, not always.
Crucially, that "not_specified" entry can be changed and deleted at will, so there's no guaranteed meaning behind it.
Also, sometimes like in the contact form the salutation…
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.
-
Display order details clearly on one page instead of using tabs (similar to Shopware 6.4)
The details of an order should be clearly displayed on one page. Unfortunately, the details are currently spread across several tabs.
Clicking around, loading the various tabs and changing details takes longer than if everything could be done on one page.
Shopware 6.4 is clearer than Shopware 6.7.
Please change this.
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 selection field in user profile settings for measurement preferences
When a user changes the unit in a product, this change is applied at the user level and stored in the database in the
user_configtable with the keymeasurement.preferenceUnit. If there is already a dedicated entry for this in the database, it would be nice if the selection could be changed directly in the user profile.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.
-
Bitte in der Anzahl der Produktverkäufe die Produktnummer mit anzeigen (Artikelnummer)
Es wäre sehr hilfreich, die Produktnummer in der Liste der Produktverkäufe sehen zu können.
Bitte blenden Sie die Produktnummer im Analytics Plugin mit ein. (Artikelnummer)Vielen Dank
11 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.
-
organisation unit should be defined in new emplyee
As the organisation units are available with version 6.7, it should be possible to map the unit for new employees.
Currently only the role can be set.
Employees can only be mapped within the organisation unit when the employee is active (invitation link is clicked within the 2 hours reaction time).
If organisation units are active in the customer and units are defined, it should be possible to map it within the employee mask. For existing and new employees.
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 empty alt tags to untagged thumbnails in image galleries
Untagged images in the gallery get an empty alt tag when not tagged, which is a good default behaviour. The thumbnails in the gallery also need this. Currently, untagged images don't get any alt tag at all. This is an accessibility problem!
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.
-
CAPTCHAs: Different keys per sales channel
You can currently only store one key pair per CAPTCHA in the Basic information. If you change the sales channel in the
Basic information and enter another key, the previous one will be overwritten.9 votes -
Image keyword assistant for logos
The image keyword assistant should be able to recognize well-known logos, not just objects.
For example, when you upload the Shopware logo, only “Logo” appears as the alt text. When you upload Facebook logo, “Symbol, sign, cross” appears, which isn't really accurate, and nothing appears at all for Instagram logo.
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.
-
delivery time as variable for email templates
enable display of delivery time per item within the e-mail template via variable
9 votes -
Set product sorting permanently.
The sorting under Catalogs - Products cannot currently be changed permanently. For example, if sorting by the creation date is desired, it must always be triggered manually and cannot be defined per user.
13 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 delete documents
It should be possible to delete documents, especially invoices.
Several reasons why it should be possible are listed here: https://forum.shopware.com/t/loeschen-von-dokumenten-nicht-mehr-moeglich/97011
Without this function you cannot really test the invoice generation on a production system and you cannot change false invoices that customers have never received.
Due to a bug multiple invoices can be created for the same order with the only difference of the invoice number. Currently you cannot delete the redundant invoice.
56 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.
-
UI / UX Improvements on Data Mapping in Shopping Experiences
Please add pagination and search field to the data mapping (Datenzuordnung) list in CMS elements.
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.
-
Multi Inventory - Adding stock redirects annoyingly
When working with the Shopwares Multi Inventory feature and wanting to assign stock to products, there is an annoying redirect to the first Warehouse Group after every update of stock in another Warehouse group.
I have recorded this to showcase:
https://www.awesomescreenshot.com/video/44724575?key=28cd44e9f3bd2e226b5b66e013185d70As you can see in the video, whenever I apply changes to warehouse group 2 & 3, you get redirected to the group 1 again, even if I might still need more changes applied in those previous groups. This interrupts and slows down the process, because I have to navigate back to either group 2 & 3 again.
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 "Show password" button to registration form and account profile
It's currently not possible to see the password you've entered when registering or changing your existing password in your account profile
6 votes -
Replace Webpack with Vite in Shopware Administration Panel
Switching from Webpack to Vite in the Shopware Administration Panel would significantly improve development speed and the developer experience. Vite offers faster builds, better HMR (Hot Module Replacement), and modern JavaScript tooling. Its optimized build process and plugin ecosystem make it a future-proof choice for modern frontend development.
By adopting Vite, Shopware developers would benefit from shorter feedback loops during development and an overall more efficient and enjoyable workflow. Additionally, it aligns Shopware with the latest frontend development trends, ensuring continued relevance and appeal to a broader developer community.
9 votes -
Individual mandatory fields in the components
In Shopware, there are both optional and required fields for the billing address and delivery addresses, where this assignment makes no sense in the B2B sector. A personal contact person is, in most cases, an optional addition in the B2B sector.
The typical billing information for a company address is: Mustermann GmbH Musterweg 1 12345 Musterhausen
Persons are also rarely listed in the delivery addresses. Here, too, it should only be an option. In the delivery addresses, it may be necessary to explicitly list a recipient: Mustermann GmbH, Attn: Marketing Department - Uwe Kleemann, Musterweg 1 12345 Musterhausen.
Currently, the following required fields are available:
First name, Last name, Street and house number, City, Countryand the following
optional
fields: Company, Department, ZIP code, StateThe following distribution would make sense for the B2B sector, and therefore for us:
Required fields:
Company, Street and house number, ZIP code, City, CountryOptional fields:
First name, Last name, Department, StateIn Shopware, there are both optional and required fields for the billing address and delivery addresses, where this assignment makes no sense in the B2B sector. A personal contact person is, in most cases, an optional addition in the B2B sector.
The typical billing information for a company address is: Mustermann GmbH Musterweg 1 12345 Musterhausen
Persons are also rarely listed in the delivery addresses. Here, too, it should only be an option. In the delivery addresses, it may be necessary to explicitly list a recipient: Mustermann GmbH, Attn: Marketing Department - Uwe Kleemann, Musterweg 1 12345 Musterhausen.
Currently, the…
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.
- Don't see your idea?