- or
329 results found
-
Filters for Flow Builder
For bigger lists of any entity, it is super important to have filters in order to find efficiently what you are looking for. We have filters for the Products, Customers, Rule Builder overviews and probably in many other menus as well.
There for we should most definitely also have this kind of filtering also for the Flow Builder overview.
Finding the flow you are looking for only with the search is a pain. Try to search for the flow "Order placed". Since the string "order" is part in 90% of all flows out of the box, you will not be able to find it but will need to filter manually through the list of flows again.
For bigger lists of any entity, it is super important to have filters in order to find efficiently what you are looking for. We have filters for the Products, Customers, Rule Builder overviews and probably in many other menus as well.
There for we should most definitely also have this kind of filtering also for the Flow Builder overview.
Finding the flow you are looking for only with the search is a pain. Try to search for the flow "Order placed". Since the string "order" is part in 90% of all flows out of the box, you will not be…
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.
-
Improved coupon code generation: Reuse of patterns & exclusion of certain characters
Problem:
Currently, coupon templates (e.g., SHOP-{random}) can only be used once. If the same template is used in a subsequent campaign, Shopware prevents its creation with a message indicating that the template already exists.Furthermore, it is not possible to exclude specific characters from the random code, which can lead to potential confusion (e.g., I vs. l or 0 vs. O).
Solution/Request:
A pattern may be used multiple times as long as no duplicates are created in the generated codes.During generation, the system only checks whether a code already exists, not whether the pattern has already been used.
Optional configurable exclusion list for specific characters.
Relevance increases with the growing number of parallel voucher campaigns (marketing, promotion, campaign management). Customers with f.e. 400+ promotions are having a very difficult time due to the current situation.
Problem:
Currently, coupon templates (e.g., SHOP-{random}) can only be used once. If the same template is used in a subsequent campaign, Shopware prevents its creation with a message indicating that the template already exists.Furthermore, it is not possible to exclude specific characters from the random code, which can lead to potential confusion (e.g., I vs. l or 0 vs. O).
Solution/Request:
A pattern may be used multiple times as long as no duplicates are created in the generated codes.During generation, the system only checks whether a code already exists, not whether the pattern has already been used.
Optional…
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 additional items in returns management
Currently, no additional new items can be added to a return. It would be great if this option were available, for example, to add return costs that cannot be processed via the shipping costs.
3 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.
-
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, eine physische und eine digitale.
Den Lagerbestand kann ich trotzdem im ParentProduct als im Hauptprodukt ändern, aber es hat keine Auswirkung auf den Lagerbestand der physischen Variante (die digitale hat ja sowieso 0, weil unendlich).
Entweder sollte dies auch vererbar sein, so dass man den Lagerbestand im Elternprodukt einstellen kann ohne in die physische Variante gehen zu müssen, oder aber, es sollte im Elternprodukt ausgegraut werden, da sowieso keine Funktion.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.
-
Rule Builder: add company name as condition
Please add company name to the rule builder (contains / does not contain) as new condition.
Why: if merchants want to block company to checkout / block payment methods etc.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 the GMV extension more transparent
As can be read in the forum and tickets, many customers are skeptical about the GMV extensions and what happens in the background.
Customers would install the extension if, for example, there was a preview function of the transfer and a log of exactly when what was transferred.
This transparency would enable Shopware to reach more customers.
5 votes -
Dynamic Access: Rule based product images
It would be great, if we could use the Dynamic Access feature to further customize, when which images are supposed to be displayed in the storefront.
Examples:
- As an erotic store for example, I want to show different pictures depending on if someone is logged in or not.
- Depending on the time of the year, I want to display different pictures automatically.
- Different Customer Groups should see different pictures.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.
-
Advanced search for additional information in the order overview
In connection with the order overview, there is a customer need to be able to search for external order references (e.g., Amazon/eBay order numbers or member names).
This data is currently only stored in the "additional information" of the order during import and is therefore not found in the standard administration search function.Requirement/Use Case:
Customers want to be able to search the order overview for these external references to more easily find orders for accounting or support.
Typically, this involves fields such as:
Amazon order number
eBay order number
eBay username
Current status:
The standard search in the order overview only accesses certain indexed fields (e.g., order number, customer, email).
Data in "additional information" or unstructured JSON fields is not searched.
Proposal for a possible technical solution:
Introduction/use of custom fields at the order level (customFields.amazonordernumber, customFields.ebayordernumber, etc.),
Indexing these fields in the DAL search or in the Elasticsearch index,
Expanding the admin order overview with filter/search fields for these custom fields.
Assessment:
This use case is often relevant for Shopware 5 migrations and multi-channel integrations (Amazon, eBay, Idealo, etc.). A generic solution for making such external references searchable would therefore be desirable or should at least be documented as an extension interface.In connection with the order overview, there is a customer need to be able to search for external order references (e.g., Amazon/eBay order numbers or member names).
This data is currently only stored in the "additional information" of the order during import and is therefore not found in the standard administration search function.Requirement/Use Case:
Customers want to be able to search the order overview for these external references to more easily find orders for accounting or support.
Typically, this involves fields such as:
Amazon order number
eBay order number
eBay username
Current status:
The standard search in the order…
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.
-
Treat quote management like a normal checkout.
Quotes should be treated in the same way as normal orders. Availability rules such as items in the shopping cart do not work in Quote Management, because the items are not in the shopping cart when placing an quote order.
Third-party extensions that extend the checkout process often also not work, either partially or completely.
2 votes -
Convert digital <> physical products
It should be possible to convert a physical product to digital or the other way around in the product module
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.
-
Net margin of sold products
Hello,
We are missing the net margin of products sold that day. It would be cool if this could be added e.g. an average margin for all sales and a margin per supplier and/or product.
(price.net-purchaseprice.net)/price.net
Thanks in advance!
Kind regards,
6 votes -
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.
-
Logging of running flows
For monitoring the system and testing flows, it is extremely important that there is logging in the admin area.
The following information is important for logging:
- When did the flow run?
- Which trigger was activated?
- Which data was fed into the flow?
- Which data was decisive for the conditions?Zapier provides excellent logging for such systems.
3 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.
-
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.
-
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
- Don't see your idea?