- or
113 results found
-
Synonym configuration in Admin
Currently its not possible to configure synonyms directly within the backend. What adds to this problem is that lots of ecom teams do not have the capacity and knowledge people to handle them in the code directly and hence do not have the advantages of having synonyms to enrich search results
3 votes -
Bulkedit for the visibility of products
In Shopware 6, there is the option to edit products via bulk editing. Unfortunately, the ability to adjust the visibility of products is missing. It would be useful if one wants to hide products from search, etc.
2 votes -
Shopware Account Plugin License List Update
The current license list overview of the shop in the account.shopware.com is sadly not really handy for customers / agencies.
When updating to later Shopware Versions, you need mostly plugin updates to get back from a broken to a working state (e.g. 6.6 > 6.7, php bin/console fails as well):
- Therefore I have to go to said website, search for the plugin name (somehow over name / description mixed, because names are handled differently in the search)
- Then click on the plugin (when i finally found it) and get the update version.
- Another plugin must be found the same…
1 vote -
Opensearch
It would be great if the search would be defined as OpenSearch, so I can quickly use it in the address line of my browser.
1 vote -
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…
2 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 -
Improvements of the Order creation in the administration.
One of our customers with a relatively large number of customers and orders has some problems with creating orders in the administration. Here are a few suggestions:
The search for customers takes a very long time with several customers (More than 500k customers in the system). After selecting a customer, the grid seems to reload which may be superfluous?
You could take some pain here if the way to create an order via the customer module would select the customer directly, but here you have to search for the customer again, which makes no sense.If a product is to…
2 votes -
Don't use the first page of a paginated sequence as the canonical page
Use URLs correctly:
- Give each page a unique URL. For example, include a ?page=n query parameter, as URLs in a paginated sequence are treated as separate pages by Google.
- Don't use the first page of a paginated sequence as the canonical page. Instead, give each page its own canonical URL.
Currently, the canonical page in categories is always the first page. Without pagination URLs.
According to Google, the canonical URL should be set up including pagination.
Please correct this.
3 votes -
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 vote -
Boosting for categories
As a shop owner I want to be able to boost categories for certain search terms.
1 vote -
Improve accessibility
The new store is not very accessible for keyboard navigation.
The tab order on the search result page starts in the filters, but I want to go through the results first.
On the detail page you can't navigate through gallery images with the arrow keys.1 vote -
Better deletion of customers in admin: after opens a customer a delete button is needed
Currently, only in the customer overview, while selecting the three dots you can delete the customer.
The problem: if you search customer by exact name or mail address it is not possible to highlight the customer in the overview so can't easily delete the customer account. If you have many customers and some requests to delete the account, there is a problem (time consuming) the finish this task.
So please add the function to delete the customer account after open the customer account.
2 votes -
Enable app extensions to use advanced prices for precomputation
Currently, it's not possible to use advanced prices in apps for purposes such as indexing and displaying them in the storefront, e.g. in an app that provides a custom search. The reason is that the app doesn't know the applicable rules, e.g. the rule can change while browsing.
1 vote -
AI Copilot - ChatGPT Code Interpreter Integration
Integrate ChatGPT specifically for the use of code interpreter to be able to create shop data analysis and data visualisation for different shop entities e.g. for order statistics, (anonymised) customer behaviour, product data, recommendation performances, search statistics, etc.
More info about ChatGPT Code Interpreter: https://openai.com/blog/chatgpt-plugins#code-interpreter1 vote -
Output the favicon of the sales channel for Google as well
Although other favicons are stored in the theme, Google seems to favour the favicon.ico in the public folder that displays your logo.
In fact, I have noticed this in several Shopware 6 shops in Google search results.
If you only have one public sales channel, you can simply replace the favicon.png with your own, but we have four sales channels with different favicons.
In this case, you have to set up redirects.
It would be better if the corresponding favicons of the respective shops were actually used and displayed.
2 votes -
Native Multi-Vendor Marketplace Engine + Next.js Headless Support
Shopware 6 is excellent for single-vendor eCommerce, but it lacks core features required to build true multi-vendor marketplaces like Amazon, Etsy, or Alibaba. I propose a Marketplace Engine as a core module or premium extension with:
Vendor Accounts: Sellers can register and manage their own products, orders, and store settings from a dedicated dashboard.
Split Payments & Commissions: Automated payment distribution using Stripe Connect, PayPal Payouts, etc., with platform-level commission control.
Product & Seller Reviews: Customer reviews for products and vendors with moderation workflows, boosting trust and SEO.
Search Personalization: Intelligent search with vendor filters, ratings, and behavior-based ranking. Ideal…
1 vote -
Filter visibility by selected sales channels
For products, there is an option to set visibility for selected sales channels.
This setting determines whether a product appears in search results or in the product listing.
However, to see what is set for a product here, you have to open the product page and then click the settings button again.It would be nice to have an option right here in the product overview to filter by visibility settings.
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…
4 votes -
Enhanced in-app purchase API for usage-based models
We want to develop extensions that are billed entirely via IAP (comment from Shopware: IAP stands for In App Purchases) – without our own subscription logic or external billing. Typical use cases are usage-based features such as quotas (e.g., search volume per month), limits, or activations with periodic renewal.
Currently, Shopware.InAppPurchase.isActive(‘MyExtensionName’, ‘my-iap-identifier’) only returns a Boolean (purchased: true/false).
However, for usage-based models, we lack the specific billing period, e.g., to reliably reset quotas when transitioning to the new period.Our request/feature request:
In addition to isActive(), minimal contract information would be helpful, e.g.:
- Purchase or start date of the…1 vote -
Migration: Automatic placeholders for missing values
Customer migrations are tedious and involve a lot of work, as data records are often not transferred to Shopware 6 because they are missing from Shopware 5.
For example, if the salutation of a customer is not filled in Shopware 5, but the field has become a mandatory field in Shopware 6. Or the first name.
To make migrations much easier, the migration wizard should store a meaningful placeholder in such cases so that the data is transferred correctly.
Within Shopware 6, you can then search for these placeholders and adjust the entries. This takes away the frustration that many…
3 votes
- Don't see your idea?