How the App Works: From Application to Approval
What you will achieve in this guide
Follow this step-by-step documentation to configure custom B2B registration forms, approval workflows, and customer tagging.
Rivio B2B Registration Forms collects storefront applications, applies approval rules or manual review, and onboards approved Shopify customers.
Before you begin
Open the app from the Shopify admin of the store you intend to configure. Have a test applicant email ready and decide who will review applications. A form, its storefront placement, and its approval settings are saved separately.
What happens at each stage
The storefront validates answers and receives the application. Approval rules evaluate the submitted answers in their saved order; the first matching active rule decides whether to approve, reject, or route the application for review. A reviewer can also decide an application manually.
Approval creates or reuses the Shopify customer by email, adds the form's approval tags, and can create a company, location, and contact when enabled. Notifications and integration events follow the relevant event. Pricing access, catalogs, payment terms, and tax settings must still be configured in the appropriate Shopify workflow.
Example
Application submitted → decision → customer upsert by email → approval tags → optional company → notifications and integration events.
Expected result
The received application, final decision, linked customer, approval tags, optional company, and relevant notifications can each be inspected as separate stages.
Limits and important behavior
- The first matching approval rule determines the decision.
- Manual admin, API, and automatic approvals send approval events to integrations; each approval event is sent once.
- Creating a B2B company does not assign catalogs, payment terms, or tax exemptions.
Troubleshooting and verification
Trace one reference through receipt, decision, customer link, tags, optional company, and destination event. Stop at the first missing result. A success message proves receipt, while an Approved status and linked records establish the later onboarding steps.
Screenshots to add
Screenshot placeholder: Capture the app screen or test result described in “How the App Works: From Application to Approval”. 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.