EU GPSR, VAT, and IOSS: What to Check Before Selling in Europe
15 parts · 2 checkpoints
Show all 15 parts
- 01EU launch evidence desk
- 02Plain terms
- 03EU boundary table
- 04Basics evidence relay
- 05Responsibility surfaces
- 06Consistency check
- 07Use one page case to connect operator, tax display, and package evidence
- 08EU Readiness Checklist
- 09Pause/continue
- 10Evidence chain and incomplete boundary
- 11Quick Check, has a checkpoint
- 12EU Operating pressure-check practice
- 13If another gap is blocking
- 14EU operating-boundary handoff record
- 15Compliance risk next steps
Before selling a Shopify product in the EU, do not treat GPSR, the responsible operator, VAT/IOSS, low-value imports, and DDP/DAP as separate acronyms. Pick one country and one SKU, compare the product page, package, checkout, and internal record, then choose Go, Small test, Hold, or Escalate based on who owns each promise and where its evidence lives.
What this lesson answers
EU launch evidence desk
Entering the EU is not learning tax law in one day. It is knowing which missing evidence blocks scaling.
This workflow splits EU launch work into three operating questions: who owns product safety, how tax is displayed, and how low-value imports are declared. GPSR, VAT/IOSS, HS code, origin, DDP/DAP, and responsible operator still stay in the table, but they no longer hit the reader as isolated legal acronyms.
Do not write “EU is open” first. Start with three operating questions and six pieces of evidence: country scope, SKU safety files, responsible operator, tax/import path, page and package promise, and escalation lead. If one is unclear, do not let ads, email, or full-scale selling run ahead.
- EU boundary table: Artifact
- Go / Hold / Escalate: Decision
- Not tax or legal advice: Boundary
Lesson deliverable
- Who owns product safety
- How tax is shown to customers
- How low-value imports are declared and reviewed
- Country and SKU scope
- Product safety and responsible-operator evidence
- VAT/IOSS, HS code, origin, and DDP/DAP path
- Page, package, and archive consistency
- Pause/continue rule, responsible lead, and review date
Plain terms
Translate regulatory terms into operating fields.
You do not need to memorize definitions, but you must know which table, page, package, and responsible lead each term touches.
- EU launch evidence
EU launch evidence is not the Shopify Markets switch. It is whether one country and one SKU have product-safety, tax-display, import-declaration, page-promise, and escalation evidence. Example: For a food-contact tumbler entering Germany, shippable does not mean ready; product files, responsible operator, HS code, origin, VAT/IOSS, and DDP/DAP still matter.
- GPSR
GPSR is the EU General Product Safety Regulation. Operationally, treat it as product safety files, traceability, responsible operator, and incident handling. Example: If the product is sold into the EU but the team cannot locate manufacturer, importer, responsible operator, or safety files, hold.
- Responsible operator
A responsible operator is a reachable party in the EU product responsibility chain. This material does not decide legal status; it keeps page, package, and archive aligned. Example: If the page, package, and internal archive name different parties, the evidence chain is broken.
- HS code and country of origin
HS code is the customs classification; country of origin is the source declaration. They affect import declaration, tax estimation, carrier data, and support explanations. Example: If page, invoice, carrier data, and internal records disagree, customs issues and customer tax questions get harder to resolve.
- VAT/IOSS tax and low-value consignments
VAT is value-added tax. IOSS is an EU mechanism for VAT on some low-value imported consignments. Operations must document who collects, where it displays, exclusions, and escalation. Example: If checkout does not explain tax responsibility, later fees often become refusal, refund, or dispute pressure.
- DDP/DAP
DDP/DAP describe delivery duty responsibility. DDP usually means the seller handles more import-duty responsibility; DAP usually means the buyer may pay at delivery. Here we ask you to document the promise and evidence. Example: If ads promise no extra fees while shipping is DAP, delivery charges create support, refund, and chargeback risk.
- Product feed
A feed is the product-field table read by Merchant Center, Meta Catalog, or another platform. This material does not use a feed to decide compliance; it keeps platform fields, product pages, package labels, and internal records aligned. Example: If the feed says stainless steel, the page highlights child use, and the package lacks matching material/contact details, review and support costs rise later.
- Consent
Consent is the user permission layer in a cookie banner, privacy app, GA4 Consent Mode, or marketing signup. It is not a VAT issue, but it affects pixels, email, and remarketing during EU launch. Example: If third-party scripts fire before the banner decision, or signup forms do not explain marketing use, write it as a separate privacy review item for whoever owns consent; the EU boundary table records only who owns it and the review date.
- Fulfillment exception readiness
Here, deliverability means fulfillment and exception readiness, not email inbox placement. A carrier quote proves possible delivery, not readiness for refusals, returns, customs requests, and safety complaints. Example: A test order should pass through page promise, checkout, label/invoice, package label, support wording, and escalation before scaling.
EU boundary table
Check six entries before deciding to continue.
This is not a compliance memo. Click the six entries to find the weakest evidence layer: country, SKU, evidence, responsible lead, and review date. Then put the weakest entry into the EU operating-boundary handoff record.
Choose a case: Country entry
- Check
- Clarify whether Germany, France, all EU, or only delivery zones are open. Country changes tax, language, return, carrier, and support pressure.
- Evidence
- Shopify Markets settings, shipping zones, policy page version, checkout record, responsible lead, and review date.
- Hold signal
- Markets is open, but nobody can explain why this country or which SKUs are affected.
- Responsible lead
- Market / operations lead
- Check
- Whether hero SKUs have material, intended use, label, traceability, safety files, and page-claim records.
- Evidence
- Product files, supplier documents, label samples, page versions, and safety-complaint path.
- Hold signal
- Only product copy exists; safety and traceability records are not reviewable.
- Responsible lead
- Merchandising / supply-chain lead
- Check
- Whether manufacturer, importer, responsible operator, or contact details match across page, package, and archive.
- Evidence
- Internal archive, package documents, page details, supplier confirmation, and change log.
- Hold signal
- EU sales are live, but contact party and evidence location are unclear.
- Responsible lead
- Compliance coordination / operations lead
- Check
- Whether VAT/IOSS, HS code, origin, DDP/DAP, and carrier capability support the current promise.
- Evidence
- Tax settings, carrier notes, invoice fields, checkout record, and support explanation.
- Hold signal
- Customers discover tax responsibility at delivery and support has no unified answer.
- Responsible lead
- Finance / fulfillment lead
- Check
- Whether product page, shipping, returns, warranty, checkout, and package label say the same thing.
- Evidence
- Page version, policy page version, package sample record, return address, support response script, and mobile path record.
- Hold signal
- Front-end promises exceed back-end capacity, such as free returns, fast delivery, or no extra fees.
- Responsible lead
- Content / support lead
- Check
- Who can pause ads, hold orders, update pages, and notify support during customs issues, refusals, safety complaints, recalls, or platform review.
- Evidence
- Escalation path, pause scope, recovery condition, review date, and responsible leads.
- Hold signal
- Safety or customs issues rely on ad-hoc chat coordination.
- Responsible lead
- Founder / operations lead
Basics evidence relay
The EU boundary table should reuse the foundations already built in Basics.
If entity, policies, payment, shipping, and launch QA are not already working, the EU table becomes empty paperwork. Reuse Basics outputs as EU fields: where evidence comes from and which missing field blocks scaling.
- Overseas entity: Decides responsible-operator copy, payment KYC, invoice entity, and who confirms tax.
- Policy pages: Checks EU page promises, consumer-facing information, operator details, and escalation paths.
- Payment and tax display: Decides whether VAT/IOSS, DDP/DAP, and low-value import cost changes are clear before purchase.
- Shipping and fulfillment: Shipping zones, carrier capability, DDP/DAP support, return address, tracking, and exception records.
- Launch QA: Turns launch readiness into reviewable go, hold, or escalation decisions instead of instinct.
Operating rule
Do not start evidence collection only when the EU lesson begins. Return to Basics entity, policies, payment, shipping, and launch QA, then write each record path into the EU boundary table. Ads, support, finance, and fulfillment should read one table, not separate stories.
Minimum deliverable: for every EU country, record entity, policy-page version, payment/tax settings, carrier capability, test-order record, and next review date. If one is missing, do not treat the market as ready to scale.
Responsibility surfaces
Do not collapse GPSR, VAT, and fulfillment issues into one todo.
"EU compliance pending" has no action. Split it into four surfaces so the team knows who to ask, what to fix, and when to stop.
Choose a case: Product safety surface
- Job
- Connect SKU, material, label, traceability, safety files, and page claims.
- Evidence
- Product archive, supplier files, label sample, page version, and Safety Gate review path.
- Failure mode
- Product page sells, but no one can locate safety files or SKU scope.
- Job
- Keep page, package, and archive contact parties aligned and reviewable by support and platform review.
- Evidence
- Responsible operator or contact record, package documents, page/policy versions, and change log.
- Failure mode
- Different touchpoints name different parties and the team assembles evidence after issues.
- Job
- Align VAT/IOSS, HS code, origin, DDP/DAP, carrier capability, and checkout promise.
- Evidence
- Shopify tax settings, carrier notes, invoice fields, checkout records, and support scripts.
- Failure mode
- Customers learn fee responsibility after payment, creating refusal, refund, or dispute pressure.
- Job
- Turn customs issues, refusals, returns, safety complaints, and recalls into an escalation flow.
- Evidence
- Order hold rules, ad-pause lead, support escalation template, recovery condition, and review date.
- Failure mode
- Support calms customers, operations keeps spending, and finance discovers the issue at refund time.
Consistency check
The table below is not a set of options; it is three surfaces that have to say the same thing: the market and the responsible party are written down, the tax line reads the same on the page and at checkout, and the parcel matches the internal archive, so building the boundary table is the only move that connects the promise to evidence.
Page, package, and archive must say the same thing.
Many EU risks are not from ignorance; they come from page promises, package documents, and internal records disagreeing.
At one checkpoint: what the page, the parcel and the archive each say
Product claims
- Page
- Material, safety, intended use, warranty, return promise.
- Package
- Label, instructions, invoice, origin, contact party.
- Archive
- Supplier files, page versions, change log, responsible lead.
Tax promise
- Page
- Shipping, checkout, and FAQ explain tax and import responsibility.
- Package
- Invoice, HS code, origin, and DDP/DAP match carrier setup.
- Archive
- Tax setting record, carrier notes, support explanation, issue log.
Incident handling
- Page
- Return, safety complaint, contact, and timeline promises do not exceed capacity.
- Package
- Package materials point to required contact and return/complaint path.
- Archive
- Who can pause ads, hold orders, update pages, and notify support.
Use one page case to connect operator, tax display, and package evidence
Start with one product page, then decide which evidence is missing, which copy changes first, and which promises must pause. Definitions for GPSR, IOSS, and DDP/DAP only help when they change that decision.
Choose a case: Germany 20oz food-contact tumbler
- Visible page
- The product page says Germany shipping is available, the tumbler fits commuting and camping, and tax appears at checkout.
- Hidden risk
- The page does not connect responsible operator, food-contact/material evidence, origin, HS code, IOSS fit, and DDP/DAP responsibility into one evidence chain.
- Responsible-operator line
- Page, package label, and archive must point to the same reviewable contact party; if they disagree, pause scaling.
- Tax-display line
- Tax display must clarify who collects at checkout, which orders are excluded, and whether the customer may still pay at delivery.
- Package/archive line
- Package file, invoice fields, HS code, origin, material evidence, and page version belong on the same record.
- First fix
- First add the product-page responsibility and tax-display case, then run one German test order through page, checkout, package, and support wording.
- Visible page
- The page says "sensitive-skin friendly" and "taxes included", while ads promise no extra charges.
- Hidden risk
- Sensitive-skin wording, ingredient evidence, label language, import-cost responsibility, and refund wording have not been reviewed together.
- Responsible-operator line
- Responsible-operator information cannot live only in a private sheet; support and page copy need a clear answer for safety questions.
- Tax-display line
- "Taxes included" must match tax setup, IOSS/VAT position, carrier capability, and refund handling for tax amounts.
- Package/archive line
- Labels, ingredients, batch, page version, support wording, and return address must trace to one version record.
- First fix
- Remove unsupported sensitive-skin and no-extra-fee wording first, then restore only after evidence is complete.
- Visible page
- The order is at or below EUR 150, so the team assumes IOSS removes import-cost issues.
- Hidden risk
- IOSS mainly simplifies VAT declaration and payment for qualifying low-value imports; it does not erase every import cost, carrier fee, or future low-value duty change.
- Responsible-operator line
- Electronics accessories still need safety files, contact party, package label, and incident path, not only order value.
- Tax-display line
- Cross-check the European Commission guidance of 2026-06-08 with its public news of 2026-06-29: from 2026-07-01, the temporary EUR 3 customs duty is calculated per item/category based on tariff classification—not per parcel or quantity. The technical guidance says the temporary measure runs through 2028-07-01. It affects display, margin, and support wording; this is not tax advice.
- Package/archive line
- Label, invoice, HS code, origin, DDP/DAP, and product-page tax wording must align.
- First fix
- Change low-value orders from "low risk" to "date-sensitive review" and record the review date in the EU operating-boundary handoff record.
EU Readiness Checklist
Every EU decision needs a checklist the team can actually verify.
The checklist is not decoration. It prevents the team from skipping evidence when the store feels almost ready. Pick a scenario and see what must pass and what must pause.
Choose a case: Small Germany test
- Scenario
- The team wants to run a small Germany campaign for the 20oz tumbler before every country file is complete.
- Checklist
- Country and SKU are scoped; the team is not saying "all EU" vaguely. Responsible operator, safety files, material/label, HS code, and origin sit on one row. VAT/IOSS, DDP/DAP, carrier ability, checkout tax display, and support wording align. Package, invoice, page version, policy page, and archive are reviewable by the next teammate. Use the European Commission guidance of 2026-06-08 and its 2026-06-29 public news to check the temporary EUR 3 customs duty from 2026-07-01: it is calculated per item/category based on tariff classification, not per parcel or quantity; the technical guidance says it runs through 2028-07-01, so write the post-effective-date review trigger.
- Verification record
- The verification record should name Germany / 20oz tumbler / this week's capped budget / last verification date / finance and fulfillment leads / escalation if Safety Gate, IOSS, or DDP/DAP evidence is missing.
- Pass condition
- A small test can run, but country, SKU, budget, and review date must stay limited.
- Hold condition
- If responsible operator, safety files, or tax responsibility is unclear, ad budget cannot replace evidence.
- Scenario
- The EU page already has traffic and orders, but the team finds package labels, page contact, and archive records disagree.
- Checklist
- Record the current page, checkout, policy page, and package sample first. List conflicting contact parties, tax wording, return address, and safety-complaint path as blockers. Pause new ad scaling; keep only controllable order handling and support explanation. After the fix, record recovery conditions instead of only saying "updated".
- Verification record
- The verification record should name the locked page version, policy version, parcel sample, conflicting fields, temporary pause scope, recovery condition, and escalation lead.
- Pass condition
- Resume scaling only after page, package, archive, and support wording align.
- Hold condition
- If any layer is not reviewable, freeze scaling and high-risk promises first.
- Scenario
- The European Commission technical guidance of 2026-06-08 and public news of 2026-06-29 confirm that from 2026-07-01 the temporary EUR 3 customs duty for low-value imports from outside the EU is calculated per item/category based on tariff classification, not per parcel or quantity; the technical guidance says it runs through 2028-07-01, so the team cannot keep old exemption assumptions.
- Checklist
- List EU hero SKUs and target countries at or below EUR 150. Recheck price, margin, tax display, carrier charges, and support wording. Review how the temporary EUR 3 customs duty calculated per item/category based on tariff classification—not per parcel or quantity—affects page tax wording, margin, carrier charges, and support explanation; do not write old low-value exemption assumptions into pages. Write the review date into the EU operating-boundary handoff record and assign finance or fulfillment ownership.
- Verification record
- The verification record should name SKUs at or below EUR 150, target countries, price/margin impact, page tax wording, support explanation, last verification date, and next review trigger.
- Pass condition
- Continue EU scaling only after low-value impact, official-update check date, and post-2026-07-01 review trigger are in pricing, page, support, and fulfillment records.
- Hold condition
- If the team still uses old exemption assumptions, pause related "no extra fee" wording first.
Pause/continue
Market and responsible party not read back
| Stop here | Go |
|---|---|
Do not launch pages or ads yet; a missing market, responsible party, tax, or parcel fact breaks the promise. | Write the applicable market, operator, tax display, and logistics evidence into one record first. |
| Evidence Market, responsible party, tax, and parcel fields in the record. | |
Promise and page evidence disagree
| Stop here | Go |
|---|---|
When page, checkout, and support disagree, do not scale or cover it with new copy. | Align price, tax, and delivery promises across page, cart, and after-sales notes, then recheck. |
| Evidence Page screenshots, checkout flow, and support replies. | |
Official source has expired
| Stop here | Go |
|---|---|
Do not reuse an old conclusion when the source date is stale or rules may have changed. | Read the official source again, update the review date, then decide to continue or pause. |
| Evidence Official link, verification date, and review owner. | |
This page gives operating boundaries, not tax or legal conclusions.
When tax, legal, or product-safety risk is high, the right move is escalation. The table shows which fields block scaling.
- Go: SKU, page, package, and archive align: Launch or scale modestly, with a review date recorded.
- Small test: tax path needs confirmation but scope is controlled: Limit country, SKU, budget, and order volume; set an evidence deadline.
- Hold: responsible operator, product safety, or tax responsibility is missing: Pause scaling and fix page, package, archive, and checkout evidence.
- Escalate: tax, legal, or product-safety high-risk decision: Escalate to tax, legal, product-safety, or external professionals; this workflow does not decide it.
- Restore: evidence completed: Before restoring, record counter-signals, review date, and next responsible lead.
Evidence chain and incomplete boundary
Make every promise return to evidence before choosing test, pause, or escalation.
The nodes and checklists above supply their individual controls. The traceability, incomplete-scope, and recovery method below connect to that interactive judgment so one selection is not mistaken for permanent release.
- Turn every customer-visible promise into a traceable evidence chain: EU readiness connects public rule, internal fact, customer touchpoint, and operating action into one reviewable chain. For each line on a product page, feed, order email, or parcel, keep the customer-facing wording on the left, the SKU, supplier file, label sample, or internal setting that supports it in the middle, and the person who rechecks it after product, market, or fulfillment change on the right. Material, contact details, and “deliverable” then become replayable operating promises rather than words held separately by copy and operations. If feed and product page name different materials, pause the ad or feed update that would amplify the error, temporarily narrow public wording to the proven scope, and trace the source before waiting for every file to arrive. Customers read evidence in buyer time: ad and product page, checkout, order email, parcel, then support. A contradiction between steps is not a later optimization; it breaks the current evidence chain. Record conflicting source, temporarily narrowed promise, the responsible lead, and the observation that permits recovery. Supplier-lot changes, page edits, price or delivery-region changes, carrier wording changes, safety complaints, or repeated tax questions reopen the affected row; preserve evidence that still holds and assign the new gap to its responsible lead.
- An incomplete state needs scope, due date, and freeze action: When a small test is allowed, limit country, SKU, or traffic at the same time and name the first gap, responsible person, due date, and action that cannot scale until it closes. For a Germany 20oz tumbler, Product brings the current lot, material record, and page claims; Operations confirms Germany market and return route; Finance records order-value and tax-treatment assumptions as reviewable internal notes; Fulfillment confirms what the carrier can actually deliver on that route; Ads and Support use only language those inputs support. If material, HS code, and origin are ready but the return address is changing and Support lacks a parcel-exception script, the result is not “80% ready”: retain completed evidence, freeze German traffic and “no extra fee” wording, keep the page in draft, and give Fulfillment and Support distinct work; after address and script align, reread PDP, checkout, and parcel sample. IOSS can simplify VAT declaration and payment for qualifying low-value imported goods up to EUR 150; it does not erase every import cost. Internal calculation and buyer explanation must also stay separate: the first evaluates price, margin, carrier, and refund cost, while the second asks whether checkout, shipping policy, order email, and parcel exception leave the buyer facing surprise cost or contradictory wording. If the team has confirmed only part of cost or treatment for only some orders, page and support keep the boundary rather than filling the gap with “tax included” or “no extra fee”; pause the promise and escalate to Finance, Fulfillment, or a qualified professional when uncertain.
Quick Check
Shippable to Germany does not mean scalable.
You opened Germany in Shopify Markets for a food-contact tumbler, but responsible operator, HS code, origin, and DDP/DAP are not in one table yet. What should you do?
Self-check: choose before reading feedback
Self-check not answered
Can this EU launch continue?
Note
Pick a move first
Proceed to the launch check
Finish it before continuing
EU Operating pressure-check practice
The real risk is not ignorance. It is pressure that skips evidence.
Practice this judgment: the store can sell, collect tax, or ship, but first evidence is not closed. Pick a pressure scenario; the panel gives the wrong move, first evidence, allowed move, and freeze rule for the EU operating-boundary handoff record.
Choose a case: EU Operating pressure-check practice
- Tempting wrong move
- Treat the Shopify Markets switch as proof of EU readiness and open ads.
- Safer read
- A market switch only says the store can sell there. It does not prove the evidence chain is reviewable across country, SKU, safety, operator, tax, promises, and escalation.
- First evidence
- Open the EU boundary table first and confirm responsible operator, safety files, HS code, origin, VAT/IOSS, DDP/DAP, and review date.
- Allowed move
- If evidence is incomplete, allow only a scoped test by country, SKU, budget, and order count, with an evidence deadline.
- Freeze rule
- Do not scale when responsible operator, product safety files, or tax responsibility is missing.
- Tempting wrong move
- Treat the supplier file as complete GPSR evidence and skip label, traceability, SKU scope, and page-claim checks.
- Safer read
- A supplier file is only one piece of evidence. Operations must confirm SKU, batch, material, page claim, label, and archive alignment.
- First evidence
- Sample one hero SKU and put supplier file, label sample, page version, manufacturer/importer/operator, and complaint path on one row.
- Allowed move
- Fix page and archive first; decide Go, Small test, or Escalate only after evidence is complete.
- Freeze rule
- Pause the EU page when the certificate cannot be tied to SKU, material, or page claims.
- Tempting wrong move
- Assume a checkout tax line means the customer will not see extra charges at delivery.
- Safer read
- Tax display is not tax responsibility. You still need who collects, who remits, exclusions, IOSS fit, DDP/DAP path, and support wording.
- First evidence
- Check tax setting record, IOSS/VAT position, HS code, origin, carrier DDP/DAP capability, checkout, and shipping policy copy.
- Allowed move
- Write tax responsibility into support and page copy, then validate page/package/support alignment with a small order sample.
- Freeze rule
- Do not scale if customers may discover fees at delivery or DDP/DAP conflicts with page promises.
- Tempting wrong move
- Treat deliverability as exception readiness and ignore refusals, returns, customs requests, and safety complaints.
- Safer read
- EU fulfillment is not just label generation. Package, invoice, contact party, returns, duty responsibility, support escalation, and ad pause must move together.
- First evidence
- Run one test order through page promise, checkout, label/invoice, package label, support wording, and escalation path.
- Allowed move
- Small traffic can continue only with exception lead, pause scope, recovery condition, and review time recorded.
- Freeze rule
- Do not open major budget when return address, duty responsibility, or safety escalation is unclear.
If another gap is blocking
Backfill the blocking evidence, then return to the EU boundary table.
Do not turn every missing field into one EU compliance todo. Backfill the lesson that matches the first gap, then bring that evidence back here.
- Market entry risk map: — Use it when market priority or country scope is still unclear.
- Policy and compliance pages: — Use it when policy, returns, safety contacts, or page promises are incomplete.
- Shipping and fulfillment setup: — Use it when tax responsibility, carrier support, or fulfillment promises are incomplete.
- Promo launch compliance QA: — Use it when campaign pages, promotion materials, or pre-launch checks are incomplete.
- High-risk incident response and escalation: — Use it once safety complaints, customs exceptions, payment risk, or platform risk have appeared.
EU operating-boundary handoff record
Turn the EU operating boundary into reusable notes.
Do not copy "EU is open." First name the leading gap from the entries and pressure-check practice, then write why this country and SKU can continue, where to hold, who owns evidence, and when to review.
EU operating-boundary handoff record
This is a practice record stored only in the current browser. It does not connect to, read, or write Shopify, tax services, carriers, products, orders, customers, markets, or production data. It only prepares material for human review and does not replace tax, legal, product-safety, or live-launch conclusions.
No checkpoint finished in this lesson yet. Start with “Go to the exercise”.
Self-check not answered
FAQ
- Before entering the EU, do I need to master GPSR, VAT, and IOSS first?
No. You do not need to learn tax law or product-safety regulation in one day. First split the work into product-safety ownership, customer-facing tax display, and low-value import declaration. Then document country scope, SKU safety files, responsible operator, tax/import path, page and package promise, and escalation lead in the EU operating boundary table. If one item is unclear, limit country, SKU, ads, email, or budget before scaling.
- Is it enough to keep the GPSR EU responsible person only in an internal sheet?
No. Check whether product page or policy page, parcel or label, and internal evidence pack point to the same reachable party. Also record SKU scope, manufacturer/importer information, last verification date, and escalation lead.
- If I use IOSS, do orders at or below EUR 150 avoid every import cost?
No. IOSS is a VAT declaration and collection mechanism for some low-value imported consignments. You still need to check order value, DDP/DAP, carrier fees, checkout tax display, shipping policy, support wording, and the 2026-07-01 temporary EUR 3 customs duty review trigger.
- Checkout already shows tax. Why still check DDP/DAP and the shipping policy?
Because tax display and delivery responsibility are different. Checkout, shipping policy, carrier capability, parcel files, and support wording must agree; otherwise the buyer may discover delivery fees, return cost, or refusal risk after payment.
- Who should own HS code, country of origin, and Safety Gate records?
Do not leave them scattered across merchandising, fulfillment, finance, and support spreadsheets. The EU boundary table should name the field source, responsible lead, review date, pause scope, and recovery condition so the team knows who adds evidence, who updates pages, and who pauses ads.
- If Shopify Markets enables Germany, why should I not scale immediately?
The Markets switch only means the country can buy. It does not prove product safety files, responsible operator, VAT/IOSS, DDP/DAP, parcel labels, returns, and support escalation are ready. Use a test order and the boundary table before deciding small test or scale.
- If a supplier sends one certificate, is EU product safety ready?
Not by itself. The certificate must map to the exact SKU, batch, material, label, page promise, manufacturer/importer/responsible operator, and complaint escalation path. If it does not, pause the EU page promise or narrow SKU scope.
- What should the EU operating-boundary handoff record include?
Write country and SKU scope, leading gap, first evidence, pause/continue decision, responsible lead, last verification date, 2026-06-08 guidance and 2026-06-29 official news checked, escalation record, next review trigger, and low-value duty impact. Do not only write “EU is open”; that gives ads, support, finance, and fulfillment no usable action.
Compliance risk next steps
After the EU readiness check, route each gap to the matching compliance path.
The table organizes country, SKU, and evidence boundaries. Privacy and consent, plus US tax and chargeback risk, still need separate readback rather than one EU record standing in for both.
Return to the Compliance Risk Hub
- Privacy and consent: verify market and data paths: Before EU launch, confirm which evidence proves language, consent, tracking, and policy boundaries.
Sources
Public copy cites official checking paths.
EU product safety, responsible operator, Safety Gate, VAT/IOSS, low-value consignments, and duties/import taxes vary by country, product, and fulfillment path. These links check boundaries, not automatic conclusions.
Sources: 9Last checked
European Commission public news: EUR 3 duty (2026-06-29) (opens in a new tab)Checked
European Commission GPSR / Product Safety (opens in a new tab)Checked
EUR-Lex GPSR Regulation (EU) 2023/988 (opens in a new tab)Checked
Shopify collecting duties and import taxes (opens in a new tab)Checked
European Commission low-value consignments (opens in a new tab)Checked
EU temporary low-value customs duty 2026 (opens in a new tab)Checked
European Commission VAT e-commerce / IOSS (opens in a new tab)Checked