34 results found
-
Rule Builder administration improvements
Currently the rule builder has some usability traps that could be improved.
This is esp. important for merchants working with a lot of different rule with different users.11 votes -
deactivate emails to customers after status change globally
After manual status change in the orders, even if I delete all the flows in the shop, Shopware6 always asks me to send emails to the actual customers. I need settings the skip this step.
9 votes -
Admin Notification when multiple users working parallel
Backend Notification when multiple users working in parallel
Providing a way for shopware to handle multiple people editing the same
The following frosh feature (FroshSimultaneousEditNotification) for sw6 in the core
https://github.com/FriendsOfShopware/FroshSimultaneousEditNotification6 votes -
Mark rules as active/inactive in the Rule Builder
Improve the visibility of active and inactive status of rules within the Rule Builder.
It is possible to extend the list view to check where the rule is assigned but that clutters the GUI with unnecessary information.
An added red or green light would probably do the trick.
That would make it easier for the admin or editors to delete old and unused rules.6 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.5 votes -
Product Related Flowbuilder Reactions
Current problem: You cannot send e-mails with "back-in-stock" notifications or use mailings for your internal staff if products need to be reordered
Proposed approach: certain product related attributes should be triggerable in the flow builder5 votes -
More generic flow builder actions
The current order status triggers in the Flow Builder are limited, requiring users to set up individual triggers for each specific order status. To react to "any order status change" you would currently have to set up multiple identical flows.
We propose the addition of a more versatile "Order Status Changed" trigger that allows users to create workflows responding to any change in order status.
This applies to order status, payment status, delivery status, ... any fields that are currently very strict and could be handled more generally as well.3 votes -
Allow adding multiple values to multi-select fields (e.g. list of products, list of countries, etc.) by pasting a list
Currently, at many places in the administration, there is the option to use an auto-completer to add values to a field one at a time. An example for this would be "add products to a 'product is one of...' field in the rule builder or the selection of products assigned to a category.
It would be helpful to paste a list of identifiers (e.g. product numbers) into these fields and get them assigned in one go. Specifically with large lists, that would save a lot of "clickwork" in the administration. Some simple reporting (failures / successes) in a message window…
3 votes -
Retry logic for webhooks
If a webhook call in a Flow
Builder flow fails today, it is captured in a log, but no action is
taken on it beyond that. This makes the webhooks unreliable
as if there is ever a failure, the customer wouldn't know
without actively monitoring the logs. Adding a configurable
retry process (number of times to retry and retry interval)
would allow customers to have more confidence in using
Flow Builder webhooks.3 votes -
Flow Builder Trigger for Customer Feedback
There should be a trigger in the Flow Builder for customers who give a feedback. So it will be possible to send them an email automatically.
3 votes -
Disable Shop/Prices with Rules
As a shop owner I want to only show prices for certain customergroups and show the MRP to all other groups.
3 votes -
Event-/Ticketsystem
Implement an event-/ticket system to help merchants sell events and or tickets within one system.
A current struggle oftentimes is, that mixed baskets lead to difficulties in configurations.3 votesCurrently this will not be covered by Shopware. Most merchants using a Ticketsystem/selling events do have individual requirements that would be difficult to cover for a broad target group.
-
Ability to use data from the response to a webhook call
Description of the opportunity: In Flow Builder, the webhooks are effectively notifications only. By extending the capabilities to be able to consume the response from the calling system and pull information out of the response, we could do further no-code business logic rules in Flow Builder.
For example, as part of a shopper registration workflow, Shopware could potentially submit that information via webhook to System A, System A might make some decisions internally about what customer group that shopper should belong to and respond to the webhook with an answer. Based on the response, in the flow, Shopware could determine…2 votes -
Alerts for anomalies
As a shop owner, I want to be informed about anomalies in my shop. Example: At a normal day, the shop makes 100 offers per day. But in case of a price error the shop makes 1000 order per hour. For this it would be great so set "alerts" based on rule. Condition: "amount orders per second/minute/hour/day greater than 1000" > mailt to shop owner.
2 votes -
Rules by Referrer
As a merchant, I want to choose different layouts for a product detail page depending on the sessions referer, to address these customers optimally
Should be part of the session context and available in the conditions to decide which layout is choosen, depending on URL parameter2 votes -
Flowbuilder triggers creation of promotion
Current problem: you cannot create a promotion directly within the flow builder but have to configure many steps via tags to fulfill that purpose. That´s quite complicated and limits the customer loyalty options the flow builder could give to merchants.
Current workaround: set a tag as action in flow builder, reuse this tag on promotion level and in a separate step configure sending out an e-mail to customers with this promocode2 votes -
Select multiple Dynamic Product Groups
Current problem: you cannot assign multiple DPG to build a category. Therefore you have to define and create a category elsewhere and cannot do it dynamically within shopware.
2 votes -
Flowbuilder Webhooks UX Improvements
The current UX for setting up a Webhook is only understandable for a "technical" person.We should ensure, that its easy understandable even for non-technical people to set up a webhook in the flow builder.
2 votes -
Shopware as a marketplace tool
As a shop owner I want to use Shopware as a market place
so that merchants have the option to sell their goods through a platform.2 votesWe are currently not planning to set up Shopware as a market place.
To connect your store to several market places you can search for plugins or apps within our store.
-
Flowbuilder Timeframe Setting
Current problem: You cannot prepare campaigns or flows for a certain time period.
Current workaround: with rule setting for shopping experiences and or promotions you can already display certain content for a limited time period. However it would be handy to have the possibility to prepare whole campaign worlds upfront. For flows we do not have a workarount so far.
Hypothesis: By being able to set timeframes merchants can automate even more of their processes. Targeting of certain customer segments gets easier.
Possible scenarios: Black friday campaigning with landingpage, product visibility, e-mailings and promotion codesregular flows: every three months trigger…
2 votes
- Don't see your idea?