When creating a workflow, you may wish to develop it further using a rule. Implementing a rule or two gives you the ability to tailor a workflow to your store and marketing strategies. Each rule comes with comparison statements such as is, matches any, is less than and is greater than which you can pair with the value of each rule. This gives you unique tools to create powerful logic that would usually require the skills of a developer to create.

You may have already discovered that the trigger you select dictates which actions you can pair with it. This is also true in the case of rules, as the trigger you choose will cause certain rules to become available. Since there are a wide range of rules to choose from, we’ve provided descriptions for each one to make life easier.

Combining Rules

You can easily add multiple rules by clicking the and button at the end of each rule. This modifies the workflow so that after a trigger fires, all rules must be satisfied for the workflow to run. This tailors your workflow to more specific circumstances, for example when a customer buys from the watches category and has more than two items in their order.

Alternatively, you can modify a workflow so that it runs if only one of your rules is satisfied. This is done simply by adding a new rule group. In this example, the workflow will run if a customer buys an item from the watches category or has more than two items in their order.

Types of Rules

As you may have noticed in triggers and actions, we divide rules into subcategories according to their function. The subcategories for rules are Order, Workflow, User, Cart, Guest, Subscription, and Referrals.


Order Item Count

  • Restricts workflow to customers who have a certain number of items in their order. Pair this rule with statements such as “is greater than” to target customers who buy many products at once.

Order Total

  • Restricts a workflow to orders which have a specified total cost. You could pair this rule with “is greater than 100” to target customers who have placed an order over that amount.

Order Items

  • Pair this rule with “includes” or “does not include” and enter in products from your store. The workflow will only run if an order includes the products you specify.

Order Item Categories

  • Restricts a workflow to orders which contain products from certain categories. Use this rule with the comparison statement “matches all of” to specify that the order must contain at least one item from every single category you select. Alternatively, including the comparison statement “matches any of” specifies that at least one item from any specified category must be included in the order.

Order Item Names – Text Match

  • Restricts workflow to orders which have items which contain particular keywords in the title.

Order Coupons

  • Use this rule to target orders that contain a specific coupon. You can also target orders that don’t use a specific coupon.

Order Payment Gateway

  • Targets a particular payment method. e.g. Stripe or Direct Bank Transfer.

Order Shipping Country

  • Restricts workflow to orders which are being shipped to a country of your choice.

Order Billing Country

  • Restricts workflow to a billing country of your choice.

Order Shipping Method

  • Allows you to target customers which require an order shipping method such as flat rate, free shipping, local pickup etc.

Order Shipping Method – text match

  • Restricts workflow to shipping methods which contain a keyword.

Order Has Cross-Sells Available

  • Targets orders with items that have cross-sells in your store. This can be used to ensure you don’t send a cross-sell follow-up email that doesn’t contain any valid cross-sell products.

Order is Customer’s First

  • Targets first-time customers.

Order Placed by Guest

  • Target orders that are placed by guest customers or target only registered users by setting the rule value to ‘No’.

Order is Subscription Renewal

  • Restrict workflow to orders that are / are not for subscription renewals. You could use this rule to send a thank you email or a discount coupon.

Order Customer Provided Note

  • Targets orders which have a note provided by the customer containing certain keywords.

Order Meta

  • Use this rule to target users based on their order meta/custom fields.

Order Item Meta

  • Use this rule to target users based on their order item meta/custom fields.


This Workflow’s Run Count for Order

  • This limits the workflow from triggering too many times for a customer’s order.

This Workflow’s Run Count for User

  • Limits the workflow so it only runs a certain number of times for each user. A useful precaution so that your customers don’t receive too many emails or coupons. For example, you can pair this with the comparison statement “is less than” and “1” to ensure that the workflow only runs once per user. Once the workflow’s run count has reached 1, this rule will prevent it from running a second time.

This Workflow’s Run Count for Guest

  • Identical to the previous rule, except it applies to guests in your store.


User Role

  • Restricts the workflow to users with certain roles. This is useful if your store uses multiple customer tiers such as VIP or Wholesale. You also might just want to test your workflow by restricting it to administrators only.

User Tags

  • Restricts workflow to users who have certain tags attached to their profile.

User Total Spent

  • Targets customers who have spent over or under a certain amount in your store.

User Order Count

  • Restricts workflow to customer who have placed a certain number of orders.

User Email

  • Targets customer email addresses that start with or contain a specific word

User’s Purchased Products (All Time)

  • This rule searches through all the user’s purchased products for a particular product.

User has Active Subscription?

  • Pair with “Yes” or “No” to target users with or without at least one active subscription.

User’s Order Statuses

  • Restricts workflow to users that have orders of a certain status e.g. the user has at least one completed order.

User Meta

  • Use this rule to target users based on their user meta/custom fields. Please note it will always return as false if user is a guest.


Cart Total

  • Total cost of the customer’s cart is a certain amount.

Cart Item Count

  • Number of items in cart is more than or greater than a certain amount.

Cart Items

  • include a certain product(s).

Cart Item Categories

  • Cart includes products from a certain category.

Cart Coupons

  • Coupons being used in cart match a particular type you have created in your store.


Guest Email

  • The guest’s email address contains a particular keyword. Alternatively, you can enter a particular customer’s exact email.

Guest Order Count

  • Targets guests who have placed a particular number of orders in your store. You could create a workflow that targets guests who have placed greater than 3 orders and encourage them to sign up.


Subscription Payment Count

  • Restricts workflow to subscribers who have paid for their subscriptions a certain number of times. You could use this rule to reward loyal subscribers with a special discount or VIP status.

Subscription Payment Method

  • Targets subscribers who pay using a certain method.

Subscription Meta

  • Use this rule to target subscribers based on their subscription meta/custom fields.


Advocate Approved Referral Count

  • Targets advocates who have had a specified number of referrals approved in your store.

Advocate Rejected Referral Count

  • Targets advocates who have made a number of rejected referrals.

Advocate Potential Fraud Referral Count

  • Although you may approve certain cases initially marked as potential fraud, using this rule can be a good way to ensure things don’t get out of hand. This rule targets advocates whose referrals have been marked as potential fraud a number of times.


Now that you’ve been introduced to the exciting capabilities of rules, it can be tempting to use them in every workflow in many exciting combinations. Please be careful about the different rules you set up, as certain rules can trigger hundreds of emails to be sent from a single workflow. Alternatively, if a workflow hinges on a certain rule with too narrow a spectrum, you may find yourself wondering why that particular workflow never runs. Here are some Do’s and Don’ts to watch out for.


Do include rules which help your workflows target high spenders. You can include a shipping country if you offer free shipping to that country for a limited time.

Do use a combination of rules to target customers purchasing from a certain category and then offer them cross-sells.

Do target high spenders who still have active subscriptions to single them out for rewards. Specify that “this workflow’s run count for user” shall be “less than 1” so that the workflow only runs once for each subscriber.


Don’t set a workflow run count to 1. This means the workflow will check if it has run in the past before allowing it to run for the first time. To be safe, pair this rule with a comparison statement such as “is less than” and “1”. This way, the workflow will stop once it has reach a run count of 1 for each user.

Don’t create a workflow which triggers for a product from a certain category but then include a rule which blocks orders with that category. This workflow will never run.

Don’t spam your customers by creating a workflow which fires for almost every single one of them. Repeatedly.

Don’t use impossible logic. You can’t have an order which has both 1 and not 1 item in it!

Don’t set a trigger which fires for a completed order and then include a rule restricting it to users who have never placed an order. A completed order will immediately register as a user order count of 1.

Don’t create a rule where the order item count is zero. An order will always have an item in it. And this workflow will never see the light of day.