What is Rule Builder and how is it different from Flow Builder?

Rule Builder and Flow Builder solve two different problems inside Shopware. Rule Builder decides when something should apply. Flow Builder decides what should happen after an event occurs. In practice, Rule Builder acts like conditional logic for pricing, shipping, promotions, customer groups, or payment methods. Flow Builder handles automation tasks like sending emails, tagging customers, changing order states, or triggering external systems. Most medium and large Shopware stores end up using both together.

Think of Rule Builder as the decision engine behind your store configuration. You create conditions such as cart value, customer type, country, product category, or order count. Then Shopware checks those conditions everywhere rules are supported. Flow Builder sits one layer higher. It listens for events like “order placed” or “payment failed” and runs automated actions based on those events and rules.

How it works

Rule Builder is embedded across the Shopware admin. You’ll see it attached to shipping methods, promotions, dynamic product groups, CMS visibility, and checkout logic. A single rule can be reused in multiple places, which keeps stores easier to manage as they grow.

Flow Builder works more like an automation platform. You define a trigger event, optionally attach Rule Builder conditions, then add actions. For example, “when a B2B order exceeds €5,000, notify sales and tag the customer for manual review.” The trigger comes from Flow Builder. The conditional logic inside that flow usually comes from Rule Builder.