• FORM FIELDS AND CONDITIONAL LOGIC • SETUP GUIDE

How to Use the Number 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 Number for a numeric amount you want to compare in approval rules. 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 a numeric amount you want to compare in approval rules. 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 Number

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

  2. Expand its settings and enter a clear label or heading, such as Expected annual purchasing volume.

  3. Explain the unit and period in the label or help text, such as units per year. Choose the available numeric validation settings and use a Number answer when your rule compares quantities.

  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: Expected annual purchasing volume

Example: 1000

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 999, 1000, and 1001 on controlled applications if the policy is at least 1000. Compare the rule result at the boundary as well as on either side.

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

A number field is not payment collection and does not calculate an order total. Avoid treating a registration number or a value with significant leading zeros as a quantity.

Troubleshooting

If a threshold rule behaves incorrectly, inspect whether the operator is greater than or at least and whether the rule uses All or Any. Confirm the original field is Number, not Short text.

Screenshots to add

  • Screenshot placeholder: Builder with Number expanded, showing Expected annual purchasing volume 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