- or
No existing idea results
- ~ No ideas found ~
1488 results found
-
Produktvergleich
EXPORT TOO SLOW!!!
The export from the product comparison is much too slow at >170k products. In SW5, it took me less than a minute for the PriceAndStock feed. Now it takes at least an hour. We need at least a half-hourly export.
Please fix this. Thank you.
2 votes -
Absolute discount should be possible per item
Currently it is not possible to give an absolute discount of e.g. 5€ on every item in the shopping cart but only a percentage discount or an absolute discount on the entire shopping cart.
It should be possible to give an absolute discount per item in the shopping cart.
4 votes -
Dynamic Access for Manufacturers
Dynamic Access is not yet available from manufacturers. It would be nice if there were an option to control the display of manufacturers in the front end via Dynamic Access.
2 votes -
EU Geo-Blocking Regulation
According to the EU Geo-Blocking Regulation (Regulation EU 2018/302), merchants must not discriminate against customers based on their residence or delivery country regarding access to goods and pricing.
Most legal interpretations agree that:
A unified net price across EU markets is compliant, and
Gross prices may vary depending on the applicable VAT rate,
as long as the underlying net price is identical.
However, Shopware currently forces the opposite approach:
It keeps gross prices constant, and recalculates net prices differently per country.
This makes it impossible to maintain a consistent net price across EU countries and can cause compliance concerns for merchants expanding their international sales.
For merchants selling to many EU countries, maintaining separate price rules is impractical and extremely time-consuming.
According to the EU Geo-Blocking Regulation (Regulation EU 2018/302), merchants must not discriminate against customers based on their residence or delivery country regarding access to goods and pricing.
Most legal interpretations agree that:
A unified net price across EU markets is compliant, and
Gross prices may vary depending on the applicable VAT rate,
as long as the underlying net price is identical.
However, Shopware currently forces the opposite approach:
It keeps gross prices constant, and recalculates net prices differently per country.
This makes it impossible to maintain a consistent net price across EU countries and can cause compliance concerns for…
1 vote -
AI-powered product recommendations for B2B reorders
Instead of classic recommendations like “You might also like,” B2B shop customers should proactively receive notifications about which products they are likely to run out of soon, based on their individual order history.
Example: “You will probably run out of this product in about 3 months.”:
- Configurable forecast periods (weeks/months).Especially useful for shops with high order volumes (several hundred orders per customer).
Benefit: Simplifies reordering, increases customer satisfaction, and can boost sales.
2 votes -
Modern, accessible email templates should be built into Shopware by default — just like Shopify
Right now, the standard templates are plain and outdated:
• Not fully responsive on all devices
• No real focus on accessibility (screen readers, contrasts, alt-texts)
• Hard to adapt to a shop’s corporate identityIn 2025, merchants expect more. Platforms like Shopify already provide beautiful, responsive, accessible templates out of the box — Shopware should do the same.
👉 Having this built in would save time, improve customer experience, and make Shopware more competitive. Please vote if you agree!
3 votes -
Create Rule via AI prompt
Instead of only creating rules manually, it would be cool if we could create the rules via prompt. So rather describing what the rule is supposed to do and then have it built for you, reducing the manual effort.
1 vote -
Möglichkeit, die Anrede in allen Formularen zu entfernen
Die Anrede sollte in allen Formularen entfernt werden, wenn man sie ausstellt.
Im Kontaktformular wird sie angezeigt, wenn man die Anrede im Registrierungsformular deaktiviert (Shopware 6.7.1.2).
Formulare sind ohne Anrede einfacher und schneller ausgefüllt. Viele Nutzer sind von der Auswahl der Anrede genervt.
The salutation should be removed in all forms if you display it.
It is displayed in the contact form if you deactivate the salutation in the registration form (Shopware 6.7.1.2).
Forms are easier and quicker to fill out without a salutation. Many users are annoyed by the choice of salutation.
2 votes -
Ensure “Success” build status means the environment is ready
In Shopware Native PaaS, a build from a commit SHA can sometimes show as “Success” even though the environment isn’t actually accessible and returns a 404 error. This causes downtime and confusion. The build process should only mark a build as “Success” once the environment is fully functional.
2 votes -
Avoiding errors with PayPal partial refunds
The PayPal API built into Shopware enables refunds with a single click. Unfortunately, in the hustle and bustle of everyday customer service, mistakes often occur with partial refunds—for example, instead of a $20 discount, the entire amount ($100) is accidentally refunded. This happens to every employee at least once a month because the entire amount is preset in the “Amount” field by default and it is easy to forget to adjust it.
Possible solutions:
1) The “Amount” field is empty and the amount must be actively entered.
2) The amount is highlighted in red.
2) A warning message appears: “Do you really want to refund the full amount?”
4) A second button with a less saturated color, “Partial refund,” is placed next to the blue “Refund” button.
Can Shopware or PayPal do anything about this, or is there already a solution?
The PayPal API built into Shopware enables refunds with a single click. Unfortunately, in the hustle and bustle of everyday customer service, mistakes often occur with partial refunds—for example, instead of a $20 discount, the entire amount ($100) is accidentally refunded. This happens to every employee at least once a month because the entire amount is preset in the “Amount” field by default and it is easy to forget to adjust it.
Possible solutions:
1) The “Amount” field is empty and the amount must be actively entered.
2) The amount is highlighted in red.
2) A warning message appears: “Do…
7 votes -
Allow importing only gross or net price with automatic calculation of the other value
It is currently impossible to import only an updated net or gross price without also providing the other price. The calculation of the missing gross or net price does not take place during import.
If one value is empty in the CSV or not mapped in the profile, the price will not update. No error or indication is shown that it failed.
If both net and gross prices, as well as the price.DEFAULT.linked value, are supplied, both prices will be set exactly as provided, but the gross/net link will not trigger recalculation. This can lead to broken scenarios where tax rates (e.g., 19%) are not respected.
Proposed improvement:
When importing prices and price.DEFAULT.linked = true is set, allow merchants to provide only one price (net or gross) and have Shopware automatically calculate the other based on the configured tax rate — exactly as it works when editing prices manually in the admin.It is currently impossible to import only an updated net or gross price without also providing the other price. The calculation of the missing gross or net price does not take place during import.
If one value is empty in the CSV or not mapped in the profile, the price will not update. No error or indication is shown that it failed.
If both net and gross prices, as well as the price.DEFAULT.linked value, are supplied, both prices will be set exactly as provided, but the gross/net link will not trigger recalculation. This can lead to broken scenarios where tax…
2 votes -
Exclude Variants From Sitemap If Canonicals Are Used
Please implement an option that allows to exclude variants from sitemap generation. Especially in cases where all variants are using a cononical which points to the main product it would be good to exclude these kind of entries, which all refer to the same product anyway.
3 votes -
Multi Inventory - Save multiple stock updates at once
Feature: Multi Inventory
If you have multiple warehouses in a warehouse group, at the moment you need to save the changes for every single warehouse one after the other. This does not feel intuitiv and slows down the process.
I have recorded this in a test environment:
https://www.awesomescreenshot.com/video/44727162?key=8481c10b30e8e71a1daeda1cee4be3daAs you can see this can be quite annoying.
In my opinion, it would be more user friendly if there would be one global save button for the multi inventory window than having to save every single change for every single warehouse.
2 votes -
Custom product descriptions per saleschannel
It would be nice to allow inserting a custom product description per saleschannel for products. This way it would be possible to easily adjust the voice of tone and the highlighted information to my target group (ex. B2B & B2C). It could be also relevant for other text fields in the product like the title.
1 vote -
AI generated content for all text fields
It would be helpful to have the option to create a text via AI (as it is possible in shop experiences and product desrciption) would be available to all text fields, including custom fields, when creating/editing a product.
1 vote -
B2B Components: Include divergent mail addresses in search results
Shop owners sometimes report having difficulties finding B2B root accounts when provided with little more than a mail address of an employee in case it is not conforming to the companies' mail structure.
For example:
Our B2B root account is company@example.com.
Our employee's mail address is employee@shopware.com.Since the mail addresses don't match, when searching for employee@shopware.com, we will find no results for customers. This is sometimes the case where entire departments have separate mail addresses like a purchase department.
So the request is to have an option to index employee mail addresses and associate them with the B2B account for search results.
Shop owners sometimes report having difficulties finding B2B root accounts when provided with little more than a mail address of an employee in case it is not conforming to the companies' mail structure.
For example:
Our B2B root account is company@example.com.
Our employee's mail address is employee@shopware.com.Since the mail addresses don't match, when searching for employee@shopware.com, we will find no results for customers. This is sometimes the case where entire departments have separate mail addresses like a purchase department.
So the request is to have an option to index employee mail addresses and associate them with…
1 vote -
Social Shopping / Product comparison: Media URL with sales channel domain
EN
We often receive enquiries about how image links in product comparisons or social shopping can be adjusted to use the domain of the exporting sales channel. There were already tickets for this in the old issue tracker: e.g. https://issues.shopware.com/issues/NEXT-17674.However, this ticket was then created last year https://github.com/shopware/shopware/issues/4807, reporting that CDN media were receiving the wrong domain.
Programme request:
Please adjust the URL determination for media so that the handling of media links follows the same pattern as the product links within a product comparison. Of course, it must be possible to resolve the link. CDNs must also be taken into account, whereby the request was also made that it should be possible to resolve the domains per sales channel.According to tests in Shopware 6.7.4.2, the domain from APP_URL is used during export; no adjustment to other sales channels is made. Neither AI nor humans can find any information in the (dev) documentation as to whether and, if so, how it is possible to change this behaviour. If there are already settings options for the media link, it would be necessary to document these clearly and display them in the search.
DE
Es kommt öfter die Nachfrage, wie in Produktvergleichen oder Social Shopping die Bildlinks so angepasst werden können, dass sie die Domäne des exportierenden Verkaufskanals nutzen. Da zu gab es im alten Issuetracker bereits Tickets: z.B. https://issues.shopware.com/issues/NEXT-17674.Jedoch wurde im letzten Jahr dann dieses Ticket erstellt https://github.com/shopware/shopware/issues/4807, worin gemeldet wurde, dass CDN Medien die falsche Domain erhielten.
Programmwunsch:
Bitte die URL Ermittlung für Medien so anpassen, dass die Behandlung von Medienlinks dem gleichen Schema folgt wie die Produktlinks innerhalb eines Produktvergleichs. Natürlich muss der Link aufgelöst werden können. Außerdem berücksichtigt werden müssen naturlich CDNs, wobei hier auch der Wunsch geäußert wurde, dass es ebenfalls möglich sein soll die Domänen pro Verkaufskanal aufzulösen.Gemäß Versuchen in Shopware 6.7.4.2 wird beim Export die Domäne aus der APP_URL verwendet, eine Anpassung an andere Verkaufskanäle erfolgt nicht. Weder KI noch Mensch finden in der (Dev-)Dokumentation Hinweise, ob und wenn ja wie, eine Änderung des Verhaltens möglich ist. Falls es bereits Einstellmöglichkeiten für den Medienlink gibt, wäre es notwendig diese verständlich zu dokumentieren und in der Suche anzuzeigen.
EN
We often receive enquiries about how image links in product comparisons or social shopping can be adjusted to use the domain of the exporting sales channel. There were already tickets for this in the old issue tracker: e.g. https://issues.shopware.com/issues/NEXT-17674.However, this ticket was then created last year https://github.com/shopware/shopware/issues/4807, reporting that CDN media were receiving the wrong domain.
Programme request:
Please adjust the URL determination for media so that the handling of media links follows the same pattern as the product links within a product comparison. Of course, it must be possible to resolve the link. CDNs must…1 vote -
Admin content language selection
When you currently access an overview in our Admin (e.g. Product overview), the content will always be shown in the system default language, no matter what your admin user setting is. I have attached a screenshot, where you can see, that the menus overall are all in english but the content is showing the german language instead, since it's the default system language.
This really annoying since it forces me to switch in every menu the content language back to english.
My suggestion would be to take the language settings of the admin user into account and always show the content also in that language.
When you currently access an overview in our Admin (e.g. Product overview), the content will always be shown in the system default language, no matter what your admin user setting is. I have attached a screenshot, where you can see, that the menus overall are all in english but the content is showing the german language instead, since it's the default system language.
This really annoying since it forces me to switch in every menu the content language back to english.
My suggestion would be to take the language settings of the admin user into account and always show the…
1 vote -
API extension: Make trial status for plugin rentals queryable
For extensions with usage-based features (e.g., character quotas, API limits, etc.), it would be very helpful to be able to query the current trial status of a plugin rental via API.
Specifically, the following scenario applies:
For plugins that unlock the full range of functions during the trial month (e.g., a translation plugin that can translate almost the entire shop), we are increasingly observing that users take advantage of the free month to translate the entire shop once and then cancel. Without a technical way to recognize the trial month, it is difficult to limit this fairly.A simple flag would be desirable, e.g., isTrialActive, which can be queried via API. This would allow us to activate a transparent limitation during the trial period and automatically unlock full functionality after it expires.
Example application:
During the trial month:
- quota of, for example, 100,000 characters.
- All functions can be tested realistically.
- However, the free trial month is not used as a full “free full version.”After the end of the trial: Automatic release of the full quota/scope with active rental
Such a trial flag would make it possible to design fair trial periods – both for merchants (realistic testing) and for developers (protection against abuse) – without complicated workarounds or external billing logic.For extensions with usage-based features (e.g., character quotas, API limits, etc.), it would be very helpful to be able to query the current trial status of a plugin rental via API.
Specifically, the following scenario applies:
For plugins that unlock the full range of functions during the trial month (e.g., a translation plugin that can translate almost the entire shop), we are increasingly observing that users take advantage of the free month to translate the entire shop once and then cancel. Without a technical way to recognize the trial month, it is difficult to limit this fairly.A simple flag…
1 vote -
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 current billing period
- Billing interval (e.g., monthly, annually)
- Flag indicating whether it is a wildcard/stage environmentThis would allow usage-based features (such as search volume, API quotas, free requests, etc.) to be implemented correctly, transparently, and fairly— without having to implement a parallel subscription or billing solution alongside Shopware IAPs.
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
- Don't see your idea?