Dashboard → Settings → Tagging Rules
A rule that looks correct but isn’t tagging anything almost always comes down to one of a handful of causes. Work down the list below, then check the questions underneath. For how rules are built and rerun, see Tagging Rules.
Why a Rule Isn’t Applying
Work down this list:- The rule is new and hasn’t been rerun — rules aren’t retroactive.
- The record has a tag someone added by hand, which hides automatically applied tags.
- The record’s GL code was edited by hand, so GL code rules skip it permanently.
- Another GL code rule already claimed the order, and only one GL code is kept.
- A not equals or not contains condition is being used on records whose field is empty.
- One condition is failing. All conditions must be true for the rule to fire.
- For a load rule, order-level conditions are checked against the load’s linked orders, so a load with no linked orders won’t match them.
Common Questions
I created a rule — why didn't it tag my existing orders?
I created a rule — why didn't it tag my existing orders?
Rules aren’t retroactive. Open the rule and use Rerun Rule to apply it to records you already have.
Why did I get two rules when I only made one?
Why did I get two rules when I only made one?
You ticked both Order and Load in guided mode, which creates one rule per record type. This is expected — the conditions are checked differently on each.
Why does my order only have one GL code when two rules match it?
Why does my order only have one GL code when two rules match it?
A record keeps a single GL code, no matter how many GL code rules match. Rewrite the rules so they don’t overlap.
How do I change a rule?
How do I change a rule?
Create the corrected rule, then delete the old one. Rules can’t be edited in place.