Condition groups
| Group | Inspects |
|---|---|
| Cart amount | Cart subtotal or total against a threshold |
| Customer | Customer status, and location checks |
| Location | Country, country lists, province or state codes |
| Cart contents | Whether specific items are in the cart |
| Per-product quantity | Quantity checks per product or variant |
| Dates | Date after, date before |
Each condition takes an operator and a value. How several conditions combine is set by the match type.
Location conditions
The most-used group, because limits so often vary by market.
| Condition | Value |
|---|---|
| Country | A single country |
| Country List | Several countries at once |
| Province / State | Comma-separated codes |
Date conditions
Date After and Date Before bound a rule in time — a sale window, a seasonal minimum, a holiday cap.
Use both, on All match type, to make a window. On Any they produce a rule that matches every date, which is a common and silent mistake.
Cart contents
Conditions that check whether particular products are in the cart, including a variant-aware check across all products. Useful for “this limit only applies when the order contains X”.
Confirm the behaviour you need on a mixed cart before going live — whether a condition wants any matching item or all items matching changes the outcome substantially.
Testing conditions
Build the rule, then test three carts: one that should match, one that should not, and one on the boundary. Conditional rules fail quietly — a condition that never matches looks identical to a rule that is switched off.