• ORDER VALIDATIONS • SETUP GUIDE

How to combine validation conditions using ALL and ANY matching

By Rivio Support Team
1 min read

What you will achieve in this guide

Follow the feature-specific setup and testing instructions below. Check the supported pages and plan requirements before activating the feature.

EXPECTED SETUP TIME Varies by feature
COMPATIBILITY See requirements in this guide
TECHNICAL DIFFICULTY Zero Code Required

Group invalid-state conditions so a rule blocks the intended checkout cases.

When to use this guide

Use this when a rule blocks more customers than expected or fails to match a combination.

Before you begin

Open Apps → Rivio Checkout Customizer in the intended store. Use supported conditions from the current editor and record the exact amount, product, customer, or address basis before testing.

Worked example

For a wholesale minimum, block only when customer tag wholesale AND the eligible amount is below $100.

Step-by-step instructions

  1. Create or open the validation and add the supported wholesale tag condition.
  2. Add the amount condition less than 100 and record its basis.
  3. Choose ALL/AND where the editor exposes the grouping control. Both conditions must match this invalid-state policy.
  4. Enter an actionable wholesale minimum error, save, and activate at the intended run location.
  5. Test tagged/below, tagged/at, untagged/below, and untagged/at cases.
  6. For an ANY/OR policy, use a separate controlled example and explain that one invalid branch is enough. Do not change the wholesale rule to OR unintentionally.

Screenshot to add: The grouped invalid-state conditions and error message.

Verify the result

Test Expected result or check
Tagged buyer at $99 Both invalid conditions match; blocked.
Tagged buyer at $100 Amount condition no longer matches.
Untagged buyer at $99 Tag condition does not match.

Screenshot to add: Results for the four customer and amount combinations.

Limitations

  • Use grouping controls only where the editor exposes them.
  • Customer tags require available customer context.
  • An empty or broad invalid branch can block unintended checkouts.

Troubleshooting

Problem What to check
The expected result does not appear Check the saved state, exact feature configuration, supported page, and matching test inputs.
The preview and actual page differ Use a real test checkout, completed order, or signed-in account; editor data is simulated.
A change has an unexpected effect Repeat the same test with one relevant setting changed. Review other active rules before adding another copy.

Need help?

Email support@rivioapps.com with your store domain, feature name, saved settings, target page, and the expected and actual results. Include the test cart, order, or customer context needed to reproduce the issue.