Number Field

Number Options

• Default Value
  • What it does:
    • The Default Value setting allows you to pre-fill the number field with a specific value when the form loads. This value appears in the field before the customer makes any changes, and they can either keep it, modify it, or delete it entirely.
  • How to use:
    • Enter the exact numeric value you want to appear by default
    • Use defaults to provide starting values, common quantities, or suggested amounts
    • Defaults are editable – customers can change or delete them
    • The value must be within the min/max range and match the step increment
  • Use Cases:
    • Common Quantities: Pre-fill with the most frequently ordered quantity
    • Starting Points: Provide a reasonable starting value for measurements
    • Minimum Orders: Set default to minimum required quantity
    • Suggested Values: Guide customers toward typical or recommended amounts
  • Example Default Values:
    • Quantity field: `1` (single unit)
    • Weight field: `1.0` (1 kg)
    • Hours field: `2` (2 hours)
    • Measurement field: `10.5` (10.5 cm)
  • Best Practice:
    • Use defaults that are helpful and realistic. Choose values that most customers will use or that serve as good starting points. Avoid defaults that might mislead customers or cause them to overlook the field.
  • Technical Details:
    • Default values must be valid numbers
    • They must fall within the min/max range if specified
    • They should match the step increment (e.g., if step is 0.5, default should be 0.5, 1.0, 1.5, etc.)
    • Empty defaults are allowed – the field will start empty
• Minimum Value
  • What it does:
    • The Minimum Value setting establishes the lowest number that customers can enter in the field. This creates a lower boundary that prevents invalid or unrealistic values and helps ensure data quality.
  • How to use:
    • Enter the lowest acceptable numeric value
    • Consider your product constraints and business rules
    • Leave empty to allow any negative or zero values (if applicable)
    • The minimum must be less than the maximum value
  • Use Cases:
    • Quantity Limits: Set minimum order quantities (e.g., minimum 10 units)
    • Measurement Constraints: Define smallest acceptable measurements (e.g., minimum 1 cm)
    • Business Rules: Enforce minimum purchase requirements
    • Physical Limits: Prevent values that are physically impossible
  • Example Minimum Values:
    • Quantity: `1` (at least one unit)
    • Weight: `0.1` (minimum 0.1 kg)
    • Hours: `0.5` (minimum 30 minutes)
    • Distance: `0` (allow zero or positive values)
  • Best Practice:
    • Set realistic minimums based on your product capabilities and business requirements. Consider both technical constraints and customer expectations. For, Quantities 1 is usually appropriate. For measurements, consider the smallest practical value.
  • Technical Details:
    • Minimum values can be negative, zero, or positive
    • They work in combination with step increments
    • Values below the minimum are automatically adjusted or rejected
    • Empty minimum allows any value (including negative numbers)
  • Common Minimum Values by Use Case:
    • Quantities: 1 (single unit minimum)
    • Measurements: 0.1 or 0.01 (smallest practical unit)
    • Time: 0.5 (30 minutes minimum)
    • Weight: 0.1 (100 grams minimum)
    • Distance: 0 (zero or positive)
• Maximum Value
  • What it does:
    • The Maximum Value setting establishes the highest number that customers can enter in the field. This creates an upper boundary that prevents unrealistic or excessive values and helps maintain data quality and business constraints.
  • How to use:
    • Enter the highest acceptable numeric value
    • Consider your product constraints, inventory limits, and business rules
    • Leave empty to allow unlimited values (use with caution)
    • The maximum must be greater than the minimum value
  • Use Cases:
    • Quantity Limits: Set maximum order quantities (e.g., maximum 1000 units)
    • Measurement Constraints: Define largest acceptable measurements (e.g., maximum 100 cm)
    • Business Rules: Enforce maximum purchase limits
    • Physical Limits: Prevent values that exceed physical capabilities
  • Example Maximum Values:
    • Quantity: `1000` (maximum 1000 units)
    • Weight: `50` (maximum 50 kg)
    • Hours: `24` (maximum 24 hours)
    • Distance: `100` (maximum 100 km)
  • Best Practice:
    • Set realistic maximums based on your product capabilities, inventory availability, and business requirements. Consider both technical constraints and practical limits. For quantities, consider inventory levels. For measurements, consider physical constraints.
  • Technical Details:
    • Maximum values must be greater than minimum values
    • They work in combination with step increments
    • Values above the maximum are automatically adjusted or rejected
    • Empty maximum allows unlimited values (use carefully)
  • Common Maximum Values by Use Case:
    • Quantities: 1000 or 10000 (based on inventory)
    • Measurements: 100 or 1000 (based on product size)
    • Time: 24 or 168 (hours in day/week)
    • Weight: 50 or 100 (kg, based on shipping limits)
    • Distance: 100 or 1000 (km, based on service area)
• Increment Step
  • What it does:
    • The Increment Step setting defines the increment value between valid numbers in the field. This determines the precision and granularity of the input, controlling how values increase or decrease when customers use the spinner buttons or enter values manually.
  • How to use:
    • Enter the step increment value (e.g., 1 for whole numbers, 0.5 for half increments, 0.01 for two decimal places)
    • Consider the precision needed for your use case
    • The step must be a positive number
    • Step values determine what increments are valid (e.g., step of 0.5 allows 0.5, 1.0, 1.5, 2.0, etc.)
  • Use Cases:
    • Whole Numbers: Step of 1 for quantities, counts, or whole units
    • Half Increments: Step of 0.5 for measurements that allow half units
    • Decimal Precision: Step of 0.1 or 0.01 for precise measurements, weights, or financial values
    • Custom Increments: Step of 5 or 10 for bulk quantities or rounded values
  • Example Step Values:
    • Quantity: `1` (whole numbers only)
    • Weight: `0.1` (0.1 kg increments)
    • Hours: `0.5` (30-minute increments)
    • Price: `0.01` (cent precision)
    • Bulk orders: `10` (10-unit increments)
  • Best Practice:
    • Choose step values that match your product requirements and customer needs. For, quantities 1 is usually appropriate. Related to measurements, consider the smallest practical increment. For financial values, use 0.01 for cent precision.
  • Technical Details:
    • Step values must be positive numbers
    • They determine valid increments (values must be multiples of the step from the minimum)
    • Step works in combination with min/max values
    • Smaller steps allow more precision but may be harder to use
  • Common Step Values by Use Case:
    • Quantities: 1 (whole numbers)
    • Measurements: 0.1 or 0.01 (decimal precision)
    • Time: 0.5 or 1 (30-minute or hourly increments)
    • Weight: 0.1 or 0.01 (100g or 10g increments)
    • Financial: 0.01 (cent precision)
    • Bulk: 5 or 10 (rounded increments)
  • Step Value Examples:
    • Step 1: Allows 1, 2, 3, 4, 5… (whole numbers)
    • Step 0.5: Allows 0.5, 1.0, 1.5, 2.0, 2.5… (half increments)
    • Step 0.1: Allows 0.1, 0.2, 0.3, 0.4, 0.5… (one decimal place)
    • Step 0.01: Allows 0.01, 0.02, 0.03, 0.04, 0.05… (two decimal places)
    • Step 5: Allows 5, 10, 15, 20, 25… (five-unit increments)