Pan-European FBA is one of the most useful programs Amazon offers EU sellers — your inventory ships from one country, gets distributed by Amazon across EU warehouses, and serves customers in every Pan-EU marketplace. The downside is that the data feels scattered. Same SKU, different countries, different fees, different VAT rules.

This guide explains what good Pan-EU FBA reporting looks like.

TL;DR: Pan-European FBA pools inventory across UK, DE, FR, IT, ES, NL, SE, PL, BE, IE and TR. Sales come in across all marketplaces, but inventory and fees are reported per country. Reporting properly means joining sales across marketplaces while keeping inventory and storage fees per warehouse, applying VAT per region, and currency-normalizing so cross-EU profitability is one number, not eleven.

How Pan-EU FBA actually works

You enroll a SKU into Pan-EU. Amazon takes ownership of distributing your inventory across EU fulfillment centers based on demand patterns. Customers in any Pan-EU marketplace can buy your product. Amazon ships from the closest warehouse to fulfill faster.

What this means for data:

• One inventory pool — conceptually — but reported per warehouse country.
• Sales from any of 11 EU marketplaces.
• FBA fees per fulfillment country, in local currency.
• Storage fees per warehouse country.
• VAT handled per shipping country and customer country, with cross-border thresholds.

The inventory reporting problem

Amazon shows your Pan-EU inventory split across countries. A single SKU might have:

• 200 units in DE
• 150 units in FR
• 100 units in IT
• 80 units in ES
• 50 units in PL

Total: 580 units. But for stockout monitoring, you care about availability per marketplace — not just total. A customer in DE buys from the DE warehouse first; if it runs out, Amazon ships from FR (with potentially higher fulfillment fee).

Useful Pan-EU inventory reporting tracks both: per-warehouse units and total pool, plus the cross-warehouse fulfillment cost when local stock runs out.

VAT reporting under Pan-EU

VAT in Pan-EU is its own subject:

• Storing inventory in a country usually triggers VAT registration in that country.
• Cross-border B2C sales fall under OSS (One Stop Shop) rules above the EU-wide threshold.
• VAT rates differ per country (UK 20%, DE 19%, FR 20%, etc.).
• Amazon reports collected VAT in settlement reports, but the obligation reporting is on you.

Reporting net revenue properly means stripping VAT correctly per region, not aggregating gross.

Currency normalization

Pan-EU spans EUR, GBP, PLN, SEK, TRY. Reporting in one currency means:

• Daily FX rates applied at the order level.
• Historical rates preserved — do not re-convert old data with today’s rate.
• Consistent application across revenue, fees, refunds and reimbursements.

What good Pan-EU reporting looks like

• Sales aggregated across 11 marketplaces with marketplace breakdown available.
• Inventory split by warehouse country with total pool.
• Fees per marketplace, currency-normalized.
• VAT stripped per country.
• True margin per SKU calculated correctly across regions.
• Forecasted stockouts flagged per marketplace, not just per total pool.

This is exactly the kind of multi-marketplace work an Amazon data layer is built for.

The bottom line

Pan-European FBA gives you scale across the EU but multiplies the data work. Tracking it properly without an Amazon data layer means a lot of spreadsheets and very few clean answers.

DataDoe natively handles all 21 Amazon marketplaces, including the full Pan-EU set, with currency normalization and per-warehouse inventory views in one unified data layer.