Flow Builder extension: Time delay (minutes, hours, days)
Technical Information
Highlights
-
Execute flows either after a time delay or at fixed times
-
Clear management of all delays
-
Supplied flows, rules and e-mail templates
Features
-
Flow Builder action for delaying by minutes, hours or days
-
Execution possible on a fixed weekday or calendar day
-
List of triggered flows waiting to be processed (after which they are removed from the list)
-
Manual execution of delayed flows possible
-
Several samples of useful flows, Rule Builder Rules and an e-mail template for demo purposes are included
-
Logs older than the defined period can be deleted automatically
Purpose of the plugin
Flow Builder is a powerful tool for automating workflows and business processes in Shopware. However, the standard version lacks the ability to flexibly define, schedule and centrally manage time-delayed actions.
This plugin extends Flow Builder with a delay action that not only allows flows to be delayed by minutes, hours or days, but also allows them to be executed at a fixed time. In addition to relative delays, it is now possible to specify that a flow should be executed on a specific day of the week or on a fixed calendar day of the month, for example. This allows recurring processes such as payment reminders, status checks or rating requests to be planned precisely.
All delayed flows are displayed in a central overview while they are waiting to be executed. After execution, they are automatically removed from the list. In addition, it is possible to execute waiting flows manually without having to wait for the delay to end. This facilitates testing and short-term adjustments to processes.
In addition, several preconfigured flows, rules, and email templates are provided to cover typical use cases and make it easier to get started. These include payment reminders, automatic status changes, and rating emails after an order has been shipped.
Installation
- Open Plugin Manager via Settings > System > Plugins
- Upload, install and activate the plugin
Plugin - Configuration:
6.7: Extensions > My Extensions > Flow Builder Delay > Configure
Configuration options:Enable log clean up
Under "Settings > Extensions > Flow Builder Delay" there is a table where all logs for this plugin are stored. If the switch is enabled, all logs older than the defined period will be deleted.
Flow Builder - Configuration:
6.7: Settings > Flow Builder > My Flows > Edit/Create flow
Configuration options:Delay (WAIT) action
In the three-dot menu, the delay time can be defined in days, hours, and minutes. In addition, the next execution can be specified. This can be set to the weekday and earliest/latest execution time.
Extension Configuration:
6.7: Settings > Extensions > Flow Builder Delay
Configuration options:Flow Builder Delay
All configured delays that are still waiting for execution are listed here. If they have been executed and are not set to repeat, they are removed from this list. The defined parameters of the action can be edited via the three-dot menu. In addition, it is possible to execute delayed flows manually without having to wait for the configured waiting time to expire.
Flow Builder Delay Log
This is a table that collects the information of all active and executed delays.
Additional settings
This leads to the settings mentioned first in this manual.
Templates:
These are for demo purposes only and can be edited as desired.Flows:
- ACRIS sends review email 7 days after the delivery status of an order is set to "Shipped"
Email with the product review will be sent 7 days after the delivery status "Shipped" is set in the Shopware admin for an order. - ACRIS sets order and payment status to "Canceled" after 14 days if the payment method is "Paid in advance" and the payment status is not set to "Paid"
For orders with payment status ≠"Paid" and payment method "Paid in advance", the order status and payment status will be set to "Canceled" after 14 days. - ACRIS sends payment reminder email after 7 days if the payment method is "Paid in advance" and the payment status is not set to "Paid"
Email with payment reminder will be sent if the payment method is "Paid in advance" and the payment status "Paid" has not been set after 7 days. - ACRIS sends payment reminder email after 7 days for orders with non-completed and non-cancelled payment and order status
Email with payment reminder will be sent for orders with non-completed and non-cancelled payment and order status after 7 days. - ACRIS sets the order status to "Canceled" after 24 hours if the payment status is set to "Failed"
For orders with payment status "Failed", the order status will be set to "Canceled" after 24 hours. - ACRIS sets the order status to "Canceled" after 24 hours if the payment status is set to "Canceled"
For orders with payment status "Canceled", the order status will be set to "Canceled" after 24 hours.
- ACRIS Flow Builder Delay: payment has not yet been made
Will be sent automatically after X days if the payment status is still open.
- ACRIS payment method "Paid in advance" and the payment status is not "Paid"
The rule checks whether the assigned payment method is "Paid in advance" and the payment status is not set to "Paid". It is applied in the corresponding flows. - ACRIS payment reminder for non-completed and non-cancelled payment and order
The rule checks that the assigned payment status is not one of the following: "Failed", "Chargeback", "Cancelled", "Refunded", "Paid" and that the order status is not one of the following: "Cancelled", "Done". It is applied in the corresponding flows.
Frequently Asked Questions
Yes. If delays are stored in a flow, they will still be executed even if the flow is inactive.
Option 1
Delete the flow entirely instead of just deactivating it.
Option 2
Manually delete the outstanding delays that are no longer required under ‘Settings > Extensions > Flow Builder Delay > Flow Builder Delay’.
| Version | Date | Compatibility | Changelog |
|---|---|---|---|
| 4.3.4 | 29 April 2026 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.3.3 | 14 April 2026 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.3.2 | 24 March 2026 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.3.1 | 10 March 2026 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.3.0 | 3 February 2026 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.2.4 | 29 January 2026 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.2.3 | 27 January 2026 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.2.2 | 26 January 2026 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.2.1 | 26 January 2026 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.2.0 | 26 January 2026 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.1.5 | 15 January 2026 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.1.4 | 15 December 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.1.3 | 24 November 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.1.2 | 24 September 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.1.1 | 22 September 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.1.0 | 18 August 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.0.5 | 8 August 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.0.4 | 30 July 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.0.3 | 11 July 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.0.2 | 3 July 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.0.1 | 7 May 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 4.0.0 | 5 May 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 3.3.0 | 4 February 2026 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.2.5 | 29 January 2026 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.2.4 | 27 January 2026 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.2.3 | 26 January 2026 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.2.2 | 15 December 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.2.1 | 24 September 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.2.0 | 18 August 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.1.11 | 8 August 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.1.10 | 4 June 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.1.9 | 2 May 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.1.8 | 29 April 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.1.7 | 14 April 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.1.6 | 8 April 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.1.5 | 7 April 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.1.4 | 1 April 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.1.3 | 25 March 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.1.2 | 14 March 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.1.1 | 5 March 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.1.0 | 20 February 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.0.7 | 5 December 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.0.6 | 29 October 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.0.5 | 28 October 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.0.4 | 12 September 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.0.3 | 6 August 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.0.2 | 4 July 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.0.1 | 12 June 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 3.0.0 | 19 March 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 2.6.0 | 18 August 2025 | >=6.5.0.0 < 6.6.0.0 |
|
| 2.5.0 | 13 March 2025 | >=6.5.0.0 < 6.6.0.0 |
|
| 2.4.3 | 5 December 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 2.4.2 | 29 October 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 2.4.1 | 6 August 2024 | >=6.5.0.0 |
|
| 2.4.0 | 17 January 2024 | >=6.5.0.0 |
|
| 2.3.12 | 21 December 2023 | >=6.5.0.0 |
|
| 2.3.11 | 20 December 2023 | >=6.5.0.0 |
|
| 2.3.10 | 13 October 2023 | >=6.5.0.0 |
|
| 2.3.9 | 10 October 2023 | >=6.5.0.0 |
|
| 2.3.8 | 9 October 2023 | >=6.5.0.0 |
|
| 2.3.7 | 4 October 2023 | >=6.5.0.0 |
|
| 2.3.6 | 22 September 2023 | >=6.5.0.0 |
|
| 2.3.5 | 12 September 2023 | >=6.5.0.0 |
|
| 2.3.4 | 5 September 2023 | >=6.5.0.0 |
|
| 2.3.3 | 30 August 2023 | >=6.5.0.0 |
|
| 2.3.2 | 27 July 2023 | >=6.5.0.0 |
|
| 2.3.1 | 21 July 2023 | >=6.5.0.0 |
|
| 2.3.0 | 19 July 2023 | >=6.5.0.0 |
|
| 2.2.0 | 12 May 2023 | >=6.5.0.0 |
|
| 2.1.1 | 10 May 2023 | >=6.5.0.0 |
|
| 2.1.0 | 9 May 2023 | >=6.5.0.0 |
|
| 2.0.0 | 30 April 2023 | >=6.5.0.0 |
|
| 1.5.7 | 4 July 2024 | >=6.4.18.0 < 6.5.0.0 |
|
| 1.5.6 | 27 March 2024 | >=6.4.18.0 < 6.5.0.0 |
|
| 1.5.5 | 6 February 2024 | >=6.4.18.0 < 6.5.0.0 |
|
| 1.5.4 | 4 October 2023 | >=6.4.18.0 < 6.5.0.0 |
|
| 1.5.3 | 5 September 2023 | >=6.4.18.0 < 6.5.0.0 |
|
| 1.5.2 | 24 July 2023 | >=6.4.18.0 < 6.5.0.0 |
|
| 1.5.1 | 19 July 2023 | >=6.4.18.0 < 6.5.0.0 |
|
| 1.5.0 | 21 June 2023 | >=6.4.18.0 < 6.5.0.0 |
|
| 1.4.7 | 22 April 2024 | >=6.4.0.0 < 6.4.18.0 |
|
| 1.4.6 | 5 September 2023 | >=6.4.0.0 < 6.4.18.0 |
|
| 1.4.5 | 27 July 2023 | >=6.4.0.0 < 6.4.18.0 |
|
| 1.4.4 | 21 June 2023 | >=6.4.0.0 < 6.4.18.0 |
|
| 1.4.3 | 14 June 2023 | >=6.4.0.0 < 6.5.0.0 |
|
| 1.4.2 | 13 June 2023 | >=6.4.0.0 < 6.5.0.0 |
|
| 1.4.1 | 13 June 2023 | >=6.4.0.0 < 6.5.0.0 |
|
| 1.4.0 | 12 May 2023 | >=6.4.0.0 < 6.5.0.0 |
|
| 1.3.1 | 10 May 2023 | >=6.4.0.0 < 6.5.0.0 |
|
| 1.3.0 | 9 May 2023 | >=6.4.0.0 < 6.5.0.0 |
|
| 1.2.0 | 27 April 2023 | >=6.4.0.0 |
|
| 1.1.0 | 26 April 2023 | >=6.4.0.0 |
|
| 1.0.0 | 29 March 2023 | >=6.4.0.0 |
|
Login
Einfach super!
Das Team von Acris kommuniziert völlig umkompliziert und bietet schnelle Hilfe.
Ich würde beim Support sogar mehr Sterne geben, wenn das möglich wäre.
Da können sich Andere eine Scheibe von abschneiden.
TOP! Grüße nach Linz
Idealer Plugin für die Automatisierung des Shops
Am Anfang hatte ich einige Probleme mit der Ausführung, der Team von ACRIS hat mir aber freundlich und sehr schnell geholfen um das Problem zu beheben. Ich kann es weiterempfehlen.
Schneller Support, PlugIn funktioniert perfekt und ist eine sehr gute Ergänzung für viele Flows
Herausragender Service. Hat schnell und kompetent ein Kompatibiltätsproblem behoben.
perfect plugin
I initially had a problem but the Acris team is very helpful. 5 stars for them, very serious company.
Unverzichtbares Plugin für alle die Workflows automatisieren möchten
Ein absolutes Muss für alle Shopbetreiber, die ihre Workflows automatisieren möchten! Dieses Plugin erweitert den Shopware-Standard basierend auf dem FlowBuilder und bietet die Möglichkeit, zeitverzögerte "Actions" durchzuführen. Dadurch können Bestellstatus und Zahlungsstatus automatisch gesetzt werden, ebenso wie zeitlich verzögerte E-Mails verschickt werden können, wie beispielsweise Zahlungserinnerungen oder Bewertungsanfragen nach erfolgreicher Lieferung und Nicht-Retournierung der Produkte. Dieses Plugin ist praktisch unverzichtbar für jeden Shopbetreiber!