LEYUN · SITE SPEC & COMPONENT LIBRARY独立站技术规范手册

Capacity and Lead Time Table Template for B2B Selection

Section:DATA TABLE SPEC · Reviewed:2026-11-20 · Template asset

Key takeawayThis section defines the structure template, field dictionary, integration points and compliance boundaries for 「Capacity and Lead Time Table Template for B2B Selection」 in DATA TABLE SPEC. Templates are for reference only; verify local regulations and platform rules before launch.

Industries and use cases

  • Overseas buyers screen suppliers on lead time first
  • Categories where limited capacity stretches the production queue
  • Sites that want to show buyers how scheduling works
  • Industries with a wide lead-time gap between peak and off season
Template / code snippethtml
<table class="lead-table">
  <caption>交期与产能说明</caption>
  <thead>
    <tr>
      <th scope="col">订单数量区间</th>
      <th scope="col">标准型号</th>
      <th scope="col">非标定制</th>
      <th scope="col">当前排产周期</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <th scope="row">样品(1-5 件)</th>
      <td>3-5 个工作日</td>
      <td>15-20 个工作日</td>
      <td>视现货情况</td>
    </tr>
    <tr>
      <th scope="row">小批量(6-50 件)</th>
      <td>10-15 个工作日</td>
      <td>20-30 个工作期</td>
      <td>${currentLead}</td>
    </tr>
    <tr>
      <th scope="row">批量(51-500 件)</th>
      <td>20-30 个工作日</td>
      <td>30-45 个工作日</td>
      <td>${currentLead}</td>
    </tr>
  </tbody>
</table>

<p class="lead-note">
  交期自订单确认与定金到账之日起算。
  数量较大时按实际排产确认。
  旺季(${peakPeriod})交期可能延长,请提前咨询。
</p>
Fields and parameters
Field / parameterTypeDescription and values
Order quantity bandTextBands set around actual order sizes
Standard model lead timeNumber + working daysStock and made-to-order stated separately
Custom lead timeNumber + working daysState whether sampling is included
Current production queueTextDynamic value, requires regular updates
Start pointParagraphOrder confirmation or deposit received
Peak season noteParagraphSpecific period and size of the impact

SEO and structured-data notes

SEO and structured-data checkpoints
Lead time must state its start point"30 days" counted from which day is a frequent source of dispute
Band the lead time by quantityBuyers care about the band they fall into; a single lead time is useless for most orders
Separate standard from customThe two follow completely different scheduling logic; one column for both misleads
Give the queue its own columnIt is dynamic information, and a separate column lets it be updated alone
State the peak season explicitlyWithout it, a peak-season delay is treated as a routine breach
Keep production time apart from transit timeManufacturing lead time and shipping time are not the same thing

Compliance risk notes

  • Lead times that cannot be guaranteed must not be promised
  • Peak-season impact must not be concealed
  • Lead-time wording must not conflict with the contract terms
  • Queue figures must reflect the current situation
  • Phrases such as "ready to ship anytime" must not mask real scheduling pressure

Do not reuse this template verbatim in regulated contexts; verify local regulations and platform rules before going live.

Modification example

<!-- Modification example: turn a one-line lead time into a banded table -->
<!-- Original -->
<p>Lead time: 25-30 days.</p>

<!-- Modified -->
<table class="lead-table">
  <caption>Lead Time and Capacity</caption>
  <thead>
    <tr><th scope="col">Order quantity band</th>
      <th scope="col">Standard model</th>
      <th scope="col">Custom build</th>
      <th scope="col">Current production queue</th></tr>
  </thead>
  <tbody>
    <tr>
      <th scope="row">Sample (1-5 units)</th>
      <td>3-5 working days</td>
      <td>15-20 working days</td>
      <td>Subject to stock</td>
    </tr>
    <tr>
      <th scope="row">Batch (51-500 units)</th>
      <td>20-30 working days</td>
      <td>30-45 working days</td>
      <td>${currentLead}</td>
    </tr>
  </tbody>
</table>
<p class="lead-note">
  Lead time is counted from order confirmation and receipt of the deposit.
  In peak season (${peakPeriod}) the queue is tight and lead time may extend by 5-10 working days,
  so early confirmation is advised.
</p>

<!-- What changed:
     1. banded by quantity — buyers immediately see their own band
     2. peak season states the concrete period and the size of the extension
        ("may be longer" without figures says nothing)
     3. the production queue has its own column, so routine updates
        do not require rewriting the paragraph -->

FAQ

How many bands should the table use?
Three or four. Too many bands force repeated cross-checking; too few leave most orders without a reference.
How often should the queue be updated?
As often as it actually moves. Daily in peak season, weekly in quiet periods. A stale queue is worse than none.
Should capacity figures be published?
Annual capacity is fine, provided the definition is stated (calculated on the standard configuration). Buyers use it to judge supply stability.
Should lead time and transit time appear together?
Keep them separate. Manufacturing time and transit time are different concepts, and buyers add them up themselves.
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.

Note: 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.