Flow Delay Suite

About the Extension

Reci Flow Delay Suite extends the Shopware Flow Builder with powerful and reliable time-based automation.

It allows flow actions to be delayed by minutes, hours or days and executed safely in the background.
Unlike simple delay plugins, Reci Flow Delay Suite focuses on transparency, control and real-world usability.

Why Reci Flow Delay Suite?

Many automated processes such as payment reminders, dunning steps or order follow-ups run in the background and are difficult for employees to track.

Reci Flow Delay Suite makes these processes visible and controllable by displaying all scheduled actions directly on the order.

Employees can immediately see:

• which automated actions are currently pending
• when the next action will be executed
• which process step the order is currently in

This is especially valuable for accounting, support and operations teams.

Typical Use Cases

• Payment reminders and dunning processes
• Order follow-ups after defined time periods
• SLA-based customer notifications
• Transparent monitoring of automated processes

Business Hours & Execution Windows

Reci Flow Delay Suite supports executing delayed actions within defined business hours.

For each delay, you can define:

• allowed weekdays (e.g. Monday to Friday)
• a specific time window (e.g. 08:00–12:00)

If the calculated execution time falls outside the defined window (for example Sunday at 04:00), the action is automatically shifted to the next valid execution time.

This ensures that:

• customer-related actions are not executed at night or on weekends
• processes follow internal business hours
• automated workflows appear professional and controlled

Built for Production Use

Execution is handled asynchronously via scheduled tasks.
The plugin includes safeguards to prevent duplicate or parallel executions and is designed for productive environments and large order volumes.

Migration from Existing Delay Plugins

Reci Flow Delay Suite provides a technical migration option for existing delay plugins.

The migration is intentionally performed via the console to ensure maximum control and safety.

Migration process:

1. Simulation (Dry-Run)
         Existing delays are analysed and potential conflicts are reported.
   No data is modified.
2. Final Migration
         Existing delays and pending (not yet executed) actions are migrated.
         Duplicate executions are prevented.  

Note: Migration is performed via the console and is intended for technically experienced users or agencies.

Planned Enhancements

• Dynamic execution dates based on entity fields (e.g. customer birthday or custom fields)
• Additional preconfigured process templates for dunning and time-based workflows
• Further control options for more advanced automation scenarios

Feedback & feature requests:
Is a feature missing or do you have a specific use case?
Feel free to contact us. We carefully review feature requests and actively incorporate practical requirements into further development.