All posts

Shopify Tag Orders Automatically: Every Condition

Use Auto Tags to tag Shopify orders automatically by defining an order rule with conditions, AND or OR logic, tags, an enable flag and priority. The app evaluates rules in near real time from Shopify webhooks, and matching orders receive the tags you chose. This reference separates order-level conditions from line-item matching, then explains how duplicate tag triggers affect the plan quota.

How do you build an order rule?

Set the resource type to orders, add the condition set, choose the tags, set the enable flag and assign priority. Lower priority numbers run first, and the default priority is 10.

Select AND or OR for the condition set. The documented rule examples include total > $500 and country = US OR country = CA.

Comparison of AND and OR matching requirements for order rules

Keep the rule disabled while you prepare it if you do not want it processing events yet. Duplicating a rule creates a disabled copy with “(Copy)” appended to its name.

Which values, sizes, sources and risks can match?

Use this group when order value, size, discount input, source or risk should decide the tag. Each item is a separate condition in the order rule.

  • Order total: use the order value, including the documented total > $500 example.
  • Line item count: match the number of line items on the order.
  • Discount codes: match the codes attached to the order.
  • Source name: match the source recorded for the order.
  • Risk level: match Shopify’s risk level for the order.

Order total covers the value of the complete order, while line item count covers its size. For a product title or vendor inside the order, use line-item matching instead.

Which status and shipping conditions can tag an order?

Use status and shipping conditions for payment, fulfillment and destination decisions. Order rules expose five separate fields in this group.

  • Fulfillment status
  • Financial status
  • Shipping country
  • Shipping province
  • Shipping city

Country, province and city remain separate conditions, so select the geographic level named in your rule. Fulfillment status and financial status also remain distinct, letting the rule test the state it actually needs.

Which customer fields can tag the order?

An order rule can test customer email and customer tags. Keep the resource type set to orders when the tag belongs on the order; select customers as the resource type when you want to tag the customer.

Customer email supplies the email condition on the order, while customer tags let an existing customer tag participate in the match. These fields can join order total, status, shipping or another order condition in the same AND or OR condition set.

Turn on Reset on Mismatch when the app should remove a rule’s tags after the resource stops matching that rule. The setting removes the tags that rule added rather than unrelated tags on the resource.

How do line-item matches and duplicate tags count?

Use “line_items.title contains …” or “line_items.vendor = …” when the tag depends on what is inside the order. These conditions inspect line-item title or vendor, while line item count tests how many line items the order has.

Several rules can apply the same tag. The tag appears once on the resource, but every rule trigger counts as an operation against the plan quota. One tag applied counts as one operation, and the quota resets monthly.

Billing & Usage shows the current plan, this month’s usage against the limit, the last three months of usage and a progress bar. When the monthly quota runs out, rules stop processing new events and the app shows a warning banner; upgrading applies the larger quota immediately.

How do you test a rule before enabling it?

Save the rule disabled, run Data Reprocess against one resource ID, and check the result in the Activity Log before enabling the rule. This sequence tests the conditions against a specific existing order without enabling the rule first.

After that check, Data Reprocess can apply the new rule to historical orders by resource ID, date range or all resources. Shopify events trigger every rule; scheduled batch tagging uses Data Reprocess over a date range or Shopify Flow’s scheduled triggers.

The Activity Log records each rule trigger with a timestamp, details and a status of Success, Failed or Pending. Filter those entries by category, status or date range when you check the result.

More posts on Auto Tags are on the blog.

Read more posts