Define the unit first
Determine whether the service expects a count, duration, fixed package, or another documented input. Do not assume every quantity field uses identical units. Keep the unit attached to the service mapping so downstream calculations use the same interpretation.
Validate representation and range
Check whether whole numbers, minimums, maximums, and increments apply. Reject malformed input instead of silently rounding it into a different purchase. If rounding is an intended feature, show the resulting quantity and obtain approval before submitting.
Preserve accepted values
Record both the approved input and the quantity accepted in the provider response where available. A mismatch should trigger review rather than being hidden by formatting. Use exact identifiers and documented field types instead of loosely converting every numeric-looking string.
Decision checklist
| Decision | What to check |
|---|---|
| Unit | Count duration or package |
| Rules | Range and increments |
| Record | Approved and accepted values |
Worked example
A hypothetical service accepts whole-number quantities in increments of 100. A customer enters 250. The system should request a valid approved quantity rather than silently sending 200 or 300, which changes the purchased scope.
Example figures explain the decision; they are not current prices or promised results.