VAT compliance suspension in the EU: what changed and what to do

TL;DRA VAT compliance suspension on Amazon IT means the platform has restricted or deactivated a seller's listings because Amazon has flagged a gap in the seller's VAT registration, reporting, or documentation for Italy or another EU member state. The suspension does not automatically resolve once a VAT number is supplied – the seller must follow a specific procedural path within Amazon's compliance system while also addressing the underlying tax-authority requirements. EU law, including the Platform-to-Business (P2B) Regulation and the Digital Services Act (DSA), gives sellers defined rights in this process that many do not know they hold.

This briefing covers what a VAT compliance suspension on Amazon IT actually is, how it differs from a standard performance deactivation, the procedural path under EU rules, the decision points where sellers go wrong, and what is still genuinely uncertain about how the regime is applied. If you are an Amazon IT seller whose account has been restricted or whose listings have been delisted on VAT grounds, this is the read your operations lead needs before anyone files a response.

What is a VAT compliance suspension on Amazon IT, and why is it different from other deactivations?

A VAT compliance suspension is a restriction imposed by Amazon when the platform determines that a seller does not meet the VAT registration or reporting obligations that apply to sales in Italy or other EU markets where the seller's products are offered. Amazon operates under a distinct legal obligation here: EU rules – most directly the P2B Regulation and the broader VAT compliance architecture introduced through EU VAT reform – require platforms to take active steps to ensure sellers trading on their marketplace are VAT-compliant. Amazon is not acting purely on its own commercial judgment; it is also responding to a regulatory obligation that applies to it as a platform.

That distinction matters immediately. A performance deactivation, such as a Section 3 suspension under the Amazon Business Solutions Agreement (BSA), is a contractual action. A VAT compliance restriction has a regulatory overlay. It triggers a different internal Amazon process and, critically, different rights for the seller under EU law. In matters we handle on Amazon IT, sellers frequently treat the two types identically and use the standard Seller Central appeal path – which is the wrong tool for a VAT compliance case and often makes things worse by creating a confusing paper trail before the real issue is addressed.

The practical trigger is usually one of three things: Amazon's automated VAT validation system fails to verify a seller's Italian VAT number (Partita IVA) or EU VAT registration for cross-border distance sales; Amazon receives information from a tax authority or a data-sharing trigger suggesting the seller is not registered where required; or the seller has not enrolled in Amazon's own VAT Services or provided the relevant VAT certificates during a periodic compliance sweep. Each of these has a different fix, and conflating them is a common source of prolonged suspension.

What changed under EU law, and why does it affect Amazon IT sellers now?

Several overlapping legal developments – EU VAT reform, the Platform-to-Business (P2B) Regulation, and the Digital Services Act (DSA) – have together created a compliance environment on Amazon IT that is meaningfully different from what existed even a few years ago.

Under the EU VAT rules for e-commerce (commonly referenced as the OSS/IOSS framework and related obligations for deemed-supplier platforms), Amazon in its role as a "deemed supplier" for certain cross-border transactions took on VAT collection and remittance responsibility for specific categories of sale. That repositioning changed how Amazon monitors seller VAT status: the platform now has a direct financial and regulatory stake in whether sellers on its marketplace are properly registered. What was once a background compliance check has become a front-line enforcement mechanism.

The P2B Regulation – the Platform-to-Business Regulation that applies across the EU – requires platforms to give sellers a statement of reasons before or at the moment of any restriction, suspension, or termination. It also requires platforms to maintain an internal complaint-handling system that sellers can use to challenge those decisions. On Amazon IT, this means that a VAT compliance suspension must come with a statement of reasons, and the seller has a documented right to contest it through Amazon's internal complaint mechanism. In matters we handle, sellers often receive a generic compliance notice that does not clearly satisfy the statement-of-reasons requirement – which is itself a point of leverage in the complaint process.

The Digital Services Act (DSA), which designates Amazon as a Very Large Online Platform (VLOP), adds another layer. Under the DSA, the internal complaint-handling system must be easy to access, effective, and handled within a reasonable time. For EU sellers, and particularly for Amazon IT sellers selling into the Italian market, this creates a procedural right that sits on top of the platform's own policies. The complete guide to EU marketplace regulation for sellers covers the interaction of these instruments in more detail.

What has not changed – and this is where complexity rises – is that the underlying VAT obligation itself is a matter of Italian and EU tax law, not Amazon policy. Amazon can lift the suspension once it is satisfied with the seller's compliance documentation; it cannot and does not resolve the seller's actual tax position with the Agenzia delle Entrate or other EU tax authorities. Those are parallel tracks, and both must move.

Who is affected, and what does the suspension actually look like in practice?

Amazon IT sellers affected by VAT compliance suspensions typically fall into several categories, and the appropriate response differs between them. Knowing which category applies is the first task in any competent handling of the matter.

The first group is sellers who are validly registered for Italian VAT – or for OSS covering Italian sales – but whose VAT certificate, number, or enrollment status has not been correctly reflected in Amazon's system. This is a documentation and process issue, not a substantive tax problem. The account can usually be reinstated once the correct certificates are uploaded in the right format through the Seller Central tax information section and, where needed, a direct verification request is escalated to Amazon's seller support compliance team. That said, getting the escalation in front of the right team is less straightforward than it sounds.

The second group is sellers who genuinely were not registered for Italian VAT when they should have been – for example, because they crossed the distance-selling threshold for Italy and did not register or enroll in OSS in time. Here, the Amazon compliance process and the Italian tax registration process must run simultaneously. Resolving the Amazon suspension without addressing the underlying registration exposes the seller to a renewed suspension the moment Amazon runs another VAT check.

The third group, which we regularly see in our practice, is sellers who received a VAT compliance notice as part of a broader account review – often because a related account or a third-party complaint triggered a sweep. In these cases, the VAT suspension is a symptom; the root cause may be a KYC/identity verification issue or an account health flag that needs to be addressed at the same time.

In all three scenarios, the seller's listings on Amazon IT are restricted or taken down during the review period. Sales stop. Inventory may be held in Amazon's Italian fulfillment centers (if the seller uses FBA). Disbursements may be paused. The commercial cost accumulates daily, which is why clarity on the actual category of problem – early – is the only thing that limits the damage.

What is the realistic procedural path?

The procedural path for a VAT compliance suspension on Amazon IT has two tracks that must be coordinated, not run sequentially.

Track one is the Amazon internal process. Under the P2B Regulation, the seller has the right to use Amazon's internal complaint-handling system to contest a suspension. The practical entry point is a formal response to the compliance notice, structured not as a standard Seller Central appeal but as an internal complaint that invokes the seller's rights under P2B and, where applicable, the DSA. This response should identify which specific VAT obligation is alleged to be unmet, provide the documentation that addresses it, and request a statement of reasons if the original notice did not adequately explain the basis for the restriction.

Where the notice fails to meet the P2B statement-of-reasons standard, that is noted explicitly in the complaint. Platforms are aware that procedurally deficient notices are a vulnerability. In our experience, a well-constructed internal complaint that names the relevant regulation tends to receive more substantive handling than a generic Seller Central case.

Track two is the underlying VAT position. If the seller needs to register for Italian VAT or enroll in the OSS scheme, that process runs in parallel. Italian VAT registration through the Agenzia delle Entrate, or OSS enrollment through the seller's home-country tax authority, takes a period of weeks. The Amazon process needs to know that this registration is in progress – documentation of the application, not just the final registration number, can be submitted to Amazon to demonstrate that the compliance gap is being actively closed. Amazon does not always accept in-progress documentation, but in a number of matters we have handled, a pending-registration letter from the relevant tax authority, submitted alongside the Amazon internal complaint, has supported reinstatement before the final registration number was issued.

Beyond these two tracks, sellers facing a suspension that is part of a broader account health action may also need to file a Plan of Action (POA) addressing the non-VAT elements of the deactivation. The VAT track and the POA track must be consistent – any inconsistency in timeline or factual description between them is an immediate red flag for Amazon's review team.

For sellers who have gone through the internal complaint process without resolution, the DSA provides a further escalation path: out-of-court dispute settlement through DSA-certified bodies. This is a newer tool, and the practical infrastructure for it is still developing across EU member states. Its utility for VAT compliance suspensions specifically is still being tested. The step-by-step guide to appealing an EU delisting covers the escalation options in detail.

A seller who has already exhausted the internal complaint path and is considering whether arbitration or another formal mechanism is the right next step should weigh the BSA dispute-resolution path against the EU regulatory tools. The BSA path depends on the version of the agreement that applies to the account – this is something we check at the outset of any matter. It is not safe to assume that the path available under a BSA version the seller signed several years ago is still the operative one.

Where do sellers go wrong, and what does the decision matrix look like?

The most consistent mistake is treating a VAT compliance suspension as a standard performance appeal and filing a root-cause Plan of Action through the normal Account Health channel. That approach addresses the wrong procedural path. It may also create a record that contradicts the parallel VAT track if the timelines or descriptions of the compliance gap are not precisely aligned.

A second common mistake is resolving the Amazon compliance case without addressing the underlying Italian or EU VAT registration. The account comes back, the seller resumes trading, and three months later Amazon runs another compliance sweep and the same suspension recurs – now with a worse account history. The fix that does not include the underlying tax position is not a fix.

Third – and this is the mistake that costs sellers the most time – is failing to invoke P2B and DSA rights explicitly. Platform compliance teams handle high volumes of cases. A response that names the Platform-to-Business Regulation, requests a proper statement of reasons, and identifies the specific compliance obligation at issue signals to the reviewer that this is not a case that can be closed with a form response. That signal alone can change the trajectory of a case.

The decision matrix, in practical terms, looks like this. If the notice specifies a VAT registration gap and you hold the correct registration or OSS enrollment: the route is a documentation-and-escalation complaint on the Amazon internal track, typically resolved within several weeks if the documentation package is complete. If the notice specifies a gap and you do not yet hold the required registration: the route is parallel registration plus a documented in-progress submission to Amazon, with the timeline set by the tax authority's processing speed. If the notice is vague or does not meet the P2B statement-of-reasons standard: the first step is a formal request for a compliant statement of reasons before any substantive response to the compliance allegation – that request itself resets the clock on Amazon's response obligation.

If earlier responses have already been submitted and rejected, the question becomes whether the internal complaint path has genuinely been exhausted or whether an earlier response simply used the wrong channel. In a number of matters we have seen, what the seller believed was a final rejection was actually a Seller Central case closure that had never been routed through the P2B complaint mechanism at all. That distinction leaves a path open. The analysis of Bundeskartellamt proceedings and their implications for sellers is a useful parallel read on how EU regulatory mechanisms interact with Amazon's platform governance more broadly.

An Amazon IT electronics seller (winter 2025) came to us after a VAT compliance suspension that had run for nearly two months. The original notice cited an unverified Italian VAT number; the seller had in fact enrolled in OSS in their home country but had not uploaded the OSS certificate in the format Amazon required, and had filed three standard Seller Central appeals without invoking P2B rights. We reconstructed the compliance documentation package, filed a formal P2B internal complaint with the OSS certificate and a covering explanation of the enrollment structure, and the listings were restored. The underlying OSS registration had been valid throughout – the issue was entirely in the Amazon documentation and escalation path.

If a first response to a VAT compliance notice was filed through the standard Seller Central appeal channel without invoking P2B or DSA rights, the process may not be as closed as the seller believes. A second read of the case history can identify whether a formal internal complaint has actually been filed at all.

For a confidential review of your Amazon IT compliance suspension, email info@tutamenlaw.com. We will assess the notice, the account history, and the VAT position before recommending a path.

What is still uncertain, and what sellers should watch

Several aspects of how VAT compliance suspensions interact with EU marketplace law are genuinely unsettled, and sellers should understand the limits of what is predictable.

The DSA's out-of-court dispute settlement mechanism for VLOP-imposed restrictions is operationally new. The bodies certified to handle these disputes under the DSA are still being designated in different EU member states, and their practical track record on VAT compliance cases specifically is limited. This tool exists in law; its utility in practice for Amazon IT VAT cases is still being established. We are tracking how it develops, but it would be misleading to present it as a reliable fast-track remedy at this stage.

The interaction between Amazon's deemed-supplier VAT obligations and individual seller registration requirements is also an area where the rules have not been uniformly applied or interpreted. In specific transaction categories, Amazon's assumption of the deemed-supplier role may reduce or eliminate the seller's individual Italian VAT registration requirement for those sales. The line between transaction types where this applies and those where it does not is not always clear in Amazon's compliance notices, and we have seen cases where Amazon issued a VAT compliance suspension for a registration obligation that the deemed-supplier rules may have displaced. This is a point worth examining in any matter before a substantive response is filed.

Platform enforcement automation is also evolving. As Amazon tightens its VAT compliance checks across EU marketplaces, the automated sweep systems are catching more edge cases – including sellers who are compliant but whose documentation is in a format or naming convention that the system does not recognize. The rate of false-positive VAT suspensions driven by documentation-format mismatches, rather than genuine compliance gaps, is something we regularly see in our practice. It does not make the suspension less disruptive, but it does change the response strategy considerably.

Finally, the P2B Regulation's enforcement varies by EU member state. In Italy, the relevant enforcement authority has discretion in how it prioritizes P2B complaints from individual sellers against platforms. Direct enforcement action through a national authority is a theoretically available route but is not a practical short-term remedy for most sellers. What the P2B Regulation does provide, practically, is the statement-of-reasons and internal complaint rights that a seller can assert directly on the platform – and those rights are the most useful lever in the near term.

Seller rights under the DSA and P2B: a summary of what applies

Sellers on Amazon IT facing a VAT compliance suspension hold specific rights under EU law that do not depend on Amazon's goodwill to exist. Understanding them is not just useful background; it is the foundation of an effective response strategy.

Under the P2B Regulation, Amazon must provide a statement of reasons before or at the time of any suspension or restriction. The statement must identify the specific facts and circumstances that led to the decision, and the specific grounds from Amazon's terms of service that apply. A generic notice citing "VAT compliance" without specifying which obligation, for which territory, based on which specific factual trigger does not meet this standard. A seller can request a compliant statement of reasons, and Amazon's failure to provide one is a procedural breach of the P2B Regulation.

The internal complaint-handling system required by P2B must be free of charge, accessible, and handled within a reasonable time. Amazon maintains such a system, though its accessibility for VAT compliance matters is not always obvious from the Seller Central interface. Invoking it correctly – naming the regulation, identifying the decision being challenged, attaching the relevant documentation – is meaningfully different from opening a standard Seller Central case.

Under the DSA, as a VLOP, Amazon has additional obligations around the speed and quality of its complaint-handling. VLOP-designation creates an accountability layer that sellers can reference in formal complaints. The DSA also provides access to out-of-court dispute settlement through certified bodies, as noted above. This is a developing area of practical law, and the value of the tool will become clearer as the certified-body infrastructure matures across the EU.

For Amazon IT sellers, an additional consideration is the Italian Consumer Code and sector-specific Italian consumer-protection rules, which in some configurations apply to relationships between platforms and their business users. These instruments are generally less directly relevant to a VAT compliance suspension than the P2B Regulation and DSA, but they form part of the broader regulatory context that an experienced practitioner will map at the outset of a matter.

A health-and-beauty FBA seller on Amazon IT (spring 2026) reached out after receiving a VAT compliance suspension that cited Italian VAT registration. The seller's Italian VAT number was valid, but the relevant tax authority certificate had expired during an automatic renewal delay – not because the seller had deregistered. We identified the gap, obtained the renewed certificate from the Italian tax authority, filed a formal P2B internal complaint naming the specific P2B statement-of-reasons deficiency in the original notice, and the account was restored. The broader account history was otherwise clean, which reduced the complexity considerably; the suspension was driven entirely by the expired documentation.

Related areas

• EU marketplace regulation for sellers – the full P2B, DSA, and DMA picture for Amazon and other platforms
• Appealing an EU delisting – step-by-step process for challenging a listing removal or suspension under EU rules

If an earlier response to a VAT compliance notice has already been rejected, or if the internal complaint path has not yet been used, we can review the case history and advise on what, if anything, remains open. Email info@tutamenlaw.com with a summary of the notices received and the responses filed so far.

Frequently asked questions

How long does resolving a VAT compliance suspension in the EU usually take on Amazon IT?

The timeline depends on which of the three seller categories applies – a documentation mismatch, a genuine registration gap, or a mixed account-health issue. A documentation-only case, where the seller holds the correct VAT registration or OSS enrollment but has not correctly uploaded it in Amazon's system, can resolve within several weeks of a properly filed P2B internal complaint with a complete documentation package. A case that requires a new Italian VAT registration or OSS enrollment adds the tax-authority processing time on top of the Amazon internal complaint timeline – that parallel process typically runs over several weeks to a couple of months, depending on the registering country's administration. Cases involving concurrent account health issues take longer, because the VAT track and the broader account health track must both be resolved, and the documentation across them must be consistent.

What are the main risks if I handle a VAT compliance suspension in the EU alone?

The principal risk is using the wrong procedural channel. Filing through the standard Seller Central performance-appeal process rather than the P2B internal complaint mechanism means the seller's rights under EU law are not being invoked, the case may be handled by a lower-tier review team, and a paper trail may accumulate that is inconsistent with the parallel VAT track. A second significant risk is resolving the Amazon suspension without fully addressing the underlying Italian or EU VAT registration position: the account returns, the seller resumes trading, and the suspension recurs on the next compliance sweep. A third risk is missing the interaction between the deemed-supplier rules and the seller's individual registration obligations – incorrectly admitting a registration gap that may not legally exist can complicate both the Amazon and the tax-authority track. For sellers whose inventory is held in Italian FBA centers, a prolonged suspension also means accumulating storage fees and the risk of a removal order for the inventory.

Do I need a lawyer for a VAT compliance suspension in the EU?

Not every VAT compliance suspension requires legal representation. A straightforward documentation-mismatch case, where the seller clearly holds the correct registration and the fix is an upload with a correct certificate format, can often be handled by a well-briefed seller or their compliance team. Legal representation adds consistent value where the original notice does not meet the P2B statement-of-reasons standard, where earlier responses have already been filed and rejected, where the underlying VAT registration question is genuinely complex (for example, across multiple EU member states or involving the deemed-supplier boundary), or where the VAT suspension is part of a broader account action. In matters we handle on Amazon IT, the cases that benefit most from attorney involvement are those where the seller has already used the wrong channel, created a confusing record, and needs a structured restart through the correct P2B mechanism – which is also, in practice, the most common situation by the time sellers reach us.

---

About Tutamen

Tutamen is an independent law firm for online marketplace sellers. We represent Amazon, Walmart, Etsy and eBay sellers in account deactivations, frozen-funds recovery, intellectual-property disputes, arbitration and Notices of Dispute, and US federal Schedule A defense, plus EU marketplace regulation. Our work is attorney-led and confidential, with fees quoted up front. We act for founders, brand owners and in-house teams who need a specialist for a marketplace dispute. Work is conducted in English; for matters involving EU regulatory instruments, our practice includes dedicated coverage of P2B, DSA, and DMA proceedings. To discuss your situation, email info@tutamenlaw.com.

Disclaimer: This article is general information, not legal advice, and does not create an attorney-client relationship. Marketplace policies and the law change, and every account and case is different. For advice on your situation, contact Tutamen at info@tutamenlaw.com.

By Dmitri Aronov – Partner, EU Marketplace Regulation | February 12, 2027