B2B Inquiry Module: Fields and Conversion Specification
Key takeawayThis section defines the structure template, field dictionary, integration points and compliance boundaries for 「B2B Inquiry Module: Fields and Conversion Specification」 in B2B COMPONENT SPEC. Templates are for reference only; verify local regulations and platform rules before launch.
Industries and use cases
- B2B independent sites whose sole goal is inquiries
- Sites where too many form fields depress the submission rate
- Sites that need enough information to judge customer quality
- Sites that want fewer invalid inquiries and more efficient sales follow-up
Template / code snippethtml
<form class="inq" method="post" action="/api/inquiry">
<div class="inq-grid">
<label>公司名称 <input type="text" name="company" required></label>
<label>联系人 <input type="text" name="name" required></label>
<label>工作邮箱 <input type="email" name="email" required></label>
<label>WhatsApp / 电话
<input type="tel" name="phone" autocomplete="tel"></label>
<label>国家或地区
<select name="country" required></select></label>
<label>关注产品
<select name="product">
<option value="">请选择</option>
<option>MODEL-A</option>
<option>MODEL-B</option>
<option>其他 / 未确定</option>
</select></label>
<label>预计数量
<select name="qty">
<option>样品 1-5 件</option>
<option>试产 6-50 件</option>
<option>批量 51-500 件</option>
<option>批量 500 件以上</option>
</select></label>
</div>
<label>需求说明
<textarea name="message" rows="4"
placeholder="型号、规格、数量、目的国等"></textarea></label>
<label class="inq-consent">
<input type="checkbox" name="consent" required>
我同意贵司根据本表单所留信息与我联系
</label>
<button type="submit">提交询盘</button>
<p class="inq-note">一个工作日内回复,通常更快。</p>
</form>| Field / parameter | Type | Description and values |
|---|---|---|
| Company name | Required | Identifies business buyers and separates them from personal purchases |
| Contact person | Required | Who to address and communicate with |
| Work email | Required | type=email; email is easier to follow up than phone |
| Phone / WhatsApp | Optional | Not mandatory in a B2B context |
| Country or region | Required | Determines export compliance and shipping conditions |
| Product of interest | Optional | Predefined options reduce typing effort |
| Estimated quantity | Optional | Predefined ranges help judge demand authenticity |
| Requirement description | Optional | Free text for model and application details |
| Consent checkbox | Checkbox | Records authorization to be contacted |
SEO and structured-data notes
| Keep required fields at 4 or fewer | Company, contact, email, country. Every additional required field lowers the submission rate |
|---|---|
| Use select instead of text inputs | Predefined options for quantity, country and product reduce typing and yield structured data for filtering |
| Keep phone optional | Forcing a phone number turns away some high-quality leads |
| Consent must be a real checkbox | Do not replace it with a text statement; without a check record there is nothing to show in a compliance review |
| Give clear feedback after submission | The success message should state the next step and timing, not just "submitted successfully" |
| Use verb phrases on submit buttons | "Submit inquiry" or "Request a quote" is clearer than "Submit" |
Compliance risk notes
- Personal data collection requires a processing notice
- Data must not be reused for other purposes without notice
- Cross-border data transfer must meet the target market's requirements
- Do not ask for information unrelated to the inquiry (such as ID numbers)
- Outgoing inquiry notification emails must not expose sensitive details in the subject line
Do not reuse this template verbatim in regulated contexts; verify local regulations and platform rules before going live.
Modification example
<!-- Modification example: collect structured requirements with select instead of free text -->
<!-- Original: one big textarea, fields hard to analyze -->
<label>Requirement description <textarea name="message" rows="5"></textarea></label>
<!-- Modified: key fields become structured; free text becomes a supplement -->
<label>Estimated quantity
<select name="qty">
<option value="">Please select</option>
<option value="sample">Sample (1-5 pieces)</option>
<option value="trial">Trial run (6-50 pieces)</option>
<option value="batch">Batch (51-500 pieces)</option>
<option value="bulk">Batch (500+ pieces)</option>
</select>
</label>
<label>Requirement description
<textarea name="message" rows="4"
placeholder="Model, specification, destination country and other details"></textarea>
</label>
<!-- Value: quantity and country are the primary signals for judging
whether a lead is real; once structured they can be filtered and
counted directly, and free text is reserved for what truly
needs human reading. -->FAQ
How many required fields should an inquiry form have?
About four: company, contact, email, country or region. Everything else optional, and use dropdown options instead of text inputs wherever possible.
Is collecting phone numbers worth it?
Yes, but keep it optional. B2B buyers communicate by email; a mandatory phone field lowers both the submission rate and form completion.
Where should the form submit to?
To a follow-up-capable system (CRM or lead system), not mailto — email client misconfiguration silently loses large numbers of orders.
How do you judge inquiry quality?
By country, quantity range and how specific the requirement description is. With those three fields structured, rules can pre-screen and humans only review what passes.
Version notes2026-11-20: first release, compiled from official Google documentation and public technical sources; updated as engine rules change. Engine behaviour details follow the latest official Google documentation.
Related reading
B2B Industrial Product Detail Page Component SpecificationIndustrial Multi-Model Spec Comparison Table Component SpecificationIndustrial Product Certificate Display Module SpecificationB2B Factory Capability Display Module SpecificationIndustrial OEM Customization Process Module SpecificationNote: this page is a summary of publicly documented search-engine rules and is for self-check reference only. Engine behaviour is subject to the latest official Google documentation; verify against your own Search Console data.