334 results found
-
Indication of orders created from quotes
It should be clearly visible whether an order was created from a quote.
Ideally, this information should be displayed directly within the order overview to allow quick identification.
If displaying this information in the order overview is not feasible, it should alternatively be available within the order details, for example via a dedicated field or a custom field.This improves transparency and makes it easier for users to distinguish regular orders from those originating from quotes, especially in B2B workflows.
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.
-
Cannot respond to comments if quote has been expired
While the customer who did set up a quote is still able to add new comments to a quote that already has been expired, the shop owner / admin cannot respond to these comments accordingly.
Either remove the possibility to add new comments (for the customer) on expired quotes or the shopw owner / admin should have the possibility to respond to those comments accordingly.
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.
-
Add notifications for new comments on quotes
Currently, new customer comments on offers are not actively communicated. An email or in-administration notification would ensure timely awareness and faster responses.
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.
-
Possibility to negate promotion combination exclusion or add a seperate inclusion
Currently I only have 2 options: "Prevent combination with other promotions" or "Do not combine with".
When I have e.g. 2 promotions which should work together but not with other promotions I would have to add all other promotions to the "Do not combine with" field which can be tediuos when having a lot of individual promotions.I would be nice to have either an option to negate the "Do not combine with" condition making it an inclusion or having a seperate inclusion field where both, exclusion and inclusion can be combined.
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.
-
Inconsistent Stock Management Between Parent and Variant Products
I have an item that comes in two versions, one physical and one digital.
I can still change the stock level in ParentProduct as the main product, but it has no effect on the stock level of the physical variant (the digital one has 0 anyway, because it is infinite).
Either this should also be inheritable, so that you can set the stock level in the parent product without having to go into the physical variant, or it should be greyed out in the parent product, as it has no function anyway.Ich habe einen Artikel, der hat zwei Varianten,…
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.
-
Include purchase history in search
EN:
Include purchase history in search like it is mentioned here: https://www.shopware.com/en/deep-search-powered-by-nosto/:
"70% of visitors are more likely to buy when search results match their purchase history."
DE:
Beziehe die Kaufhistorie in die Suche ein, wie hier beschrieben: https://www.shopware.com/de/deep-search-powered-by-nosto/:
„70% der Besucher kaufen eher, wenn die Suchergebnisse ihrer Kaufhistorie entsprechen. “
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.
-
Search of support tickets also at content level
The search in the account under Merchant > Support> Support Tickets should also be done at content level.
Currently, the search only runs through the ticket titles using the filter.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.
-
Hide inactive sales channels in selection fields
If a sales channel gets set to "inactive" it should no longer be visible in selection fields (e.g. field "visibility" on product level)
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 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.
-
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…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…
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…
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…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.
-
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…
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.
-
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…1 vote -
Improve Safety and Flexibility for Promotion Code Configuration
Context
In the current version of Shopware 6, when creating a new promotion, the field “Promotion code type” is automatically set to “No promotion code required”.
This UX choice was made intentionally to simplify creation of general cart-level discounts, which are the most common use case.However, this default selection can lead to unintended activation of promotions when a user forgets to change the option to “Fixed” or “Individual promotion code.”
In such cases, discounts may be applied to all customers instead of a limited target group, which can cause serious financial and operational issues.Problem
Users may overlook that…
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.
-
"not specified" salutation handling
This is handled rather inconsistently in Shopware. In some but not all places, if you leave out the salutation, Shopware searches the database for the "not_specified" entry that comes with the installation and inserts it if found. If also sometimes inserts it just for display in the Administration if the real salutation reference is null, so you wouldn't even know the real value without looking directly into the database, but again, not always.
Crucially, that "not_specified" entry can be changed and deleted at will, so there's no guaranteed meaning behind it.
Also, sometimes like in the contact form the salutation…
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.
- Don't see your idea?