AND vs OR in Checkout Rules — Condition Match Type

Condition match type

In short

Condition Match Type decides whether every condition must be true (All) or just one (Any). All makes a rule narrower as you add conditions; Any makes it broader.

Applies to

Any rule with two or more conditions

Doesn't apply to

Rules with one condition — All and Any behave identically

The two options

All Conditions Pass

AND · narrower with each condition

✓ Cart subtotal ≥ 500
✕ Shipping country is BR

Rule does not fire

One condition fails, so the rule does not fire.

Any Condition Passes

OR · broader with each condition

✓ Cart subtotal ≥ 500
✕ Shipping country is BR

Rule fires

One condition passes, so the rule fires.

Same conditions, opposite results.

Setting	Meaning	Effect of adding conditions
Only apply when All Conditions Pass	Every condition must be true (AND)	Fires less often
Only apply when Any Condition Passes	One is enough (OR)	Fires more often

The most common logic mistake

A rule is firing too often, so you add a second condition to tighten it — and it fires even more. That is an “Any” rule doing exactly what it was told. Check the match type before touching the conditions.

Which one you want

Ask what the conditions describe.

Use All when they describe one situation from several angles: “orders over $500 and going to Brazil”. Both must be true for the rule to be right.

Use Any when they are alternatives: “customers tagged wholesale or customers tagged distributor”. Either qualifies.

Most rules want All. Any is the exception, and worth a second look whenever you pick it.

Worked examples

Goal	Conditions	Match type
Hide COD on large orders to one country	Cart subtotal ≥ 500 · Shipping country is BR	All
Hide COD for either of two customer groups	Customer tag is one of `risky` · Customer tag is one of `chargeback`	Any
Free shipping first for domestic logged-in customers	Shipping country is US · Customer is logged in	All

Note the second one is better written as a single condition — Customer tag is one of risky, chargeback — since Is one of already means “any of these”. Reach for Any only when the conditions are genuinely different fields.

With one condition

All and Any behave identically. The setting only starts to matter at two.

Frequently asked

My rule fires too often. Should I add another condition?

Only if the match type is All. On Any, adding a condition makes it fire more often, not less — which is the opposite of what most people expect.

Can I mix AND and OR in one rule?

No. A rule is entirely All or entirely Any. For genuinely mixed logic, split it into two rules — they stack.

What if I add no conditions at all?

The rule applies to every checkout, whatever the match type says.