- or
No existing idea results
- ~ No ideas found ~
1498 results found
-
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 -
Dynamic pricing or promotions based on affiliate code
Currently, Shopware does not allow evaluating the affiliate code via the rule builder prior to ordering or registering a new customer account, making it impossible to have affiliate-specific pricing or discounts based on those affiliate codes. This functionality should be added to the rule builder.
3 votes -
Quotes: Shipping and payment
For offers, the shipping method and payment method used cannot be changed or edited. A shipping method and a payment method are still specified. It should be possible to change this data when editing.
Bei Angeboten kann die verwendete Versandart und die Zahlungsart nicht geändert oder bearbeitet werden. Deonnoch wid eine Versandart und eine Zahlungsmethode angegeben. Bei der Bearbeitung sollte die Möglichkeit bestehen diese Daten zu ändern.
4 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…
1 vote -
Add hreflang support across multiple sales channels
Currently hreflang only applies to different domains within one sales channel. It would be useful to be able to define other languages for hreflang tags across multiple sales channels (i.e. separate sales channels for EU and US, linking to each other)
7 votes -
Delivery time as Rule Builder condition
The Rule Builder is missing the option to use the delivery time of a product as a condition. This would be a useful improvement, for example to use this as an availability rule for shipping methods.
7 votes -
Logging of running flows
For monitoring the system and testing flows, it is extremely important that there is logging in the admin area.
The following information is important for logging:
- When did the flow run?
- Which trigger was activated?
- Which data was fed into the flow?
- Which data was decisive for the conditions?Zapier provides excellent logging for such systems.
2 votes -
Show detailed error message why a voucher could not be redeemed.
Regardless of whether a promotion is no longer valid (end date reached) or the maximum number of redemptions has already been reached, the error message in the offCanvas is always the same and therefore confusing for the customer.
Currently, the content from snippet ‘checkout.promotion-not-found’ is displayed per se.
It would be desirable if the exact reason why the voucher code cannot be used was given in relation to the above examples, i.e.
- ‘Promotion is no longer valid / expired’
- ‘Maximum number of redemptions already reached....’
5 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 vote -
Hide empty entities in search results
Add an option that allows to hide empty entities in search results.
One example here would be manufacturers that are not being assigned to any products in the given sales channel.
2 votes -
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 vote -
Image keyword assistant multi-language support
It should be possible to generate the alt texts for multi-language shops in the respective language.
5 votes -
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 vote -
Shopware Publisher: Creates a possibility to restore old versions
Creates a way to restore old versions within Shopware Publisher
5 votes -
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.
80 votes -
Export SEO route by product main category
Several times it had been asked to send a TWIG variable for exporting the path of the main category, that is defined via catalogues > products > SEO and can be found if a special sales channel was selected in section seo-urls.
Currently the sales channels for product comparision (product export) or Social Shopping have no working variable to read the main category's seo-route.
Please check if it can be added to provide an easier export.
3 votes -
Integration of background videos in worlds of experience
It is currently not possible to integrate a background video - comparable to the display on https://scd.shopware.com/ - natively into a CMS page with the standard experience world elements in Shopware 6. Although video and HTML elements exist, these do not allow a combination of background video and overlaying content (e.g. text, buttons, HTML block).
The integration of a video as a background is a common design element in modern web design and is used in particular for landing pages, campaigns or emotional brand appearances. The current CMS structure only allows this with considerable technical effort (e.g. through individual CMS components, theme customizations or third-party plugins). This significantly restricts the creative and design freedom of editors.
Proposal for implementation:
- Expansion of the worlds of experience to include a new standard element with the following features:
- Option to integrate a video (MP4 or external source) as a background video
- Option to activate autoplay, mute, loop and poster image
- Overlaying content layer with configurable slots for:
- Text (WYSIWYG)
- HTML editor
- buttons
- Full responsiveness (mobile optimization, optional fallback image)
- Optional transparency or color overlay settings for better readabilityBenefits:
- Greater visual design options without technical hurdles
- Enables conversion-oriented landing pages directly in the Shopware backend
- Improves usability and reduces dependency on third-party developers or plugins
- Contributes to branding through modern visualsIt is currently not possible to integrate a background video - comparable to the display on https://scd.shopware.com/ - natively into a CMS page with the standard experience world elements in Shopware 6. Although video and HTML elements exist, these do not allow a combination of background video and overlaying content (e.g. text, buttons, HTML block).
The integration of a video as a background is a common design element in modern web design and is used in particular for landing pages, campaigns or emotional brand appearances. The current CMS structure only allows this with considerable technical effort (e.g. through individual CMS…
3 votes -
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 vote -
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 vote -
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
- Don't see your idea?