- or
334 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 votesGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
Add newsletter subscription checkbox on account registration
Add the ability to activate newsletter subscribe checkbox on the account registration (/account/login and /checkout/register). So a switch in the admin settings (probably Log-in & sign-up or Newsletter), when it's turned on, a checkbox in the registration pages appear to subscribe for the newsletter, just above the CTA.
9 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 votesGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
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 voteGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
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 -
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 votesGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
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 voteGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
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 voteGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
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 voteGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
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 voteGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
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 voteGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
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 voteGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
Use Flow Builder for automatic refunds
If an order's status is changed to 'cashback', the Flow Builder should automatically trigger a PayPal refund for that order. This reduces the need for manual work and eases the burden on customer support.
1 voteGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
Create Quote-Documents before sending the Quote
Currently, in the quote module, generating quote documents is only technically possible when the quote is sent. This means that employees cannot review the details and final layout of the documents in advance or coordinate with colleagues. Especially in complex B2B processes, where quality assurance and coordination are essential, this causes unnecessary sources of error and additional effort.
Specific Improvement Proposal:
The function for generating quote documents (e.g., PDF) should be decoupled from the sending process.
It should be possible at any time—at the latest after saving the quote as a “draft”—to create, download, and review the final quote document before the quote is actually sent.
Optionally, a release workflow can be integrated, allowing, for example, the sales or back-office teams to approve or comment on the documents before they are sent to the customer.Added Value and Benefits:
Checkability: Employees can internally review quotes in advance and prevent errors in content or layout.
Transparency: The final document is visible for parallel approval processes before it is sent.
More Efficient Processes: Reduces returns, customer queries, and deletions due to faulty quotes, saving time in daily operations.
Currently, in the quote module, generating quote documents is only technically possible when the quote is sent. This means that employees cannot review the details and final layout of the documents in advance or coordinate with colleagues. Especially in complex B2B processes, where quality assurance and coordination are essential, this causes unnecessary sources of error and additional effort.
Specific Improvement Proposal:
The function for generating quote documents (e.g., PDF) should be decoupled from the sending process.
It should be possible at any time—at the latest after saving the quote as a “draft”—to create, download, and review the final quote document…2 votesGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
Make first- and last name optional for company accounts
First- and last name should be optional if setting up a new customer entry through the administration or by using the register form IF it is a company account.
32 votes -
Extended debugging e-mail/template dispatch
Many customers customize the email templates for their shop. It often happens that certain e-mail templates are no longer sent because, for example, variables are incorrect.
Troubleshooting the cause is then very difficult and time-consuming because:
- There are no errors in the log with indications of the cause.
- The e-mail test function still works with the e-mail template because variables are ignored.
As a result, the e-mail template and the variables have to be checked with a great deal of effort and there are a lot of support tickets for this, as customers quickly reach their limits.
In order to help customers and reduce the number of support tickets, it would therefore be useful to have extended debugging for sending emails. It should be possible to recognise from which line the e-mail dispatch fails.
This would allow the customer or the support team to name and recognise the line directly and, if necessary, find the error within seconds. This leads to less time for troubleshooting and frustration for customers.
Many customers customize the email templates for their shop. It often happens that certain e-mail templates are no longer sent because, for example, variables are incorrect.
Troubleshooting the cause is then very difficult and time-consuming because:
- There are no errors in the log with indications of the cause.
- The e-mail test function still works with the e-mail template because variables are ignored.
As a result, the e-mail template and the variables have to be checked with a great deal of effort and there are a lot of support tickets for this, as customers quickly reach their limits.
In order to…
24 votes -
Add separate configuration options to distinguish between “allow payment method change after checkout” and “allow retry of an aborted paymen
To better support payment workflows, especially with PayPal, it would be highly beneficial to separate two currently combined behaviors:
At the moment, the option “Allow payment method change after checkout” also controls whether customers can retry a previously aborted payment (e.g., PayPal popup was closed by mistake).
However, enabling this option on PayPal unintentionally allows customers to change from any other payment method (e.g., Prepayment/Bank Transfer) to PayPal after the order is placed. This causes serious issues in ERP/WMS integrations where such changes are not allowed.Proposed improvement:
Introduce two independent configuration options per payment method:“Allow switching to this payment method after checkout”
“Allow retrying an aborted payment for this payment method”
Benefits:
Customers can still complete PayPal payments if they accidentally aborted the payment window.
Merchants can prevent unwanted payment method changes (e.g., Prepayment → PayPal) that break ERP workflows.
Provides clearer, more predictable, and more granular control over payment behavior.
This enhancement would significantly improve flexibility and avoid unintended side effects in multi-payment setups.
To better support payment workflows, especially with PayPal, it would be highly beneficial to separate two currently combined behaviors:
At the moment, the option “Allow payment method change after checkout” also controls whether customers can retry a previously aborted payment (e.g., PayPal popup was closed by mistake).
However, enabling this option on PayPal unintentionally allows customers to change from any other payment method (e.g., Prepayment/Bank Transfer) to PayPal after the order is placed. This causes serious issues in ERP/WMS integrations where such changes are not allowed.Proposed improvement:
Introduce two independent configuration options per payment method:“Allow switching to this…
1 voteGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
Support for Spanish NIE Numbers in VAT/Tax ID Validation
In the merchant registration form (e.g., via the B2B Suite or customer registration), Spanish NIE numbers are currently rejected as invalid VAT/Tax IDs. However, the NIE (Número de Identidad de Extranjero) is the official fiscal identification number for foreigners in Spain and is accepted by the Spanish tax authorities.
A valid NIE follows this format:
Starts with X, Y, or Z → 7 digits → ends with a letter
Example: Y5432178PCurrently, the validation logic does not accept such values, blocking legitimate registrations from Spain-based users.
5 votes -
Add user friendliness to new language handling
Since Shopware 6.7.3.0 the language pack displays a warning, that it's recommended not to use it and that it will not work with 6.8.x anymore. Unfortunately the deinstallation of the language pack removes all translations included there (test with 6.7.4.0, with selection "Remove all data it even throws an exception).
The dev docs recommend this way https://developer.shopware.com/docs/resources/references/upgrades/core/translation/language-pack-migration.html. But not every customer is feeling comfortable being forced to use the command line. It is intended to activate / deactivate a language via the language itself. So why don't you add an install / uninstall routine in settings > language to process bin/console translation:install --locales it-IT linked to the switch's setting? Perhaps in addition whether the snippets should be installed / uninstalled?Since Shopware 6.7.3.0 the language pack displays a warning, that it's recommended not to use it and that it will not work with 6.8.x anymore. Unfortunately the deinstallation of the language pack removes all translations included there (test with 6.7.4.0, with selection "Remove all data it even throws an exception).
The dev docs recommend this way https://developer.shopware.com/docs/resources/references/upgrades/core/translation/language-pack-migration.html. But not every customer is feeling comfortable being forced to use the command line. It is intended to activate / deactivate a language via the language itself. So why don't you add an install / uninstall routine in settings > language to…1 vote -
Settings > Log-in & sign-up: Add company name field required
Use Case: We have two sales channels (B2B and B2C) and could set this up in the B2B sales channel.
2 votesGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
- Don't see your idea?