# Does an inquiry quantity mean the current purchase or annual demand? How the website can reduce estimation misunderstandings Source: https://www.jvds.cn/en/share/website-design/inquiry-quantity-time-horizon Language: en Published: 2026-10-08 Author: JVDS Design Studio If an inquiry quantity’s time period is unclear, the parties may discuss entirely different things. Customers enter expected annual demand while sales read it as the current purchase, or customers provide rough estimates that recipients treat as confirmed quantities. The number is not wrong; its item, period and certainty are missing. Brief website guidance can help express these bases without making the first inquiry a complete procurement plan. Separate the current discussion from future estimates. Quantities explain requirements rather than automatically become formal orders or supply commitments. ## Keep current needs and future estimates in their own contexts Current quantity usually concerns the item and arrangement being discussed now. Future needs may span later projects or a period. If both are needed, explain their respective uses rather than compress them into one “estimated quantity” field and leave users guessing. The page can say “state the quantity planned for this purchase; add future needs separately and mark them as estimates.” This identifies the basis rather than requires precise quantities for every inquiry. Preserve undecided quantities instead of arbitrary numbers entered to satisfy validation. Sales may want long-term cooperation background, but annual numbers are not inherently more reliable than current tasks. Preliminary forecasts should retain that status. A large number should not automatically imply confirmed communication priority, pricing or supply scope. Repeat purchases also need current scope restated. A past batch does not mean the same quantity now. “Same as last time” can identify the original item, but users should explain current quantities and changes. Do not infer new requirements directly from old records. See [More Website Inquiries but Fewer Deals?](https://www.jvds.cn/en/share/website-design/improve-b2b-lead-quality) for related checks. ## Numbers need product identities and units A quantity means something only for an identified item: pieces of one model, combination sets or totals across products. Use actual company business units rather than independently merge different models or packaging into one basis. For multiple models, ask for corresponding quantities. Simple information can use natural language; larger requirements can use confirmed detail methods. Do not ask for one total and leave model differences for recipients to guess. Packaging and sets create another misunderstanding. When customers estimate outer packages while the company counts products, explain the actual discussion item and let commercial staff confirm the relationship. Provide accurate prompts without inventing packaging multiples or equating every set with one piece. When units are unknown, let customers describe identifiable items. “We need complete combinations this time; details still require confirmation” identifies the gap. Forcing integers for standardized fields may hide the product scope that needs discussion first. ![Miniature scene matching quantities to models, items and combination units](https://www.jvds.cn/upload/2026/1004/1791060138532-583244.webp) ## Give forecasts periods rather than converting annual plans into fixed monthly quantities Annual, quarterly and project-cycle figures have different time bases. When future background is needed, ask which period the estimate covers and its current basis. Not every user needs a complete timetable; the main point is to recognize that the number is not an immediate purchase quantity. Annual forecasts may not occur evenly. Neither the website nor recipients should simply average them into monthly purchases and treat those as commitments. Batches, stages and relevant products require checking against actual plans. Time basis alone cannot replace arrangements. Suppose a customer is discussing a confirmed project while considering later projects. They can explain current known scope and the future estimate period separately, marking unresolved parts. This illustrates wording without giving order quantities, production or supply conclusions. If customers only intend possible ongoing purchasing, retain a text description. Whether numbers are needed to assess cooperation depends on the actual task. Do not seek unsupported annual quantities to create an impression of scale or treat interest as current purchasing conditions. Periods also need starting points. “The next year” may begin with this discussion, while “this year” means the current calendar year. Where relevant, ask for start and end scope without assigning a period for customers. Colleagues receiving shared requirements should also understand the arrangements covered, rather than only the original form user knowing what annual means. ## Certainty matters more than numerical precision Quantity may represent confirmed scope, a stage estimate or pending internal checking. An exact integer is not proof of a decision, and a range does not imply lack of seriousness. Let customers explain basis and status so recipients distinguish usable current facts from unresolved content. A prompt might say “if undecided, describe your current estimate and matters requiring confirmation.” Estimates need not be forced into numerical ranges; customers may explain that evidence is incomplete. Recipients then assess whether communication can continue rather than turn every unknown into zero. Zero requires particular care. It may mean no current purchase or that users do not know what to enter. Clear unknown-status options reduce such substitute inputs. Existing zero entries require their original intent checked rather than immediate conclusions that no requirement exists. After quantity changes, update current discussion background. Earlier numbers can remain historical context but should not remain current requirements. Customers need not manage complex versions. Contact records should at least identify recent confirmations and estimates no longer used. ![Miniature scene retaining different statuses for confirmed quantities and future estimates](https://www.jvds.cn/upload/2026/1004/1791060138532-886848.webp) ## Leave purchasing stages and batch arrangements for the appropriate discussion Quotation requests, document comparisons and formal purchases have different readiness. Quantity helps understanding but cannot identify the stage alone. A clear quantity may still serve budget comparison. Allow the contact purpose to be stated rather than call every number an order quantity. When customers mention batches, record their actual wording rather than treat the total as each batch’s quantity. Specific batches, desired timing and supply conditions need later confirmation. The route can identify pending discussion without presenting customer plans as company-accepted arrangements. If demand depends heavily on product selection, identify products of interest and tasks before checking quantity. Precise totals may be meaningless before the item is chosen. Recipients should see why quantity is unknown rather than users receive another guessing field. First inquiries need not collect every future plan. If only current scope matters, focus there; explain when long-term background is genuinely needed. Collection should depend on the judgment information changes rather than whether every form field is filled. See [What Should a B2B Inquiry Form Collect?](https://www.jvds.cn/en/share/website-design/enterprise-website-contact-form-fields) for related checks. ## Test two requirements with identical numbers but different meanings Construct one inquiry for a currently confirmed single-model need and another forecasting several projects in a future period. Use the same fictional number but change item, timing and status to check whether the website retains their distinction. Do not use actual purchasing data. Ask recipients which is current demand, which is a future forecast and what each lacks. If both are called order volume, guidance has not communicated the basis. Add corresponding background rather than merge tasks because numbers match. Test unknown quantities and multiple-model details too. Can users explain without inventing numbers, and can recipients identify units and items? Passing format validation is not the purpose. Numbers should remain correctly understandable away from the form. Finally, have business owners check that public guidance matches actual acceptance. If undecided quantities are allowed but the system saves only isolated integers, background is lost. Information should match recording methods. Without automation, use workable manual explanations rather than claim nonexistent features. Quantity guidance succeeds when item, unit, period and certainty are recognizable and current needs and future forecasts do not substitute for each other. Retained numerical intent gives both parties the same background for continued purchasing discussion. ![Scene testing requirements with identical numbers but different purchase periods and items](https://www.jvds.cn/upload/2026/1004/1791060138532-887462.webp) ## Frequently asked questions ### Can annual forecasts be entered directly as current quantities? Do not mix them. Identify periods and statuses separately so recipients recognize current tasks and future background. ### Should users enter zero when they do not know quantity? Do not substitute zero for unknown. Offer an undecided expression; check existing zero entries for no demand versus temporary uncertainty. ### Can multiple models be represented by a total alone? A total does not identify each item. Where specific scope matters, provide corresponding details or note pending confirmation instead of making recipients guess allocations. ### Does an exact quantity establish confirmed purchasing? No. It may still be an estimate. Check the current stage and confirmation status. ### Must future needs include monthly plans? Collect them only if the current task requires them. Annual forecasts should not independently become monthly commitments; check actual arrangements separately.