• FORM FIELDS AND CONDITIONAL LOGIC • SETUP GUIDE

How to Use the Checkboxes Field

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

Use Checkboxes for several choices that may apply to the same applicant. This guide explains setup, a practical example, and how to check the result on your Shopify storefront.

When to use it

Choose this type when you need several choices that may apply to the same applicant. Choose the type before configuring mappings, visibility conditions, or approval rules that depend on the answer.

Before you begin

Open the intended form in Rivio B2B Registration Forms and confirm its name and storefront slug. Inspect template fields and smart-block sub-fields so you do not ask for the same information twice. Use dummy details for your first test.

Set up Checkboxes

  1. In the form builder, select Add field and choose Checkboxes.

  2. Expand its settings and enter a clear label or heading, such as Product ranges of interest.

  3. Create independent choices that can sensibly be combined. Explain whether applicants may select several. If your workflow requires an answer, test how the available Required setting behaves on the published form.

  4. Drag the element into the intended position. If the form uses steps, review its assigned step.

  5. Select Save, preview the form, and confirm the actual storefront page loads this saved form’s slug.

Example

Question or content: Product ranges of interest

Example: Ceramics, Textiles, Lighting

Adapt this example to the information your team needs. Use help text to explain the expected answer, and require it only when your review process needs it.

Test and expected result

Submit one selection and then several. Compare the stored answers and test contains any versus contains all if using these choices in approval rules.

Expected result: the saved application contains the intended answer. Any configured visibility, rule, or mapping is checked separately; collecting an answer does not itself approve an applicant.

Limitations and important behavior

Checkbox rules distinguish contains any, contains all, contains none, checked, and not checked where available. Do not use a multi-select field when applicants must pick exactly one category.

Troubleshooting

If a rule accepts too many applicants, inspect contains any versus contains all and the rule’s separate All/Any grouping. A checked option records an answer; it does not itself prove informed consent or business eligibility.

Screenshots to add

  • Screenshot placeholder: Builder with Checkboxes expanded, showing Product ranges of interest and the applicable saved settings.
  • Screenshot placeholder: Dummy submission showing the example answer; include the storefront input if it helps explain selection or validation.

Related guides