Amazon FBA and OSS: When an Estonian Seller Needs VAT Numbers in the EU

Quick answer: OSS can cover the cross-border part of an Amazon business, but once stock sits in EU warehouses, local VAT questions appear and OSS alone is often not enough.

Amazon FBA is attractive because it puts stock closer to the customer and shortens delivery times. That same feature is what makes the VAT side harder. The moment Amazon starts storing your goods in more than one EU country, the business stops being a simple Estonia-to-EU sales flow.

I ask owners to stop thinking in terms of "we sell on Amazon" and start thinking in terms of where each SKU is stored, from which country it is dispatched, and whether the sale is domestic or cross-border. That shift is what separates a workable FBA setup from a quarter-end surprise.

Where OSS helps and where it stops

OSS can still be useful for the part of the business where goods are dispatched cross-border to EU consumers and the sale fits Union OSS rules. A typical example is stock leaving Estonia and being sold to a private customer in France, Italy, or Spain.

What OSS does not do is turn every FBA order into one neat filing route. If Amazon places the same SKU into a German warehouse and it is then sold to a German customer, that sale no longer looks like the earlier Estonia-to-France example. From the owner's side the listing may look identical. From the VAT side it is a different fact pattern.

When local VAT numbers are usually needed

Local VAT registrations usually enter the picture once Amazon creates a real local footprint. The most common trigger is simple: stock sits in a country and sales are made from that stock inside the same country. The same issue appears when Pan-EU fulfilment moves inventory between countries and nobody updates the VAT map until much later.

A short scenario shows the difference. In February your Estonian company ships one product from Tallinn to a customer in Austria. That order may fit OSS. In April Amazon moves part of the same product line into Germany and begins fulfilling German orders locally. The product, seller account, and marketplace are the same, but the VAT position is not.

  • Goods stored in Germany and sold to German buyers.
  • Pan-EU fulfilment where Amazon reallocates stock across borders.
  • Multiple warehouses with different country footprints for the same catalogue.
  • FBA plus direct sales, where one data export mixes unlike VAT flows together.

That is why I build the country map from the inventory and fulfilment reports first, not from the payout summary. The payout tells you what cash arrived. It does not tell you where the stock sat when the sale happened.

Which countries deserve the closest attention

The first countries I usually watch are Germany, Poland, Czechia, France, Italy, and Spain because Amazon commonly routes stock through those locations for Estonian sellers. That list is not a legal rule. It is a practical place to look first when a business says, "We only sell from Estonia," but the inventory report tells a wider story.

The working rule is straightforward: if the inventory report shows a new country, the VAT map should be reviewed in the same month. Waiting until the quarter closes is too late, because by then the accountant is reconstructing the history instead of booking against a clean structure.

Monthly control routine for FBA sellers

Once a month, compare three sources side by side: inventory by country, Amazon VAT or transactions reports, and your bookkeeping export. If one source shows a country or flow that the others do not, stop there and resolve the mismatch before filing.

The accountant handoff should also be specific. A usable month-end pack for FBA is usually small, but it has to be complete.

Report or fileWhy the accountant needs it
Inventory location report by countryShows where local VAT questions may have started
Amazon transactions or VAT reportLinks sales and VAT treatment to the actual Amazon flow
Returns and fees breakdownKeeps corrections separate from normal turnover
Short note on new countries or new fulfilment settingsWarns the accountant before the quarter is rebuilt manually
  • Check inventory location by country.
  • Match sales data with the VAT logic used in bookkeeping.
  • Review returns, fees, and prior-period corrections separately.
  • Confirm which part still belongs in OSS and which part no longer does.
Practical insight from Dmitri Schmidt:

For Amazon FBA, inventory location matters more than the marketplace name. Once stock moves, the VAT footprint moves with it. Related topic: register OSS Estonia.

Amazon FBA is not just another sales channel. It is a warehouse and fulfilment model with tax consequences. The safest habit for a small seller is a monthly warehouse review and a clean accountant handoff, not a hope that the payout summary will somehow explain everything later. Related topic: OSS in Estonia.

If Amazon has already started storing stock in Germany, Poland, Czechia, or another EU country and you are not sure which sales still belong in OSS, use the contacts page. We can map the warehouse footprint, separate the local flows, and show your accountant exactly what should be handed over each month.

Sources cited in this article

Need help with Amazon FBA VAT setup? We work with Estonian founders, e-residents, and online stores that need a clean VAT structure. Contact us if you need the FBA country map, the OSS boundary, and a clear monthly handoff for your accountant.

Frequently asked questions

Does Amazon FBA automatically mean I need VAT numbers in the EU?

Not automatically, but it often creates local VAT questions once inventory is stored in another country.

Can OSS cover FBA sales?

Only the part that really fits cross-border OSS logic.

Which country should I watch first?

Start with the country where stock is actually stored.

How often should I review inventory data?

Monthly at minimum.