Understanding Available Features and Limitations

Rivio B2B Registration Forms collects wholesale, retailer, trade, distributor, and other application responses on your Shopify storefront. Your team can review them manually or apply approval rules. On approval, the app creates or reuses the Shopify customer, adds your approval tags, and can create basic B2B company records.

All current app features are included in the Free plan, with unlimited forms and submissions. This guide separates what the app does from the Shopify and third-party configuration you still need.

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.

Features at a glance

Use this table to identify the app capability that fits your workflow. A feature being available does not mean it is already configured for your form.

Form and storefront limitations

The app collects applications; it is not a checkout, order-creation, or payment-collection form. A Quote Request records requirements for your team to quote separately.

Custom CSS is supported, but custom JavaScript is not. Conditional visibility supports one condition per field, without AND/OR groups or skipping steps. Approval rules have their own All/Any logic, which is a different feature.

• Uploads have a hard maximum of 20 MB per file. Each field can restrict allowed types and set a lower size limit. Passing upload validation does not verify the document contents.
• No automatic closing of a form after a set number of entries or on a closing date is established in this feature set.
• reCAPTCHA v2 checkbox is supported; v3, hCaptcha, and Cloudflare Turnstile are not part of this setup.
• Built-in storefront text is translated. Your custom questions, help text, and email content still need appropriate language content.

Approval and Shopify B2B limitations

Applications are reviewed individually or decided by rules; there is no bulk approve/reject action in this feature set. The first matching active rule determines the decision, so multiple matches do not combine into several decisions.

Company creation is basic onboarding. The app does not assign B2B catalogs, price lists, payment terms, or tax exemptions. A customer tag does not itself grant wholesale pricing, discounts, or content access.

• Submitted company tax ID, phone, and website remain available in the submission under the documented persistence limits; do not assume every Company answer is written to the Shopify company record.
• Approval mail is not a Shopify customer-account activation invite. Configure the appropriate account/login workflow separately.
• Only the application-received auto-responder is fully editable. Approval and rejection templates are fixed, with an optional rejection reason and relevant rule email settings.
• No Shopify Flow triggers or actions are part of the documented app feature set.
• Rejecting a previously approved application removes app-added tags and deletes the company the app created. Inspect those records before reversing a decision.

Integration, API, and analytics limitations

Spam is not forwarded to integrations. Email-marketing connections need an applicant email. Integrations run in the background, so a destination failure does not mean the application was not received. Check the app record and external destination separately.

The API covers submissions, not form creation or editing. Its rate limit is 60 requests per 60 seconds per key; a 429 response provides Retry-After. Use the current in-app documentation or Postman collection for exact paths and payloads.

• A/B setup uses a JSON settings box and supported design/theme keys. It does not run different approval policies or arbitrary JavaScript.
• Each visitor keeps a design variant. Evaluate views, submissions, sample size, and significance before declaring a winner.
• Analytics tracking does not block a submission if tracking fails. Views, submitted applications, approvals, and sales are different measures.
• AI scoring reads text answers, not uploaded files. Sidekick drafts and links; a person reviews and saves or approves in the app.
• Email and webhook logs are documented as retained for seven days. Export information your process needs within the available workflow.

What changed in the latest release

Google Sheets is production-ready for all shops, with Google-approved drive.file authorization. Create new spreadsheet creates and connects a file in the merchant account; Choose existing spreadsheet uses Picker through a secure time-limited link. Merchants can select the destination tab, see the file name/link, reconnect old-scope access, and disconnect to revoke access. Sync errors are logged.

Customer-segment creation/update is available from form settings. Changing approval tags shows a warning; update the segment query through the action. Duplicating a form does not copy the original segment link.

Manual admin, API, and automatic approvals now all send approval events to integrations, with each approval emitted once. Customer upsert by email preserves an existing name, phone, and tags. Built-in storefront text and country names are translated across the 20 supported languages with English fallback. The blank navigation response, particularly on Integrations, now recovers automatically.

Example: a wholesale onboarding workflow

A brand wants a business email, store website, resale document, and expected annual purchasing before approving retailers. Start with Retailer / Stockist, review the generated questions, and add only the qualification fields the reviewer needs.

1. Publish the form and add its slug to the Wholesale form block on the application page.

2. Keep document-sensitive cases under manual review; a File provided rule does not validate the certificate.

3. Set the intended approval tags and use Create customer segment to create the matching saved Shopify query.

4. Connect a Google spreadsheet and choose Applications as its destination tab.

5. Submit a controlled test, inspect its recorded answers and sheet row, then approve it and inspect the customer/tag/optional-company result.

6. Configure any catalog, terms, pricing access, or marketing workflow in the corresponding Shopify or connected service settings.

This setup demonstrates the app capabilities without assuming that receiving an application verifies the business or that adding an approval tag completes the entire B2B selling configuration.

Troubleshooting and verification

If the dashboard opens but no form appears on your storefront, installation has succeeded; finish form publication and block placement. If you cannot open the app, check the signed-in store and your Shopify app permissions first.

Screenshots to add

Screenshot placeholder: Capture the relevant app screen for “Understanding Available Features and Limitations” after completing the setup. Show the controls used to publish the form and add its slug to the Wholesale form block on the application page. Add a second screenshot showing the result of this check: Configure any catalog, terms, pricing access, or marketing workflow in the corresponding Shopify or connected service settings. Use dummy applicant details and mask any secrets.

Related guides

• Getting Started with Rivio B2B Registration Forms
• How to Install Rivio B2B Registration Forms
• Understanding the Dashboard and Setup Guide