“Quantity: 20” looks precise until staff ask the obvious question: 20 what? The answer could mean individual items, boxes, hours, square feet, linear feet, or people. A form can require a number and still send an ambiguous request into the queue.
A bare number makes staff stop and ask what it measures. Collect the number, the unit, and any dimension or packaging detail that changes the next decision. Then keep those facts separate in the saved record so staff and review tools do not have to guess.
Start with the decision the quantity supports
A quantity field should help someone do a specific job. A rental coordinator may need item count. An installer may need area and access constraints. A training inquiry may need attendee count and session length. A shipping request may need cases, items per case, and destination.
Write the staff question first: “Can we prepare an availability check?” or “Do we have enough information to estimate the work?” That question tells you which units and dimensions belong on the form.
Collect the number and unit in separate fields
| Visitor answer | What is still unclear | Better field pair |
|---|---|---|
| 20 | Items, boxes, or pallets | Quantity plus packaging unit |
| 500 | Square feet or linear feet | Amount plus measurement unit |
| 3 | Hours, days, or sessions | Duration plus time unit |
| 12 by 8 | Order and unit of each dimension | Length, width, and a shared unit |
A structured unit list works when the valid choices are known. Keep an “other” path when a legitimate request may use a unit you did not predict. Label the fields in ordinary language and give one example only when the expected format is not obvious. The W3C forms guidance on instructions explains why input formats and required details need to be stated before an error occurs.
Ask for dimensions only when they change the work
Do not add length, width, height, weight, and packaging fields to every request. Ask only for measurements that change pricing, scheduling, availability, or routing. Hide irrelevant fields with native conditional logic when the form builder supports the branch you need.
The guide to using form logic before AI review shows how to keep deterministic branches in the form. If someone selects delivery, reveal the dimensions needed for access planning. If they select pickup, those fields may not apply.
Separate estimated from confirmed quantities
A rough count can still be useful, but staff should not mistake it for a verified number. Add a simple status such as estimated, measured, customer-confirmed, or staff-confirmed when that distinction changes the next action.
Keep the submitted value and status together. Do not silently round a measurement, change a package count, or convert a unit in place. The guide to preparing form inputs before AI review explains why the original and any normalized representation should remain distinguishable.
Use review tools to expose gaps, not invent conversions
An Entry Summary can put quantity, unit, dimensions, and confidence into a readable review result for staff. A Missing Information Review can flag “quantity supplied, unit missing” against a checklist you configure.
Do not ask a model to choose a unit from context, perform an undocumented conversion, check live inventory, or calculate a binding price. Those jobs need explicit rules and an authoritative data source. If the source entry says “about 20 boxes,” the review note should preserve both “about” and “boxes.”
Test edge cases before staff rely on the field
- Submit zero and confirm it is not treated as blank.
- Leave an optional quantity empty and confirm the record does not invent zero.
- Enter a decimal when the workflow permits partial units.
- Change the unit after entering a number and inspect the saved record.
- Use an “other” unit and confirm staff can read the explanation.
- Compare the public confirmation, source entry, staff notification, and review result.
Retest the public path after form or plugin changes. The scheduled WordPress form test gives you a repeatable way to check that the same quantity still reaches the saved record and staff view.
Measure fewer requests for clarification
Choose one form and a fixed sample before and after the change. Count submissions that require staff to ask what the number means, correct a unit, or reopen the source entry because the review note lost a qualifier.
That is a local operating measure, not a promise of conversion or revenue. Keep the form version, sample window, and staff owner with the result so the next edit has something real to compare.
Fix one recurring number first
Find the form where staff most often ask “how many, measured in what?” Split that answer into the smallest useful fields, test the saved record, and stop there until real submissions show another gap.
Use separate fields for the number and unit. Add dimensions, packaging, duration, or an estimated-versus-confirmed status only when those details change the next staff decision.
No. Blank means the visitor did not provide a value. Zero is a supplied value and may be valid. Preserve that distinction in the source entry and review output.
Do not assume it should. Conversions and pricing need explicit rules, verified inputs, and an authoritative system. A safer review step restates the submitted quantity and flags a missing or unclear unit.
