- or
1412 results found
-
Improve navigation menu on mobile devices / Show all categories of the menu on mobile devices
If Shopware uses the hamburger menu (i.e. on small screens and windows), the navigation menu is confusing.
It works on the homepage, because you can see the different categories.
If you are on a product page, you see “Back” and “Show [category name]” in the menu.
This is very confusing because you are used to the navigation menu being the same on all pages. In addition, you can't immediately see which categories the online store has.
If you have a "About us" and a "Contact" page in the menu, visitors do not see it, which costs a lot of trust.
This unusual behavior costs a lot of sales.
The mobile menu should show all main categories to improve the usability, because it makes the navigation more intuitive and faster.
If Shopware uses the hamburger menu (i.e. on small screens and windows), the navigation menu is confusing.
It works on the homepage, because you can see the different categories.
If you are on a product page, you see “Back” and “Show [category name]” in the menu.
This is very confusing because you are used to the navigation menu being the same on all pages. In addition, you can't immediately see which categories the online store has.
If you have a "About us" and a "Contact" page in the menu, visitors do not see it, which costs a lot of trust.
…
6 votes -
Categories or landing pages should be excluded from the search
Categories or landing pages should be excluded from the search so that no incorrect search results can arise with nearby products.
1 vote -
Search for content for admin and frontend
The admin and frontend should also search for content from Content. There are always CMS pages that match certain search terms. For a better shopping experience, these should also be displayed in the search.
1 vote -
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 -
Add "Closeout" Filter to Product Overview
A filter to show only closeout products in the product overview would simplify stock management and make it easier to identify and update these items. This is especially useful for larger catalogs and shops with frequent assortment changes.
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 -
User permissions: Selective access to elements (Shopping Experience Layouts, products, etc)
It would be great, if the user permissions would also allow to give users only access to specific elements of a menu.
For example, if a user is only supposed to have access to one specific Shopping Experiences layout to work on, it currently requires the user to get access to all layouts.
Especially when you are working with external partners, which should only have access to designated elements, a more detailed permission level would be useful.
2 votes -
Connect multiple databases to a Shop
Customer data is often a very sensitiv topic. In our case, the desired set up for storing the data would be to have one database for the Shop relevant and a complete separate database for all customer related data.
2 votes -
Product sets configurator
Many Shopware users are lacking the function "product sets", which allows the buyers to pick a selection of products from a list of products on product detail pages. This function is available via extensions, but this is considered a standard functionality, that a Shopsystem should provide out of the box.
Simular extension:
https://store.shopware.com/de/dvsn895115432267m/produkt-konfigurator-fuer-sets-bundle-konfigurator.html3 votes -
Configuration of the display of cross-selling (Shopping Experiences)
Within the cross-selling configuration or the ‘Shopping Experiences’, it should be possible to select different positions for the different cross-sellings.
This would allow the product detail page to be quickly customised even without individual programming.
4 votes -
Add possibility to change shop default language
It is not possible to change the global default language of the Shopware 6 store after installation. This often leads to frustration or unexpected problems in the management of products and translations. Changing the global default language is currently only possible via a new installation or risky DB adjustments,
Please add a function that allows you to change the default store language in the settings.
3 votes -
Improve Admin search customer module
When creating a new order (Orders > Create order), the first step is for colleagues to search for a customer, usually using the e-mail address.
The customer they are looking for often only appears on page 4-5 of the search results - if they are found at all.
If no matching customer is found, colleagues use the “Create customer” button and enter the relevant customer data.
However, when saving, it is often found that the email address entered already exists, which leads to an abort.
Suggestions for improvement:
Optimization of customer search:
Improve search algorithms to find customers faster and more accurately based on their email address (or other unique criteria).
Implementation of a “live search” that displays possible hits as they are entered.
Check during customer creation:
Introduction of real-time validation of the e-mail address during entry in the “Create customer” form.
Immediate display of a message if the e-mail address already exists in the system to avoid the abandonment process.
When creating a new order (Orders > Create order), the first step is for colleagues to search for a customer, usually using the e-mail address.
The customer they are looking for often only appears on page 4-5 of the search results - if they are found at all.
If no matching customer is found, colleagues use the “Create customer” button and enter the relevant customer data.
However, when saving, it is often found that the email address entered already exists, which leads to an abort.
Suggestions for improvement:
Optimization of customer search:
Improve search algorithms to find customers faster and…
3 votes -
It is currently not possible to search for a specific discount code in the order overview.
For example, when filtering for the discount code "LENABLACK", all orders containing codes such as "ANNALENABLACK" are also shown.
Since the overview does not include a column displaying the discount code, each order must be opened individually to see which code was actually used.It would be helpful to have a dedicated column for the discount code in the order overview or to enable filtering based on exact matches.
1 vote -
Include search bar in the order overview
In the shopping list overview, you can see a ‘small’ search which helps you to find your way around larger lists.
We would like this ‘small’ search bar and its functionality to also be used on the order overview. It should also be possible to search for article numbers there, as is already the case with the shopping list, and also be able to search for order numbers as an additional extension.
5 votes -
Manufacturer pages in the same tab
It would be useful if the shop owner could decide/set whether the link to the manufacturer's website (click on the logo/manufacturer on the product detail page) is opened externally in the new tag or in the same tab.
If a store page for the manufacturer is to be displayed instead of the manufacturer's website, this is less useful in a new tab.
Here it would be better if the owner had the option of opening the page in a new tab or in the same one
2 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 cache key.
Proposed Solution:
- Allowlist Configuration – Define a clear set of parameters that should be part of the cache key instead of excluding specific ones.
- Event for developers – Introduce an event to allow developers to modify the allowlist dynamically.
- Control by config – Provide a config option to adjust the allowlist as needed.
This approach simplifies maintenance, optimizes cache storage, and ensures that only relevant parameters affect cache variations. 🚀
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…
3 votes -
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 confusing.
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 you have to add all related products manually in the condition of the rule.
It would help if there is a condition "item quantity of products within a dynamic prouduct group", to achieve the possibility to count items by line and use the discount per lineitem instead of the complete cart.
When a position has only 1 item an the TAG, the discount does not apply.
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 -
Two factor authentication support for admin
For security reasons it will be favorable to add native Two factor authentication support in the admin.
20 votes -
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
- Don't see your idea?