El ESPR 2026 transformará las operaciones de almacén en la UE
23 mayo 2026
Los retrasos aduaneros frenan la expansión marketplace en la UE
24 mayo 2026
FLEX. Logistics
Ofrecemos servicios de logística a minoristas en línea en Europa: preparación para Amazon FBA, procesamiento de órdenes de eliminación FBA, reenvío a Centros de Fulfillment — tanto para envíos FBA como de Vendedor.
Los vendedores transfronterizos que se expanden por múltiples países de la UE a menudo asumen que registrarse en el régimen de la ventanilla única (OSS) cubre su exposición al IVA. No es así — y la brecha entre lo que gestiona OSS y lo que no es donde reside la mayor parte del riesgo de auditoría. El IVA en la Era Digital (ViDA) es la reforma estructural de la UE sobre cómo se declara, recauda y verifica el IVA en las transacciones digitales y las cadenas de suministro de los marketplaces. Para los vendedores que utilizan FBA Pan-Europeo, almacenamiento en varios países o plataformas de marketplace, ViDA introduce nuevas capas de reporting que interactúan directamente con las obligaciones existentes de registro OSS. La decisión central que debe tomar todo vendedor es si su estructura actual de IVA — países de registro, método de declaración y configuración de facturación — sigue siendo válida bajo las normas que se están configurando. Este artículo mapea las obligaciones, los puntos de fallo y los controles operativos que determinan si su expansión en la UE se mantiene conforme o se convierte en un pasivo.
Qué cambia realmente ViDA para los vendedores de marketplaces
El IVA en la Era Digital no es un único cambio de norma. Es un paquete de reformas que cubre tres áreas principales: los requisitos de reporting digital, el modelo de proveedor considerado para las plataformas y el alcance actualizado de OSS e IOSS. La Comisión Europea ha estado implementando estas reformas por fases, y aunque los plazos de implementación han variado, la dirección está confirmada: el reporting de transacciones en tiempo real o casi real reemplazará a las declaraciones resumen periódicas en la mayoría de los Estados miembros en los próximos años.
Para los vendedores de marketplaces, el impacto operativo más inmediato proviene de las normas ampliadas del proveedor considerado. Bajo este modelo, la plataforma de marketplace — no el vendedor — se convierte en la parte responsable del IVA para ciertas transacciones B2C. Esto cambia quién declara, quién remite y quién asume la exposición a auditorías. Los vendedores que no entienden dónde se sitúa el límite del proveedor considerado pueden declarar dos veces, declarar de menos o estructurar su facturación incorrectamente frente a sus propias declaraciones OSS.
IVA de la UE para vendedores estadounidenses y otras marcas no comunitarias añade otra capa: la estructura del importador registrado, el registro EORI y el punto de entrada aduanero afectan a qué número de IVA se aplica a cada transacción. Un vendedor que importa a Alemania y vende desde un almacén en Polonia se enfrenta a un nexo de IVA diferente que uno que utiliza un único punto de entrada en Países Bajos. ViDA no simplifica esto — añade requisitos de precisión en el reporting sobre una estructura multi-país ya de por sí compleja.
Registro OSS: Qué cubre
El régimen de la ventanilla única permite a los vendedores declarar y remitir el IVA de las ventas B2C en todos los Estados miembros de la UE a través de un único registro en un país. Esto elimina la necesidad de registrarse por separado en cada país donde se entregan las mercancías, siempre que el vendedor no mantenga stock en esos países.
OSS cubre las ventas a distancia de bienes enviados desde un único Estado miembro de la UE a consumidores en otros Estados miembros. También cubre ciertos servicios digitales. El umbral que anteriormente permitía a los pequeños vendedores utilizar el tipo de IVA de su país de origen fue eliminado, lo que significa que OSS se aplica desde la primera venta transfronteriza.
Para los vendedores que utilizan servicios de logística transfronteriza con un único país de envío, OSS es una herramienta práctica. La declaración consolida el reporting y reduce la carga administrativa. Pero el registro OSS por sí solo no resuelve las obligaciones de IVA que surgen del inventario mantenido en múltiples países — eso requiere registros locales separados.
Dónde falla el registro OSS
OSS no cubre las ventas nacionales dentro de un país donde el vendedor mantiene stock. Si el inventario está en un centro de fulfillment en Alemania y un consumidor alemán lo compra, se trata de una transacción nacional alemana — queda fuera de OSS y requiere un registro de IVA alemán con obligaciones de declaración locales.
La exposición al IVA del FBA Pan-Europeo es el punto de fallo más común aquí. Los vendedores se inscriben en FBA Pan-Europeo sin darse cuenta de que Amazon mueve el inventario entre múltiples ubicaciones de FC en diferentes países. Cada país donde se mantiene stock crea un nexo de IVA local. OSS no absorbe esas obligaciones. Los vendedores que confían solo en OSS mientras ejecutan FBA Pan-Europeo suelen estar sub-registrados y expuestos a requisitos de declaraciones retroactivas.
La misma lógica se aplica a cualquier modelo de almacenamiento en varios países. Si un búfer de almacenamiento pre-Amazon en Polonia abastece tanto a consumidores polacos como checos desde stock local, ambos países pueden requerir registro directo independientemente del estado OSS.
The Deemed Supplier Rule and Your Invoicing Structure
Under the deemed supplier model, a marketplace that facilitates a sale may be treated as the VAT-liable party rather than the underlying seller. This applies to specific transaction types — typically B2C sales of goods where the seller is established outside the EU, or where goods are in a fulfilment warehouse at the point of sale.
The practical consequence for sellers is that the marketplace remits VAT on those transactions directly. The seller receives a net payment and must not also report those sales through OSS or a local VAT return. Doing so creates a double-reporting error that can trigger a VAT audit support request from the relevant tax authority.
The invoicing structure must reflect who is the deemed supplier for each transaction type. Sellers running mixed models — some sales through marketplace fulfilment, others through their own warehouse — need to segment their reporting carefully. E-invoicing EU requirements under ViDA will make this segmentation machine-readable and verifiable, reducing the margin for manual reconciliation errors.
Personal Liability and the Importer of Record Problem
One of the least-discussed risks in EU VAT compliance is personal liability exposure tied to the importer of record structure. When goods enter the EU, someone must be named as the importer of record on the customs declaration. That entity takes on legal responsibility for import VAT, customs duties, and the accuracy of the declared value and tariff classification.
For non-EU sellers — including US brands entering the EU market — the importer of record is often a logistics provider, a customs agent, or a local entity set up for that purpose. If the arrangement is not correctly structured, the seller may inadvertently hold personal liability for VAT debts that arise from incorrect customs entries, even if a third party filed the declaration.
This matters under ViDA because digital reporting will make the link between customs entries and VAT filings more transparent. A mismatch between the declared import value and the VAT reported on subsequent sales is a visible discrepancy in a real-time reporting environment. Tax authorities will have tools to flag these gaps automatically.
For sellers using DDP (Delivered Duty Paid) incoterms, the freight forwarder or logistics partner typically acts as importer. Sellers must confirm in writing who holds the importer of record role, which VAT number is used on the import declaration, and how that VAT is recovered. Assuming the logistics provider handles everything without a documented agreement is a structural risk that ViDA's reporting layer will expose.
Inventory Movement and VAT Nexus Triggers
Every time inventory crosses an EU internal border as part of a fulfilment operation, it can create a VAT event. Stock transfers between warehouses in different member states — even within the same seller's network — are treated as intra-community movements and must be reported.
Under current rules, these movements require a corresponding entry in the recapitulative statement (EC Sales List equivalent) and may require a VAT registration in the destination country. ViDA's digital reporting requirements will make these movements more visible to tax authorities across member states.
Sellers using Amazon FC forwarding across multiple countries, or running their own multi-country distribution model, need to map every inventory movement against their VAT registration footprint. A movement into a country where the seller is not registered is not just a reporting gap — it is a potential VAT debt from the date the stock arrived.
Marketplace Reporting Gaps and Audit Triggers
Marketplaces report seller transaction data to tax authorities in the countries where sales occur. Under ViDA's expanded data-sharing framework, this reporting becomes more granular and more frequent. Tax authorities can cross-reference marketplace-reported sales against the seller's own VAT filings.
Common audit triggers include: OSS filings that do not match marketplace-reported sales volumes; VAT numbers that appear on import declarations but not on local VAT returns; and sellers who stop filing in a country without formally deregistering.
A frozen seller account is often the first signal of a VAT compliance failure, not the last. Marketplaces are increasingly required to withhold VAT remittances or suspend accounts when a seller's VAT registration status cannot be verified. By the time an account is frozen, back-filing obligations may already cover multiple periods across several countries.
VAT audit support becomes essential at this point — not just for resolving the immediate dispute, but for reconstructing the transaction history that the audit will require.
A Practical Owner Map for Multi-Country VAT Obligations
When a seller operates across multiple EU countries, VAT obligations do not belong to a single party. The seller owns the registration decision and the filing accuracy. The marketplace owns the deemed supplier remittance for qualifying transactions. The freight forwarder or customs agent owns the import declaration. The fulfilment partner owns the inventory location data that determines which countries trigger a nexus.
In practice, these parties rarely communicate proactively about VAT consequences. A fulfilment partner moves stock to a new country to improve delivery speed. The seller's VAT adviser is not informed. A new nexus is created without a corresponding registration. Six months later, the seller receives a notice from the local tax authority.
The fix is not complex, but it requires a documented handoff protocol: any inventory movement that crosses an EU internal border must trigger a VAT review before the movement is confirmed. This is an operational control point, not a legal formality. Sellers who embed this check into their inbound planning process — whether for Amazon FC assignments or pre-Amazon storage decisions — catch the exposure before it becomes a debt.
E-Invoicing Under ViDA: What Sellers Often Miss
E-invoicing EU requirements under ViDA are among the most misunderstood elements of the reform. Many sellers assume e-invoicing means sending PDF invoices by email, or that their existing accounting software already handles it. Neither assumption is reliable.
ViDA's e-invoicing framework moves toward structured digital invoices — machine-readable formats that can be submitted to or validated by tax authority systems in real time or near-real time. Several EU member states have already introduced or announced mandatory B2B e-invoicing requirements ahead of the broader ViDA rollout. France, Germany, Italy, and Poland are among the countries with active or planned mandates, each with their own format requirements and submission timelines.
For cross-border sellers, the operational challenge is that invoice format requirements vary by country. An invoice that satisfies German requirements may not satisfy French or Italian requirements for the same transaction type. Sellers who issue a single invoice template across all EU markets risk non-compliant documentation for a portion of their transactions.
The second missed risk is the link between e-invoicing and VAT deduction. If a seller's purchase invoices from EU suppliers do not meet the local e-invoicing format requirements, the input VAT recovery on those invoices may be challenged during an audit. This affects cost-to-serve calculations for sellers who import goods and then sell through EU-based stock.
Sellers should audit their current invoice templates against the e-invoicing requirements of every country where they hold a VAT registration or operate a fulfilment node. This is a documentation control, not a technology project — but it requires country-by-country verification, not a single global template assumption.
VAT Registration and Filing Checks
- Confirm VAT registration in every EU country where inventory is physically held
- Verify OSS registration covers only dispatch-country sales, not local stock sales
- Check that IOSS registration is active if selling low-value goods directly to EU consumers from outside the EU
- Confirm the importer of record VAT number matches the VAT number used on local returns
- Review whether any marketplace transactions fall under the deemed supplier rule and are excluded from your own OSS filings
- Verify that EC Sales List or equivalent intra-community movement reports are filed for all cross-border stock transfers
Invoicing and Audit Readiness Checks
- Audit invoice templates against e-invoicing format requirements for each country where you hold a VAT registration
- Confirm that purchase invoices from EU suppliers meet local format requirements for input VAT recovery
- Verify that marketplace-reported sales data matches your OSS and local VAT return figures for the same periods
- Document the importer of record arrangement in writing with your freight forwarder or customs agent
- Confirm that any inventory movement across EU internal borders triggers a VAT nexus review before the movement is executed
- Retain transaction-level records for the minimum retention period required in each country where you are registered
Sequencing Your ViDA and OSS Compliance Review
Sellers who approach ViDA compliance as a single project tend to underestimate the sequencing problem. The obligations are interdependent: you cannot correctly scope your OSS filings until you know which transactions fall under the deemed supplier rule; you cannot confirm your deemed supplier exposure until you have mapped your inventory locations; you cannot map your inventory locations until your fulfilment partner provides accurate stock movement data.
A practical sequence starts with the inventory location audit. List every EU country where your stock has been physically present in the last 12 months — including temporary storage, cross-docking, and Amazon FC assignments. For each country, confirm whether you hold a local VAT registration. Any country with stock and no registration is a priority gap.
The second step is the transaction classification review. For each sales channel, determine which transactions are covered by OSS, which fall under the deemed supplier rule, and which require local VAT reporting. This classification drives the invoicing structure and the filing calendar.
The third step is the e-invoicing readiness check. For each country where you hold a registration, confirm the current invoice format requirement and whether your accounting system can produce compliant output. Flag any country where your current template does not meet the local standard.
The fourth step is the importer of record documentation review. Confirm in writing with your customs agent or freight forwarder who holds the importer of record role for each import lane, which VAT number is declared, and how import VAT is recovered. This documentation is the first thing a tax authority will request in a cross-border VAT audit support process.
When the Logistics Structure Creates the VAT Problem
VAT exposure in cross-border ecommerce is rarely caused by a filing error alone. More often, the root cause is a logistics decision made without a VAT review. A seller switches from a single-country fulfilment model to Pan-EU FBA to improve delivery speed. The logistics decision is sound. But without a corresponding VAT registration review, the seller is now holding stock in five or six countries with obligations in each.
The same pattern appears when sellers add a pre-Amazon storage buffer in a new country to reduce inbound lead times. The storage facility is in a different member state from the dispatch country. The stock movement into that facility is an intra-community transfer. The sales dispatched from that facility are local sales, not distance sales. OSS does not apply. A local registration is required.
Cross-border logistics services and VAT compliance are operationally linked. The logistics partner who manages the inbound flow, the customs clearance, and the FC forwarding holds data that the VAT adviser needs. Sellers who keep these two functions in separate silos — logistics on one side, tax compliance on the other — consistently discover their VAT exposure after the fact, not before.
OSS Scope Check
Before each OSS filing period, confirm that every transaction included is a genuine distance sale dispatched from a single country. Remove any transaction where stock was already located in the consumer's country at the point of sale — those require local VAT reporting, not OSS.
Deemed Supplier Boundary
For each marketplace channel, confirm which transaction types fall under the deemed supplier rule. Do not include those transactions in your own OSS or local VAT filings. Request transaction-level reports from the marketplace to reconcile against your own sales data each period.
Inventory Movement Protocol
Require written confirmation from your fulfilment partner before any cross-border stock movement is executed. The confirmation should include the destination country, the expected arrival date, and whether a local VAT registration exists for that country. No movement without a nexus check.
What to Lock Before Your Next EU Expansion Step
ViDA and OSS compliance is not a one-time setup. It is an ongoing operational discipline that must keep pace with logistics decisions, marketplace rule changes, and member state implementation timelines. The sellers who manage this well are not necessarily the ones with the most sophisticated tax software — they are the ones who have connected their logistics data to their VAT reporting process.
Before adding a new fulfilment country, a new marketplace, or a new inbound lane, the VAT review should happen at the planning stage, not after the first shipment arrives. The inventory location audit, the transaction classification review, and the importer of record documentation are not annual tasks — they are triggered by operational changes.
The practical next step for most sellers is a gap audit: map current VAT registrations against current inventory locations, identify any country where stock is present without a registration, and confirm that OSS filings exclude any transactions that fall under the deemed supplier rule or involve local stock. This audit does not require a full compliance overhaul — it requires accurate data from your logistics and marketplace partners, reviewed against your current filing structure.
Sellers using multi-country fulfilment models should also confirm that their customs clearance and forwarding arrangements include a documented importer of record agreement. This single document resolves a significant portion of the audit exposure that ViDA's enhanced reporting will make visible.
FLEX. supports cross-border sellers with the logistics and customs layer that sits underneath VAT compliance — including customs clearance, importer of record structuring, inbound forwarding, and inventory movement documentation across EU markets. If your current fulfilment or inbound setup may be creating VAT exposure you have not yet mapped, speak with the FLEX. team about the operational controls that can close those gaps. Verify your legal and tax obligations separately with a qualified VAT adviser — FLEX. handles the logistics infrastructure that makes compliant EU operations possible.
