All posts

Shopify Tagging Rules Priority: Which Rule Runs First?

Shopify tagging rules priority controls evaluation order: the lower number runs first, and the default is 10. In SO: Auto Tags, overlapping rules do not compete for ownership of a tag. If several rules apply the same tag, the resource keeps one copy, while every rule trigger still counts against the plan quota.

Which priority is evaluated first?

Each rule contains a resource type, conditions, AND or OR logic, tags to apply, an enable flag and a priority. Priority places that complete rule in the evaluation order; it does not replace the rule's conditions.

A lower priority number is evaluated before a higher number. A rule left at the default uses 10, so any rule assigned a number below 10 is checked earlier.

Match logic remains separate from order. With AND, every condition must match; with OR, any one matching condition is enough. Evaluation can therefore reach several qualifying rules in sequence rather than selecting one exclusive winner.

What happens when rules apply the same tag?

Several matching rules can request the same tag. The tag appears once on the order, customer or product, but each rule trigger counts as an operation against the plan quota.

The deduplicated Shopify tag does not make the additional trigger free. Operation counting covers each tag applied, each resource cleaned and each modified resource in a bulk job, and the quota resets monthly.

Priority changes timing, not quota accounting. If two enabled rules still match and request the same tag, moving one earlier only changes which rule is evaluated first.

How do you reorder existing rules?

Give the rule that should be evaluated first the lower priority number. Leave another rule at 10 when its default position is suitable, or assign priorities that place the rules in the required order.

Use each rule's enable toggle if you need to keep it out of event processing while checking the order. Duplicating a rule creates a disabled copy and appends "(Copy)" to its name, giving you a separate rule to configure before enabling it.

Rule order can also move between stores with the rest of the configuration. Export all rules to a JSON file, import that file into the other store, then inspect the imported priority values before enabling the relevant rules.

How do two overlapping product rules run?

Product rules can evaluate vendor, product type, title, tags, price, compare-at price, minimum and maximum variant price, inventory quantity, status (active, draft or archived), published state, and created or updated date. Two rules can qualify through different fields and still request the same tag.

  • Earlier rule: a priority below 10, a matching vendor condition and the tag to apply.
  • Later rule: the default priority of 10, a matching product type condition and the same tag.
  • Result: the lower-numbered rule is evaluated first, the product holds one copy of the tag, and two triggers consume quota.

Changing the later rule to OR logic could broaden its match because any one condition would be enough. Keeping AND would require all of that rule's conditions, but its place in the sequence would still come from priority.

How do you test a priority change?

Data Reprocess can apply rules to a specific resource ID, a date range or all resources. A specific ID limits the check to one existing order, customer or product before you expose the rule to more matching resources.

Flow showing a disabled rule tested against one resource and checked in the Activity Log before enablement

Every rule trigger receives a timestamp, a status of Success, Failed or Pending, and details in the Activity Log. Filter those records by category, status or date range when several triggers sit close together.

The app supports this check without enabling the rule first: save it disabled, run Data Reprocess for one resource ID, and inspect the result in the Activity Log. Enable the rule after the recorded result matches the configuration you intended.

Where do you check the operation limit?

Billing & Usage shows the current plan, this month's usage against its limit, the last three months of usage and a progress bar. Check that page when overlapping rules produce more trigger operations than the number of distinct tags suggests.

Free costs $0 and includes unlimited rules, 200 tagger tags, 500 bulk operations, 500 cleaner operations and 10 AI rule generations per month. Basic costs $4.99 per month or $49.99 per year and includes 2,000 tagger tags, 3,000 bulk operations, 3,000 cleaner operations and unlimited AI rule generations.

Pro costs $14.99 per month or $149.99 per year, removes every operation limit, and adds Backup & Revert and priority support. If a limited plan uses its monthly quota, rules stop processing new events and a warning banner appears; upgrading applies the larger quota immediately.

More posts on the app are on the blog.

Read more posts