The Number component collects a numeric value — quantities, amounts, scores, percentages — with built-in formatting and range validation so you don't have to police the format yourself.
The problem: a free-text "quantity" field lets people type anything — words, stray characters, inconsistent formatting — which downstream automation then has to clean up or guess at.
In practice: the person enters a real order quantity, and the field shows it with the configured suffix so both sides know what unit it's in:
The value: downstream automation (pricing, inventory checks, approvals) receives a clean, validated number it can act on immediately — no parsing or guessing required.
Open your form in Form Studio.
In the component panel, find Number under Input.
Drag it onto the canvas, or click it to add it to the end of the page.
Click the field to open its settings.
1. wewe
2.
Content
Label – the question or field name.
Default Value – a starting numeric value, fixed or bound to existing data.
Required – blocks submission until a number is entered.
View only – shows the value without allowing edits.
Formatting
Prefix / Suffix – text shown before or after the number, e.g. $ as a prefix for currency, or " units" as a suffix for quantities.
Decimal precision – how many digits to show after the decimal point.
Decimal separator – choose the character used for decimals (e.g. . or ,) to match your audience's locale.
Thousands separator – turn on grouping (e.g. 1,000 vs 1000) for easier reading of large numbers.
Validation
Range validation presets – quick presets for common ranges, like 0–100 (percentages), 0–1 (ratios), or "must be zero or greater."
Formula validation – for anything the presets don't cover, write a validation formula (for example, requiring the number to be less than another field's value).
A numeric input that formats itself as they type (prefix/suffix, separators) if you've configured those.
Inline validation feedback if their entry falls outside the allowed range.
Use Suffix for units (" units", "%") instead of asking people to type them — it keeps the underlying value clean and numeric.
Combine Decimal precision with the right Range validation preset for percentages or ratios so the display and the validation agree (e.g. 0–100 with 0 decimal places for a whole-number percentage).
If a number needs to be validated against another field on the form (like "end quantity must be greater than start quantity"), use Formula validation rather than trying to force it with a range preset.
