Why Didn’t an Approval Rule Match?
What you will achieve in this guide
Follow this step-by-step documentation to configure custom B2B registration forms, approval workflows, and customer tagging.
Check active status, saved conditions, field values, and rule order when a Shopify application receives an unexpected decision.
Before you begin
Record the affected store, form name, slug, application reference if available, and approximate time. Reproduce the issue once with dummy data and note the exact message before changing settings.
Compare the saved answer and the rule order
Check that the rule is active, saved, and using the field whose answer was actually submitted. Then compare the operator, value, All/Any relationship, and earlier active rules that may have already matched.
Test the exact boundary or choice combination that failed with a fresh application. Visibility logic does not decide approval, and a supplied file is not proof of business-document authenticity.
Reference and examples
| Check | Why it matters |
|---|---|
| Rule active and saved | Unready settings are not an active decision path. |
| Submitted value and field | Rule must refer to the actual saved answer. |
| Operator and boundary | At least differs from greater than. |
| All/Any | All can fail when one condition fails. |
| Earlier rule | First match can decide before this rule is reached. |
Diagnose and resolve the problem
Open the application and read its recorded rule decision.
Open the form’s Advanced settings and inspect the relevant rule.
Confirm the rule is Active and changes were saved.
Compare submitted values with the selected field types and operators.
Check All/Any matching and earlier rules that may win first.
Submit matching and nonmatching tests and verify the decision again.
Example
Set Annual volume at least 1000 with All matching and an additional country condition. Submit 1500 with a nonmatching country.
Expected result
The rule does not match because both conditions are required; inspect earlier rules before changing the operator.
Limits and important behavior
- The first matching rule wins.
- Basic visibility conditions do not control the approval decision.
- File provided is not a business-document verification check.
If you still need help
If the checks do not resolve the issue, contact support@rivioapps.com with the affected form or application reference, time, exact error, and what you already tested. Mask private applicant data and never include API keys or SMTP passwords.
Screenshots to add
Screenshot placeholder: Capture the relevant app screen for “Why Didn’t an Approval Rule Match?” after completing the setup. Show the controls used to open the application and read its recorded rule decision. Add a second screenshot showing the result of this check: Submit matching and nonmatching tests and verify the decision again. Use dummy applicant details and mask any secrets.
Related guides
- Why Is My Form Not Appearing on the Storefront?
- Why Are My Form Changes Not Showing?
- Why Can’t an Applicant Submit the Form?
- Frequently Asked Questions About Shopify B2B Registration Forms
If these checks do not resolve the issue, contact RivioApps Support with the form name, application reference where relevant, error, and time. Do not include passwords or access keys.
Was this article helpful?
Your feedback helps us continuously improve our setup guides and documentation.
Thank you for your feedback! Our documentation team reviews all suggestions.