• EMAILS AND NOTIFICATIONS • SETUP GUIDE

Understanding Merchant and Applicant Emails

By Rivio Support Team
1 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

Rivio B2B Registration Forms can notify merchants about new applications and send applicants received, approved, and rejected emails.

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.

Four separate notification events

New-submission notifications go to the merchant and configured recipients. The application-received auto-responder goes to the applicant. Approval and rejection messages report decisions and are different from receipt confirmation.

The received message's subject, content, and text/HTML format can be customized. Decision templates are fixed, with an optional rejection reason and relevant rule email controls. Sender configuration is shop-wide rather than an approval rule.

Reference and examples

Message Recipient/event Customization
New submission Merchant and configured recipients Recipient configuration
Application received Applicant on receipt when enabled Subject, text/HTML message, supported variables
Approved Applicant for enabled approval notification Fixed template; review rule email option
Rejected Applicant for rejection notification Fixed template with optional reason

Example

Submit once, then approve the application after reviewing the received message. Use inboxes you control for merchant and applicant recipients.

Expected result

New-submission notifications, the received auto-responder, and the approval message correspond to separate events.

Limits and important behavior

  • Only the application-received auto-responder is fully editable in the documented feature set.
  • Approval and rejection messages use fixed templates.
  • Receiving an application email is distinct from confirming an approval integration event.

Troubleshooting and verification

If a message is absent, confirm its event occurred and the relevant email option was enabled. Check the recipient’s spam folder, available email logs, and SMTP verification if using your own sender. A received application and a delivered email are separate results.

Screenshots to add

Screenshot placeholder: Capture the app screen or test result described in “Understanding Merchant and Applicant Emails”. 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