Understanding Automatic Approval Rules
What you will achieve in this guide
Follow this step-by-step documentation to configure custom B2B registration forms, approval workflows, and customer tagging.
Automate Shopify wholesale application decisions with ordered rules that approve, reject, or send a submission to manual review.
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.
One matching rule makes one decision
Rules compare submitted answers and choose Approve, Reject, or Send to manual review. They run in the saved order, and the first matching active rule wins. Several matching rules do not combine their decisions.
Use All when every condition is needed and Any when one acceptable condition is enough. Put exceptions ahead of broad approval rules. File presence is a technical condition; keep manual review for evidence that must be inspected.
Reference and examples
| Decision | Appropriate use | What it means |
|---|---|---|
| Approve | Your policy can be determined from accepted answers | Run approval onboarding effects. |
| Reject | A defined disqualifying condition | Decline the application. |
| Manual review | Evidence or exceptions need a person | Leave it awaiting review. |
Example
Create a rule that sends a selected buyer type to manual review and a separate rule for a qualifying numeric volume. Test each with controlled inputs.
Expected result
The first matching active rule determines the decision; rule order is part of the policy.
Limits and important behavior
- The first matching rule wins.
- A rule makes one decision: approve, reject, or manual review.
- The workflow has no bulk approve or reject action; use rules or individual review.
Troubleshooting and verification
If a decision differs from your policy, inspect the first matching active rule and its All/Any setting. If the decision is correct but access is missing, inspect the linked customer tags and any separate catalog or pricing configuration.
Screenshots to add
Screenshot placeholder: Capture the app screen or test result described in “Understanding Automatic Approval Rules”. 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
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.