50 results found
-
Delivery time as Rule Builder condition
The Rule Builder is missing the option to use the delivery time of a product as a condition. This would be a useful improvement, for example to use this as an availability rule for shipping methods.
5 votes -
Change flow trigger without entire flow is reset
Why is the whole flow always reset when I want to change the flow trigger? You create your flow and realize at the end that the trigger is the wrong one. Now you only want to adjust the trigger but the system deletes everything? why? that makes no sense?
Please change the function so that you can also delete the trigger without a reset.
4 votes -
Add flow trigger for document generation event
It should be possible to trigger a flow when a document is created for an order. It should be possible to select a trigger for each document type. We need a way to start a flow when a credit note (Gutschrift) has been issued and the credit note document has been created. Then we would like to add a tag to the this order or execute further actions.
3 votes -
Scheduling: Publish changes on a specific date and time
With this, you can schedule the publication of content such as products, categories, layouts, or promotional banners in advance. This allows you to automate time-sensitive campaigns, reduce manual effort, and ensure content goes live exactly when needed.
1 vote -
New Trigger for the Flow Builder: Customer Login
Currently, the Flow Builder does not offer a dedicated trigger for logging into a customer account, only in connection with the checkout process. This significantly limits automation possibilities.
Proposed Enhancement:
A new "Login" trigger that activates whenever a customer logs into their account – independently of the checkout process.Possible Use Cases:
Automatic tag assignment based on login frequency.
Customer group changes for logged-in users, e.g., granting access to exclusive content or discounts.
Automated email dispatch, e.g., a welcome back message after a long period of inactivity or targeted marketing campaigns.
2 votes -
Different flows for different forms
It is currently not possible to send different actions, for example different e-mail templates, if different forms are sent.
A differentiation through a rule in the Rule Builder or different flow triggers would be helpful here.2 votes -
Automatically syncing of "Pay in Advance" transaction
It would be a nice to have a feature that automatically tracks incoming "Pay in advance" payments and syncs those with the corresponding order, without manual effort.
For payments, where it's unclear, an overview for manual check up would be nice.
1 vote -
Select customer to preview dynamic product groups
In the case of a dynamic product group, the default values such as customer group etc. are always displayed in the preview. A dynamic product group, which should output products for customers with a specific additional field, does not display these. It would be desirable to be able to add a customer to the preview selection. This would make the preview options much more precise.
1 vote -
flowbuilder - flow can trigger a flow
It would be nice if one could trigger a flow from within another flow.
This would give the option to implement the programming concept of "functions" within the flowbuilder.
Our problem is, that our order placed flow is rather complex with a lot of rule checks,
it would be nice to split the trees up into differnt flows, that could be triggered.Other example, you have a flow "send discount code and tag customer"-flow, which could be used in different flows without the need to rewrite the actions.
7 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.
13 votes -
Customer Repository and Context:SKIP_TRIGGER_FLOW by default
The idea is to modify the injected context to the customer repository by SKIPTRIGGERFLOW.
During the creation of the integration plugin with any system in the customer synchronization process, we always have to remember to add Context:SKIPTRIGGERFLOW otherwise a lot of emails are sent to the imported customers.1 vote -
Dynamic urls for flow builder webhooks
It should also be possible to insert variables in the URLs to be called up in the webhooks in order to assemble them dynamically. Many interfaces require this, e.g. for DELETE requests. Example: DELETE https://example.com/api/v1/users/test@example.com
This example cannot currently be implemented, which is a major problem when using the function.1 vote -
rule-Builder
we are missing a rule-type "category"
So it should be possible to automate e.g. the visibility of categories in relation to products
- category visible when there is at least one active product
- visibel when products with special offers
- ....3 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/FroshSimultaneousEditNotification7 votes -
New Trigger in Flow Builder for Approved Reviews
I am encountering a limitation with the Flow Builder in Shopware 6, version 6.6.1.1. The only available trigger concerning reviews at the moment is "review got submitted". This does not align with the Rule Builder rule "Number of submitted reviews", which counts only approved reviews, and not all submitted reviews. I have reported this issue under the ticket number: NEXT-35548.
This misalignment prevents the effective monitoring of the total number of approved reviews after approval, and the total number of all reviews when a new review is submitted.
To address this, I would like to suggest the introduction of a…
4 votes -
Assign tag for newsletter recipients via the Flow Builder
It is not yet possible to automatically assign a tag to a newsletter recipient via the Flow Builder. This function would be desirable, as newsletter recipients can be assigned a tag anyway, just not automatically via the Flow Builder.
1 vote -
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.11 votes -
Hint when exceeding stock of a product
Hint when exceeding stock of a product while pressing on +
Now:
only when clearance sale is active and the add to cart button is exceeding stock a yellow hint box is shown, but not when exceeding stock when adding up with +-Button1 vote -
New customer - new option for the rule builder
I would like to be able to set rules in the Rule Builder:
New customer - yes/no
This would help with setting up many promotions.
I have found an option in the shopware store- but the manufacturer is no longer available in the shopware list. And realase date is set at a very out of reach level...
1 vote -
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.5 votes
- Don't see your idea?