The Carrier Cost Control Playbook: 3 Steps to Protecting Your Bottom Line
6 March 2026
IOSS vs OSS – the main differences
6 March 2026
OUR GOAL
To provide an A-to-Z e-commerce logistics solution that would complete Amazon fulfillment network in the European Union.
Expanding into the EU is exciting… right up until the moment someone asks, “So, do you need a VAT number?”
That’s usually when the guessing game starts. Some sellers are told that IOSS is enough. Others hear that Amazon will “take care of it.” And many assume they can worry about VAT later, after they’re already shipping orders to Europe.
If you’ve been trying to make sense of all this, you’re not alone. VAT rules in the EU are clear on paper, but in real life they’re triggered by things sellers don’t always think about: where your inventory physically sits, which Amazon program you choose, or how a marketplace classifies your account. Here’s the part most first-time EU sellers never hear upfront: IOSS only covers a very specific slice of cross-border ecommerce. The moment your operations move even one step closer to the EU customer — a warehouse, a 3PL, FBA Europe — IOSS stops being enough.
This article breaks down what actually triggers VAT registration, why these triggers are surprisingly easy to hit, and how non-EU brands can plan their EU expansion without stumbling into unexpected tax obligations. Basically, it’s about understanding the rules first, so you can scale with confidence.
IOSS vs VAT registration — why IOSS isn’t the whole story
IOSS was designed to make life easier for non-EU sellers. And to be fair, it does exactly that — but only in a very narrow set of situations. If your entire EU strategy is built on the assumption that IOSS equals full compliance, here’s where things start to fall apart.
IOSS works well when your business model is simple: you ship low-value orders (under €150) directly from outside the EU to EU consumers. VAT gets collected at checkout, customs procedures move faster, and you don’t need local VAT numbers because the goods never enter the EU before the sale is completed. For lightweight, direct-from-warehouse dropshipping or early-stage D2C brands, this setup is often enough — at least at the beginning. But here’s the catch: IOSS only covers imported B2C shipments under €150 where the goods were outside the EU at the moment of sale. The moment any of these conditions change, IOSS becomes irrelevant, and VAT registration enters the chat.
That means IOSS does not apply when:
- Your goods are stored inside the EU (even temporarily),
- Your shipments exceed €150,
- You sell B2B instead of B2C,
- You make domestic sales inside any EU country,
- You dispatch goods from an EU warehouse to customers in other EU states,
- A marketplace requires you to have a VAT number for compliance or payment flows.
This is the part most non-EU sellers underestimate. IOSS is a great tool for direct-to-consumer imports, but it is not a substitute for VAT registration when your operations grow beyond the “ship everything from abroad” model. And because most e-commerce expansion plans involve faster delivery, EU-based fulfillment, and marketplace distribution, the IOSS-only setup usually has a short lifespan.
With that foundation set, the natural question becomes: So what exactly forces a seller to register for VAT in Europe?
Storing inventory locally (your own warehouse or 3PL)
Storing products inside the EU—whether in your own space or through a 3PL partner—is one of the clearest and most unavoidable VAT triggers. The logic behind it is simple: once your goods physically sit in an EU country, tax authorities treat any future sale from that inventory as a domestic transaction. And domestic transactions require a local VAT registration, even if you're a non-EU business and even if the majority of your sales still ship internationally. Here’s what this means in practice:
- You must register for VAT in the country where your stock is stored: It doesn’t matter whether you own the warehouse, rent a shelf in a 3PL facility, or use a fulfillment provider as part of a logistics bundle. Physical presence of goods = local VAT presence.
- You must charge and report VAT on sales made from that inventory: Once the goods are “in country,” the sale to an EU consumer is treated the same way as if a domestic seller fulfilled the order. So VAT reporting shifts from IOSS or import VAT to local VAT returns.
- You can still use OSS for cross-border EU sales — but not instead of local VAT: If your stock sits, for example, in Poland or the Netherlands, your first VAT registration will be in that country. OSS can then be added on top to simplify VAT reporting for deliveries to customers in other EU member states.
Important: This trigger applies regardless of
• whether you sell B2C or B2B,
• whether your shipments exit the same country or go cross-border,
• whether you also use IOSS for separately imported orders,
• what your company’s legal structure is outside the EU.
The key takeaway: the moment your goods touch EU soil before the sale, you're in VAT-number territory.
Using Amazon FBA Europe (including Pan-EU and CEE programs)
Amazon FBA Europe is one of those setups that looks simple at first glance. You send your products to one fulfillment center, Amazon handles the logistics, and you get fast delivery and Prime eligibility. The complexity only shows up once you realize what “handling the logistics” actually means: Amazon can move your inventory between countries whenever it wants to improve delivery times. And it’s that physical movement of goods — not your sales volume — that creates VAT obligations.
The rule is straightforward: wherever Amazon stores your products, you’re expected to have a VAT registration. It doesn’t matter whether you personally chose that location or not. Maybe you shipped everything to Germany. That’s great — but Amazon may still shift part of your stock to France, Poland, Italy, Spain, or the Czech Republic. And every one of those moves changes your tax footprint inside the EU. A lot of sellers are surprised by how little control they actually have over this. In many FBA programs — especially Pan-EU or CEE — cross-border redistribution is built into how the system works. Even the more contained EFN setup still requires you to register for VAT in the country where your goods first enter Amazon’s network.
And this is where IOSS stops playing any role. For FBA, it simply doesn’t apply. Your goods aren’t being imported one order at a time; they’re already inside the EU. Any sale fulfilled from that stock is treated as a domestic or intra-EU transaction, and those fall squarely under VAT rules, not IOSS.
In practice, once you adopt FBA Europe, a VAT number in one country is the bare minimum. Most sellers end up with several, simply because Amazon’s logistics model spreads their inventory across borders and forces them to handle multiple tax registrations.
Marketplace-specific VAT obligations
Selling through marketplaces in the EU introduces another layer of VAT expectations that many non-EU sellers don’t see coming. Even if you never store inventory yourself and even if your sales model seems “lightweight,” some marketplaces require you to have a local VAT registration simply to operate on their platform under certain conditions.
This usually isn’t because the marketplace wants to make your life difficult. It’s because EU governments have tightened marketplace liability rules over the past few years. If a seller fails to charge VAT correctly, the marketplace can be held responsible — which means platforms now build their own compliance filters. In practice, this can translate into: no VAT number, no payouts or no VAT number, no listing activation in specific cases.
France is a common example of where this shows up first for global sellers. French tax authorities have historically enforced strict marketplace compliance, and platforms often require sellers to provide local VAT details to continue selling certain categories or to avoid account restrictions. The same trend is now visible across multiple EU markets as platforms try to protect themselves from liability.
What matters here is the principle, not the country-by-country detail:
even if your operations don’t naturally trigger VAT registration, a marketplace’s internal compliance rules might.
For sellers planning an EU expansion through marketplaces, it’s worth checking in advance whether the platform expects local VAT registration based on your sales volume, product type, or fulfillment method. Marketplace requirements aren’t always aligned with the legal minimum — sometimes they're stricter, simply because the platform wants to reduce risk.
Domestic supplies within an EU country
One of the simplest VAT triggers — and one of the easiest to underestimate — is making a domestic sale inside an EU country. The rule is completely universal across the EU: if your goods are already located in a country at the moment of sale, the transaction is considered a domestic supply. And domestic supplies almost always require a VAT registration in that country, no matter where your business is legally established. This means that even a single sale fulfilled from stock stored in Germany is treated just like any sale made by a German retailer. The same goes for goods sitting in the Netherlands, France, Italy, Poland — the location of the inventory defines the tax treatment, not your company’s base of operations.
A lot of non-EU sellers assume that if they “don’t sell much domestically,” they can avoid VAT registration until they scale. Unfortunately, VAT doesn’t work that way. Even low-volume or irregular domestic sales trigger the need for a VAT number because the obligation is based on where the goods are when the sale occurs, not how frequently you sell.
This is also where sellers sometimes hope IOSS or OSS might fill the gap — but neither applies to domestic transactions. IOSS only covers imports under €150, and OSS only helps with cross-border EU deliveries. Domestic sales sit outside both systems, making local registration the only compliant route.
The practical takeaway is simple:
if your products are physically in an EU country and you sell them to a customer in that same country, you need a VAT registration there — even if it happens just once.
Cross-border sales from an EU warehouse (and the role of OSS)
Once your products sit inside the EU, another VAT dynamic kicks in: shipping orders from that warehouse to customers in other EU countries. These transactions aren’t domestic anymore, but they’re also not imports — they fall into the category of intra-EU distance sales. And this is exactly where OSS becomes useful, but also where many sellers misunderstand what it can and cannot replace.
Here’s the heart of it: using OSS does not remove the need for a VAT registration in the country where your inventory is stored. You still need that local VAT number to report the domestic side of the transaction. OSS simply helps you handle the VAT owed in the customer’s country without registering for VAT in every single EU market you sell into.
So the flow looks like this:
inventory sits in Country A → you ship an order to Country B → Country A’s VAT number handles the origin → OSS handles the destination.
Both pieces are required for the transaction to be considered fully compliant.
A typical misunderstanding among non-EU sellers is thinking that OSS itself is a “universal VAT solution.” But OSS only simplifies reporting, not registration triggers. It doesn’t give you permission to avoid the initial VAT number where your goods are stored. It also doesn’t cover B2B transactions or domestic sales — it’s strictly a mechanism for cross-border B2C fulfillment within the EU.
What this means in practice is that any seller using an EU warehouse — whether through a 3PL or an FBA-lite model — ends up with a combination setup: a local VAT registration for the warehouse country + OSS for multi-country deliveries. That’s the standard structure for almost every D2C brand once they centralize their stock.
Why most non-EU sellers end up with at least one VAT registration
For many brands outside Europe, the first instinct is to look for a “minimal-compliance” path — a way to start selling without dealing with multiple VAT numbers right away. And in theory, IOSS feels like it should cover that need. But once you follow the actual operational steps most ecommerce businesses take when expanding into the EU, the picture changes quickly.
In practice, the very steps that make EU expansion work — placing stock in a local warehouse, joining FBA, offering faster delivery, or routing orders through an EU fulfillment hub — are the same steps that trigger VAT registration. Not because the EU is trying to “tax ambition,” but because each of those actions changes how your transactions are treated legally. Once your inventory is inside the EU, every order fulfilled from that stock becomes a domestic or intra-EU sale. When Amazon reallocates your units across multiple countries, each relocation creates a taxable presence in that new location. And when you deliver an order from an EU warehouse to a customer in another EU country, that movement falls under distance-selling rules that require a combination of local VAT reporting and OSS.
And that’s why most non-EU brands end up with at least one VAT registration much earlier than expected. It isn’t a penalty or a sign of complexity gone wrong — it’s simply the compliance framework that allows you to operate like a local seller once your products enter the local market. In practice, VAT registration becomes a milestone of growth: it means your business has moved from experimental cross-border shipping into real European fulfillment.
How to approach VAT registration strategically
Once you understand what actually triggers VAT obligations in the EU, the next step is shifting from reactive compliance to intentional planning, meaning shaping your setup so the tax footprint matches your logistics strategy, not the other way around.
A good starting point is choosing where your inventory will live. That decision alone determines your first VAT registration, and it also influences delivery speed, fulfillment cost, and which markets you’ll reach most efficiently. Many non-EU sellers start by placing all their EU inventory in one specific country because it keeps the VAT footprint contained. For example, choosing Germany, the Netherlands, or Poland isn’t random — each of these countries is a major entry point for ecommerce logistics, with predictable VAT processes and strong fulfillment infrastructure. By keeping all stock in a single location, every order dispatched from that warehouse is treated as originating from that country. That means you deal with one VAT registration, one set of domestic VAT returns, and a clean foundation for using OSS for cross-border B2C orders.
If you’re considering Amazon FBA Europe, you need to know upfront how each program changes your VAT footprint. With EFN (European Fulfilment Network), your inventory stays in one country — for example, Germany — so you only register for VAT there, and every FBA sale is treated as a German domestic sale or a German-origin EU sale reported through OSS.
But the picture changes completely once you switch to Pan-EU or the CEE program. In these models, Amazon automatically moves your units into multiple fulfillment centers — commonly Poland, the Czech Republic, France, Italy, or Spain. Each relocation is treated by tax authorities as you placing stock in that country, which immediately triggers a VAT registration requirement there. That’s why sellers who start with a single VAT number often end up needing five or six once Pan-EU is activated.
So the real planning question isn’t “Which FBA program should I choose?” but rather “Am I prepared for the VAT footprint created by that program’s inventory movements?” Making that decision deliberately prevents you from discovering new VAT obligations only after Amazon has already redistributed your stock.
It also helps to map your fulfillment flow from end to end: where goods enter the EU, where they sit, where they ship, and which marketplaces or sales channels you use. That flow tells you which VAT numbers are required and where OSS fits into the puzzle. OSS can simplify reporting for cross-border B2C sales, but you’ll still rely on your local VAT registration to handle the domestic side of each transaction.
The main idea is simple: don’t let VAT just "happen" to you. If you choose your warehouse country intentionally, understand how your fulfillment partner moves stock, and design your sales model around clear logistics, VAT registration stops being a surprise and becomes part of your operational setup — predictable, manageable, and aligned with growth.
Turning VAT triggers into a clear action plan
VAT registration is simply the point at which your business becomes part of the local ecommerce ecosystem. And for most non-EU sellers, that moment arrives earlier than expected: as soon as inventory enters an EU warehouse, as soon as Amazon shifts units across borders, or as soon as a marketplace asks for a VAT number before releasing payouts.
Once you understand these triggers, the VAT landscape stops feeling unpredictable. You can choose your warehouse location intentionally, decide whether FBA fits your model, and design a fulfillment flow that keeps your VAT responsibilities clear and manageable. With the right structure in place, VAT becomes just another operational step — not a barrier to entering one of the world’s largest ecommerce markets.
If you'd like help understanding which VAT registrations your setup requires, or you want guidance before choosing a warehouse or FBA program, our team at FLEX is happy to walk you through it. A short consultation can save you from months of guessing — and make sure you start selling in the EU on the right footing.
