VAT OSS vs. Local Registration: Which to Choose When Selling in the EU

The situation changes when the sales model becomes more complex. If a business begins storing inventory in a warehouse in another Member State and fulfilling local sales from there, a local VAT registration requirement may arise — and in typical fulfilment models, this is a very common scenario. For example, transferring a business’s own goods from its home Member State to a warehouse in Germany will generally give rise to a deemed intra-Community supply in the country of departure and a corresponding intra-Community acquisition in Germany. Such movements are not reported through OSS. If the goods are then supplied from the German warehouse to a German consumer, this will generally constitute a domestic sale that must be reported locally in Germany. If, on the other hand, goods from the same warehouse are dispatched to a consumer in France, the transaction may qualify as an intra-Community distance sale of goods and be reportable through the Union OSS scheme. This is why, in a more developed e-commerce structure, a local VAT number in one Member State and OSS used through the Member State of identification can operate in parallel.

For this reason, when expanding cross-border sales, it is better to look at VAT through the lens of the entire operating model rather than focusing on a single sales channel or turnover level alone. The key questions are: where are the goods dispatched from, who are you selling to, and where does the transport end? The answers to these three questions largely determine where VAT is due and how it can be reported. A business operating from a single warehouse in its home Member State and shipping goods to consumers across multiple EU countries is in a very different position from a business using several fulfilment centres in different Member States. In the latter case, some transactions may be reported through OSS, while others will need to be included in local VAT returns. This distinction depends primarily on the type and location of the transaction, rather than on which countries the business would prefer to cover through OSS. Where a business uses the Union OSS scheme, qualifying intra-Community distance sales should be reported through that scheme rather than selectively divided between OSS and local VAT returns on a country-by-country basis.

TL;DR: when should you use OSS, and when do you need local VAT registration?

If you need a quick answer, the key principle is this: OSS works best for a model in which a business makes cross-border B2C sales and dispatches goods from one EU Member State to consumers located in other Member States. For intra-Community distance sales of goods, however, the common EU-wide threshold of EUR 10,000, excluding VAT, must be taken into account. As long as the conditions for applying the threshold are met and it has not been exceeded in either the current or the previous calendar year, the sales may continue to be taxed in the Member State in which the transport begins. Once the threshold is exceeded, the place of taxation shifts to the consumer’s Member State, and OSS is usually the simplest way to report such sales without having to register for VAT separately in every destination country solely for this reason. OSS can also be used before the threshold is exceeded if the business voluntarily opts to tax these sales in the Member States of consumption.

For IOSS, the relevant limit is the intrinsic value of the consignment, which must not exceed EUR 150. The scheme applies to distance sales of goods imported from outside the European Union directly to consumers in the EU and does not cover goods subject to excise duties. It should not be confused with the Union OSS scheme, which is used, among other things, for qualifying intra-Community distance sales carried out within the EU. The mere fact that goods are shipped to a consumer in another country therefore does not, by itself, determine which scheme can be used. The place from which the transport begins, the value of the consignment, the status of the customer and the way the entire supply chain is organised are also relevant.

For a typical EU-based e-commerce business that holds its inventory in one Member State and dispatches goods from there to consumers in several other EU countries, VAT OSS is usually the administratively simpler solution once the EUR 10,000 threshold has been exceeded or where the business has voluntarily opted to tax sales in the Member States of consumption. It allows qualifying sales and the related VAT payments to be reported centrally, although the business must still apply the correct VAT rates in the consumers’ respective Member States. If, however, the business moves part of its inventory abroad as it expands, uses warehouses in several Member States, or makes local sales from a foreign warehouse to customers in the same country, OSS alone may no longer be sufficient. In such a model, OSS is often combined with local VAT registrations in the jurisdictions where local VAT obligations actually arise. It is also worth remembering that the rule of thumb that “a foreign warehouse means local VAT registration” is a useful simplification for a typical e-commerce business, but it should not be treated as an absolute rule for every possible logistics and transaction model.

What is VAT OSS and what does it actually simplify?

VAT OSS in simple terms

VAT OSS, or the One Stop Shop, is a scheme that allows a business to report VAT due on certain B2C transactions in different European Union Member States through the tax administration of a single Member State of identification. For a business established in one EU country, this will generally be that Member State. In practice, this means that if an online store sells goods to consumers in several EU countries and the transactions meet the conditions of the scheme, it does not have to register for VAT separately in every Member State of consumption solely because of those sales. Instead of filing several different VAT returns under local procedures, the business can report qualifying sales in a single OSS return and make a single payment. The VAT is still ultimately due to the Member States in which the sales are taxable under EU rules, but the reporting and payment process is centralised. This is the main purpose of OSS: it simplifies the way VAT obligations are fulfilled, but it does not change the underlying rules that determine in which country a particular sale should be taxed.

For a growing e-commerce business, the difference is important mainly from an operational perspective. Without OSS, expanding sales into additional countries could mean setting up further local tax processes, tracking different deadlines and filing returns across multiple jurisdictions. OSS helps reduce this fragmentation for transactions that actually fall within the scheme. If an EU-based online store dispatches goods from one Member State to consumers in Germany, France, the Czech Republic and other EU countries, it may, once the relevant conditions are met, report qualifying intra-Community distance sales through OSS in its Member State of identification. The business still needs to know where the consumer is located, where the transport ends and which VAT rate applies to the relevant product in the Member State of consumption, but it does not need to create a separate reporting mechanism for those sales in every country. OSS therefore does not simplify the underlying VAT logic itself. It mainly simplifies the reporting and payment of VAT arising from cross-border sales.

What OSS does not do

One of the most common misunderstandings arises when OSS is treated as a single “European VAT” system that replaces all local tax obligations. That is not how it works. OSS is not a separate, universal VAT number that can be used for every type of activity throughout the European Union. Nor does it mean that a business can apply the VAT rate of its home Member State everywhere simply because the OSS return is filed there. For qualifying sales taxable in the Member State of consumption, the business should apply the rate applicable in that country to the particular type of goods or services being sold. Centralised reporting therefore does not change where VAT is due. A business may file a single OSS return in its Member State of identification, but that return can contain VAT relating to sales to Germany, France, the Czech Republic and other EU markets, calculated using the rates applicable in each country.

OSS also does not cover every transaction carried out by an e-commerce business. Typical B2B sales generally remain outside the scheme, as does a local sale of goods from a business’s own warehouse in another Member State to a consumer located in that same country. Events such as transfers of a business’s own goods between Member States also fall outside OSS. Registering for OSS therefore does not automatically remove the need for local VAT numbers. A company that stores goods in another country, carries out domestic transactions there or performs other activities requiring local VAT reporting may need a local VAT registration even if it also uses OSS. This is why, in more developed logistics models, OSS and local VAT registrations often operate side by side, each covering different types of transactions.

How sales through OSS work in practice

Assume that an EU-based company operates an online store, keeps all of its inventory in a warehouse in its home Member State and dispatches orders from that warehouse to consumers in Germany, France and the Czech Republic. If the sales qualify as intra-Community distance sales of goods and are taxable in the Member States of consumption, the business does not simply charge the VAT rate of its home country to every foreign customer. For a sale to a consumer in Germany, it should apply the German VAT rate applicable to the relevant goods; for a sale to France, the appropriate French rate; and for a sale to the Czech Republic, the rate applicable there. Information about the consumer’s country and the correct allocation of the VAT rate therefore become part of the day-to-day sales process. OSS does not remove this responsibility. Instead, it allows qualifying transactions from several Member States to be brought together within one reporting mechanism rather than requiring separate VAT reporting solely because intra-Community distance sales are made into each market.

In practice, a business may therefore sell into several or even a dozen markets, apply different VAT rates depending on the consumer’s country, and then report those sales in a single quarterly OSS return filed in its Member State of identification. The tax administration of that Member State subsequently distributes the relevant VAT amounts to the appropriate Member States of consumption. From the business’s perspective, this is a far more scalable model than creating a local VAT registration in every country simply because consumers there purchase goods dispatched from another Member State. A clear distinction must nevertheless be maintained between sales that qualify for OSS and other events. If the same business moves part of its inventory to a warehouse in Germany and then begins supplying German consumers from that warehouse, that part of the activity will require separate analysis and, as a rule, will no longer be a standard intra-Community distance sale reported through OSS.

The EUR 10,000 threshold — why does it matter?

What the EUR 10,000 threshold covers

The EUR 10,000 threshold, excluding VAT, is one of the most important elements of the EU rules governing cross-border B2C sales, but its significance is easy to misunderstand. It is not a sales threshold that a business must reach before it is “allowed to use OSS”, nor is it calculated separately for sales of goods to each individual country. It applies in aggregate to certain categories of transactions, primarily intra-Community distance sales of goods and certain telecommunications, broadcasting and electronic services supplied to consumers in other Member States. Its significance lies in the fact that, where the statutory conditions are met, it affects the Member State in which those transactions are taxed. For an e-commerce business selling physical goods, the most relevant part of this mechanism will usually be intra-Community distance sales.

If a business is established in only one Member State and meets the other conditions for applying the threshold, the place of taxation of intra-Community distance sales may remain in the Member State from which the goods are dispatched until the threshold is exceeded, with VAT charged according to the rules of that country. The position must be assessed by reference to both the current and the previous calendar year. If the threshold was already exceeded in the previous year, the business cannot automatically return to taxing those transactions in the Member State of departure simply because the annual sales count starts again from zero in January. The threshold is therefore not merely an indicator of the size of the business. It is part of the rules determining the place of taxation for a specific category of B2C sales, and its application depends on a number of conditions being satisfied.

One threshold for the whole EU, not a separate threshold for each country

A common mistake is to treat EUR 10,000 as a separate threshold for each market. A business does not have one EUR 10,000 allowance for Germany, another EUR 10,000 for France, a further EUR 10,000 for the Czech Republic and separate thresholds for the remaining Member States. The threshold is shared and refers to the combined value of qualifying transactions made to other EU countries. If a business sells into several Member States at the same time, the relevant intra-Community distance sales and services covered by the threshold must be added together. This is particularly important for online stores that may not yet generate very high sales in any single market but are rapidly increasing their overall cross-border turnover by operating across several countries. A number of relatively small markets can together cause the threshold to be exceeded much earlier than a country-by-country view would suggest.

For example, a business may generate moderate sales in Germany, the Czech Republic, France and Austria without approaching EUR 10,000 in any one of those countries individually. That does not mean the common threshold has not already been exceeded. What matters is the combined value of qualifying transactions across the EU. For a growing e-commerce business, this is a strong reason to monitor qualifying cross-border sales as a single stream for threshold purposes rather than only as a collection of independent markets. If a company launches in several new Member States at the same time, the threshold may be reached even while each individual market is still at a relatively early stage of development. Without ongoing monitoring, the business may realise too late that the place of taxation has changed.

What happens after the EUR 10,000 threshold is exceeded

Once the common EUR 10,000 threshold is exceeded, qualifying transactions covered by the mechanism no longer benefit from the rule that, where the relevant conditions are met, allows the place of taxation to remain in the Member State from which the transport begins. For intra-Community distance sales of goods, VAT is then due in the Member State where the transport to the consumer ends. For an online store dispatching goods from one EU country, this means that a sale to a German customer will be taxed in Germany, a sale to a French customer in France, and a sale to a Czech customer in the Czech Republic. The business must therefore apply the VAT rates applicable in the respective Member States of consumption and allocate sales correctly to each country. The change is not postponed until the following year. Once the threshold is exceeded, sales covered by the intra-Community distance sales rules become taxable in the Member State where the transport ends, which is why the threshold should be monitored on an ongoing basis rather than only when the annual accounts are closed.

Exceeding the threshold does not, however, automatically mean that the business must obtain a separate VAT number in every Member State to which it sells. This is where OSS becomes particularly important in practice. If the sales qualify for the scheme, the business can report VAT due in several Member States of consumption through a single Member State of identification. Instead of creating local registrations solely because VAT becomes due in Germany, France or the Czech Republic after the threshold is exceeded, qualifying intra-Community distance sales can be reported through OSS. This does not mean that the EUR 10,000 threshold affects all of the business’s foreign VAT obligations. If the company stores goods abroad or carries out transactions outside the scope of OSS, the obligations arising from those activities need to be analysed separately. The threshold is important for specific B2C transactions, but it is not a general exemption threshold that removes the need for VAT registration in other Member States.

Can a business choose taxation in the Member State of consumption and use OSS before exceeding the threshold?

A business does not have to wait until it exceeds EUR 10,000 before choosing to tax intra-Community distance sales in the Member State of consumption and then use OSS as the reporting mechanism. If it meets the conditions that would otherwise allow taxation to remain in the Member State from which the transport begins, it may opt out of applying the threshold and instead follow the general place-of-taxation rules even while its qualifying sales remain below EUR 10,000. In practice, this means that a business that is only beginning to expand cross-border can choose to apply the VAT rates of the Member States of consumption and report qualifying transactions through OSS before reaching the threshold. The exact notification or procedural steps required to make that choice are handled under the rules of the business’s Member State of identification. The choice of place of taxation and the use of OSS are closely connected but separate issues: first, the business opts for taxation in the Member State of consumption, and OSS can then be used as a simplified method of reporting the VAT due in those countries.

Such a decision may make sense, for example, where the business expects rapid growth in cross-border sales and wants to operate under one consistent VAT model from the outset. It should not, however, be treated as a setting that can be changed freely from one month to the next. An election to tax in the Member State of consumption before the threshold is exceeded is generally binding for two calendar years. The decision should therefore be made deliberately, taking into account the company’s expansion plans, expected turnover and the readiness of its sales and accounting systems to apply the correct VAT rates in different Member States. For a business planning to scale quickly across the EU, moving earlier to a destination-based VAT model may reduce the need to change the reporting approach during a period of rapid growth. On the other hand, the mere availability of this option does not mean it will be operationally preferable for every business. The key distinction remains the difference between choosing the place of taxation and using OSS as the mechanism for centralised VAT reporting.

VAT OSS vs local VAT registration — key differences

How should OSS be compared with local VAT registration?

VAT OSS and local VAT registration solve two different problems, so comparing them only in terms of the number of returns or administrative cost can lead to the wrong conclusions. OSS is primarily designed for the centralised reporting of certain B2C transactions taxable in other EU Member States, particularly intra-Community distance sales of goods. Local VAT registration, by contrast, is required where a business carries out activities in a particular Member State that cannot be reported through OSS or that otherwise create a local VAT obligation. For a company expanding into several countries, this means the two solutions are not always alternatives. Very often, they simply cover different parts of the same sales model. A business may therefore report qualifying intra-Community distance sales through OSS while at the same time holding a local VAT number in a Member State where it stores inventory, reports transfers of its own goods or makes domestic sales.

There are exceptions to the general rule regarding domestic sales from a foreign warehouse. One may apply to certain supplies facilitated by electronic interfaces that are treated as the supplier for VAT purposes, known as the deemed supplier rules. In those situations, the platform may in certain cases report domestic supplies of goods through the Union OSS scheme as well. For a typical e-commerce seller supplying its own goods, however, the practical starting point remains the same: if the goods are located in a particular Member State and are supplied from there to a consumer in that same country, the transaction should first be analysed as a domestic sale rather than as an intra-Community distance sale covered by OSS.

You do not choose between OSS and local VAT for the entire business

The distinction becomes particularly important when an e-commerce business starts using warehouses in several Member States. Imagine a company that holds inventory in both its home Member State and Germany. Goods dispatched from the home Member State to a consumer in France may qualify as an intra-Community distance sale reported through OSS. If the goods are already stored in the German warehouse and are sold to a German consumer, the transaction will generally be a domestic German sale that must be reported locally. If a product is dispatched from that same German warehouse to a consumer in France, it may once again qualify as an intra-Community distance sale eligible for OSS. The earlier transfer of the company’s own inventory from its home Member State to the German warehouse, however, is a separate event and, under the current framework, is not reported through OSS. In a typical case, this means recognising a deemed intra-Community supply in the Member State of departure and a corresponding intra-Community acquisition in Germany, subject to any special procedures or exceptions that may apply.

In practice, the same business, the same online store and even the same product can therefore generate completely different VAT obligations depending on where the goods were located before the sale and where they were dispatched. In simplified terms, this can be seen through three different flows: a sale from Germany to a German consumer generally means local German VAT; a dispatch from Germany to a consumer in France may qualify as an intra-Community distance sale reported through OSS; while a transfer of the business’s own goods from another Member State to a German warehouse remains outside OSS and may give rise to an intra-Community supply and acquisition. This is why storing goods abroad can create a need for local VAT registration even where the business is already using OSS for its cross-border B2C sales.

OSS does not allow you to choose freely which countries to report through it

It is also important to understand that the Union OSS scheme does not work like a menu from which a business can select individual Member States or individual transactions. Once a taxable person chooses to use the Union scheme, it should report through OSS all transactions it carries out that fall within the scope of that scheme. A business should therefore not report qualifying intra-Community distance sales to France through OSS while voluntarily leaving equivalent sales to German consumers, which also meet the relevant conditions, in a German VAT return simply because it prefers to account for that particular market in a different way. The division is not based on a free choice of countries, but on the nature of the transactions being carried out.

This is particularly important when designing accounting and reporting processes. If a company has a local VAT registration in Germany because it holds inventory there and makes domestic sales, that does not mean every transaction connected with Germany should be reported in the German VAT return. A sale from a German warehouse to a German consumer will generally be reported locally, but a qualifying intra-Community distance sale from that same warehouse to a consumer in another EU Member State may fall within OSS. The accounting system should therefore distinguish transactions not only by country, but also by their nature. The right question is not “which option is better?”, but rather: “which of my transactions can be reported through OSS, and which create a local VAT obligation?”

“Is VAT OSS right for me?” — a quick test for sellers

VAT OSS is probably right for you if you sell B2C from one country to consumers across the EU

The most natural candidate for OSS is a business whose model is still based around one main Member State of dispatch but which is rapidly increasing consumer sales across additional EU markets. If inventory is held in one EU country and orders are dispatched from there to consumers in Germany, the Czech Republic, France, Austria or other Member States, OSS can significantly simplify the reporting of intra-Community distance sales once the common EUR 10,000 threshold has been exceeded or where the business has opted earlier for taxation in the Member State of consumption. Instead of setting up a local VAT registration solely because of these sales in every new country, the business can centralise the reporting of qualifying transactions. For a company planning to enter several markets at the same time, this is particularly important because an increase in the number of countries in which it sells does not necessarily have to mean a corresponding increase in the number of local VAT returns.

OSS makes operational sense, however, only if the business can correctly handle the data required to report its sales. The sales system, accounting setup and reporting processes should make it possible to determine the Member State of consumption, assign the correct VAT rate and separate transactions by country and type of sale. At greater scale, manually correcting data after the end of each quarter quickly stops being a practical solution. If a business sells mainly B2C, dispatches goods cross-border to consumers in other EU Member States and has not yet expanded its logistics into a network of foreign warehouses, OSS will usually fit well with the needs of a growing e-commerce operation. This does not, however, remove the need to classify transactions correctly and ensure that all transactions that should be reported through the scheme are included, while transactions outside its scope are kept out.

OSS alone will probably not be enough if your logistics extend beyond one country

The situation changes when expansion involves not only acquiring customers but also moving inventory closer to foreign markets. If a business starts storing goods in other EU Member States, transferring its own inventory between countries or making sales from a foreign warehouse to customers located in that same country, transactions arise that cannot simply be moved into OSS. In a typical model, transferring a business’s own goods from its home Member State to a warehouse in another EU country means recognising a deemed intra-Community supply in the Member State of departure and a corresponding intra-Community acquisition in the Member State to which the inventory is moved, subject to any special procedures or exceptions. This is one of the reasons why launching foreign fulfilment operations can create a need for local VAT registration even before the business begins generating substantial sales in that market.

Other events may then follow, such as domestic sales from a foreign warehouse, local purchases, imports or other transactions that create reporting obligations in the relevant Member State. A business using multi-country fulfilment should therefore not assume that registering for OSS “solves” local VAT. Much more often, the result is a model in which OSS operates alongside one or more local VAT registrations. A business may, for example, hold a German VAT number because it stores inventory in Germany, report domestic sales and relevant movements of goods there, while at the same time reporting qualifying intra-Community distance sales from Germany to consumers in other EU Member States through OSS. The more warehouses, inter-warehouse movements and sales channels the business adds, the more important it becomes to separate these events before VAT returns are prepared.

The simplest way to assess your own model

In practice, the analysis should begin not with tax forms, but with a map of the actual movements of goods. For each main sales model, the business should determine in which country the product is located before the order is placed, where transport begins, in which Member State it ends, and whether the buyer is a consumer or a business. Only then can it determine whether the transaction is an intra-Community distance sale, a domestic sale, a B2B transaction, a transfer of the business’s own goods or another event requiring separate VAT treatment. This approach is particularly useful before entering a new market, because deciding to place inventory in a foreign warehouse can change VAT obligations far more significantly than simply increasing the number of orders received from customers in that country.

If most cross-border revenue comes from B2C shipments dispatched from one home Member State to consumers in other EU countries, OSS may serve as the central reporting mechanism for that part of the business. If, on the other hand, goods are physically held in several Member States, the company transfers inventory between warehouses and carries out both domestic and cross-border sales, a more complex model should be expected. At that point, the question of OSS becomes only one part of the analysis. Local VAT registrations, the correct reporting of transfers of own goods and the allocation of individual sales flows to the appropriate returns become equally important. For a business planning expansion, performing this analysis before changing the logistics model is considerably easier than trying to organise the VAT position only after inventory has already been distributed across several countries and each warehouse is serving multiple sales destinations.

When is local VAT registration necessary?

Storing goods in another EU country

Entering a foreign sales market does not in itself necessarily create an obligation to register for VAT locally. The situation changes, however, when expansion also involves logistics and the business starts holding its own inventory in another EU Member State. From a VAT perspective, what matters is not only where the customer is located, but also where the goods are physically located and where their transport begins. If a business transfers part of its inventory to a warehouse in Germany, the Czech Republic, France or another Member State, a taxable event may arise independently of the subsequent sale to consumers. In a typical model, moving a business’s own goods from one Member State to another requires the business to recognise a deemed intra-Community supply in the country of departure and a corresponding intra-Community acquisition in the country to which the stock has been moved, subject to any special procedures and exceptions. These movements are not currently reported through OSS.

This is why opening a foreign warehouse can have greater VAT consequences than simply increasing sales to customers in that country. A business that previously dispatched all orders from its home Member State and reported qualifying intra-Community distance sales through OSS may, after moving part of its stock to Germany, need a German VAT number to handle transactions connected with that inventory. This does not mean that simply having goods abroad automatically results in a registration requirement in every possible model. Special procedures, exceptions relating to transfers of own goods, the structure of the particular supply chain and, in some situations, local mechanisms under which VAT is accounted for by the customer may affect the analysis. For a typical e-commerce business using foreign fulfilment, the most practical rule is therefore this: holding stock abroad should trigger an analysis of local VAT obligations before the first batch of goods is shipped, rather than only once regular sales from the warehouse have begun.

Selling from a foreign warehouse to a customer in the same country

The clearest example is a model in which a business owns goods stored in a warehouse in Germany and then sells them to a German consumer. The transport begins and ends in Germany, so this is not an intra-Community distance sale from another Member State or another cross-border supply that an ordinary seller can simply report through the Union OSS scheme. As a rule, it is a domestic sale in Germany, subject to German VAT and local reporting. In practice, this means that a business using a German warehouse may need a local VAT registration even where it continues to use OSS for other parts of its sales. This distinction is important because the country in which the business is established does not determine the VAT treatment of every sale. What matters is the specific movement of the goods, where the transport begins and ends, and the nature of the transaction.

It is useful to compare two orders that may initially look very similar. If a product is located in Germany and is dispatched to a consumer in Berlin, it is generally a domestic German sale and is not reported through OSS by an ordinary seller. If the same product from the same warehouse is dispatched to a consumer in France, a cross-border B2C supply from Germany to France arises and may meet the definition of an intra-Community distance sale that can be reported through OSS. The difference does not depend on where the owner of the online store is established or which sales channel the customer used to place the order. It depends primarily on where the transport begins and ends. There are specific exceptions, including certain electronic interfaces treated as the supplier for VAT purposes, but for a typical e-commerce business selling its own goods, the practical starting point remains: German warehouse → German consumer = local German VAT reporting.

Transferring your own goods between EU Member States

Transfers of inventory between a business’s own warehouses are sometimes treated by businesses as purely logistical operations because there is no external buyer, conventional sale or revenue. From a VAT perspective, however, such a movement may have independent significance. If a business transfers its own goods from a warehouse in one Member State to a warehouse in Germany, the typical treatment is a deemed intra-Community supply in the Member State of departure and a corresponding intra-Community acquisition in Germany. The subsequent sale of those goods is then a separate VAT event. If the product is supplied from the German warehouse to a German consumer, it will generally constitute a domestic sale. If it is dispatched to a consumer in another EU Member State, an intra-Community distance sale may arise. A single physical movement of stock can therefore begin a sequence of several different VAT events, each of which must be classified separately.

OSS is not currently used to report transfers of a business’s own goods. This is particularly important for companies rapidly increasing the number of warehouses they use and assuming that, because a large proportion of their B2C sales appears in a single OSS return, inter-warehouse movements will also fall within the same simplification. Under the current system, they do not. A business needs to know not only how much it sold in a particular country, but also what quantities of goods were previously transferred there and what VAT consequences arose from the transfer itself. Special arrangements, such as certain warehousing procedures, and other exceptions provided for under VAT rules may change the treatment of a particular movement, so not every case should automatically be handled in the same way. In a standard multi-warehouse model, however, transfers of the business’s own inventory are one of the main reasons why foreign fulfilment can lead to local VAT obligations independently of the use of OSS.

Imports, local purchases and other transactions outside OSS

The scope of OSS is considerably narrower than the entire VAT lifecycle of a growing business. The scheme may work very well for reporting VAT due on qualifying B2C sales to consumers in several Member States, but it does not take over every other VAT event connected with the business. If a company imports goods, makes local purchases, holds inventory abroad, transfers stock between Member States or carries out B2B transactions, each of these activities may require separate analysis. This does not mean that a local purchase automatically creates an obligation to register for VAT locally. It may, however, involve foreign input VAT, and the way in which that VAT can be accounted for or recovered will depend on the business’s overall activities in the relevant Member State, the transactions it carries out there and its registration status.

This distinction is particularly important because the OSS return is used to report VAT due on transactions covered by the scheme and is not a mechanism for deducting input VAT on purchases. If a business receives invoices containing foreign VAT for costs connected with its activities in a particular market, it cannot simply deduct that tax from the amount payable in its OSS return. The method for recovering that VAT must be determined separately. Depending on the circumstances, input VAT may be accounted for through a local VAT return where the business is registered in that Member State and meets the conditions for deduction, or an appropriate foreign VAT refund procedure may be available if its conditions are met. In practice, it is therefore useful to think in terms of three separate areas: OSS is used to report output VAT on qualifying transactions, local VAT returns deal with local obligations and may allow input VAT to be recovered, while a VAT refund procedure may, where the relevant conditions are met, be used to recover VAT paid abroad.

OSS + local VAT: why many businesses need both

One sales model can create several different VAT obligations

The easiest way to see this is through the example of an EU-based e-commerce business expanding its logistics into Germany. Initially, the company keeps all of its inventory in its home Member State and dispatches orders directly to consumers in different EU countries. Qualifying intra-Community distance sales can be reported through OSS in the Member State of identification. As sales in Germany increase, the business decides to move part of its inventory to a German warehouse in order to shorten delivery times and simplify fulfilment. From that point on, it is not only the storage location that changes. From a VAT perspective, new types of transactions arise and need to be separated. A transfer of the company’s own goods from its home Member State to Germany may give rise to a deemed intra-Community supply in the Member State of departure and a corresponding intra-Community acquisition in Germany. A subsequent sale from that warehouse to a German consumer will generally be a domestic transaction reported locally. At the same time, a shipment from Germany to a consumer in another Member State may qualify as an intra-Community distance sale covered by OSS.

As a result, two mechanisms operate in parallel within the same business model without replacing one another. A German VAT registration may be needed to deal with inventory, stock movements and domestic sales, while OSS continues to be used for the centralised reporting of qualifying cross-border B2C supplies to other EU Member States. This is not double reporting of the same sale. It is the allocation of different VAT events to the appropriate mechanisms. It is particularly important to understand that simply holding a German VAT number does not mean every sale beginning in Germany must be included in the German VAT return. If a transaction from a German warehouse to a consumer in another Member State meets the conditions for an intra-Community distance sale and the business uses the Union OSS scheme, it may be reported through OSS. A local VAT number and OSS therefore operate side by side because they cover different obligations.

Home Member State → warehouse in Germany → customer: three different operations

The most practical way to understand this model is to split the entire flow into three separate operations. The first is the transfer from the business’s home Member State to its own warehouse in Germany. This is not a sale to a consumer, but in a typical model it is a separate VAT event giving rise to a deemed intra-Community supply in the Member State of departure and a corresponding intra-Community acquisition in Germany, subject to any special procedures or exceptions that may apply. The second operation arises when a product already stored in the German warehouse is sold to a German consumer. This is generally a German warehouse → German consumer transaction, meaning a domestic sale taxable in Germany and reported locally rather than through OSS by an ordinary seller. The third scenario is German warehouse → consumer in France, or a consumer in another Member State. Such a flow may qualify as an intra-Community distance sale for which VAT is due in the Member State where transport ends and which may be reported through the Union OSS scheme.

Breaking the model down in this way shows why the question “OSS or German VAT?” is too simplistic. A business may need both at the same time because each covers a different type of transaction. A local VAT number may be required to deal with obligations arising in Germany, while OSS makes it possible to centralise qualifying cross-border consumer sales to other Member States. In a larger e-commerce operation, many more combinations may arise because inventory can be held in several warehouses and dispatched from each of them to customers across different markets. As the business grows, reporting based on the actual movement of goods therefore becomes critical: the country where inventory is located, the Member State in which transport begins, the Member State in which it ends and the status of the customer. Without this data, even correctly established VAT registrations do not guarantee that a particular transaction will be reported in the right place.

OSS and local VAT numbers are not competing solutions

In a more developed e-commerce operation, it is important to move away from the idea that implementing OSS should eliminate every foreign VAT registration. OSS can indeed reduce the number of registrations where the only reason for registering would otherwise be qualifying intra-Community distance sales to consumers in additional Member States. It does not, however, remove registrations arising from other events such as holding inventory, making domestic sales or transferring a business’s own goods. The more decentralised the logistics structure becomes, the more common it is for the right model to combine OSS with local VAT numbers. A business may have one OSS registration in its Member State of identification alongside several local VAT registrations resulting from the location of its warehouses and the nature of the transactions it carries out. At the same time, foreign input VAT relating to business costs remains a separate issue and is not recovered by reducing the amount due in an OSS return.

It is also important not to organise this split according to convenience or arbitrarily selected countries. Where a business uses the Union OSS scheme, it should report through OSS all transactions it carries out that fall within the scope of that scheme. OSS cannot therefore be treated as an optional channel used only for selected markets while equivalent qualifying intra-Community distance sales to other Member States are voluntarily left in local VAT returns. The distinction should follow the nature of the transaction. Domestic sales go into the relevant local reporting system, transfers of the business’s own goods are reported outside the current OSS framework, and qualifying intra-Community distance sales covered by the scheme should be reported through OSS. For a company planning further expansion, this approach is much clearer than trying to assign every operation connected with a particular country to a single system merely because the business holds a local VAT number there.

Specific scenarios: what fits your sales model?

One warehouse in one EU Member State, D2C sales across the EU

This is the simplest model when comparing OSS with local VAT registrations. The business holds all inventory in one Member State and dispatches goods directly from there to consumers in Germany, the Czech Republic, France, Austria or other EU countries. If the conditions for applying the common EUR 10,000 threshold are met and the threshold has not been exceeded in either the current or previous calendar year, the place of taxation for intra-Community distance sales may remain in the Member State of departure. Once the threshold is exceeded, or where the business has opted earlier for taxation in the Member States of consumption, VAT should be accounted for according to the rules of the countries in which transport ends. In this model, OSS is usually the most natural solution because it allows qualifying intra-Community distance sales to multiple Member States to be reported through a single scheme instead of creating separate registrations solely because of consumer sales into each additional country.

This does not mean that entering OSS reduces the process to one VAT rate and one aggregated sales figure. The business still needs to know which Member State the goods were delivered to, which VAT rate applies to the particular product and how much of its sales relate to each country. The faster the company grows, the more important it becomes to capture this information correctly at order level rather than only when preparing the VAT return. If all inventory genuinely remains in one Member State and the company does not carry out additional activities abroad that create local VAT obligations, OSS may in practice allow it to scale D2C sales across many EU countries without proportionally increasing the number of local VAT registrations. This is precisely the type of model for which the scheme provides a particularly significant administrative simplification.

An online store dispatching exclusively from one Member State

An online store selling through its own website and dispatching all orders from one Member State is in a similar position, but the technical side of the model deserves particular attention. The fact that a company uses OSS does not mean that the reporting process becomes automatic. The sales system should correctly identify the Member State of consumption, apply the appropriate VAT rate for the relevant goods and retain the data needed to allocate sales to the correct country later. The accounting system, in turn, must receive the data in a format that allows OSS transactions to be separated from domestic sales, B2B transactions and other activities outside the scheme. With several thousand orders per month, even a small error in VAT-rate logic or country allocation can be repeated hundreds of times, so the process should be prepared before sales volumes increase.

For a business planning expansion, continuous monitoring of the common EUR 10,000 threshold is also important. It should not be tracked separately for each market because the relevant transactions are counted together. Once the threshold is exceeded, the change in taxation is not deferred until the next year. If the company expects rapid growth, it may also opt earlier for taxation in the Member States of consumption and use OSS, while taking into account the consequences of that decision. In practice, the model of one warehouse, one online store, B2C sales into multiple EU Member States is one of the cases in which OSS can provide the greatest administrative benefit, provided that the sales and accounting data are set up to handle multiple VAT rates and correct country-by-country reporting.

Fulfilment or warehouses in several EU countries

A multi-warehouse model changes the analysis fundamentally. If a business stores goods not only in its home Member State but also, for example, in Germany, the Czech Republic or France, it is no longer enough to look only at the customer’s country. It is also necessary to determine where the goods were located before the sale and where transport began. A transfer of the business’s own inventory from one Member State to a warehouse in another country may itself constitute a separate VAT event which, in a typical model, gives rise to a deemed intra-Community supply in the Member State of departure and a corresponding intra-Community acquisition in the country of destination. If the goods are subsequently sold to a consumer located in the same country as the warehouse, a domestic sale will generally arise and be reported locally. Only a dispatch from that warehouse to a consumer in another Member State may once again qualify as an intra-Community distance sale eligible for OSS.

In practice, multi-country fulfilment therefore usually leads to a mixed model: local VAT registrations in the Member States where relevant obligations arise, combined with OSS for qualifying cross-border B2C supplies. This does not mean that every foreign warehouse in every possible structure automatically creates identical obligations, as specific exceptions and special procedures may affect the analysis. For a typical e-commerce business, however, establishing foreign stock should always be preceded by a review of the VAT consequences. The biggest mistake would be to assume that because the company is already registered for OSS, it can report every transaction generated by a new warehouse through that scheme. OSS simplifies specific types of transactions, but it does not replace local VAT reporting across the entire logistics chain.

Selling into only one foreign market

If a business sells only into one foreign market, for example Germany, the choice of reporting structure may initially appear less obvious. Once the EUR 10,000 threshold has been exceeded, or where taxation in the Member State of consumption has been chosen, intra-Community distance sales to German consumers may be reported through OSS. Local VAT registration may be an alternative in some circumstances, but it should not be assumed to be automatically preferable simply because the business currently operates in only one foreign market. If the only activity in Germany consists of B2C sales of goods dispatched from another Member State, OSS may still reduce administrative work and provide a single mechanism that can easily be extended to other countries if the company expands further.

The position may be different where activity in that one foreign market involves more than distance sales alone. If the business holds inventory there, makes certain local purchases, imports goods or carries out transactions requiring local reporting, VAT registration may be needed independently of OSS. At that point, the decision is no longer a simple choice between two equivalent methods. OSS may continue to cover qualifying cross-border transactions, while the local VAT number is needed for other events. Even where a company sells into only one foreign market, the analysis should therefore consider not only the number of customers but the entire logistics and transaction structure. Those factors determine whether OSS is sufficient or whether the company will in practice also need local VAT reporting.

Goods dispatched from outside the EU directly to consumers

If, before the sale, the goods are located outside the European Union and are dispatched directly from a third country to an EU consumer, the analysis is different from an intra-Community distance sale between two Member States. In this model, it is necessary to determine whether the Import One Stop Shop, or IOSS, may apply. IOSS covers distance sales of imported goods in consignments with an intrinsic value not exceeding EUR 150, excluding goods subject to excise duties. It should therefore not be confused with the Union OSS scheme used for qualifying supplies within the EU. Although both systems are designed to simplify VAT compliance, they apply to different movements of goods and operate under different rules. The reporting frequency also differs: while the Union OSS scheme is generally reported quarterly, IOSS returns are filed monthly.

It is also important to distinguish the EUR 150 limit used for IOSS from the customs rules applying to low-value consignments. From 1 July 2026, EU customs rules for such consignments changed and a temporary customs duty of EUR 3 per item category in a consignment was introduced, generally applying until 1 July 2028, subject to the relevant rules and exceptions. This means the previous simplification often expressed as “consignment up to EUR 150 = no customs duty” no longer accurately describes the legal position. The change in customs rules did not, however, remove the EUR 150 limit applying to the IOSS scheme itself. A business dispatching goods directly from outside the EU therefore needs to analyse separately how VAT is handled through IOSS and what current customs charges and import obligations apply.

For the business, this means the analysis should begin by identifying where the product is physically dispatched from. If goods first enter a warehouse in one EU Member State and are only then sold to consumers in other countries, the business is operating under a different model from a seller dispatching individual consignments directly from outside the EU to consumers. In the latter case, the key issues are the conditions for IOSS, the value of the consignment, the nature of the imported goods and the current customs rules. It would therefore be a mistake to assume that being registered for the Union OSS scheme automatically resolves the VAT and import issues associated with B2C sales fulfilled directly from third countries.

“What happens if I don’t do it?” — the consequences of ignoring VAT obligations

You may account for VAT in the wrong country

The first risk is determining the place of taxation incorrectly. If a business does not distinguish between domestic sales, intra-Community distance sales, B2B transactions and other movements of goods, VAT may end up being declared in a different Member State from the one in which it is actually due. The problem is not always visible at the level of a single order. An online store may charge VAT, issue a sales document and recognise the revenue, with the mistake only becoming apparent when the VAT return is prepared or warehouse movements are analysed. When operating across several countries, it is therefore not enough to know that the customer is “abroad”. The business needs to establish where the goods were physically dispatched from, where they were delivered and what type of transaction actually took place.

In practice, the risk becomes particularly significant when a company changes its logistics faster than it updates its VAT setup. A business may spend several years dispatching all goods from one Member State and then open a warehouse abroad while continuing to treat orders according to the previous rules. Yet a sale to the same customer may become a completely different transaction for VAT purposes once the place of dispatch changes. If the reporting process is not updated alongside changes in the supply chain, VAT returns may stop reflecting the actual flow of transactions. The longer such a model continues, the more transactions may later need to be reviewed and corrected.

OSS will not “fix” a sale that requires local VAT

One of the riskiest assumptions is treating OSS as a safe place into which all European B2C sales can be placed. The scheme does not change the nature of the transaction. If goods are held in a German warehouse and dispatched to a German consumer, the transaction will generally be a domestic German sale. Reporting it through OSS as an ordinary seller does not turn it into an intra-Community distance sale. Likewise, transferring a business’s own inventory between two Member States does not become an OSS transaction simply because the company uses OSS for other parts of its activity. Each event first needs to be classified correctly, and only then can the business determine which return it belongs in.

This mistake can be particularly easy to make in a company that started with a simple single-country dispatch model and later expanded its logistics into other Member States. While all goods were leaving one warehouse, most cross-border B2C sales may have followed a similar pattern. Once local inventory is introduced, however, one sales channel can begin generating several different types of transactions. If the business continues sending all of them into one OSS “bucket” without taking account of where transport begins, part of the reporting may be incorrect. OSS is a mechanism for declaring specific types of transactions, not a system that automatically corrects an incorrect sales classification.

A foreign warehouse may create obligations earlier than you expect

Businesses often focus on sales levels because thresholds and new obligations are commonly associated with turnover. With a foreign warehouse, however, the relevant VAT event may arise before the first order is ever fulfilled from the new location. The transfer of a business’s own goods from one Member State to a warehouse in another EU country may, in a typical model, give rise to a deemed intra-Community supply in the Member State of departure and a corresponding intra-Community acquisition in the Member State of destination. This does not depend on whether B2C sales from that warehouse have already reached a particular scale. A company may therefore enter a new set of VAT obligations while reorganising its logistics, rather than only once the foreign market begins generating substantial revenue.

This is why the EUR 10,000 threshold should not be treated as a universal safe harbour for all cross-border activity. It applies to specific transactions and to the rules determining their place of taxation, not to every possible operation carried out by an e-commerce business in the EU. A company may have consumer sales below this amount and still carry out activities abroad that require separate VAT analysis. This is particularly relevant when introducing a new fulfilment model or moving inventory into another country. The tax consequences should ideally be analysed before the goods are physically moved. Reviewing the position later means reconstructing flows that have already taken place and may require earlier periods to be corrected.

Errors can grow together with sales volumes

In a small online store, a single mistake can sometimes be traced relatively easily to one specific order. In a medium-sized e-commerce business operating across several markets at once, the situation is very different. A company may use several warehouses, multiple sales channels and numerous delivery routes, while the same product might one day be dispatched from one Member State to Germany, another day from Germany to France, and on another occasion from a German warehouse to a German customer. If the transaction-classification logic is designed incorrectly, the problem does not occur only once. It is automatically repeated across future orders. As a result, a small logical error in the system can affect a significant proportion of sales after several quarters.

Scale also makes it more difficult to establish later which transactions should have been included in OSS, which should have appeared in local VAT returns, and which related to transfers of own goods or B2B sales. As a company grows, an approach based on manually correcting reports only at the end of the reporting period becomes increasingly ineffective. It is much safer to assign the correct transaction type at the moment the transaction occurs, based on the storage location, the country where transport begins, the country where transport ends and the status of the customer. Otherwise, expansion that delivers the expected commercial growth may at the same time increase the number of unidentified or incorrectly classified VAT events.

Poor records make later corrections much harder

OSS does not reduce record-keeping obligations to the quarterly return alone. A business using the scheme must maintain detailed records that make it possible to determine which transactions were reported, in which Member States they were taxed, which VAT rates were applied and where the transport began and ended. Businesses using OSS are also required to retain the relevant records for 10 years from the end of the year in which the transaction took place. For a company operating at scale, this means maintaining consistent transaction data for much longer than a single quarter or tax year. Data points such as ship-from, ship-to and the warehouse from which a specific order was physically fulfilled therefore become particularly important.

Good records are also essential when the company itself discovers an error and needs to determine how extensive it is. Without information about the dispatch warehouse, the country where transport ended, the customer’s status, the sales value and the VAT rate applied, it can be difficult to establish whether a particular transaction should have been included in OSS, a local VAT return or another reporting mechanism. If tax reports are built from data that cannot later be linked back to individual orders and stock movements, reconstructing several previous quarters may require substantial work. The more markets and warehouses a business operates, the more important it becomes to be able to recreate the full path of the product from warehouse to final customer.

Backdated VAT, corrections and retroactive registration may only be the beginning

Incorrectly classifying a transaction can mean much more than simply moving one amount from the wrong return to the correct one. If a business should have reported certain transactions locally but failed to do so for an extended period, it may need to register for VAT retroactively, file overdue returns, correct previous reporting and pay any outstanding VAT together with interest. Depending on the rules of the relevant Member State, additional penalties or other procedural consequences may also arise. There is no single universal “EU penalty” for incorrect OSS reporting or failure to register locally, because detailed rules on penalties, interest and local compliance are determined by individual Member States.

For a medium-sized e-commerce business, the cost of an error can therefore go far beyond the amount of unpaid VAT itself. It can include the time needed to reconstruct historical data, identify the actual dispatch location of thousands of orders, prepare corrections, manage local registration procedures and redesign processes for the future. If the issue affects several Member States and multiple reporting periods, the workload can increase quickly. The most problematic scenario is therefore not simply that a business “did not choose OSS”. The real issue arises when OSS is treated as a solution covering all transactions, causing local VAT obligations to go unnoticed. The precise consequences of each error must ultimately be assessed under the law of the Member State in which the VAT obligation arose.

The most common mistakes when choosing between OSS and local VAT

“I use OSS, so I no longer need any foreign VAT numbers”

This is one of the most common oversimplifications because OSS can indeed reduce the number of foreign VAT registrations, but only for transactions that fall within the scope of the scheme. If a business dispatches goods from one Member State to consumers in other EU countries, qualifying intra-Community distance sales can be reported through OSS without the company having to register separately in every Member State of consumption solely because of those sales. The position changes, however, when the business begins using foreign warehouses, transferring its own inventory, making domestic sales from local stock or carrying out other activities outside OSS. In that kind of model, a local VAT number may be required even though the business uses the Union OSS scheme at the same time.

The best way to think about OSS and local registrations is as two parts of the same VAT framework rather than mutually exclusive alternatives. A company may hold a German VAT number because it stores inventory in Germany and makes domestic sales to German customers, while at the same time reporting qualifying intra-Community distance sales from Germany to consumers in France, Austria or other Member States through OSS. Simply having an OSS registration therefore does not answer the question of whether the business needs a local VAT registration. The first step is to identify what transactions the company actually carries out in each Member State and which of them fall within the scheme.

“The EUR 10,000 threshold applies separately in every country”

The EUR 10,000 threshold, excluding VAT, does not operate as a set of separate limits for individual markets. A business does not receive one threshold for Germany, another for France, another for the Czech Republic, another for Austria and further limits for each additional Member State. Where the conditions for applying the threshold are met, the relevant figure is the combined value of qualifying intra-Community distance sales and certain telecommunications, broadcasting and electronic services supplied to other EU Member States. A company may therefore remain below EUR 10,000 in every individual country and still exceed the threshold in aggregate. For a business developing several markets at the same time, this is particularly important because the total of multiple smaller sales streams can quickly change the place-of-taxation rules.

A second mistake is monitoring the threshold only after the end of the year. Exceeding it does not mean the business can continue using the previous VAT treatment until 31 December and switch to destination-country VAT only from January. The threshold needs to be monitored continuously because exceeding it affects the place of taxation of the relevant transactions. The previous calendar year also matters. For a company selling into many Member States, it is therefore useful to maintain one report showing the combined value of transactions counted towards the threshold rather than relying solely on separate reports for individual markets.

“I can report every B2C sale through OSS”

The fact that the customer is a consumer is not enough to make a transaction eligible for OSS. The business still needs to establish what type of supply has actually taken place. If goods are located in Germany and are dispatched or transported to a German consumer within Germany, an ordinary seller will generally be making a domestic German sale rather than an intra-Community distance sale. The transaction cannot simply be moved into OSS because the buyer is a private individual. The position is different if the same goods are dispatched from the German warehouse to a consumer in France. In that case, the transport takes place between two Member States and the transaction may qualify as an intra-Community distance sale eligible for the Union scheme.

In practice, this means that the “B2C” label should only be the beginning of the analysis. The business also needs information on where the goods were located, the Member State in which dispatch began and the Member State in which it ended. Only by combining these data points can the company determine whether a specific order belongs in OSS, a local VAT return or another reporting mechanism. Special rules may also apply, including to certain platforms treated as the supplier for VAT purposes, so even consumer sales should not be covered by one universal rule across every possible business model.

“A foreign warehouse does not matter until I exceed the sales threshold”

The EUR 10,000 threshold applies to specific cross-border B2C transactions and is not a general threshold below which a business can ignore every foreign VAT obligation. If a company transfers its own inventory from one Member State to a warehouse in another EU country, VAT consequences may arise from the movement of the goods itself. In a typical model, such a transfer gives rise to a deemed intra-Community supply in the Member State of departure and a corresponding intra-Community acquisition in the country to which the inventory has been moved, subject to the relevant exceptions and special procedures. Local VAT obligations may therefore arise before the first sale to a consumer is ever made from the foreign warehouse.

This becomes particularly important when the logistics model changes. A business may spend several years selling exclusively from one Member State and correctly focus on the rules for intra-Community distance sales and OSS. Once it moves part of its inventory abroad, however, the old logic is no longer sufficient. The new warehouse should be analysed before the goods are physically transferred because, for VAT purposes, the transfer itself, subsequent domestic sales and later cross-border shipments may all be relevant. B2C sales volume is therefore only one part of the overall analysis.

“OSS lets me apply my home-country VAT rate to sales across the EU”

OSS does not mean that cross-border sales become sales taxed at the VAT rate of the business’s home Member State. The Member State of identification acts as the jurisdiction through which the business files its OSS return and makes the payment relating to qualifying transactions in other Member States. Where an intra-Community distance sale is taxable in the Member State of consumption, the business should apply the rate applicable in the country where transport ends. A sale to a consumer in Germany is therefore subject to the appropriate German VAT rate, a sale to a consumer in France to the relevant French rate, and a sale to a customer in the Czech Republic to the rate applicable there for the goods concerned.

This distinction has very practical implications for online-store configuration and reporting. One OSS return does not mean one VAT rate or one tax market. The business still needs to identify the Member State of consumption correctly and know which VAT rate applies to the product in each country. OSS centralises reporting, but it does not remove differences between national VAT-rate systems. An error at this stage can be repeated across every subsequent order, which is why, at greater scale, correct VAT-rate configuration should be treated as part of the sales infrastructure rather than as a manual adjustment made shortly before the end of the quarter.

“I can report B2B sales through OSS as well”

Typical B2B sales are not reported through OSS simply because the seller and buyer are located in different EU Member States. OSS is primarily a mechanism for certain B2C transactions, which means the status of the customer is highly relevant when classifying a sale. A company serving both consumers and business customers should be able to distinguish these two streams at the sales-data level. The delivery country alone is not enough. The business also needs information that allows it to determine the nature of the customer and apply the VAT rules appropriate to the particular type of transaction.

The opposite assumption should also be avoided: a B2B transaction does not automatically create a local VAT registration requirement for the seller. The fact that a transaction falls outside OSS does not determine how it should ultimately be reported. For B2B sales, the ordinary VAT rules applicable to the specific type of supply and movement of goods must be applied. A sound reporting architecture should therefore include at least two basic layers of classification: first, whether the customer is a consumer or a business, and second, where the transport begins and ends and what type of transaction has taken place.

How to prepare your business for correct VAT reporting in the EU

Start with a map of your goods flows, not with tax forms

The best starting point is to establish who owns the goods, where the inventory is physically located and where orders are actually dispatched from. In a simple model, one warehouse in a single Member State may mean one dominant pattern for cross-border sales. Once a business starts using fulfilment centres in Germany, the Czech Republic, France or other countries, however, the number of possible flows increases quickly. The same product may be dispatched from one Member State to Germany, from Germany to France, or from a German warehouse to a German customer, and each of these movements may have different VAT consequences. In more complex models, it may also matter whether the company sells its own goods, operates under a consignment model, uses call-off stock arrangements or sells through an electronic interface that has a specific role for VAT purposes.

A practical map should therefore show at least the owner of the goods, the inventory location, the Member State in which dispatch begins, the Member State in which it ends, the customer’s status and the sales channel. It should also include inventory movements that do not immediately result in a sale. If goods are regularly transferred between the business’s home country and foreign warehouses, these movements should also be visible in the system and capable of being linked to the appropriate VAT treatment. For a company planning expansion, carrying out this analysis before opening a new warehouse is particularly important. It is much easier to determine the VAT consequences before inventory is moved into another country than to reconstruct later exactly when stock transfers began and which location fulfilled individual orders.

Determine the customer’s status and where transport ends

The second pillar is correctly establishing who the business is selling to and where the goods are actually delivered. The distinction between B2C and B2B affects whether a transaction can fall within the scope of OSS at all. The customer’s country alone is also not enough. Correct classification requires customer data to be combined with information about where transport begins and where it ends. Only then is it possible to determine whether the transaction is an intra-Community distance sale, a domestic sale, a B2B transaction or another event requiring separate VAT treatment. For sales to businesses, the customer’s EU VAT number and the result of its verification may also be relevant where they affect the VAT treatment of the particular transaction.

The B2B/B2C distinction should not, however, be reduced to the question of whether the customer entered a VAT number when placing the order. The buyer’s status should follow from the overall facts of the transaction and should be capable of being documented. From a systems perspective, what matters is retaining the information needed to reconstruct that assessment later. If, after the end of a quarter, the finance team receives only a report of turnover by customer country, without information about the dispatch warehouse, customer status or the data needed to verify B2B sales, correctly allocating transactions can become very difficult. At higher order volumes, commercial, logistics and tax data should therefore be connected.

Separate OSS, domestic sales and other VAT events

The next step should be to assign individual transaction flows to the correct reporting mechanism. Qualifying intra-Community distance sales may be reported through OSS, domestic sales from a foreign warehouse will generally be reported locally, while transfers of a business’s own inventory currently remain outside OSS. The company should also identify B2B sales, imports and other transactions subject to the ordinary VAT rules separately. This distinction should already exist in the underlying data before VAT returns are prepared, rather than being created manually only at the end of the process. Holding a German VAT number does not mean every order dispatched from Germany should be reported locally, just as using OSS does not mean that every B2C sale can be included in the scheme.

It is equally important to separate output VAT from input VAT. An OSS return is used to account for VAT due on transactions covered by the scheme, but it is not used to deduct input VAT shown on foreign cost invoices. If a business receives invoices containing foreign VAT, for example for logistics services or other operating costs, the method for recovering that VAT needs to be analysed separately. Depending on the circumstances, it may be accounted for through a local VAT return or recovered through the appropriate VAT refund procedure where the conditions are met. This is an important distinction because the fact that sales into a particular country are reported through OSS does not mean that foreign input VAT connected with the activity is also dealt with through OSS.

Check VAT rates and how they are updated

Once the place of taxation has been established, the correct VAT rate must be determined. Under OSS, a business still applies the VAT rate applicable in the Member State of consumption to the specific type of goods or services being sold. A company selling the same product in several countries may therefore need to apply different rates depending on the market. It should not automatically transfer the product classification used in its home Member State to other countries. The fact that a product qualifies for a reduced VAT rate in one Member State does not mean the equivalent rate will apply in Germany, France, the Czech Republic or elsewhere in the EU. The classification and applicable rate need to be established for the relevant Member States of consumption.

This is particularly important in categories where reduced rates are common, such as food, books, certain medical products and other goods subject to special rules. The broader the product range and the greater the number of markets, the more important a consistent product-classification and tax-data update process becomes. For a medium-sized e-commerce business, the aim should be to avoid situations in which the finance team discovers an incorrect VAT rate only after the quarter has ended. The rate should already be assigned correctly when the order is placed, and the company should be able to reconstruct later which rate was applied to a particular transaction and on what basis.

Make sure your reporting can reconstruct the entire transaction

At a small scale, many businesses can prepare VAT reporting using relatively simple reports exported from their online store. As the business expands, however, the limitations of this approach become clear very quickly. A report showing only the customer’s country and the order value is not enough where several warehouses are involved. Correct classification requires information about where the product was physically dispatched from, where transport ended, the customer’s status and the VAT rate applied. B2B sales may also require information about the customer’s VAT number and its verification, while multi-channel models may require the sales source to be distinguished as well.

For compliance purposes, it is therefore useful to build a data model that includes, among other things, the order or transaction ID, date, stock location, ship-from, ship-to, B2B or B2C status, customer VAT number where relevant, taxable amount, currency, VAT rate applied, VAT amount, transaction type and sales channel. This does not mean that every one of these items is a separate statutory field required for OSS records. The objective is to maintain a level of detail that allows the company to reconstruct how a sale was classified and to prepare the correct VAT reporting later. This also matters because OSS documentation must be retained for an extended period. A business therefore needs to know not only whether it can calculate today’s return, but also whether it will still be able to reconstruct the path of a specific order from warehouse to customer several years later.

Analyse VAT before changing your logistics, not after

The most important moment for VAT analysis often comes not when launching a new language version of an online store, but when changing the way orders are fulfilled. As long as a business dispatches goods from one Member State to customers across the EU, the model may remain relatively straightforward. Opening the first foreign warehouse introduces new flows: transfers of the company’s own stock, domestic sales and intra-Community distance sales beginning in a different Member State. Every additional warehouse increases the number of possible combinations, which is why the VAT consequences should be analysed alongside the logistics decision rather than several months after implementation.

For a business planning expansion, the practical question should therefore not only be “which country do we want to store the goods in?”, but also “who will own that inventory, what new VAT flows will arise, and can our system distinguish between them?”. The answer may affect the need for local VAT registration, the reporting setup, the treatment of inventory transfers, the recovery of input VAT and the scope of data required from the logistics provider. The earlier these elements are considered, the easier it is to build a model that can scale into additional markets without having to reconstruct thousands of historical transactions manually at a later stage.

VAT OSS or local VAT registration — summary

One warehouse in one EU Member State and B2C sales across the EU will often point towards OSS

If a business keeps all of its inventory in one EU Member State and dispatches orders from there to consumers in other EU countries, OSS will often be the most natural way to report qualifying intra-Community distance sales once the common EUR 10,000 threshold has been exceeded or where the business has opted earlier for taxation in the Member States of consumption. The scheme allows VAT due in multiple countries to be reported through a single Member State of identification, without creating a local VAT registration solely because the online store has started selling to consumers in another market. This does not, however, mean applying the VAT rate of the business’s home Member State to all sales. The company still needs to determine the correct Member State of consumption, apply the appropriate VAT rate there and maintain data that allows each order to be assigned to the correct reporting mechanism. For a business expanding from a single warehouse, OSS can therefore significantly simplify administration, but it does not remove the need to classify transactions correctly.

A foreign warehouse can create local VAT obligations

The situation changes when expansion involves not only sales but also physically moving inventory into another Member State. A foreign warehouse should trigger an analysis of local VAT obligations before the first batch of products is moved. In a typical model, transferring a business’s own goods from its home Member State to a warehouse in another EU country may give rise to a deemed intra-Community supply in the Member State of departure and a corresponding intra-Community acquisition in the Member State of destination. A subsequent sale from that warehouse to a consumer in the same country will generally be a domestic sale and may require local VAT reporting. This does not mean that every possible form of storing goods abroad automatically creates identical obligations, as exceptions, special procedures and the structure of the particular model may also be relevant. For a typical e-commerce business, however, establishing foreign stock is often the point at which OSS alone may no longer be sufficient.

In a multi-warehouse model, OSS and local VAT numbers often operate in parallel

The more decentralised the logistics structure becomes, the less useful the question “OSS or local VAT registration?” becomes. A company holding inventory in several Member States may simultaneously make domestic sales, transfer its own goods between warehouses and carry out intra-Community distance sales to consumers in other countries. Each of these flows may be subject to different VAT rules. For example, a sale from a German warehouse to a German consumer will generally be reported locally, while a shipment from that same warehouse to a consumer in France may qualify as an intra-Community distance sale reported through OSS. The transfer of inventory from another Member State into Germany remains a separate event. In practice, this means that local VAT numbers and OSS are not competing solutions. They can operate as two parallel components of the same VAT reporting framework, with each covering a different type of transaction.

For this reason, the key when planning expansion is not to find one VAT solution for the entire business, but to separate the individual flows correctly. The company needs to know where the goods are located, where transport begins, where it ends, who the customer is and what type of transaction has taken place. Only then can it determine which transactions should be reported through OSS, which require local VAT reporting and which fall outside the scope of the scheme altogether. This is particularly important before launching fulfilment in another Member State, changing the point of import or moving inventory closer to customers. A logistics decision can change VAT obligations even when the online store, product range and customer-acquisition model remain exactly the same.

Not sure which transactions should be reported through OSS and which require local VAT registration? Before entering another market, it is worth analysing the entire sales and logistics model rather than looking only at turnover in a particular country. amavat can help map the movement of goods, identify where local VAT obligations may arise and determine where OSS may apply. This gives the business a clearer view of the tax consequences of expansion before inventory has already been distributed across several warehouses and sales are being carried out simultaneously in multiple markets.

Check what VAT obligations your sales model may create

If you are planning to enter another EU market, open a foreign warehouse or expand fulfilment across several Member States, start with a short description of your model. Specify where you currently store your goods, which countries they are dispatched from, which markets you sell into, and whether your customers are mainly consumers, businesses or both. If you already use local VAT numbers or the OSS scheme, it is also worth including this information. This makes it easier to identify which areas require further analysis and where obligations relating to local VAT registration or OSS reporting may arise.

Legal status: September 2026. This article describes the rules applicable at the time of publication. Changes arising from the ViDA package may affect, among other things, the rules on foreign VAT registrations and transfers of own goods in the coming years, so the current legal position should be checked before implementing a new sales or logistics model.

This material is for information purposes only and does not constitute a tax filing, legal advice or individual tax advice. For more complex models, particularly multi-country fulfilment, call-off stock arrangements, sales through platforms covered by the deemed supplier rules, or imports made directly into foreign warehouses, the correct VAT treatment should always be determined based on the specific business model and the rules in force at the relevant time.