Shopify Tag Rules: Write AND and OR Conditions

Use AND when every condition must match. Use OR when one matching condition is enough. SO: Auto Tags All-in-One applies this logic to rules for orders, customers and products, then evaluates enabled rules in near real time from Shopify webhooks.

Require every order condition with AND

Choose AND when each condition is a requirement rather than an alternative. An order matches only after every condition returns a match; one failed check prevents the rule from applying its tags.

The worked rule below combines two values already available to order rules. The order must exceed the stated total and carry the stated shipping country. An order meeting only the total does not pass this AND rule, and an order meeting only the country check does not pass it either.

Keep AND for a tag whose meaning depends on the complete set. Removing one condition broadens the match because the remaining checks become the whole requirement.

Accept either shipping country with OR

Select OR when several conditions describe acceptable alternatives. For the location example, set one condition to country = US and another to country = CA. An order matches when either country condition matches; it does not need to satisfy both.

OR changes the size of the matching set. Adding another alternative gives the rule another route to a match, while adding another condition to an AND rule adds another requirement.

Order contents can also supply conditions. A rule may test whether line_items.title contains a value or whether line_items.vendor equals a value. Use those fields when the tag depends on what the customer bought rather than the order destination or total.

Choose the order fields each rule tests

Order rules can test commercial values, order state, destination and customer data. The available condition vocabulary is:

• order total and line item count
• discount codes
• fulfillment status and financial status
• shipping country, shipping province and shipping city
• customer email and customer tags
• source name and risk level

Pick the field that represents the decision you intend to encode. A financial status condition answers a different question from a fulfillment status condition, while shipping city narrows location more than shipping country.

Set which matching rule runs first

Priority controls evaluation order when several rules can inspect the same event. It does not replace the conditions: each rule still has its own resource type, condition set, AND or OR mode, tags, enable flag and priority.

Assign the lower number to the rule you want evaluated earlier. Leave rules at the default when their relative order does not require a separate decision. Every rule also has an enable toggle, so its place in the priority order matters only while the rule is enabled.

Test one resource before enabling the rule

Save a new rule disabled, then use Data Reprocess with one resource ID. This applies the conditions to a controlled order without opening the rule to new events. Check the result in the Activity Log before you turn on the enable toggle.

The Activity Log records each rule trigger with its timestamp, status and details. Status is Success, Failed or Pending, and the log can be filtered by category, status and date range. These fields show whether the test ran and how it finished.

After enabling the rule, use Data Reprocess by date range or across all resources if the same rule must reach existing orders. Event-triggered rules handle new events; scheduled batch tagging uses Data Reprocess over a date range or Shopify Flow scheduled triggers.

Count operations when rules share a tag

Several matching rules can apply the same tag to one resource. Shopify shows that tag once, but each rule trigger counts as an operation against the plan quota. An operation is counted whenever the app modifies a resource, and one applied tag counts as one operation.

The quota resets monthly. When it is exhausted, rules stop processing new events and the app displays a warning banner. Review overlapping rules before leaving two versions enabled, especially when both can place the same tag on the same orders.

More posts about configuring and operating the app are available on the blog.