• APPROVAL RULES AND B2B SETUP • SETUP GUIDE

Understanding Conditions and All / Any Matching

By Rivio Support Team
2 min read

What you will achieve in this guide

Follow this step-by-step documentation to configure custom B2B registration forms, approval workflows, and customer tagging.

EXPECTED SETUP TIME 5-10 Minutes
COMPATIBILITY All Shopify Themes & Plans
TECHNICAL DIFFICULTY Zero Code Required

Choose field-specific conditions and All or Any matching for Shopify application approval rules.

Before you begin

Review the form’s questions, saved approval settings, and active rule order. Have controlled applications ready for matching and nonmatching cases. Check Shopify B2B availability separately before enabling company creation.

Match operators to the answer type

The selected field determines the available operators. Number supports numeric boundaries such as at least and between; Email adds domain matching; choice fields support membership comparisons; checkbox fields distinguish any, all, and none of the selected options.

All requires every condition in the rule to match. Any requires one or more. Neither setting changes the first-match rule order. When testing numeric thresholds, include values below, at, and above the boundary.

Reference and examples

Sample data All: country US and volume at least 1000 Any: country US or volume at least 1000
US / 1500 Match Match
US / 500 No match Match
Other country / 1500 No match Match
Other country / 500 No match No match

Additional reference

Common Condition Families

Field Examples
Text Equals, contains, starts with, is one of, is empty
Email Text comparisons plus email domain is
Number Greater than, at least, between, less than, at most
Dropdown or radio Equals, is one of, is not one of, is empty
Checkboxes Contains any, contains all, contains none, checked
File upload File provided or file not provided

Example

Combine Country equals US and Annual volume at least 1000. Test US/1500, US/500, and a different country/1500 under All, then compare Any.

Expected result

All requires both conditions; Any requires at least one, producing different matches for the same data.

Limits and important behavior

  • Available operators adapt to the field type.
  • File conditions check provided/not provided rather than verifying a document’s content.
  • Basic field visibility has different limitations from approval-rule matching.

Troubleshooting and verification

If All and Any produce unexpected matches, test each condition independently using the submitted answer. All requires every condition; Any requires at least one. With Number, check boundary operators; with checkboxes, distinguish contains any, contains all, and contains none.

Screenshots to add

Screenshot placeholder: Capture the app screen or test result described in “Understanding Conditions and All / Any Matching”. Include the relevant saved settings and the example outcome so readers can connect the explanation to the interface. Use dummy applicant details and mask any secrets.

Related guides