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

Multilingual Shipping and Delivery Terms Template for Independent Sites

Section:MULTILINGUAL COPY SPEC · Reviewed:2026-11-20 · Template asset

Key takeawayThis section defines the structure template, field dictionary, integration points and compliance boundaries for 「Multilingual Shipping and Delivery Terms Template for Independent Sites」 in MULTILINGUAL COPY SPEC. Templates are for reference only; verify local regulations and platform rules before launch.

Industries and use cases

  • Sellers whose vague shipping terms cause disputes in export business
  • Sites where buyers are sensitive to lead time and freight, affecting conversion
  • Sites that must explain special arrangements: wooden crates, fumigation, dangerous-goods transport
  • Sites with large regional lead-time differences that need early explanation
Template / code snippettext
<!-- 英文版 -->
<section class="shipping">
  <h2>Shipping and Delivery</h2>

  <dl class="ship-facts">
    <div><dt>Lead time</dt><dd>${leadTime} days after order confirmation</dd></div>
    <div><dt>Shipping methods</dt><dd>${methods}</dd></div>
    <div><dt>Incoterms</dt><dd>${incoterms} (default)</dd></div>
    <div><dt>Packaging</dt><dd>${packaging}</dd></div>
    <div><dt>Freight</dt><dd>${freightPolicy}</dd></div>
    <div><dt>Customs</dt><dd>${customsNote}</dd></div>
  </dl>

  <p class="ship-note">
    ${customsNote} Import duties and taxes, where applicable, are
    the responsibility of the buyer. We provide the commercial invoice
    and packing list required for clearance.
  </p>

  <table class="ship-table">
    <caption>Estimated transit time by destination region</caption>
    <thead><tr><th scope="col">Destination</th>
      <th scope="col">Sea (days)</th><th scope="col">Air (days)</th></tr></thead>
    <tbody>
      <tr><th scope="row">European Union</th><td>30-35</td><td>3-5</td></tr>
      <tr><th scope="row">North America</th><td>28-35</td><td>4-6</td></tr>
      <tr><th scope="row">Southeast Asia</th><td>7-12</td><td>3-4</td></tr>
    </tbody>
  </table>
</section>

<!-- 多语言措辞要点:
英:Lead time 与 transit time 必须分开 —— 前者是备货,
    后者是运输;混用是纠纷高发点。
德:写明"ab Werk"(出厂)、"ab Lager"(库存)、
    "frei Haus"(送到目的地)等交货条款术语
法:同样区分 délai de préparation 与 délai de transport
西:区分 tiempo de preparación 与 tiempo de tránsito -->
Fields and parameters
Field / parameterTypeDescription and values
Preparation timeNumber + daysState the start point: order confirmation or deposit receipt
Shipping methodsListSea / air / courier, with carrier types
IncotermsTextEXW / FOB / CIF / DAP etc.; state the default
PackagingTextStandard packaging or wooden crate; whether fumigated
Freight responsibilityTextCollect or prepaid; whether address changes are allowed
Customs responsibilityParagraphWho bears duties and taxes; which clearance documents are provided
Regional transit tableTableDestination region, sea days, air days

SEO and structured-data notes

SEO and structured-data checkpoints
Separate preparation time from transit timeMixing the two is the most common cause of lead-time disputes; distinguish them in both heading and body
Present the transit table as a tableRegional differences are large; a table is clearer than prose and lets buyers verify by themselves
State the default IncotermWithout a stated default, terms inferred from the buyer's location rarely match reality
Name the customs documentsCommercial invoice, packing list, certificate of origin — missing one stalls clearance
Be explicit about wooden crates and fumigationDestination countries require fumigation of wood packaging; leaving it unstated risks rejection at the destination port
Write the start point explicitly"Order confirmation" and "deposit received" differ by days to weeks in practice

Compliance risk notes

  • Do not make absolute delivery promises unless they can be guaranteed
  • Do not hide peak-season freight-capacity fluctuations; add notes where necessary
  • Freight and tax responsibility must be stated clearly, never vaguely
  • Transport requirements for dangerous and controlled goods must be disclosed explicitly
  • Transit figures must be identical across all language versions

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

Modification example

<!-- Modification example: split a merged "preparation + transit" sentence -->
<!-- Original -->
<p>Delivery within 25-35 days after order.</p>

<!-- Modified: two concepts separated, start points given -->
<dl class="ship-facts">
  <div>
    <dt>Preparation time</dt>
    <dd>15-20 working days after order confirmation and deposit receipt</dd>
  </div>
  <div>
    <dt>Transit time</dt>
    <dd>Sea 25-35 days / Air 5-8 days, depending on destination</dd>
  </div>
  <div>
    <dt>Total estimated lead time</dt>
    <dd>40-55 days by sea (EU), 20-28 days by air (EU)</dd>
  </div>
</dl>

<!-- The combined range lets buyers compute the budget themselves.
     The original single "25-35 days" makes buyers anchor on the fastest end,
     and the resulting gap is a common source of negative reviews. -->

FAQ

How long is a typical preparation period?
7-15 working days for small-batch standard products, 15-30 for non-standard custom work. The key is stating the start point, not just the number of days.
Should freight amounts be written concretely?
Freight varies with weight and destination; usually write "calculated by destination and weight" and note whether it can be prepaid. Fixed figures quickly become inaccurate.
Can language versions share one document?
Share the facts, but add one localized lead-time sentence per version — expectations about delivery time differ regionally.
How detailed should customs documents be?
State which documents you provide (commercial invoice, packing list, certificate of origin, plus certificates some destination countries require) and what the buyer must supply.
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.