Before Brexit, UK Amazon sellers had one European fulfilment decision to make: ship a pallet to Coventry and let Amazon route it to buyers in Paris, Munich, or Madrid. The customs paperwork was Amazon's problem. The VAT was Amazon's problem. The border was a line on a map, not a fee schedule.
That world is gone. And most UK sellers are still operating as if it isn't.
The reality since 2021 is that every unit you sell to an EU buyer from UK stock carries a Brexit tax — sometimes called an EFN fulfilment premium, sometimes called cross-border VAT, sometimes just called "the reason my UK Amazon margin used to be 32% and is now 22%." The name doesn't matter. The mechanic does.
This isn't a rant about Brexit. That decision is made and permanent. This is an operator's guide to the specific structural cost UK Amazon sellers pay for crossing the Channel — and the framework for deciding which of your SKUs should ever do it.
What actually changed at the border
Pre-Brexit, the European Fulfilment Network (EFN) let UK sellers store inventory in one country (typically the UK) and fulfil orders across all EU marketplaces. Amazon handled the internal transfers. The seller paid one storage fee, one fulfilment fee, and Amazon absorbed the rest of the logistics.
Post-Brexit, three things happen when a UK-stored unit ships to an EU buyer:
One — the EFN fulfilment fee increased. Amazon now charges a materially higher per-unit fulfilment fee for EFN orders crossing the Channel. On a mid-size product selling for €25, the EFN premium can eat 3-5% of the sale price on its own.
Two — you're liable for import VAT and customs on every shipment. Unless you're using the Import One Stop Shop (IOSS) scheme for low-value goods, or you've set up EU VAT registrations, customs clearance happens at the border and someone is paying for it. Usually you, indirectly, via higher freight rates. For consignments over €150, IOSS doesn't apply and full import VAT is due.
Above a €150 order value, IOSS stops applying to Amazon EU EFN and Pan-EU orders and full import VAT falls due.
Three — delivery speed drops. EU customers used to get UK-stored inventory in 2-3 days via EFN. Post-Brexit, add 1-2 days for customs handling. That's the difference between "Prime eligible" perception and "why did this take a week."
The combined effect: every UK-stored unit sold to an EU buyer costs you more in fees, more in freight, more in VAT complexity, and delivers slower. Amazon's answer to all of this is: hold stock in the EU instead. Which is why Pan-EU FBA exists as an option.
But Pan-EU has its own set of problems, and the honest framework isn't "always use Pan-EU" — it's "know which SKUs belong in each system."
The EFN vs Pan-EU decision framework
This is the part nobody writes about clearly.
Pan-EU FBA parks your stock directly in EU fulfilment centres — Germany, France, Italy, Spain, Poland, Czech Republic. Amazon distributes across those markets automatically. Fulfilment fees are lower than EFN. Delivery is faster to EU buyers. But you're now storing physical inventory across multiple EU tax jurisdictions, which triggers VAT registration requirements in each country you store in.
EFN keeps your stock in one place (typically UK) and fulfils across borders on demand. Higher per-unit fee, slower delivery, but no multi-country VAT setup and no risk of your stock being stranded in a market where it's not selling.
Here's the honest split by SKU velocity — the framework I've seen work across real UK-EU catalogues:
A-tier SKUs (5+ units/day on EU marketplaces): Pan-EU FBA makes sense.
The volume is high enough that stock cycles through before ageing becomes a risk. The lower fulfilment fees compound meaningfully over 150+ units/month. The VAT registration overhead is worth it because you're doing enough EU volume to actually need the structure.
B-tier SKUs (1-4 units/day on EU marketplaces): It depends.
The middle ground is genuinely case-by-case. If demand is stable and predictable, Pan-EU can work. If demand is seasonal or lumpy, you're at meaningful risk of aged inventory piling up in a specific EU marketplace where velocity dropped. The safer default is EFN with a plan to graduate to Pan-EU once demand consistency proves itself over 6+ months.
C-tier SKUs (under 1 unit/day on EU marketplaces): EFN, always.
This is the rule most sellers get wrong. Putting a low-velocity SKU into Pan-EU means Amazon can (and will) split your small stock allocation across multiple EU fulfilment centres. Now you have 8 units in Germany, 6 in France, 5 in Italy, and 4 in Spain — and each of those pockets is quietly ageing toward the 181-day surcharge threshold. Meanwhile the fulfilment fee saving is negligible because you're only shipping a handful of units per country per month.
Keep C-tier SKUs in UK FBA. Fulfil them to EU via EFN. Yes, the individual per-unit fulfilment fee is higher. But you completely eliminate the risk of fragmented, aged stock dying in a Spanish fulfilment centre and racking up surcharges on inventory nobody is buying.
The math works out because C-tier SKUs shouldn't be generating enough EU volume for the per-unit fee difference to matter.
The country-level velocity problem
Here's the pattern that catches Pan-EU sellers off guard.
You launch a product on Pan-EU. Amazon distributes your stock across six EU marketplaces. Sales are healthy on average. You feel good. Your total EU units-per-week is trending up. Life is fine.
Six months later you check your Aged Inventory report and discover you're paying surcharges on 200 units in Italy — which barely sells the product — while running out of stock every three weeks in Germany, where it's a hit.
Nobody warned you because "on average" your stock levels were fine. Amazon's dashboard showed healthy days-of-supply at the Pan-EU level. But the country-level breakdown told a completely different story, and the country-level breakdown is what actually determines whether specific unit pockets age out.
The fix is a weekly discipline that most sellers don't run:
Monitor sales velocity by marketplace, not by SKU total. Every SKU in Pan-EU needs a per-country velocity check. If Italy is sitting at 90 days of supply and Germany is at 12, that's a signal to intervene — even if the total Pan-EU average looks healthy.
When one country runs cold, act at the country level. Options:
- Run country-specific PPC to clear the slow-moving regional stock before it ages
- Adjust your Pan-EU distribution settings to reduce future stock allocated to that market
- Consider requesting a country-specific removal order (available for some products, expensive but sometimes the right call)
Never let country-level days-of-supply run below 40 or above 120 without a plan. Below 40, you're at low-inventory fee risk in that market. Above 120, you're on track for aged inventory surcharge in that market. Both problems compound quietly if you're only looking at Pan-EU averages.
Most Pan-EU sellers I've seen are operating without this country-level visibility. They're managing the total and getting punished by the distribution.
The stranded inventory nightmare
The worst outcome of getting Pan-EU wrong is stranded inventory: stock sitting in an EU fulfilment centre that isn't selling, isn't easily movable, and is racking up ageing fees every month.
Your options at that point are all bad:
Removal order back to the UK. Sounds simple. Isn't. You're pulling goods from an EU fulfilment centre back across the Channel, which means customs clearance (you pay), import VAT on your own goods coming back in (yes, really), and a removal fee per unit. On a low-value product, the cost of removal often exceeds the value of the inventory. You end up paying to bring stock home just to write it off.
Deep-discount promotion in the specific market. Faster than removal but assumes there's demand at some price. If Italy isn't buying at €25, dropping to €18 might move some units. Might not. You're guessing.
Cross-country transfer via Amazon. Amazon does allow you to request stock transfers between EU marketplaces via Pan-EU settings, but the internal transfer isn't guaranteed, isn't fast, and Amazon prioritises its own network optimisation over your specific request.
Wait it out and eat the fees. Sometimes the honest math is that paying six months of aged inventory surcharge is cheaper than removal costs. This is the position you never want to be in but the position many UK sellers with Pan-EU C-tier SKUs are currently in.
The lesson: the time to prevent stranded inventory is at the SKU allocation decision, not when you're already looking at 400 units of dead stock in a Polish fulfilment centre. Get the EFN vs Pan-EU decision right per SKU, and the stranded inventory problem largely doesn't happen.
The Brexit VAT footnote nobody wants to write about
Brief and factual, because most guides skip this and it matters.
If you're using Pan-EU FBA post-Brexit, you're storing inventory in multiple EU countries. Each of those countries requires you to be VAT-registered locally. Amazon offers services (VAT Services on Amazon) to help set this up, but it's not free and it's not simple. You're now managing 5-7 VAT registrations, filings in each country's language and format, and the ongoing compliance burden.
If you're using EFN from UK stock, you deal with EU VAT differently — typically via IOSS for consignments under €150, or via import VAT paid at the border. Simpler admin, but every unit sold to the EU is subject to import handling.
Neither is free of VAT complexity. Anyone selling you a "no-VAT-hassle" Amazon EU strategy is either lying or omitting something.
The practical implication: factor the VAT admin cost into your EFN vs Pan-EU decision. Pan-EU makes sense when your EU volume is high enough to absorb the multi-country VAT overhead. It stops making sense when you're doing €30k/year of EU sales split across five markets and paying €8k/year in VAT compliance to serve it.
What this means for how you plan your EU catalogue
Old model (pre-Brexit): put everything in UK FBA. Let EFN handle EU. Simple.
New model (post-Brexit reality):
- A-tier EU sellers: Pan-EU FBA with weekly country-level velocity monitoring
- B-tier EU sellers: EFN as default, graduate to Pan-EU only after 6+ months of demand stability
- C-tier EU sellers: EFN permanently, no Pan-EU exposure at all
- VAT structure: appropriate to your volume, not aspirational
None of this is complicated. It just requires making the EFN vs Pan-EU decision per SKU based on real velocity data, not doing the whole catalogue one way or the other because it's easier to think about.
The UK sellers who get this right will spend 2026 quietly recovering the 5-10% of margin that Brexit took from them. The UK sellers who don't will keep watching their EU marketplace P&L look mysteriously worse than their UK P&L and blame the algorithm.
Do the SKU-level audit. Route each product deliberately. Watch country-level velocity weekly, not Pan-EU totals monthly.
The Channel isn't going anywhere. Neither is the tax on crossing it. But you can choose which of your products pay it and which don't.
Managing UK-EU inventory strategy across multi-channel operations is what Fin Method's Strategic Retainer (£2,500/month, capped at 3 clients) exists for — ongoing operational input across Amazon Pan-EU decisions, EFN routing, country-level velocity, and VAT structure. If you'd rather diagnose the specific problem first, a Conversion & Performance Audit (£295) covers a single-asset review and prioritised fix list. Fixed price, no scoping calls, no retainer lock-in.