Table of Contents
Why POD International Expansion Is Different
Print-on-demand sellers occupy an unusual spot in cross-border e-commerce: production typically happens at a fulfillment partner's facility, which may be located in a different country than the seller's own registered business, and often in a different country still from the customer. A US-based POD seller using a European fulfillment partner to serve EU customers, for instance, has three potentially different jurisdictions in play at once — the seller's home country, the fulfillment location, and the customer's country — each with its own VAT, customs, and consumer disclosure implications. This is structurally different from a seller who manufactures and ships everything from one warehouse in one country, and it means POD sellers need to think about landed cost and disclosure requirements per corridor (seller-to-fulfillment-to-customer), not just per destination country in isolation.
VAT-Inclusive vs. VAT-Exclusive Feed Pricing
Most markets that charge VAT (the EU, UK, and a growing list of others) require consumer-facing prices to be displayed VAT-inclusive — the price a shopper sees should already include the tax, not have it added at checkout as a surprise. Google's Shopping price accuracy rules follow the same logic: your feed's price attribute for a given target country needs to reflect what the shopper in that country will actually pay, inclusive of that country's VAT, if that's how your checkout displays pricing to them (which, per that country's consumer law, it generally should be). A common POD mistake is running a single global feed with one USD price that doesn't account for VAT inclusion in EU-targeted listings, creating a mismatch between the feed price and the VAT-inclusive price the shopper sees at checkout.
| Target market | Feed price should reflect |
|---|---|
| EU countries | VAT-inclusive price for that specific country's VAT rate |
| UK | VAT-inclusive price at the UK's rate |
| US | Price before sales tax, since US sales tax is typically added at checkout by jurisdiction, not baked into a single national price |
| Countries with destination-charged VAT/GST at checkout | Follow that market's specific display convention — check per country rather than assuming |
If you run a single feed targeting multiple countries with one converted price, you are very likely misrepresenting the actual VAT-inclusive price for at least some VAT-charging markets, since VAT rates differ by country (typically somewhere in a 17-27% range across the EU alone). Country-specific feeds or country-specific price overrides within a single feed are generally necessary for accurate cross-border Shopping compliance.
Customs Duties and De Minimis Thresholds
Separate from VAT, cross-border shipments can incur customs duties depending on the destination country's de minimis threshold (the value below which no duty is charged) and the product category's duty rate. Duties are a genuinely harder disclosure problem than VAT, because unlike VAT — which is a fixed, knowable percentage you can bake into a displayed price — duty liability can depend on factors not fully knowable until the shipment actually clears customs (declared value, product classification, occasionally destination-specific exemptions). Most POD platforms handle this one of two ways: either the seller (via the fulfillment partner) prepays estimated duties and bakes an estimate into the displayed price (Delivered Duty Paid, DDP), or duties are collected from the customer on delivery (Delivered Duty Unpaid, DDU), with the customer seeing an additional charge from the customs authority or carrier separate from what they paid at checkout.
From a GMC price accuracy standpoint, DDP is the cleaner model, since the feed price and the checkout price and the total the customer actually pays are all the same number. DDU is compliant with GMC as long as the *checkout* price you display and feed matches what's charged at checkout — the separate customs charge collected on delivery is understood by both Google and consumers as distinct from the purchase price itself, provided your landing page discloses clearly, before purchase, that additional customs charges may apply on delivery for that destination.
Disclosing Landed Cost at Checkout, Not After
Whichever model you use, the core compliance principle — both for GMC price accuracy and for general cross-border consumer protection law in most markets — is that a customer should understand the total they'll be charged (or the specific additional charges that may follow) before completing checkout, not discover an unexpected customs bill on delivery with zero prior warning. For DDU shipments specifically, add a clear, visible line near the price or shipping information: something along the lines of "additional customs duties and taxes may apply on delivery for orders shipped to [country]" — this single disclosure line addresses both the GMC misrepresentation angle and separate cross-border consumer protection expectations most markets share.
Structuring Per-Country Feeds Correctly
For POD sellers targeting several countries with materially different VAT rates, duty treatment, or fulfillment partners, structuring separate country-specific feeds (or a single feed with country-specific price and shipping overrides, which most feed management tools and platforms support) is generally more accurate and more maintainable than trying to force one global feed to be correct everywhere at once. This also makes it easier to audit: if a specific country's compliance requirements change, you update that country's feed segment specifically, rather than needing to trace through conditional logic buried in a single monolithic feed.
Where This Overlaps With EU Trader Traceability
We've covered the EU's Digital Services Act trader traceability requirements in a separate article — the DSA's trader identification and contact information requirements are a distinct legal framework from VAT/customs pricing disclosure, but both apply to the same cross-border POD sellers targeting EU customers, and both intersect with GMC compliance at the landing page level. A POD seller building out EU-compliant landing pages should treat VAT-inclusive pricing, customs disclosure, and DSA trader traceability information as three separate checklist items to verify together, since they're often addressed in the same page redesign project but stem from genuinely different regulatory sources.
How Fulfillment Partner Location Affects the Compliance Picture
Where you choose to fulfill orders from has a direct effect on which VAT and customs rules actually apply to a given order, and it's worth factoring compliance complexity into that decision, not just cost and turnaround time. A POD seller using a fulfillment partner located within the destination market (an EU-based print facility serving EU customers, for instance) generally faces a simpler compliance picture — the shipment is a domestic or intra-EU movement rather than a cross-border import, VAT is typically charged at the point of sale under that market's normal domestic rules, and customs duties generally don't enter the picture at all since there's no international border crossing on the customer-facing leg of the shipment. A seller relying entirely on a single fulfillment location shipping internationally to every market, by contrast, takes on the full complexity described throughout this article for every cross-border order.
This is one of the more overlooked reasons multi-region fulfillment network options (many POD platforms now offer print facilities across the US, EU, UK, and parts of Asia-Pacific) have become popular beyond simply reducing shipping time — routing an order to the fulfillment location closest to the customer often converts what would be a cross-border VAT/customs compliance question into a simpler domestic one.
Frequently Asked Questions
Do I need a separate Merchant Center account per country? No — a single Merchant Center account can target multiple countries, generally through country-specific feeds or a multi-country feed with country-level overrides, which we cover in our multi-country feeds guide.
Is DDP (duties prepaid) always better than DDU for compliance? DDP is simpler from a price-accuracy standpoint since there's one number, but it's not strictly required — DDU is compliant as long as the additional-charges disclosure is clear and prominent before checkout.
How do I find the correct VAT rate for each country I'm targeting? Most POD fulfillment partners and payment processors that handle cross-border VAT (many now handle EU VAT collection and remittance directly) can supply current rates per country; verify with your specific partner rather than assuming a rate is static, since rates do change periodically.
Does this apply to digital products (print-on-demand digital downloads) the same way? VAT treatment of digital goods follows different rules (often destination-based digital services VAT) from physical POD merchandise; check our digital products guide for the distinct considerations there.
How do I check whether my current international feed has a VAT price mismatch? Run a free scan at gmcunbanned.com to check your feed's country-specific pricing against what your checkout actually displays.
Do marketplace-based POD sellers (Etsy, Redbubble-style platforms) need to worry about this themselves? If the marketplace itself handles VAT collection, remittance, and disclosure as part of its checkout (many large platforms do this on the seller's behalf), the seller's direct compliance burden is reduced; sellers running their own independent storefront with a Merchant Center feed carry this responsibility directly and should not assume marketplace-style handling applies automatically.
Expanding Your POD Store Internationally?
Run a free scan at gmcunbanned.com to check your country-specific pricing and disclosure setup against GMC price accuracy requirements.
Run Free GMC Scan →