- or
1510 results found
-
“Contains” and “Does not Contain” are not available for the “Description” operator for dynamic product groups, for example.
It would be nice if the options “Contains” and “Does not Contain” were available for the description. These options are available for other conditions that check text fields, but not for the description.
3 votes -
Add "priority" or "order" as a column to list overviews in the shopware backend (where applicable)
To be able to see the order or sort on priorities within a list-overview from the shopware admin would be extremely helpful in cases of for example:
Marketing > Promotions
but also for example for "Product > Properties"
And others involving orders or priorities
1 vote -
Counter duplicates by checking the e-mail address for the e-mail domain for business domains
One function would be great: Assuming you have customers with a large number of addresses (e.g. municipalities or large corporations).
Example Mustermann AG group with the mail domain: @mustermann-ag.de
Here it would be great if a check could be made during registration: if further registrations with the mail domain @mustermann-ag.de come into Shopware, a message could appear: “There is already at least one customer account with the e-mail domain @mustermann-ag.de. Are you sure that another customer account is required for this company? If necessary, contact the user who has already created the customer account to place an order.”
It is of course important here that mail domains from general hosters such as @gmx.de, @gmx.com, @yahoo.de, @yahoo.com, @outlook.de, @outlook.com etc. are not validated.
Why: we have to deal with duplicates. Every newly registered customer receives a new customer number. In some cases, we also store customer-specific prices. Of course, this only works if a new customer number is not created for each customer and a new group number is created above it (we call this a group).
One function would be great: Assuming you have customers with a large number of addresses (e.g. municipalities or large corporations).
Example Mustermann AG group with the mail domain: @mustermann-ag.de
Here it would be great if a check could be made during registration: if further registrations with the mail domain @mustermann-ag.de come into Shopware, a message could appear: “There is already at least one customer account with the e-mail domain @mustermann-ag.de. Are you sure that another customer account is required for this company? If necessary, contact the user who has already created the customer account to place an order.”
It is…
2 votes -
subscription interval should be switchable between even and uneven weeks
Currently it is possible to define subscriptions wit a 2 week interval but it is not possible to define if this turn is on even or uneven weeks.
In the detailed settings for the interval you can define on wich day of the week the order should be created but the system counts the weeks by the start of the month/year.
It should also be possible to define if it is an even or uneven 2 week term.
2 votes -
Search for amazon or ebay orders
DE
Search in orders: it should also be possible to search by ebay name and Amazon order number. When I search for names in orders, the latest order should always come up (as in SW 5).
–
EN
Suche in Bestellungen: es soll auch nach ebay Namen und Amazon Bestell-Nr. möglich sein zu suchen. Wenn ich nach Namen in Bestellungen suchen sollte immer die neueste Bestellung ob kommen (wie in SW 5 auch).2 votes -
Improve admin layout to preserve 'Select category ...' visibility
.sw-category-tree-fieldmain-wrapper > .sw-block-fieldblock {
height: fit-content !important;
overflow: visible !important;
}1 voteHello!
Thanks for sharing this with us—good eye! It looks like what you’ve reported is actually a bug rather than an idea or feature request. To make sure it gets the right visibility and tracking, could you please add it to our GitHub Issues board? That’s where our engineering team triages and fixes bugs most efficiently.
How to report bugs:
Shopware 6 - Tutorials & FAQs - Why do we use Github Issues?
Once it’s logged there (a quick description, steps to reproduce, and any screenshots are super helpful), we’ll be able to jump on it. Thanks again for helping us keep things running smoothly!
-
Bitte in der Anzahl der Produktverkäufe die Produktnummer mit anzeigen (Artikelnummer)
Es wäre sehr hilfreich, die Produktnummer in der Liste der Produktverkäufe sehen zu können.
Bitte blenden Sie die Produktnummer im Analytics Plugin mit ein. (Artikelnummer)Vielen Dank
7 votes -
Export existing Product Reviews
Currently there is no way to export product reviews from Shopware. This prevents us from using this very valuable data throughout the company.
We need an export function for product reviews because it allows shop owners to efficiently analyze customer feedback, identify trends, and improve products and services. This feature also helps with marketing and compliance, making it easier to share insights across all departments and stakeholders.
4 votes -
Search - Exclude specific categories from the search.
Currently, it is not possible to exclude individual categories from the search. This would be useful for footer categories.
7 votes -
Change product detail page layout for more than 25 items
EN
If a separate layout has been designed for some products, for example because these products have a special property for which there should be an explanation, then I can select the products under Content > Experience worlds > Layout assignment > Assign layout. However, the selection list is limited to 25 elements. To do this, we have added a filter to filter the selection for additional products. However, this only works as long as the search terms are different.If I have 80 products with, for example, ‘variant’ in the name, I can only select 25, after which further products could only be selected if there was another unique criteria with which further products could be selected. The only other alternative is to select each product individually and then change the layout manually.
It is not possible to link the products to the layout via a dynamic product group and it is also not possible to set a new layout in the additional change.
DE
Wenn für einige Produkte ein eigenes Layout entworfen wurde, beispielsweise weil diese Produkte eine spezielle Eigenschaft haben, zur der es eine Erläuterung geben soll, dann kann ich unter Inhalte > Erlebniswelten > Layout-Zuweisung > Layout zuweisen die Produkte auswählen. Jedoch ist die Auswahlliste auf 25 Elemente beschränkt. Dafür haben wir den Filter eingebaut, mit dem die Auswahl auf weitere Produkte gefiltert wird. Das funktioniert aber nur so lange, wie die Suchbegriffe unterschiedlich ausfallen.Haben ich 80 Produkte mit zum Beispiel "Variante" im Namen kann ich nur 25 auswählen, danach gingen weitere nur noch, wenn es ein weiteres eindeutiges Kriterium gäbe, mit dem weitere Produkte ausgewählt werden können. Die einzige andere Alternative jedes Produkt einzeln auszuwählen und dann das Layout manuell zu ändern.
Es ist nicht möglich die Produkte über eine Dynamische Produktgruppe mit dem Layout zu verbinden und auch in der Mehränderung kann kein neues Layout gesetzt werden.
EN
If a separate layout has been designed for some products, for example because these products have a special property for which there should be an explanation, then I can select the products under Content > Experience worlds > Layout assignment > Assign layout. However, the selection list is limited to 25 elements. To do this, we have added a filter to filter the selection for additional products. However, this only works as long as the search terms are different.If I have 80 products with, for example, ‘variant’ in the name, I can only select 25, after which…
4 votes -
Searching and editing variant properties
EN
A store with many variant-forming properties cannot search efficiently for the required property set. For example, if I have the property black several times and now want to add a variant in white, I get all such properties displayed by searching for “black”, but the matching “white” is missing. I then have to scroll through step by step and check when a property set has multiple properties selected. Even with more than 10 pages, this becomes a tedious task, as I can neither enter “Go to page 26” nor search specifically for the name of the set. An improved search or selection would significantly improve handling.DE
Ein Shop mit vielen variantenbildenden Eigenschaften kann das benötigte Eigenschaften-Set nicht effizient suchen. Wenn ich zum Beispiel mehrmals die Eigenschaft schwarz habe und nun eine Variante in weiß hinzufügen möchte, bekomme ich durch die Suche nach "schwarz" alle solchen Eigenschaften angezeigt, aber das passende "weiß" fehlt. Dafür muss ich dann Schritt für Schritt durchblättern und prüfen, wann ein Eigenschafts-Set mehrere Eigenschaften ausgewählt hat. Bereits bei mehr als 10 Seiten wird das eine langwierige Sache, da ich weder eingeben kann "Gehe zu Seite 26" noch gezielt nach dem Namen des Set suchen kann. Eine verbesserte Suche oder Auswahl würde das Handling bedeutend verbessern.EN
A store with many variant-forming properties cannot search efficiently for the required property set. For example, if I have the property black several times and now want to add a variant in white, I get all such properties displayed by searching for “black”, but the matching “white” is missing. I then have to scroll through step by step and check when a property set has multiple properties selected. Even with more than 10 pages, this becomes a tedious task, as I can neither enter “Go to page 26” nor search specifically for the name of the set. An…5 votes -
Analytics: Add user permission to see statistics
Currently, when the Shopware Analytics extension is installed and active, any user has access to those statistics. Since these statistics show partly sensitive organisation data, there should be a user permission, in order to define which user can access the statistics.
Example:
We access our Admin in our local store, when customers ask for certain products. Now we access the dashboard and the customer will see exactly how much revenue we made.4 votes -
external order id / externe Auftragsnummer
EN:
In B2B, it is common practice for the purchaser to provide an external order number to ensure matching within customer accounting. Therefore, an optional field with “external order number” should be possible in the shop when placing the order (can be switched on/off in admin and per channel). This should be displayed in the order overview for the customer when logged in.DE:
Im B2B ist es üblich eine externe Auftragsnummer seitens des Bestellers zu übergeben, um das matchen innerhalb der Kundenbuchhaltung zu gewährleisten. Daher sollte ein optionales Feld mit "externe Auftragsnummer" im Shop bei der Bestellabgabe möglich sein (im admin ein/ausschaltbar und das pro Channel). Dieses sollte für den Kunden einloggt in der Bestellübersicht angezeigt werden.EN:
In B2B, it is common practice for the purchaser to provide an external order number to ensure matching within customer accounting. Therefore, an optional field with “external order number” should be possible in the shop when placing the order (can be switched on/off in admin and per channel). This should be displayed in the order overview for the customer when logged in.DE:
Im B2B ist es üblich eine externe Auftragsnummer seitens des Bestellers zu übergeben, um das matchen innerhalb der Kundenbuchhaltung zu gewährleisten. Daher sollte ein optionales Feld mit "externe Auftragsnummer" im Shop bei der Bestellabgabe möglich sein…15 votes -
Custom templates or custom template modules/blocks for product comparisons
It would be very beneficial if there was a way to save your own customized templates for product comparisons and/or to save/create building blocks or blocks of template parts so that you can then use them in all or various product comparisons in the template.
Especially if you make many customizations and want to use them in different product comparison sales channels, or e.g. have 10x a very similar template and want to make a change or correct an error, you currently have to correct the error in 10 templates. This would be possible centrally in the module or custom template and could be adopted everywhere.
It would be very beneficial if there was a way to save your own customized templates for product comparisons and/or to save/create building blocks or blocks of template parts so that you can then use them in all or various product comparisons in the template.
Especially if you make many customizations and want to use them in different product comparison sales channels, or e.g. have 10x a very similar template and want to make a change or correct an error, you currently have to correct the error in 10 templates. This would be possible centrally in the module or custom…
3 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 for large catalogs and vendor competition.
Additionally, I recommend official Next.js storefront support for better performance (SSG/ISR), React developer adoption, and edge rendering via Vercel. While Shopware PWA is great, Next.js would accelerate frontend development and modernize the developer experience.
Use Cases:
A retailer wants to build a regional platform where independent artisans can sell directly to consumers, with the platform managing logistics, payments, and reviews.
An eCommerce enterprise needs a scalable platform for thousands of vendors offering competitive pricing, search-filtered by seller, and user-driven trust signals.
These features would position Shopware as a strong alternative to Magento or Shopify Plus for multi-vendor businesses and open doors to large-scale SaaS and marketplace use cases.
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 -
Official Next.js Frontend Framework Support for Shopware 6
As Shopware continues to evolve as an API-first platform, it would be highly beneficial to offer official support and tooling for Next.js as a first-class frontend framework option. Next.js brings powerful features like:
Incremental Static Regeneration (ISR) and Static Site Generation (SSG) for blazing-fast performance
Built-in API routes and middleware for seamless integration
React ecosystem benefits with hooks, server components, and a vibrant community
Easy deployment on platforms like Vercel, enabling edge caching and global CDN
Simplified developer experience with TypeScript support and modern tooling
By providing an official Next.js storefront starter kit, sample components, and API client libraries, Shopware could attract React developers and modernize frontend experiences. This would complement the existing Twig-based storefront, offering more flexibility and performance for enterprise customers looking to build scalable, headless storefronts with React.
As Shopware continues to evolve as an API-first platform, it would be highly beneficial to offer official support and tooling for Next.js as a first-class frontend framework option. Next.js brings powerful features like:
Incremental Static Regeneration (ISR) and Static Site Generation (SSG) for blazing-fast performance
Built-in API routes and middleware for seamless integration
React ecosystem benefits with hooks, server components, and a vibrant community
Easy deployment on platforms like Vercel, enabling edge caching and global CDN
Simplified developer experience with TypeScript support and modern tooling
By providing an official Next.js storefront starter kit, sample components, and API client libraries, Shopware…
0 votes -
Discount Groups
Is it also possible to define groups of discounts that can or cannot be combined? As we have a lot of different codes, it would be much easier if groups could be defined.
3 votes -
B2B: Add option to product detail page like cost center, project, etc.
It would be great, if B2B store would have the option to add selection or comment fields on product detail pages.
This could be used, so that buyers can directly select the cost center or the project, which the product is bought for. This information could then be automatically integrated into the invoices, saving a lot of manually effort for the finance department.
3 votes -
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 customers experience during a migration.
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 -
New Trigger for the Flow Builder: Customer Login
Currently, the Flow Builder does not offer a dedicated trigger for logging into a customer account, only in connection with the checkout process. This significantly limits automation possibilities.
Proposed Enhancement:
A new "Login" trigger that activates whenever a customer logs into their account – independently of the checkout process.Possible Use Cases:
Automatic tag assignment based on login frequency.
Customer group changes for logged-in users, e.g., granting access to exclusive content or discounts.
Automated email dispatch, e.g., a welcome back message after a long period of inactivity or targeted marketing campaigns.
3 votes
- Don't see your idea?