Table of Contents
- Why landed cost transparency is a compliance issue
- VAT basics for cross-border Google Shopping
- DDP vs. DDU/DAP: who pays customs, and how to disclose it
- De minimis thresholds and why they matter per country
- Feed settings for tax and shipping by destination
- EU-specific requirements (IOSS, VAT-inclusive pricing)
- UK-specific requirements post-Brexit
- Common cross-border disclosure mistakes
- Cross-border compliance checklist
- FAQ
Why Landed Cost Transparency Is a Compliance Issue
When a merchant ships internationally, the price a shopper sees in a Google Shopping ad and the total amount they actually end up paying (product + shipping + VAT/GST + customs duties + any carrier brokerage fee) can diverge significantly if those additional costs aren't disclosed before checkout. Google treats this the same way it treats any other pricing misrepresentation: if the ad price and the true total cost of ownership differ in a way the shopper wasn't warned about, it's a compliance violation, not just a customer experience problem.
This is a growing area of enforcement as more merchants sell cross-border directly (rather than through marketplaces that handle duty calculation automatically), and it's one of the least well-understood compliance areas among mid-market e-commerce sellers.
VAT Basics for Cross-Border Google Shopping
Value-Added Tax (VAT), and equivalent consumption taxes like GST/HST in other countries, is charged on goods sold into most countries outside the US. If you're advertising to shoppers in a VAT-charging country, your displayed price needs to reflect how VAT will actually be handled โ either included in the displayed price (the norm in the EU/UK, where consumer-facing prices are legally required to be VAT-inclusive) or clearly disclosed as an additional charge collected at checkout or on delivery.
In the EU and UK, VAT-inclusive pricing for consumer sales isn't just a Google Shopping best practice โ it's a legal requirement under consumer protection law. Google's policy enforcement here is effectively backstopping a legal requirement you're already subject to regardless of Google's rules.
DDP vs. DDU/DAP: Who Pays Customs, and How to Disclose It
The other major cross-border cost is customs duty, and how it's collected depends on your shipping terms:
- DDP (Delivered Duty Paid) โ you (the merchant) collect and remit duties/taxes at checkout, so the customer pays one total price with no surprise fees on delivery. This is the shopper-friendliest option and the lowest compliance risk.
- DDU/DAP (Delivered Duty Unpaid / Delivered At Place) โ the customer pays duties/taxes directly to the carrier or customs authority upon delivery, separately from your checkout price. This is common but requires very clear upfront disclosure or it reads as an undisclosed cost.
If you ship DDU/DAP, your product page and checkout flow need to state clearly that additional customs duties and taxes may apply on delivery, are not included in the displayed price, and are the customer's responsibility โ ideally with an estimate or a link to a duty calculator, since "may apply" alone is a weaker disclosure than showing an actual estimated range.
De Minimis Thresholds and Why They Matter Per Country
Many countries exempt low-value shipments from duty/tax below a "de minimis" threshold โ but these thresholds vary enormously by country and change periodically (the removal of the US's de minimis exemption for many low-value imports in recent policy changes is a notable example). Your disclosure strategy needs destination-specific accuracy: a blanket "no additional fees" claim that was true when a de minimis exemption applied can become a compliance violation the moment that exemption is removed or the shipment value crosses the threshold.
Feed Settings for Tax and Shipping by Destination
Google Merchant Center's tax and shipping settings support destination-specific configuration โ use them rather than relying on your website's checkout logic alone to carry the compliance burden. Configure separate shipping/tax settings per target country reflecting: whether VAT is included in the displayed price for that country, real shipping cost including any DDP duty prepayment built into your rates, and country-specific delivery time given customs processing variability.
EU-Specific Requirements (IOSS, VAT-Inclusive Pricing)
For shipments to EU consumers, the Import One-Stop Shop (IOSS) scheme lets merchants collect EU VAT at the point of sale for consignments up to โฌ150, avoiding a customs VAT collection at the border. If you're registered for IOSS, your displayed price should be fully VAT-inclusive and your shipment documentation should reference your IOSS number so customs doesn't apply a second VAT charge. If you're not IOSS-registered, disclose clearly that VAT will be collected on import instead, since your checkout price won't include it.
UK-Specific Requirements Post-Brexit
Since Brexit, UK VAT rules for imported goods sold to UK consumers require VAT collection at the point of sale for consignments up to ยฃ135 (similar in spirit to the EU's IOSS approach but a separate registration and threshold). Merchants selling into the UK need UK VAT registration for compliant point-of-sale collection below that threshold, or clear disclosure of import VAT/duty collection at the border above it.
Common Cross-Border Disclosure Mistakes
| Mistake | Consequence |
|---|---|
| Displaying US-only, tax-exclusive pricing to EU/UK shoppers | Violates both Google policy and EU/UK consumer law |
| Generic "customs fees may apply" with no estimate or DDP/DDU clarity | Weak disclosure, still flaggable as unclear pricing |
| Applying a stale de minimis assumption after a threshold change | Undisclosed duty charge appears at delivery, triggers complaints |
| Same shipping settings used for every destination country | Inaccurate landed cost for countries with different VAT/duty regimes |
Cross-Border Compliance Checklist
- VAT-inclusive pricing for EU/UK shoppers where legally required
- Clear DDP vs. DDU/DAP disclosure with an estimate, not just "fees may apply"
- Destination-specific tax/shipping settings configured in Merchant Center, not a single global setting
- De minimis threshold assumptions checked per country and kept current
- IOSS/UK VAT registration status reflected accurately in pricing and disclosures
Building Cross-Border Compliance Into Your Expansion Roadmap
The mistake many merchants make when expanding into new international markets is treating VAT/duty disclosure as a launch-day checklist item rather than an ongoing operational responsibility. Tax regimes change โ the EU's IOSS thresholds, the UK's post-Brexit VAT rules, and de minimis policy in destination countries like the US, Canada, and Australia have all shifted meaningfully in recent years, sometimes with only a few months of advance notice. A landed-cost disclosure that was accurate and compliant at launch can silently become non-compliant a year later purely because a regulation changed, with no corresponding change on your end.
Build a recurring review (quarterly is reasonable for most catalogs) of your tax and duty disclosure settings for each country you actively target, cross-referenced against current regulations for that market. This is a small, cheap habit compared to the cost of an undisclosed-fee complaint pattern accumulating over months before anyone on your team notices the underlying rule had changed.
The Customer Trust Angle Beyond Pure Compliance
Beyond avoiding a Google policy flag, transparent landed-cost disclosure is one of the highest-leverage trust signals available to a cross-border merchant, because surprise fees at delivery are consistently ranked among the top reasons international shoppers abandon a brand after a first purchase, independent of whether the product itself met expectations. Merchants who invest in accurate, destination-specific landed cost disclosure tend to see this reflected not just in fewer compliance issues but in meaningfully lower return-to-sender rates (a common outcome when a customer refuses a shipment upon being hit with an unexpected duty bill at the door) and higher repeat purchase rates from international customers who felt the first transaction was straightforward.
Frequently Asked Questions
Do I have to include VAT in my displayed Google Shopping price for EU shoppers?
Yes, for consumer sales into the EU, prices shown to consumers must be VAT-inclusive under EU consumer protection law, and Google's policy enforcement aligns with this.
What if I ship DDU and can't predict exact customs fees per shipment?
Provide a clear disclosure that duties/taxes are collected on delivery and are the customer's responsibility, plus an estimated range or a link to a duty estimator tool if you have one โ "may apply" alone is the weakest acceptable version of this disclosure.
Does a de minimis exemption mean I never need to disclose customs fees to that country?
Only for shipments that stay under that country's current threshold โ and thresholds change. Don't treat an exemption as permanent; recheck it periodically.
Can one shipping setting in Merchant Center cover all my international destinations?
Technically yes, but it will almost always be inaccurate for at least some destinations given how much VAT/duty regimes vary by country โ destination-specific settings are strongly recommended once you're shipping to more than one or two international markets.
Selling Internationally? Check Your Landed Cost Disclosures
Run a free scan to catch VAT, duty, and shipping disclosure gaps across your target countries before they become misrepresentation complaints.
Run Free GMC Scan โ