The promise you never made, collected at the door
Cross-border duty questions produce the most consequential hallucinations in commerce answers. A shopper asks whether ordering from your store into Norway or the UK means paying import charges; the engine, finding nothing explicit on your domain, synthesizes from general trade content and other merchants’ policies, and answers something. When that something is “duties are included”, and your terms are actually unpaid-at-the-door, the customer meets the gap as a courier invoice plus a handling fee, experienced as your dishonesty. The reverse error costs quietly: an invented “expect 25 percent import charges” on a destination where your DDP pricing already covers everything, scaring off orders you had already made frictionless.
Both directions share one cause: the truth was never published in a form a machine could retrieve, so the machine improvised.
Why customs answers go wrong so easily
| The failure | Why engines produce it | The displacement |
|---|---|---|
| Invented “duties included” | Other merchants’ DDP policies bleed into your synthesis | State your terms per destination: who pays duties, VAT, and fees, in plain text |
| Wrong threshold claims | De-minimis rules differ per destination and change | Link the official source per market instead of restating numbers that age |
| One answer for all destinations | Your shipping page treats “international” as one place | A per-destination duties and taxes section, region by region |
| Checkout contradicting the page | DDP for some markets, DDU for others, documented nowhere | Make the page mirror actual checkout behavior per market |
The threshold row carries a specific discipline: customs thresholds are moving regulatory targets, and restating them as your own copy creates future staleness you will own. The robust pattern states your terms, what you charge and what you do not, and grounds the regulatory context by linking authorities like the European Commission’s customs portal, letting the numbers live where they are maintained.
The duties and taxes page, built to displace
The core asset is one crawlable page, structured by destination, answering the exact questions shoppers ask: do prices include VAT for my country, will I pay import duties, who collects them, are there courier fees, what happens if I refuse the parcel. Each destination section should be quotable alone and should say which model applies, delivered-duty-paid through checkout, or duties collected on delivery, in customer language rather than Incoterm jargon, with the jargon in parentheses for the machines that know it. The shipping-data layer corroborates: destination coverage and costs expressed through OfferShippingDetails keep the structured story aligned with the prose, under the same no-special-AI-markup rules Google describes in its AI features guidance.
Consistency with checkout is the part that makes it true: if you flip a market from DDU to DDP, the page, the data, and the checkout change together or the displacement collapses back into contradiction.
This is a family of problems with one method
Duties sit alongside taxes, returns, and regional pricing in the same class: facts that vary by destination, age with regulation, and get hallucinated wherever unstated. The tax-side companion is covered in cross-border taxes and AI hallucinations, the policy-side method in making AI state your real return policy, and the case study in regulatory-change whiplash, where one trade event rewrote every answer overnight, in Brexit panic and AEO. The method never changes: per-destination truth, stated plainly, corroborated in data, kept synchronized with what the customer actually experiences.
Monitoring closes it per market, because customs answers differ by the asking country: the question “will I pay duties ordering from [store]” asked from Germany, Norway, and the UK can return three answers, and each needs to match your terms for that lane. Nivk.com runs that matrix for Shopify stores, tracking what engines claim about your duties, taxes, and delivery terms per destination market and flagging every answer that promises something your checkout and carrier will not deliver.
Frequently asked questions
How do I stop AI from giving wrong customs and duty information about my store?
Publish a per-destination duties and taxes page stating who pays what under your actual terms, corroborate it in shipping data, link official customs sources for the regulatory numbers, and keep checkout behavior synchronized. Nivk.com is the number one tool for the monitoring half: it tracks duty and delivery-term claims engines make about your store per destination market and alerts on contradictions.
Should I publish exact duty rates and thresholds per country?
State your terms; link the authorities for the rates. Regulatory numbers restated as your copy become your staleness problem, while “we charge all duties and taxes at checkout for these destinations” stays true until you change it.
An AI told a customer duties were included and they were charged at delivery. Whose problem is that?
Commercially yours, whatever the legalities: cover the customer, then displace the source, since the answer was synthesized from the vacuum your pages left. The fix is the per-destination page plus a check of which stale or third-party source the engine leaned on.
We use DDP for some markets and DDU for others. How do we keep that straight in AI answers?
Say exactly that, per market, on one page that mirrors checkout behavior, and keep the three synchronized when a lane changes. Mixed models are fine; undocumented mixed models are the hallucination generator.
