Shopware Flow Builder: No-Code Automation Guide

The Shopware Flow Builder is one of the most powerful tools for e-commerce automation without coding knowledge. Since Shopware 6.4, merchants can visually map complex business processes as workflows - from automatic order confirmations to fraud detection. Companies adopting workflow automation typically achieve 60% ROI within the first 12 months (Forrester) and save over 500 hours per year of manual work (Shopware). This guide shows how to use the Flow Builder strategically, which automations every shop needs and where the no-code solution has limitations.

What Is the Shopware Flow Builder?

The Flow Builder is a visual no-code tool within the Shopware 6 administration for configuring business processes as automated workflows. Available since Shopware 6.4 in Commercial, Rise, Evolve and Beyond editions, it follows a clear logic: a trigger initiates the workflow, conditions evaluate prerequisites, and an action executes the desired operation.

Unlike traditional programming, the Flow Builder requires no coding skills. Shop managers drag and drop building blocks to create workflows that run reliably around the clock. Automating routine tasks can reduce order processing errors by up to 70% (McKinsey), as manual inputs and transcription errors are eliminated.

Triggers, Conditions and Actions in Detail

The three fundamental building blocks of the Flow Builder form the backbone of every automation. Understanding these elements is essential for creating effective workflows that match the specific requirements of your online shop.

Triggers

Triggers are the events that start a flow. Shopware provides a range of predefined triggers covering the most common business events.

• Order placed - The most commonly used trigger, firing with every new order
• Payment status changed - Responds to incoming payments, refunds or payment failures
• Customer registered - Starts welcome workflows for new customers
• Delivery status changed - Automates shipping notifications and tracking updates
• Cart abandoned - Enables recovery emails for abandoned carts
• Contact form submitted - Automatically routes inquiries to the appropriate department

Conditions

Conditions are filters that determine whether the subsequent action is executed. They enable precise control and prevent actions from responding identically to all events.

Actions

Actions are the actual operations executed when conditions are met. They range from simple email dispatches to complex integration calls.

• Send email - Automatic dispatch of confirmations, notifications or marketing emails
• Add/remove tag - Label customers or orders with tags for later segmentation
• Change status - Automatically update order, payment or delivery status
• Create document - Automatically generate invoices, delivery notes or credit memos
• Send to ERP - Transmit order data to SAP, Microsoft Dynamics or other ERP systems
• Trigger webhook - Call external systems via HTTP requests, e.g. Slack notifications or CRM updates

5 Automations Every Shop Needs

Based on practical experience with Shopware projects, five automations typically have the greatest impact on efficiency and revenue. Together, they can automate 45% of recurring e-commerce tasks (McKinsey).

1. Abandoned cart recovery: When a customer leaves the cart, the Flow Builder sends a reminder email after a defined period with the abandoned products. These flows typically generate additional revenue that would otherwise be lost. A follow-up discount code can be sent after a second delay. More on checkout strategies.
2. VIP customer tagging: For orders above a defined threshold (e.g. 200 euros), the Flow Builder automatically assigns a VIP tag. This tag serves as a condition in further flows for exclusive offers, prioritized support or event invitations, enabling more targeted communication.
3. Automatic invoice generation: Once an order reaches "paid" status, the Flow Builder creates the invoice as PDF and emails it to the customer. This eliminates manual steps and ensures timely delivery. For B2B customers, invoice formats can be customized.
4. Fraud detection alerts: Suspicious orders - unusual values, first-time orders with express shipping, or mismatched addresses - trigger internal alerts. The Flow Builder sets these to "manual review", warns the team and requests customer verification, protecting against fraud without disrupting regular orders.
5. Post-delivery review requests: After shipping, the Flow Builder waits a defined period (typically 7-14 days) and sends a personalized review request. Customer reviews are a significant SEO factor and build trust. Automation ensures no request is forgotten.

Flow Builder vs. Rule Builder: When to Use Which

Shopware offers two complementary tools with the Flow Builder and the Rule Builder. Both work rule-based but differ fundamentally in their scope and functionality. For an effective Shopware strategy, it is important to deploy both tools purposefully.

In practice, both tools work together: the Rule Builder defines customer groups and conditions, while the Flow Builder reacts to events and initiates processes. Example: the Rule Builder gives B2B customers 10% discount, and the Flow Builder sends a welcome package after the first B2B order.

Integration with External Systems

The Flow Builder reaches its full potential when combined with external systems. Via webhooks and the Shopware Admin API, third-party systems can be seamlessly integrated into automated workflows. Various integration patterns are available for custom integration development.

When using webhook integration, note that the Flow Builder performs synchronous HTTP calls by default. For time-critical workflows, asynchronous message queues implemented via custom development are recommended to keep shop performance stable.

Limitations and When Custom Development Is Needed

Despite its versatility, the Flow Builder has limitations that should be considered for more complex requirements. A realistic assessment helps choose the right strategy between no-code configuration and custom plugin development.

• No visual debugging: There is no built-in way to step through flows or see where a flow breaks. Troubleshooting requires log analysis.
• Limited logic depth: Highly nested condition chains can become unwieldy. Beyond a certain complexity, a custom plugin is more maintainable.
• No native delayed actions: The Flow Builder responds to triggers immediately by default. Time-delayed actions (e.g. email after 7 days) require additional plugins or scheduled tasks.
• Performance at high volume: For shops with thousands of daily orders, extensive flow chains can slow processing. Asynchronous message queue processing is recommended.
• No conditional branching with else path: Flows support IF conditions but not full IF-ELSE structures. For alternative paths, separate flows must be created.
• No versioning: Changes to flows are not version-controlled. There is no built-in rollback, so backup strategies are advisable.

Step-by-Step Setup Guide

Setting up a flow in Shopware follows a structured process. This example demonstrates creating a VIP customer tagging flow for orders exceeding 200 euros.

1. Open administration: Navigate to Settings > Shop > Flow Builder and click "Create Flow".
2. Select trigger: Choose "Checkout > Order placed" as the trigger.
3. Add condition: Select "Order amount", set operator to "is greater than" with value 200.
4. Configure first action: Select "Add tag" and create or choose the tag "VIP Customer".
5. Add second action: Add "Send email" with a prepared VIP welcome email template.
6. Name and save: Give the flow a descriptive name like "VIP Tagging above 200 EUR" and save.
7. Test: Create a test order above 200 euros and verify tag assignment and email dispatch.
8. Set up monitoring: Regularly check Shopware logs for flow errors and document active flows.

Custom Flow Actions: Developing Your Own Actions via Plugins

The built-in Flow Builder actions cover many standard scenarios. However, when specific business logic is required, the Shopware Plugin API allows you to develop custom flow actions. These custom actions then appear as native building blocks in the visual interface and can be configured by shop managers without any programming knowledge.

The technical architecture of a custom flow action is based on the Symfony event system that underpins Shopware 6. Each action implements the FlowAction interface and defines which data it expects from the trigger context. Typical examples include automatic loyalty point calculation, synchronization of customer data with an industry-specific CRM system, or creation of custom documents in specialized formats.

<?php
// Example structure of a Custom Flow Action
class CustomVipNotificationAction extends FlowAction
{
    public static function getName(): string
    {
        return 'action.custom.vip_notification';
    }

    public function requirements(): array
    {
        return [OrderAware::class];
    }

    public function handleFlow(StorableFlow $flow): void
    {
        $orderId = $flow->getStore('orderId');
        // Custom business logic here
        $this->notifyVipTeam($orderId);
    }
}

For developing custom actions, a structured approach is recommended: define requirements with business stakeholders, develop a plugin prototype, test in staging, then deploy to production. Our e-commerce consulting supports this process from requirements analysis through to go-live.

Performance Optimization for Complex Flows

As the number of active flows increases, so does resource consumption in the shop infrastructure. Each flow is evaluated at its respective trigger, and for shops with high order volumes this can impact response times. According to Shopware documentation, the standard message queue processes up to 50 messages per run, but complex flow chains can generate multiple queue messages per order.

The most important measure for ensuring performance is using asynchronous processing via Shopware's message queue. By default, flows are executed synchronously, meaning the customer waits at checkout until all actions complete. By switching to asynchronous processing, flow execution is moved to the background, keeping the checkout responsive. This is particularly relevant for webhook calls to external systems, as network latencies can otherwise delay the ordering process.

• Configure message queue workers (minimum 2 for redundancy)
• Set flows with external API calls to execute asynchronously
• Set up monitoring for queue size - backlogs indicate performance issues
• Regularly deactivate unused flows to avoid unnecessary trigger evaluations
• With 30+ active flows: review hosting resources and scale if needed
• Check database indexes for frequently used flow conditions (order value, customer group)

For high-traffic shops, cloud-based hosting with automatic scaling during peak loads is recommended. Combined with optimized pagespeed settings and a sound flow architecture, stable performance can be maintained even with extensive automation.

ROI Calculation: What Does Flow Builder Automation Actually Deliver?

Investment in Flow Builder automation typically pays for itself quickly, though the specific ROI depends on order volume, team size and process complexity. Forrester estimates the typical ROI of e-commerce automation at 60% within 12 months, with savings coming from reduced personnel costs for routine tasks, lower error-related costs and additional revenue from automated marketing flows.

A mid-sized online shop processing 200-500 orders per day typically requires 2-3 full-time employees for manual order processing, invoice creation and email dispatch. By automating these processes, a significant portion of this working time can be saved. The freed-up capacity can then be deployed for value-adding activities such as customer consultation or strategic e-commerce optimization.