87 results found
-
More AI with an advisory function
More AI with an advisory function
Admin:
- User logs in and the AI checks e.g. the stock levels of certain products and points this out and suggests a saleFrontend:
- Sorting and categories can be composed individually based on user behavior. No more rigid structure, but an AI evaluation of what might suit the customer. Gamechanger- AI sorting based on prioritized articles and e.g. seasonal conditions. For example, change the display of winter blankets in summer or move them back.
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.
3 votes -
Image keyword assistant for existing images
It should be possible to generate alt texts for existing media using the image keyword assistant.
Currently this only works for newly uploaded images.
3 votes -
Check for Database charset with warning in the admin
Some customers have incorrect charsets running in the background (database). This is normally only noticed when errors actually occur, e.g. during an update.
It would therefore be a great advantage if the charset could be checked in the background and if there was then a message in the admin, for example. This would prevent errors in future updates.1 vote -
Easier process to apply changes from Staging to Live and from Live to staging
Usually, the right way to apply changes is to first test it in your staging system. After the testing is successful, you need to apply the same changes once again in your Live system.
It would be great, if those changes could be synced easily between the two environments, allowing to apply changes from the staging easy and fast also in the live environment.
2 votes -
Handling of category editing improved
Working in the categories with large shops and a nested category structure takes a lot of time and is very cumbersome and tedious. This causes a lot of frustration for large customers.
This is due to the fact that the window with the categories cannot be enlarged, despite the fact that monitors are now large everywhere. The view can only be moved using a bar.
This is not enough for large customers. It must be possible to enlarge the window vertically.
3 votes -
Remove password prompt on "Your profile" edits (Language, Time zone)
When changing language or time zone under “Your profile” one is asked to confirm the current password. This is one of the very few locations where the password is asked for and while it may make sense for e-mail and password changes, language and time zone are more inconsequential (especially compared to what an admin account can do to a shop without ever being asked for a password)
2 votes -
Uninstallation via cli should delete the folder of an uninstalled extension
If an extension is uninstalled via cli, the folder in plugins is not removed. This may lead to incorrect licence warnings. The folder should therefore also be deleted when uninstalling.
2 votes -
Further information on a licence warning
If a licence warning is issued for an extension, only the external IP address is transmitted as the source. If there are 100 shops behind the same IP, the ‘faulty’ shop cannot be found as a result.
More meaningful details should also be transmitted (e.g. shop name, internal IP, unique shop properties).
4 votes -
Whitelist-Based Cache Key Handling for URL Parameters
Currently, Shopware allows excluding certain URL parameters from the cache key to save storage. However, this exclusion list keeps growing, making maintenance cumbersome. Instead of excluding parameters, a whitelist approach could offer more control and efficiency.
Analysis:
I tracked URL parameters in a default Shopware installation—from listing to PDP, filtering, and placing an order. These 19 parameters were captured (more possible):
cluster, keys, language, limit, locale, manufacturer, max-price, min-price, no-aggregations, order, orderId, p, paid, properties, rating, redirected, slots, timezone, searchInstead of maintaining an ever-growing exclusion list, switching to an allowlist approach would ensure that only essential parameters impact the…
2 votes -
List all assignments of a Dynamic Product Group
EN
In the Rule Builder, there is an overview with the assignments for each rule. Such an overview would also be a great addition for the dynamic product groups, because the more product groups are used in categories, product comparisons, cross-selling etc., the more difficult it becomes to determine where a particular product group is used.DE
Im Rule Builder gibt es für jede Regel eine Übersicht mit den Zuordnungen. Eine solche Übersicht wäre auch für die Dynamischen Produktgruppen eine super Ergänzung, denn je mehr Produktgruppen in Kategorien, Producktvergleichn, Cross Sellings etc. zum Einsatz kommen, um so schwieriger wird es…2 votes -
Query data from Shopware Analytics
It would be good if the data from Shopware Analytics could be accessed via the API in order to integrate it into Grafana, for example.
1 vote -
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 -
It should be possible to prevent customers without a Paypal account from buying something via Paypal.
If you enter an email address in the Paypal login window that is not registered with Paypal, you can still be paid via Paypal by direct debit. It should be possible to prevent this.
1 vote -
Rule Builder Rules for tax
There are special cases where the customer has to pay a different tax rate based on the zip code, for example. There is currently no way to use a rule to check which tax rate should be charged in such cases.
Such an option would be desirable for customers1 vote -
Rule for checking product availability
So far there are rules for checking the stock of a product. However, it would be useful to have a rule that checks whether the number of products in the shopping cart exceeds the number of available stock.
Customers could use this rule to check whether the order is really covered by the current stock or whether the number of products ordered exceeds the stock.
This is relevant for the availability of express shipping, for example.1 vote -
Loading times of the article sliders
The article sliders currently take about one second to load properly. Until then, the first product of the slider is usually displayed briefly in large format.
An optimization of the loading time for article sliders with many products would be desirable.3 votes -
Optimise enlargement of product images
The product image should be possible by spreading the thumb and index finger. The entire form currently reacts to this.
This problem only occurs in our Shopware 6 shop. Our Shopware 5 shops all react correctly at this point. We urgently need an adjustment here.
2 votes -
Accidental up / down due to slipping during the gesture should be prevented.
Since Shopware 6 there is a problem (not within our Shopware 5 shops) that when swiping to scroll the images (product slider) it is no longer excluded that the form scrolls up or down in the wrong direction if accidentally moved.
This problem does not exist with our Shopware 5 shops, but only with our Shopware 6 shop.
The aim is to prevent the form from accidentally scrolling up or down when scrolling between images.
2 votes -
Opportunity to change the order of storefront snippet files
There should be a way to customise the order in which the storefront snippet files are loaded.
Currently the snippet files are loaded in a first come first serve principle.
For example like this
vendor/shopware/core
vendor/mycompany/mytheme/
vendor/store.shopware.com/
vendor/mycompany/myplugin/
vendor/store.shopware.com/swaglanguagepackLoading the snippet files should be like this:
vendor/shopware/core
vendor/store.shopware.com/
vendor/mycompany/myplugin/
vendor/mycompany/mytheme/So that you can overwrite all others with the snippet files of your own theme.
1 vote
- Don't see your idea?