VAT is one of those topics ecommerce store owners put off until they can't anymore. It feels like an accountant problem — something to deal with later, once the store is big enough. Then a cross-border sale lands, or a marketplace flags a compliance issue, and "later" arrives faster than expected.

The rules aren't simple, but they're not incomprehensible either. This article walks through what actually triggers VAT obligations for online stores, the scenarios where things tend to go wrong, and how integrating a VAT API can take most of the ongoing work off your plate.

What triggers a VAT obligation in ecommerce

VAT — value added tax — is a consumption tax applied at each stage of a supply chain, ultimately borne by the end buyer. For ecommerce businesses, the obligation to collect and remit VAT is triggered by a combination of factors: where you're based, where your customers are, what you're selling, and how much of it.

In the EU, the rules changed significantly with the introduction of OSS (One Stop Shop) in July 2021. Before OSS, a UK or US store selling into France had to register for VAT in France once it hit the French distance selling threshold. Now, EU-based sellers can register once via OSS and cover all 27 member states through a single return. Non-EU sellers shipping physical goods into the EU face different rules again — and since the €22 low-value goods exemption was scrapped, that means VAT is due on virtually everything, including low-ticket items.

In the UK, post-Brexit rules apply independently. Stores selling into the UK from abroad are liable for UK VAT once they exceed £85,000 in taxable turnover, or from the first sale if they're using a marketplace that's responsible for collecting VAT on their behalf.

The moment you start selling across borders at any meaningful volume, VAT stops being one country's problem and becomes several countries' problem simultaneously.

The US adds another layer of complexity: there's no federal VAT, but there is sales tax, and since the 2018 South Dakota v. Wayfair ruling, states can require out-of-state sellers to collect sales tax once they exceed economic nexus thresholds — usually $100,000 in sales or 200 transactions in that state. This isn't VAT in the European sense, but functionally it creates the same compliance burden for stores selling into the US market.

Where ecommerce stores get VAT wrong

Charging the wrong rate

VAT rates aren't uniform, even within the EU. Standard rates across member states range from 17% (Luxembourg) to 27% (Hungary). Reduced rates apply to specific categories — food, books, medical goods — and vary country by country. A clothing store selling children's shoes into Ireland pays 0% VAT; the same shoes sold into Germany attract 19%. Getting this wrong doesn't just mean incorrect invoices. It means either overcharging customers (bad for conversion) or undercharging and absorbing the difference yourself (bad for margin).

Mishandling B2B vs B2C transactions

When selling to another business that's VAT-registered, the rules shift. Under the EU reverse charge mechanism, the buyer rather than the seller accounts for VAT. This means you should zero-rate the sale on your invoice — but only if the buyer has provided a valid VAT number. Accepting an invalid or fake VAT number and zero-rating the transaction anyway is a compliance failure that can result in backdated liability.

Validating VAT numbers in real time at checkout is the only reliable way to handle this. Manually cross-referencing against the VIES database for every B2B order is impractical at any volume above a handful of sales per week.

Ignoring digital goods rules

Digital products — software, ebooks, online courses, SaaS subscriptions — follow different VAT rules to physical goods. In the EU, VAT on digital services is charged at the rate of the customer's country, not the seller's. A French SaaS company selling a subscription to a German business consumer pays German VAT, not French. This applies from the first euro of sales with no threshold, which catches a lot of early-stage digital businesses off guard.

How a VAT API solves this in practice

The core problem with VAT compliance in ecommerce is that the rules are dynamic: rates change, thresholds change, country-specific exemptions shift. Maintaining a manually updated tax table is a permanent liability. One missed update — say, a rate change in a market you sell into — creates a gap between what you're charging and what you owe.

A VAT API solves this by outsourcing the data layer. Instead of your platform referencing a static internal rate table, it queries the API at the point of sale and receives the correct current rate for that transaction — based on the buyer's country, the product category, and whether it's a B2B or B2C sale.

The VAT API handles this end-to-end: real-time rate lookups across EU member states, VAT number validation against the VIES system, and clean JSON responses that integrate into any checkout stack without a heavy lift from your development team. For stores that have been managing VAT manually or relying on a plugin that updates rates infrequently, the switch to a live API feed is usually the single highest-leverage compliance improvement available.

VAT number validation at checkout

One of the most practical use cases is B2B checkout flows. When a business buyer enters their VAT number, the API validates it in real time against the official VIES registry and returns a confirmed result — including the registered business name and address — before the transaction completes. This gives you the documentation needed to legitimately zero-rate the sale and protects you in the event of an audit.

Rate lookups by country and product type

The API accepts a country code and product category and returns the applicable rate — standard, reduced, super-reduced, or zero. For stores with diverse product catalogues, this means the correct rate is applied automatically regardless of what's in the basket or where the buyer is located. No edge cases slipping through. No rate frozen at whatever was accurate when someone last updated the config.

Practical steps for getting compliant

If your store is currently handling VAT manually or not at all, here's a sensible order of operations:

• Audit which markets you're selling into and what your current turnover is in each. This tells you where you're already over threshold and where you're approaching it.
• Determine whether your sales are primarily B2C, B2B, or mixed — this affects which rules apply and whether reverse charge is relevant to you.
• Identify your product categories and check whether reduced rates apply in your key markets. Don't assume everything attracts the standard rate.
• Integrate a VAT API so rate lookups happen dynamically at checkout rather than from a static table you're maintaining yourself.
• Set up VAT number validation for any B2B checkout flow so zero-rating is only applied when the number is confirmed valid.
• Register for OSS if you're EU-based and selling across member states — this consolidates your filing significantly.

Getting VAT right is less about understanding every rule in every country and more about building a system that applies the right data automatically, without depending on someone remembering to update a spreadsheet.

What happens if you ignore it

The consequences of getting VAT wrong — or not dealing with it at all — range from annoying to genuinely damaging. At the minor end: incorrect invoices, customer complaints, and the administrative work of issuing credit notes and re-invoicing. At the serious end: backdated VAT liability with interest and penalties, removal from EU marketplaces for non-compliance, and in some cases personal liability for directors of companies that have systematically under-collected.

Tax authorities across the EU have significantly improved their ability to track cross-border digital transactions. The data sharing mechanisms introduced under DAC7 mean that sales made through platforms are increasingly visible to member state tax authorities, even when the seller is based outside the EU. Assuming you're too small to be noticed is a bet that gets harder to justify the more years pass.

The bottom line

VAT compliance for ecommerce isn't optional once you're selling cross-border at any real volume. The rules are complex enough that maintaining them manually is both time-consuming and error-prone. The practical answer for most stores is to treat VAT data the same way you'd treat any other critical external data — connect to a live source, validate in real time, and stop relying on static configurations that drift out of date.

The technical barrier to doing this properly is lower than most store owners expect. A well-documented VAT API, a straightforward integration into your checkout layer, and a one-time audit of your current obligations is usually enough to get from reactive to compliant — and to keep you there as the rules continue to evolve.