- or
3 results found
-
avif support in media
Support avif file format in media, because it is still not supported yet: https://docs.shopware.com/en/shopware-6-en/content/media#overview
avif is fully supported by modern browsers except Microsoft Edge (in beta): https://caniuse.com/?search=avif8 votes -
Automatically transform images into webp / avif format
Make it possible to transform images (especially product images) into into webp or avif. Here, you should select which one to use. Also: if you want to delete the original from the media storage.
Why: For SEO, you get a better rank while the website loading faster. The plugins for doing this are terrible.12 votes -
Support for dynamic Thumbnails through services
Short: Implement plugin FroshPlatformThumbnailProcessor into the core
Longer: Add the ability to define a pattern for thumbnails to be used instead of creating or requesting thumbnails from storage. Additionally, shopware could host a service to convert images on the fly, f.e. see imgproxy.net - maybe just with nicer links. Just add a caching before that and win.
Advantages: Any shop owner has webp/avif-images with the best compression and suitable sizes without wasting storages.
6 votes
1519 results found
-
Add CC, BCC and Reply-to features to the mail function in the flow builder
Shop admins should have the possibility to define CC and BCC contacts in the mail send function within the flow builder, as well as have the option to define a reply-to address that is used whenever a customer tries to reply to a mail.
41 votes -
Shopware App for mobiles
Please note that most competitors have an app for mobile, to follow some real time KPI statistics. That would make sense for Shopware to have. what are the thoughts about that from Shopware?
9 votes -
Expanding the Electronic Revocation Function
Current status:
Only the standard Shopware order number field is usable.Problem:
- In professional setups, the ERP system is often the primary system.
- The Shopware order number is not relevant internally.
- A custom field is used instead for the ERP order number.
- The back office works exclusively with this ERP number.Suggested improvement:
- Offer a choice in the admin panel:
- Either the standard Shopware order number
- Or a selectable custom field (e.g., ERP order number)
- Ideally, as a dropdown menu option in the admin panel.Background:
Larger retailers with multiple sales channels often use an ERP system. Therefore, this is not an isolated case.Current status:
Only the standard Shopware order number field is usable.Problem:
- In professional setups, the ERP system is often the primary system.
- The Shopware order number is not relevant internally.
- A custom field is used instead for the ERP order number.
- The back office works exclusively with this ERP number.Suggested improvement:
- Offer a choice in the admin panel:
- Either the standard Shopware order number
- Or a selectable custom field (e.g., ERP order number)
- Ideally, as a dropdown menu option in the admin panel.Background:
Larger retailers with multiple sales channels…3 votes -
Inheritance of elements in CMS pages
DE:
Aktuelle Systematik seitens Shopware:Man kann CMS-Seiten erstellen und in diesen innerhalb Sektionen verschiedene Blöcke und Elemente definieren. Nun habe ich die Möglichkeit in Kategorien entweder für jede Seite ein eigenes CMS-Layout zuzuweisen. Ebenso kann man aber auch das gleiche CMS-Layout mehreren Seiten zuweisen. Hier hat man dann die Möglichkeit die Inhalte der im Layout festgelegten Elemente zu individualisieren.
Nun entsteht dadurch folgende Problematik:
Angenommen ich habe 50 Kategorie-Seiten, welche alle das gleiche vorgegebene CMS-Layout nutzen. Dann habe ich nur die Möglichkeit die Inhalte der Blöcke/Elemente zu bearbeiten, kann aber nicht die Blöcke/Sektionen auf diverse Unterseiten vererben.
Sollte somit z.B. der Fall auftreten, dass ich von 10 dieser 50 Seiten mit dem gleichen Layout an erster Stelle keinen Slider mehr möchte (aber das restliche Layout soll beibehalten werden, bzw. der Aufbau aller darauf folgenden Elemente), so ist aktuell die einzige Möglichkeit für diese 10 Unterseiten neue Layouts anzulegen.
Diese Problematik lässt sich nun hochskalieren. Nehmen wir nun an, wir wollen von den 50 Seiten, auf 10 Seiten an erster Stelle keinen Slider und von diesen 10 Seiten soll bei 4 Seiten an letzter Stelle ein anderes Element sein, müsste ich nochmals diese 4 Seiten neu erstellen.
Obwohl von diesen 50 Seiten das Grundlayout bis auf einige Blöcke identisch ist, muss ich aktuell für jegliche Abweichung am Grundlayout neue eigene Seiten erstellen und kann nicht festlegen, dass z.B. Sektionen in einem CMS-Layout vererbbar sind.
Über eine Lösung seitens Shopware würden wir uns sehr freuen, das würde die Contentbearbeitung bei umfangreichen Inhalten mit mehr als 1000 Seiten enorm vereinfachen und wäre ein wirklicher Mehrwert.
ENG:
It is possible to create CMS pages and define different blocks and elements within sections. Categories can either be assigned their own individual CMS layout per page, or the same CMS layout can be assigned to multiple pages. In this case, the content of the elements defined in the layout can be customized individually.This leads to the following problem:
Assume there are 50 category pages that all use the same predefined CMS layout. In this scenario, it is only possible to edit the content of the blocks and elements, but it is not possible to inherit blocks or sections across different subpages.
For example, if on 10 of these 50 pages the slider should no longer appear as the first element (while the rest of the layout, including the structure of all subsequent elements, should remain the same), the only current solution is to create new layouts for these 10 subpages.
This issue can be scaled further. If, for instance, out of the 50 pages, 10 pages should not have a slider as the first element, and out of those 10 pages, 4 pages should have a different element at the last position, those 4 pages would again need to be created separately.
Although the base layout of these 50 pages is largely identical except for a few blocks, any deviation from the base layout currently requires creating entirely new pages. It is not possible to define sections within a CMS layout as inheritable.
We would greatly appreciate a solution from Shopware, as this would significantly simplify content management for large setups with more than 1,000 pages and would provide real added value.
DE:
Aktuelle Systematik seitens Shopware:Man kann CMS-Seiten erstellen und in diesen innerhalb Sektionen verschiedene Blöcke und Elemente definieren. Nun habe ich die Möglichkeit in Kategorien entweder für jede Seite ein eigenes CMS-Layout zuzuweisen. Ebenso kann man aber auch das gleiche CMS-Layout mehreren Seiten zuweisen. Hier hat man dann die Möglichkeit die Inhalte der im Layout festgelegten Elemente zu individualisieren.
Nun entsteht dadurch folgende Problematik:
Angenommen ich habe 50 Kategorie-Seiten, welche alle das gleiche vorgegebene CMS-Layout nutzen. Dann habe ich nur die Möglichkeit die Inhalte der Blöcke/Elemente zu bearbeiten, kann aber nicht die Blöcke/Sektionen auf diverse Unterseiten vererben.
Sollte somit…
9 votes -
Highlight incomplete CAPTCHA field in checkout
In the current Shopware SaaS checkout, which uses FriendlyCaptcha, users sometimes overlook the CAPTCHA field. After filling out all required fields, they attempt to continue the checkout process, but nothing happens. There is no indication that the CAPTCHA is missing.
While other required fields are highlighted in red or otherwise marked when incomplete, the CAPTCHA field does not receive any visual feedback. This can lead to confusion and interrupt the checkout experience.
It is therefore suggested that the CAPTCHA field be visually highlighted (e.g., marked in red) when it has not been completed, consistent with the behavior of other required fields. This improvement could help ensure a smoother and clearer checkout flow for users.
In the current Shopware SaaS checkout, which uses FriendlyCaptcha, users sometimes overlook the CAPTCHA field. After filling out all required fields, they attempt to continue the checkout process, but nothing happens. There is no indication that the CAPTCHA is missing.
While other required fields are highlighted in red or otherwise marked when incomplete, the CAPTCHA field does not receive any visual feedback. This can lead to confusion and interrupt the checkout experience.
It is therefore suggested that the CAPTCHA field be visually highlighted (e.g., marked in red) when it has not been completed, consistent with the behavior of other required…
11 votes -
B2B Components: allow modification of Employee invite timeout
Currently there is a hard coded timeout of 2 hours when employees are invited into an organization in B2B Components. Shop owners and potentially customers should be able to modify this time to fit their needs.
8 votes -
B2B: allow defining and using of multiple VAT IDs per customer account
Currently, only one VAT ID can be defined for a customer. This may be undesirable for some companies that are tightly related to other legal entities or have sub-companies they want to create orders for. In that case, multiple customer accounts would need to be created for proper invoicing.
The database structure already has a field to store a VAT ID with an address, so it would be useful to allow saving different VAT IDs depending on the address, so that customer can choose them during checkout.
7 votes -
Automated Calculation of Fees (Customs & Taxes) in Checkout for International Orders
Currently, Shopware 6 does not provide a native feature for automatically calculating variable fees such as customs duties, import taxes, or country-specific charges during checkout.
However, this functionality is increasingly important for international merchants to ensure a legally compliant and transparent order process.Competing platforms (e.g., Shopify) already offer this functionality as a built-in feature. It enables automated calculation and display of additional fees (e.g., customs duties, import VAT, service fees) based on product value, shipping destination, product category, or customs tariff number (HS code).
In Shopware, this can currently only be achieved through manual configuration using the shipping method price matrix, which is not dynamic and cannot handle complex calculation logic (e.g., article-based or country-based variations). Additionally, surcharges added via the price matrix are included in the cart subtotal, leading to incorrect tax and duty calculations when these are applied again on top.
Use Cases:
International Shipping: Merchants shipping outside the EU (e.g., to the US, UK, Canada, or Switzerland) need to automatically calculate and display customs and import duties.
Legal Compliance & Transparency: Customers should be informed of all applicable fees during checkout to prevent unexpected costs or returns.
Automation & Efficiency: Merchants want to automate fee calculation via integrations with external tax or logistics services (e.g., Avalara, Zonos, FedEx API, etc.) rather than maintaining manual tables.
Competitive Edge: Competing eCommerce systems like Shopify or BigCommerce already include this capability, putting Shopware at a disadvantage, especially for international merchants.
Suggested Implementation:
-
Introduce a dynamic fee calculation module within checkout, based on:
- Shipping destination
- Product item data (including tariff/HS code)
- Total cart value
- Potentially also carrier or fulfillment method
Provide API endpoints and plugin interfaces for integrating external tax or customs calculation services.
-
Add configurable admin settings to define:
- Which fee types should be calculated (customs, taxes, service fees, etc.)
- Whether the fees should be shown in the cart or added during checkout only.
The technical foundation could be a core-level extensibility module that third-party providers can build upon.
Benefits:
Increased legal compliance for international trade.
Transparent cost display for customers.
Reduced cart abandonment rates due to unexpected delivery charges.
Improved competitiveness and attractiveness for global and enterprise merchants.
Currently, Shopware 6 does not provide a native feature for automatically calculating variable fees such as customs duties, import taxes, or country-specific charges during checkout.
However, this functionality is increasingly important for international merchants to ensure a legally compliant and transparent order process.Competing platforms (e.g., Shopify) already offer this functionality as a built-in feature. It enables automated calculation and display of additional fees (e.g., customs duties, import VAT, service fees) based on product value, shipping destination, product category, or customs tariff number (HS code).
In Shopware, this can currently only be achieved through manual configuration using the shipping method…
13 votes -
Allow approvers to edit orders in B2B-Approval-Workflows
Problem Description:
In the current B2B approval workflow, users with an Approver can only approve or reject orders that are subject to approval rules.
Even if the role permissions are explicitly set to allow order-related actions, the approver cannot make any changes to the order before approving it.
This is a limitation for real-world B2B processes, where ordering mistakes are common and must be corrected by the approver instead of rejecting and recreating the order.
Current Behavior:
When an order requires approval:
- The approver can only approve or reject the order
- The approver cannot:
- Change product quantities
- Remove order positions
- Change payment method
- Change shipping method
- Edit billing or shipping addresses
- Write a comment on the order, regardless of approvalThis behavior applies even if the corresponding permissions are assigned to the approver role.
Expected Behavior:
Approvers should be able to edit an order before approval, according to the permissions defined for their role.
If the role permissions allow it, an approver should be able to:
- Remove order line items
- Adjust product quantities
- Change payment method
- Change shipping method
- Edit billing and shipping addresses
- Regardless of approval or rejection, write a comment on the orderThe approval decision (approve/reject) should then apply to the modified order.
Business Impact:
In B2B commerce, approval workflows are meant to:
- Correct ordering mistakes
- Ensure compliance with company rules
- Avoid unnecessary rejections and re-ordersRestricting approvers to only approve or reject orders leads to:
- Inefficient workflows
- Increased manual effort
- Poor user experience for B2B customersThis behavior does not reflect common B2B purchasing processes, where approvers are expected to correct errors rather than reject orders entirely.
Problem Description:
In the current B2B approval workflow, users with an Approver can only approve or reject orders that are subject to approval rules.
Even if the role permissions are explicitly set to allow order-related actions, the approver cannot make any changes to the order before approving it.
This is a limitation for real-world B2B processes, where ordering mistakes are common and must be corrected by the approver instead of rejecting and recreating the order.
Current Behavior:
When an order requires approval:
- The approver can only approve or reject the order
- The approver cannot:
- Change product quantities…6 votes -
Checkbox für AGB entfernen, weil rechtlich unnötig
Laut https://www.heise.de/hintergrund/Warum-im-Netz-Checkboxen-fuer-AGB-und-Datenschutz-meist-ueberfluessig-sind-10449542.html braucht man keine Checkboxen für Datenschutzerklärung und AGB.
Durch das Entfernen der Checkbox für die AGB im Checkout ist der Checkout viel schneller und einfacher.
Bei der verlinkten Seite sind Formulierungen für den Text angegeben. Ohne Checkbox muss der Text angepasst werden.
Viele Besucher übersehen die Checkbox, klicken auf den Kaufen-Button und bekommen dann eine Fehlermeldung, dass sie erst einen Haken setzen müssen.
21 votes -
Option for B2B Components order related mails send to customer Orga employee mail
In B2B environments, orders are often placed by employees acting on behalf of their organization. Currently, Shopware sends order confirmation emails only to the primary email address of the customer account (Main Account).
However, in many cases, it is desirable for the employee who submitted the order to also receive — or solely receive — the order confirmation email or documents.
To address this, a new configuration option should be added to the customer or organization settings, allowing administrators to define the default behavior for order confirmation emails.
Functional Proposal:
Add a setting in the B2B customer configuration:
Option A: Send order confirmation to the organization’s main (default) email address.
Option B: Send order confirmation to the email address of the employee who placed the order.
The setting should be adjustable per organization.
Optionally, allow sending to both addresses.
In B2B environments, orders are often placed by employees acting on behalf of their organization. Currently, Shopware sends order confirmation emails only to the primary email address of the customer account (Main Account).
However, in many cases, it is desirable for the employee who submitted the order to also receive — or solely receive — the order confirmation email or documents.
To address this, a new configuration option should be added to the customer or organization settings, allowing administrators to define the default behavior for order confirmation emails.
Functional Proposal:
Add a setting in the B2B customer configuration:
Option A:…
8 votes -
Revocation button for Online-Shops
The revocation button for online stores will become mandatory in the near future. You should therefore keep an eye on this now.
https://www.versandhandelsrecht.de/2024/03/27/widerrufsbutton/
https://www.golem.de/news/neuerungen-bei-onlinekaeufen-der-widerrufs-button-kommt-2507-197913.html
https://www.bmjv.de/SharedDocs/Gesetzgebungsverfahren/DE/2025_GAendVVVR.html?nn=110490
19 votes -
Hide buy button for specific products on sales channel level
Implement an option that allows hiding the buy button for specific products. Moreover, it should be possible to hide the buy button for specific sales channels while it continues to be displayed in other sales channels.
6 votes -
JSON LD
JSON LD ist seit über einem Jahrzehnt das Standardformat, um Produktdaten in Online Shops strukturiert vorzuhalten.
Es ist deutlich einfacher zu warten, separiert die Daten klar von der Markup ... und ist von Shopware zu erwarten ;)
–
JSON LD has been the standard format for storing product data in online shops in a structured manner for over a decade.
It is much easier to maintain, clearly separates the data from the markup ... and is to be expected from Shopware ;)
9 votes -
Inheritable category and menu visibility in organizational units (B2B)
Currently, category and product visibility settings can only be explicitly configured per category within organizational units.
When a parent category is selected, the subcategories beneath it are not automatically included.
This leads to the following problems with extensive category structures (several hundred subcategories):
- very high manual maintenance effort
- increased susceptibility to errors
- poor maintainability when structural changes are made
- limited scalability in a B2B contextIn addition, the main menu must be controlled indirectly via individual assignments to the contained categories, as a blanket menu activation is not possible.
Target Image:
- Selecting a parent category should optionally include all subcategories automatically.
- Menu visibility should be configurable independently of individual assignments.
- Reduction of administrative effort for complex B2B structures.Specific Improvement Suggestions
A) Inheritable Category Visibility
Option 1: "Include Subcategories" CheckboxWhen selecting a category in the organizational unit:
☐ Automatically include subcategories
Behavior:
- Recursively activates all child categories.
- New subcategories are automatically included.
- Optionally overridable at the subcategory level.Technically feasible:
- Flag at the category assignment level
- Recursive query in the CategoryTreeLoader
- Lazy resolution in the Visibility ResolverB) Global Menu Sharing
New option in the organizational unit:☐ Show full main menu
Behavior:
- Menu structure is displayed
- Visibility of individual products remains adjustable
- Alternatively: Combination with category filter logicOptional:
- Visibility only structural (navigation visible, product access checked)Benefits
For Customers
- Massive time savings
- Significantly improved maintainability
- Scalability for large catalogs
- Fewer misconfigurationsFor Shopware
- Stronger B2B positioning
- Reduced support requests
- Less need for custom development
- Competitive advantage with enterprise customersCurrently, category and product visibility settings can only be explicitly configured per category within organizational units.
When a parent category is selected, the subcategories beneath it are not automatically included.
This leads to the following problems with extensive category structures (several hundred subcategories):
- very high manual maintenance effort
- increased susceptibility to errors
- poor maintainability when structural changes are made
- limited scalability in a B2B contextIn addition, the main menu must be controlled indirectly via individual assignments to the contained categories, as a blanket menu activation is not possible.
Target Image:
- Selecting a parent category…4 votes -
Structured data for AI readability
I recently stumbled upon this press release by one of our partners - basically an ad for their plugin: https://www.openpr.de/news/1299320/Shopware-Shops-werden-KI-sichtbar-mitho-veroeffentlicht-KI-Agentic-Commerce-Plugin.html
However, as Shopware wants to go ahead with AI massively, the proposed features seem to be basic when it comes towards being prepared for AI readability:
- structured product and category feeds in JSON format
- llms.txt and other manifests for AI
- precise microdata and JSON descriptions of variants, prices, shipping etc.
6 votes -
Shopware Analytics - Beta Phase
Following the launch of the first iteration of Shopware Analytics, we are continuing to develop the next iterations, which will further enhance functionalities. Additionally, we will steadily introduce a series of new dashboards featuring more metric visualizations. These updates will be rolled out independently of Shopware minor releases, leveraging the flexibility of our App-based service.
We invite you to explore the new features of Shopware Analytics and share your feedback. Your insights and feedback will be considered during development to ensure continuous improvement.
Here you can find the original feedback, which was the base of the first iteration: https://feedback.shopware.com/forums/942607/suggestions/45651289
92 votesWe already started the further development and already added new statistics:
Added a new KPI “Promotion codes”
Added a new KPI “Sales by manufacturer”
Added a new KPI Sales by country
Added a new KPI Best selling products
UI enhancements and technical improvements
-
Change configuration category layout / homepage configuration
Recurring support tickets indicate that the shop's homepage configuration is not centralized enough.
Firstly, the shop's homepage is determined by the category layout. Secondly, the homepage can also be set within the category itself (under the "General" tab -> "Homepage" option).
These numerous different configuration options conflict with each other and lead to unnecessary support tickets. The configuration should therefore be simplified.
5 votes -
Quantity-based surcharges in Custom Products
Current Situation / Problem:
Custom Products allow merchants to offer additional services or configurations (e.g. sawing, drilling, processing) with fixed surcharges per selected option.
These surcharges are currently static and independent of the ordered quantity of the main product.While tiered pricing can be configured on the product level, it cannot be applied to Custom Product options or their surcharges.
Concrete Use Case
A merchant sells steel beams (e.g. HEB / HEA) and offers optional processing services via Custom Products.Example: Option “Sawing”
- Sub-options: Fixed cut, Center cut, Mitre cut
- Current behavior: fixed surcharge, e.g. €15 per cut
Desired behavior:
The price per cut should change depending on the ordered quantity of the main product, for example:- 1–3 items → €15 per cut
- 4–10 items → €10 per cut
- 11+ items → €7 per cut
The price tier is not based on the number of selected options, but on the product quantity in the cart.
Why Existing Features Are Not Sufficient:
- Advanced pricing on the product level applies globally to the product quantity, but does not affect Custom Product surcharges
- Rule-based surcharges can be enabled or disabled, but do not support tiered pricing
- Product variants are not a viable alternative because:
- They would result in a very large number of variants
- Custom Products are intentionally used for flexible, customer-specific configurationsBusiness Value / Benefits:
Relevant use case for:
- Metal processing
- Cutting and machining services
- Printing, engraving, personalizationKey benefits:
- Realistic representation of volume-based discounts for services
- Reduction of manual pricing agreements and individual offers
- Increased competitiveness for B2B shopsAvoidance of workarounds or external pricing logic
Current Situation / Problem:
Custom Products allow merchants to offer additional services or configurations (e.g. sawing, drilling, processing) with fixed surcharges per selected option.
These surcharges are currently static and independent of the ordered quantity of the main product.While tiered pricing can be configured on the product level, it cannot be applied to Custom Product options or their surcharges.
Concrete Use Case
A merchant sells steel beams (e.g. HEB / HEA) and offers optional processing services via Custom Products.Example: Option “Sawing”
- Sub-options: Fixed cut, Center cut, Mitre cut
- Current behavior: fixed surcharge, e.g. €15 per cut
Desired behavior:…
4 votes -
CMS-Element: Configuration options when embedding YouTube videos
When a YouTube video is embedded into an shopping experience using a CMS element, subtitles are automatically added, even though this feature is not active in the original video.
Therefore, it would be helpful to have configuration options for this within the CMS element.
2 votes
- Don't see your idea?