Understanding Approval, Rejection, and Rule Email Settings
What you will achieve in this guide
Follow this step-by-step documentation to configure custom B2B registration forms, approval workflows, and customer tagging.
Review which applicant emails are sent when Shopify B2B applications are approved or rejected manually or through rules.
Before you begin
Identify which message you are testing: merchant notification, application-received auto-responder, approval, or rejection. Confirm the recipient address and sending method before changing message content.
Decision messaging follows the chosen path
Approval and rejection emails tell an applicant the outcome. For rules, review the setting that controls whether the applicant receives an email. Manual rejection can include an optional applicant-facing reason.
The decision templates are fixed; the editable application-received message cannot replace them. Test approval and rejection separately so receipt mail is not mistaken for proof that the decision notification was sent.
Example
Submit two dummy applications. Approve one and reject the other, reviewing the relevant rule email option if automation is used.
Expected result
Each test receives the appropriate enabled decision email; fixed decision templates are distinct from the editable received auto-responder.
Limits and important behavior
- Approval and rejection templates are fixed in the documented feature set.
- The approval email links to the store login page; it is not a Shopify customer-account activation invitation.
- Integration events and applicant emails are separate parts of the workflow.
Troubleshooting and verification
If the decision exists but no message arrived, check the relevant rule’s email setting and the applicant address. Approval and rejection templates are fixed; use the application-received auto-responder for editable copy and the rejection reason for case-specific explanation.
Screenshots to add
Screenshot placeholder: Capture the app screen or test result described in “Understanding Approval, Rejection, and Rule Email Settings”. 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.