1488 results found
-
Rulebuiler condition which detects the change of payment method
Condition in the rulebuiler which determines the (non-balanced) change of payment method.
Something like: Used payment method was > Incoice > is now > prepayment
For example, in the flow builder you could influence the mails that are sent when the status changes, so that a distinction is made between manual switching (by the admin) or automated switching (by payment integrations) and the payment method change by the customer in the frontend.
Since the order also reaches the status “canceled” when the customer changes the payment method in the frontend, these mails could be prevented here, as they can be…
2 votes -
Line item rule amount of products within a dynamic product group for discounts
Currently it is not possible to add a rule to a discount that checks the amount of products per lineitem and additonal conditions.
e. g.
You want to ensure that only products with a tag and an amount of 10/above is in the cart. This has to be checked by lineitem, so products and variants that include the TAG but have only an amount of 1 in the cart do not apply to the discount.
if you use the condition "amount of products" it is related to all itemlines of the cart.
If you choose "Item quantity" it matches, but…
1 vote -
Automatically include vouchers in returns management
Currently, if the vouchers are not taken into account when an order is placed, if an item is returned via Return Management.
Although the amount of the return can be adjusted and the value including the voucher is suggested, it is not applied automatically.
An option for automation would be useful here.3 votes -
Cloud: Better debugging in case of error
There is no way for a SaaS user to find error in theme or extensions, that are in use on the SaaS environment. It would be helpful to increase the gainable information while debugging.
3 votes -
Add filters for Exports according to Shopware 5
Many customers miss the filter functionality they know from Shopware 5 especially because the AI features do not work reliably.
For example the export of orders is often needed for a year or two and the amount of data grows very quickly.8 votes -
Better filter options within e.g. customer and order overview
If you work with the customer and order overview on a daily basis, this quickly leads to frustration.
For example, the number per page cannot be set and is far too low. This should be 100 or 200. Otherwise the unnecessary effort is too high and the work quickly becomes frustrating.
Also, the filter or listing is often reset when changing pages. This also takes an incredible amount of time.
We would like to see better handling here.
2 votes -
Further evaluation of the customer search
There should be an evaluation of customer search queries within the Shopware search.
This means that the search can be adapted to customers in ever greater detail. This is requested time and again by large customers.
2 votes -
Improve UI and Logic for Postal Code Validation and Advanced Validation Rules
he current UI for the Postal Code settings is not intuitive and may confuse users. The "Advanced Validation Rules" option can only be enabled after enabling "Postal Code Validation," but there is no clear indication that these options are linked. Additionally, there is no visibility into which validation rules apply when enabling "Postal Code Validation."
Problems Identified:
Lack of clear dependency between "Postal Code Validation" and "Advanced Validation Rules."
No information on which postal code validation rules are applied by default.
Unclear if "Postal Code Required" influences the validation settings.
2 votes -
Optimierung der Dropdown Menüs (z.b. Verkaufskanal -> Auswahl Länder)
The selection of values within the dropdown menus in Shopware Admin is very error-prone.
For example, if additional countries are to be added or removed within the sales channel, the menu only ever shows 25 entries and each entry has to be clicked individually. This is very error-prone and you should also be able to select/deselect “all” entries.
This would make it easier for large customers to use the Admin, as the problem occurs at various points in the Admin.
2 votes -
Unlinking properties should be bound to a detailed privilege.
It is currently not possible to delete properties via the small X (see screenshot) using a detailed privilege.
The deletion is currently bound to the technical privilege “product.deleter”, which cannot be found in the admin and can only be given via API/DB or the general deletion permission for products.
Using "Configure properties", you can also delete the properties via a detailed privilege, but it should also be possible to simply delete properties using the small X.
1 vote -
Copying CMS content - reusable elements
It would be nice to have the option of copying elements from the shopping experiences and using them in a different place.
Example: We have the "XY" section in the start page - this should be filled and customised once and then copied in the next step and used in another page.
27 votes -
Product overview with additional filter options on variant level
The filtering at the product level under "Catalog > Products" unfortunately only works at the master/parent product level. This option is not conducive for the following reason:
All of our products have variants and we maintain the images only at the variant level. The same applies to the product status active/inactive. Text, on the other hand, is always maintained at the master/parent product level.
This approach is deliberately chosen because variants can have different images or individual variants can be inactive.It is now important for us to be able to locate the following at the variant level:
- Product active,…
13 votes -
replace Tiny Slider as the default slider
The current default slider integration with tinyslider seems not be maintained anymore.
It would be good to switch to a maintained slider lib again as tinyslider has a multitude of issues, espacially with accessibilty and it is not really customizable.4 votes -
SAML/OAuth SSO support
In discussions with large and important customers, SAML/OAuth SSO support is repeatedly asked for, as this is sometimes required/prescribed in large companies or corperations.
In view of large companies and corporations, there should be an implementation here.
2 votes -
Adding Companies as customers instead of Users
For B2B shops, often Users are irrelevant, since companies are the customers in that cases. It would be nice, if you could create customers not only on a user level, but also on company level.
Currently Users are used as placeholders, which still requires information such as first and lastname, which does not make sense for a company. This placeholder user also gets a placeholder first- and lastname which then pops up in the storefront everywhere.
2 votes -
Differentiation between manufacturer and brand
Currently you can only specify the manufacturer of a product. However, the manufacturer is not automatically the brand of the product, so it would be nice if there was an extra field here that also allows you to specify the brand.
1 vote -
Allow orders to be moved between customers (i.e. reassign guest order to customer account)
It would be useful to move orders from one customer account to another. Currently guest orders remain assigned to the guest account, even when a customer registers afterwards. Thus they cannot see the order status. Also for other scenarios (like duplicate accounts), moving orders would be useful.
Es wäre hilfreich, Bestellungen von einem Kundenkonto auf ein anderes verschieben zu können. Derzeit bleiben Gastbestellungen dem Gastkonto zugewiesen, auch wenn sich ein Kunde später registriert. Somit kann er den Status der Bestellung nicht sehen. Auch für andere Szenarien (z. B. doppelte Konten) wäre das Verschieben von Bestellungen nützlich.
5 votes -
Long category names go beyond the grid.
If the category names are slightly longer, they can no longer be displayed in the fixed grid, and a scrollbar is created. As a result, you always have to scroll first to access the three dots.
3 votes -
Offers: Reservation of articles
To ensure that items listed in an offer are not sold out in the meantime, these items should be automatically reserved by the system.
3 votes -
Delivery time display: Option to exclude specific days
It would be a nice option to have the possibility to exclude Sundays for example from the delivery time calculation. Of course, we can already cover this with the delivery time SPAN and NAME of the delivery method, saying 1-3 WORKdays or something.
But it would be a nice QoL feature, especially for customers, if the calculation took days we defined into the equation and could thus be more specific.
If we wanted to take this a step further, we could also offer a calendar where we can configure holidays and whatnot.
And if we want to take this to…
22 votes
- Don't see your idea?