- or
No existing idea results
- ~ No ideas found ~
1398 results found
-
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 improved…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 -
Admin: Save column width in overview menus
The Shopware Admin allows to customize the width of columns in our Product-, Order and Customer overview.
How ever, once a user has adjusted the width to their need and they reload the overview, they have to perform those customizations over and over again from scratch.Saving those widths would prevent the frustration of performing the same manual adjusted and improve the user experience.
4 votes -
Maintain Cost Centres for Employees in B2B Components
Would be realy nice to manage cost centres on the employee level in the B2B Components, or as a drop down of connected cost centres in the check out
7 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 -
Add flow trigger for document generation event
It should be possible to trigger a flow when a document is created for an order. It should be possible to select a trigger for each document type. We need a way to start a flow when a credit note (Gutschrift) has been issued and the credit note document has been created. Then we would like to add a tag to the this order or execute further actions.
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…
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 -
Add multiple changes to the Dynamic Access settings for products
At the moment it is not possible to make simple adjustments to the Dynamic Access rules via the bulk changes for products. Please add this function, as we often have to adjust many products at once.
3 votes -
B2B: Gift function with certificate upload and reporting
In B2B context, companies can buy products as gifts. Up to 50€ per person and year can be gifted taxfree.
It would be great, if Shopware offers this gift functionality including a certificate upload (proof) and a reporting function, that gives the company an overview of the gifts of a specific time range.
3 votes -
Deleting media via the admin search
If the admin search is used to search for media in various folders, it should be possible to select and delete several images, for example.
At the moment, the search results pop up as a small menu, which does not allow you to select and delete the results individually, for example.
This makes it very time-consuming to remove certain media.
3 votes -
Breadcrumb missing for dynamic product groups - categories / Breadcrumb fehlt bei dynamischen Produktgruppen - Kategorien
Wir nutzen die SW Funktion dynamische Produktgruppen, um automatisiert eine große Anzahl an Artikeln einer Kategorie zuzuordnen. Das funktioniert hervorragend, hat jedoch einen kleinen Fehler im Gepäck.
Leider wird kein Breadcrumb erzeugt, welcher für die SEO und Usability relevant wäre, wenn die Artikel auf diese Weise der Kategorie zugeordnet werden.
Dies klingt zunächst logisch, da der Artikel nicht direkt sondern nur dynamisch zugeordnet wurde, allerdings konnten wir mit einem Plugin einen Breadcrumb automatisch erzeugen.
Die erforderlichen Informationen sind also vorhanden, der Breadcrumb wurde bei der Entwicklung der dynamischen Produktgruppen vermutlich nur nicht berücksichtigt.Es wäre aus Sicht der SEO und der Usability wichtig dies zu korrigieren.
-
We use the SW function dynamic product groups to automatically assign a large number of items to a category. This works great, but has a small flaw.
Unfortunately, no breadcrumb is created that would be relevant for SEO and usability when the articles are assigned to the category in this way.
This sounds logical at first, since the article was not assigned directly but only dynamically, but we were able to create a breadcrumb automatically using a plugin.
So the necessary information is available, the breadcrumb was probably not taken into account when developing the dynamic product groups.From an SEO and usability perspective, it would be important to correct this.
Wir nutzen die SW Funktion dynamische Produktgruppen, um automatisiert eine große Anzahl an Artikeln einer Kategorie zuzuordnen. Das funktioniert hervorragend, hat jedoch einen kleinen Fehler im Gepäck.
Leider wird kein Breadcrumb erzeugt, welcher für die SEO und Usability relevant wäre, wenn die Artikel auf diese Weise der Kategorie zugeordnet werden.
Dies klingt zunächst logisch, da der Artikel nicht direkt sondern nur dynamisch zugeordnet wurde, allerdings konnten wir mit einem Plugin einen Breadcrumb automatisch erzeugen.
Die erforderlichen Informationen sind also vorhanden, der Breadcrumb wurde bei der Entwicklung der dynamischen Produktgruppen vermutlich nur nicht berücksichtigt.Es wäre aus Sicht der SEO und…
6 votes -
Breadcrumbs for products from blocked categories
Currently, products can have a category displayed as a breadcrumb, which is restricted by Dynamic Access. Although this can be adjusted individually for each product, an automated solution would be desirable for customers.
1 vote -
Product comparison - variables for main article attributes.
In a product comparison sales channel, it is not possible to export attributes such as the article number of the main article of a variant product. As soon as you set that variants are exported individually, only the attributes of these and not those of the main article are exported.
1 vote -
YouTube Shorts integration
YouTube videos can already be integrated into Shopping Experiences via the YouTube video element, but YouTube shorts are not yet supported by this element.
3 votes -
Confirm deletion of blocks beforehand
If you delete a block in the cms, this change is implemented and saved immediately. If this happens accidentally, it can lead to unintentional data loss, which can cause a lot of frustration.
It would therefore be good if the deletion had to be confirmed beforehand or if it was no longer saved automatically.2 votes
- Don't see your idea?