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

Shipping Disclaimer and Trade Terms Notice Rules

Section:COMPLIANCE BANNER SPEC · Reviewed:2026-11-20 · Template asset

Key takeawayThis section defines the structure template, field dictionary, integration points and compliance boundaries for 「Shipping Disclaimer and Trade Terms Notice Rules」 in COMPLIANCE BANNER SPEC. Templates are for reference only; verify local regulations and platform rules before launch.

Industries and use cases

  • Export sellers where delivery responsibility is easily disputed
  • Categories that must define responsibility before ordering: oversize items, dangerous goods, out-of-gauge cargo
  • Sites that want to cut pre-sales communication effort
  • Cases involving responsibility split with third-party carriers
Template / code snippethtml
<!-- 轻量提示条:在下单前与关键位置出现 -->
<aside class="ship-note" role="note">
  <h2>Shipping and responsibility</h2>
  <p>
    Title, risk and cost of carriage transfer according to the
    Incoterms® 2020 stated on each quotation:
    ${defaultIncoterm} unless otherwise agreed in writing.
  </p>
  <ul class="ship-points">
    <li>Delivery times are estimates and exclude customs clearance
        and carrier delays.</li>
    <li>Import duties, taxes and clearance charges in the destination
        country are the buyer's responsibility.</li>
    <li>Goods are packed for standard sea or air transport;
        special crating for oversized items is quoted separately.</li>
    <li>Damage in transit must be reported within ${claimDays} days
        of delivery, with photographic evidence.</li>
  </ul>
  <p class="ship-meta">
    See also our <a href="/terms/">terms of sale</a> and
    <a href="/warranty/">warranty terms</a>.
  </p>
</aside>

<!-- 需要确认时才弹窗:下单前勾选 -->
<label class="terms-check">
  <input type="checkbox" name="terms" required>
  I have read and accept the
  <a href="/terms/" target="_blank">terms of sale</a> and confirm that
  import duties in my country will be paid by me.
</label>
Fields and parameters
Field / parameterTypeDescription and values
Trade termTextDefault Incoterm and the year of the version
Point of risk transferTextConsistent with the trade term
Lead time noteTextExcludes customs clearance and carrier delays
Duty and tax responsibilityTextWho pays import duty and VAT at destination
Packaging responsibilityTextStandard packing and special crating stated separately
Claim windowNumber + daysDeadline for reporting transport damage
Terms linkLinkPoints to the full terms of sale

SEO and structured-data notes

SEO and structured-data checkpoints
State the Incoterms versionIncoterms 2020 and 2010 allocate responsibility differently; "Incoterms" alone is ambiguous
List the exclusions from lead timeExclude customs clearance and carrier delays, otherwise the lead-time commitment cannot be met
Shorter claim windows are the normTransport damage is usually reported within 7-14 days; stating it clearly reduces later disputes
Require confirmation before orderingPutting the responsibility boundary before the order action is far more effective than a footer note
Keep it consistent with the terms pageThe notice and the terms page must say the same thing
Explain special packaging separatelyCrating for oversize items is quoted separately; silence creates a dispute at dispatch

Compliance risk notes

  • The notice must not exclude statutory liability
  • Wording must not conflict with the terms of sale
  • Delivery times outside your control must not be promised
  • Duty responsibility must not be left ambiguous
  • All language versions must state the terms identically

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

Modification example

<!-- Modification example: turn hard-coded dialog logic into a configuration-driven rule table -->
<!-- Original: each dialog decides on its own, unaware of the others -->
<script>
if (needAge) showAge();
if (needCookie) showCookie();
</script>

<!-- Modified: one rule table plus a priority queue -->
<script>
var RULES = [
  { id: 'age', priority: 10, scope: 'all', required: ${ageRequired} },
  { id: 'prop65', priority: 20, scope: 'US-CA', required: ${prop65Required} },
  { id: 'cookie', priority: 30, scope: 'EU,UK,CH', required: ${cookiesRequired} }
];

function region() {
  return document.documentElement.getAttribute('data-region') || 'GLOBAL';
}
function inScope(scope) {
  if (scope === 'all') return true;
  return scope.split(',').indexOf(region()) >= 0;
}

var queue = RULES
  .filter(function (r) { return r.required && inScope(r.scope); })
  .sort(function (a, b) { return a.priority - b.priority; });

(function next() {
  var r = queue.shift();
  if (!r) return;
  var el = document.getElementById(r.id + 'Modal');
  if (!el) return next();
  el.hidden = false;
  el.querySelectorAll('[data-close]').forEach(function (b) {
    b.addEventListener('click', function () {
      el.hidden = true;
      var st = {};
      try { st = JSON.parse(localStorage.getItem('cs')) || {}; } catch (e) {}
      st[r.id] = true;
      localStorage.setItem('cs', JSON.stringify(st));
      next();
    });
  });
})();
</script>

<!-- Key improvements:
     1. rules live in a single table; adding another market
        means adding one scope line, not changing the logic
     2. priority sets the display order,
        blocking compliance requirements come before informational ones
     3. dialogs display one at a time
     4. the region is written by the server after an IP lookup into data-region,
        so the jurisdiction is not misjudged from browser language
     These four points make the inevitable "dialogs fighting each other" problem manageable. -->

FAQ

Is the Incoterms version really necessary?
Yes. Clause numbering and responsibility allocation differ between versions; only the version makes the applicable rules determinate.
Where should the notice sit?
One near the price on product pages, one in the cart, and a checkbox confirmation on the order confirmation page.
How should the claim window be set?
By transport mode and cargo type; 7 to 14 days after receipt is common.
Is this necessary for B2B?
More so. B2B purchases involve larger amounts and clearer responsibility splits, so unclear boundaries cost more.
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.