Why US Brands Selling Into Europe Are Rethinking DDP Incoterms After New EU Customs Rules
25.05.2026
Seller Fulfilled Prime in Europe: Can Non-EU Brands Qualify and What Logistics Setup Do They Need?
25.05.2026
FLEX. Logistics
We provide logistics services to online retailers in Europe: Amazon FBA prep, processing FBA removal orders, forwarding to Fulfillment Centers - both FBA and Vendor shipments.
A UK brand ships from a Polish 3PL warehouse to consumers in Germany, France, and the Netherlands. Each parcel crosses a consumption-country border. Each sale triggers a VAT obligation in the buyer's member state. Without a coordinated reporting structure, that brand faces up to 27 separate national VAT registrations — or a single, well-managed non-Union OSS registration that consolidates the entire reporting burden into one quarterly return filed in one EU country.
Poland's formal introduction of Bill No. UC147 in May 2026, transposing Articles 2 and 4 of EU Council Directive 2025/516 (the ViDA package), sharpens the rules non-EU sellers must follow. This article explains what changed, who owns which obligation, and what operational data your fulfillment setup must capture to keep EU-wide B2C VAT compliance manageable from day one.
What the ViDA Transposition Actually Changes for Non-EU Sellers
The ViDA package is not a new tax. It is a structural refinement of how existing VAT obligations are assigned, reported, and enforced across EU member states. For non-established sellers — those without a fixed establishment in any EU country — the most consequential changes fall into three areas.
First, the €10,000 annual threshold that previously allowed some sellers to apply origin-country VAT rates has been clarified. Bill UC147 specifies that sales dispatched from foreign or multi-country 3PL nodes do not count toward this threshold calculation. In practice, a non-EU seller using a centralized European fulfillment hub in Germany or Poland is almost certainly already above the threshold and must apply destination-country VAT rates on every B2C sale.
Second, tax-point rules have been harmonized. The moment of VAT liability is now tied to the confirmed dispatch event — the point at which the parcel leaves the warehouse — not the payment date or order confirmation. This makes dispatch-country mapping a compliance-critical data field, not just a logistics metric.
Third, the platform deemed-supplier regime has been extended to cover certain cross-border B2B transactions processed through digital marketplaces, shifting VAT collection responsibility to the platform in defined scenarios. For direct-to-consumer webshops, no such transfer occurs. The seller remains fully exposed.
The Non-Union OSS Registration Path
A non-EU seller with no EU establishment registers for the non-Union OSS scheme in any member state of their choosing. Poland and Ireland are common entry points due to administrative accessibility. Once registered, the seller files a single quarterly VAT return covering all B2C sales to EU consumers, applying the VAT rate of each buyer's country to each transaction.
Bill UC147 removes one historical friction point: the previous requirement to provide a website URL during non-Union OSS configuration has been dropped under the Polish transposition. This reduces onboarding friction for sellers operating across multiple storefronts or headless commerce architectures. The registration itself requires a valid EORI number, business identification documents, and a designated tax representative in some member states. Verify current requirements with a qualified EU tax adviser before filing.
What Happens Without OSS Registration
Without a non-Union OSS registration, a non-EU seller dispatching B2C parcels from an EU warehouse is not exempt from VAT obligations. The obligation exists regardless of whether the seller has registered to collect it. Member states can and do pursue unregistered sellers through marketplace data-sharing agreements, customs import records, and carrier manifest audits.
The practical consequence is fragmented exposure: each destination country where a sale occurred becomes a potential enforcement jurisdiction. Retroactive registration, back-filing, and associated interest charges can accumulate across multiple tax periods before the issue surfaces. For a seller running pan-European B2C fulfillment services from a single hub, the gap between dispatch volume and registered VAT reporting is visible in carrier data long before it becomes a formal inquiry. Registering before the first parcel ships is the only operationally sound position.
The Dispatch Event as Your VAT Tax Point
Under the harmonized rules introduced by the ViDA package, the VAT tax point for distance sales is the confirmed dispatch event. This is the moment the parcel is handed to the carrier and a tracking record is created. For a non-EU seller using a European fulfillment hub, this means the warehouse management system must record the dispatch country, the destination country, the applicable VAT rate, and the transaction value at the exact moment of shipment — not retrospectively at month-end.
A fulfillment partner running automated inventory tracking and real-time dispatch-country mapping can generate this data field automatically for every outbound order. Without that automation, sellers typically reconstruct dispatch records from carrier invoices and order exports — a process that introduces reconciliation errors and creates gaps in the OSS quarterly return. The tax point is a data problem before it is a tax problem.
Deemed Supplier Rules: Marketplace Sales vs. Your Own Webshop
The deemed-supplier regime is one of the most misunderstood elements of the ViDA framework for non-EU sellers operating across multiple channels. Under the extended rules, online marketplaces that facilitate certain cross-border sales are treated as the deemed supplier for VAT purposes. The marketplace collects VAT from the buyer, remits it to the relevant tax authority, and the underlying seller receives a net payment without a VAT liability on that transaction.
This applies to B2C sales where the marketplace facilitates the transaction and the seller is not established in the EU. For sellers on major EU-facing platforms, a significant portion of their B2C volume may already be covered by the marketplace's deemed-supplier obligation — meaning the seller's own OSS return should exclude those transactions to avoid double-reporting.
The critical distinction is channel. Sales through your own direct-to-consumer webshop, brand website, or any channel where no marketplace intermediary is involved carry no deemed-supplier transfer. Every one of those transactions remains your VAT obligation, must be reported under your OSS registration, and requires a clean dispatch record tied to the correct destination-country rate. Sellers running both marketplace and DTC channels need a data architecture that separates these two streams at the order level, not at the reporting stage.
What Your Data Stack Must Capture
For each B2C order dispatched from an EU fulfillment node, your system must record: the dispatch warehouse country, the buyer's delivery country, the applicable VAT rate for that country and product category, the transaction value excluding VAT, and the channel through which the sale was made. This data set is the foundation of your OSS quarterly return.
If your 3PL partner operates pan-European B2C and B2B fulfillment from multiple warehouse locations, the dispatch-country field must be assigned at the individual order level — not assumed from a default hub. A seller whose stock is split across a German and a Polish node may dispatch the same SKU from either location depending on stock availability. Each dispatch origin produces a different tax-point record and potentially a different VAT rate calculation for the same destination country.
Where the Data Architecture Breaks Down
The most common failure mode is a mismatch between the order management system and the warehouse management system. The order system records the sale channel and buyer country. The warehouse system records the dispatch location and carrier handoff. If these two systems do not share a common order identifier that survives the fulfillment handoff, the dispatch-country field is missing from the tax record.
A second failure point is product category mapping. VAT rates vary not only by destination country but by product type. A seller shipping food supplements, electronics, and clothing in the same outbound flow must apply different rates to different SKUs in the same parcel. If the product category is not mapped to the correct VAT rate in the order data before dispatch, the OSS return will contain systematic errors that compound across every quarterly filing. Catching this at the data architecture stage costs far less than correcting it after the first audit.
A Practical Owner Map: Who Files What
For a non-EU seller running EU-wide B2C operations, the VAT obligation ownership splits across three actors. The marketplace owns the deemed-supplier obligation for platform-facilitated sales and files its own VAT returns with each member state. The seller owns the OSS obligation for all direct webshop sales and files a single quarterly return in the OSS registration country. The fulfillment partner owns the data capture layer — recording dispatch country, destination country, and transaction value at the moment of shipment for every outbound order.
When this ownership map is clear before operations begin, each actor knows exactly which data fields they are responsible for generating and retaining. When it is not clear, the seller typically discovers the gap during the first OSS filing period, when the quarterly return cannot be reconciled against carrier records because the dispatch-country field was never systematically captured. Establishing the owner map at onboarding, not at filing time, is the operational control point that determines whether compliance is manageable or reactive.
The Hidden Compliance Gaps That Surface After Launch
Most non-EU sellers entering the EU market focus on customs clearance, import VAT, and initial product registration. The ongoing B2C VAT compliance layer — specifically the OSS quarterly return — is often treated as an administrative afterthought that will be handled by an accountant once the business is running. This assumption creates three specific gaps that become expensive to close after launch.
The first gap is retrospective dispatch data. If the warehouse management system was not configured to capture dispatch country as a mandatory field from day one, the seller must reconstruct this data from carrier manifests, which are not always organized by order reference. For a seller dispatching several hundred orders per week across multiple EU destinations, this reconstruction can take weeks and still produce an incomplete record.
The second gap is rate-change exposure. EU member states periodically adjust VAT rates for specific product categories. If the product-to-rate mapping in the order system is static and not updated when a member state changes its rate, the seller may under-collect VAT from buyers and under-report in the OSS return for the affected period. The liability remains with the seller regardless of what was collected at checkout.
The third gap is the B2B exception boundary. OSS covers B2C sales only. If a seller's EU customer base includes business buyers who provide a valid VAT number, those transactions must be excluded from the OSS return and handled under reverse-charge rules. A fulfillment system that does not flag VAT-registered buyers at the order level will mix B2B and B2C transactions in the same data export, requiring manual separation before each quarterly filing.
OSS Registration Checklist
- Confirm no fixed EU establishment exists that would require standard VAT registration instead of non-Union OSS
- Obtain a valid EORI number before registering — required for customs and often for OSS onboarding
- Select the OSS registration member state based on administrative accessibility and adviser availability
- Identify whether a local tax representative is required in your chosen registration country
- Map all active sales channels and confirm which are marketplace-facilitated and which are direct webshop sales
- Confirm your OSS registration country's filing calendar and quarterly deadline schedule
Fulfillment Data Readiness Checklist
- Confirm dispatch-country field is captured at order level in the warehouse management system, not assumed from a default hub
- Map every active SKU to the correct VAT rate for each destination country and product category
- Establish a shared order identifier between the order management system and the warehouse management system that survives the fulfillment handoff
- Configure buyer VAT number capture at checkout to flag B2B orders for reverse-charge exclusion
- Confirm the fulfillment partner can export dispatch records by order reference, destination country, and dispatch date for each quarterly period
- Test the data export against a sample OSS return before the first live filing period
Sequencing Your OSS and Fulfillment Setup Before First Dispatch
The operational sequence matters. A non-EU seller who selects a European fulfillment hub before completing OSS registration risks dispatching taxable B2C parcels without a valid reporting structure in place. The correct sequence runs in parallel tracks that converge before the first outbound shipment.
On the tax track: engage an EU VAT adviser to confirm your registration category, select the OSS member state, and initiate the registration process. OSS registration can take several weeks depending on the member state and the completeness of your documentation. Do not wait until stock arrives at the warehouse to begin this process.
On the fulfillment track: work with your 3PL partner to configure the warehouse management system for dispatch-country capture, product-category VAT mapping, and B2B order flagging. Confirm that the integration between your order management platform and the fulfillment system passes all required tax-point fields at the order level. If your setup uses API-based integrations, test the data flow end-to-end before go-live.
On the channel track: audit each active sales channel to determine whether marketplace deemed-supplier rules apply. For each channel where they do not apply, confirm that the OSS return will include those transactions and that the data feed from that channel is connected to the fulfillment dispatch record. The convergence point is a single, reconcilable data set that covers every B2C dispatch, every destination country, and every applicable VAT rate — ready for the first quarterly OSS filing without manual reconstruction.
Multi-Node Fulfillment and the Dispatch-Country Complexity
A seller splitting inventory across two or more EU warehouse locations — for example, a primary hub in Poland and a secondary buffer in Germany — faces an additional layer of dispatch-country complexity. The same SKU may ship from either location depending on stock levels, carrier cut-off times, or delivery promise requirements. Each dispatch origin is a separate tax-point record with a potentially different VAT treatment depending on the destination country.
This is not a theoretical edge case. Pan-European fulfillment infrastructure built around multiple nodes is specifically designed to reduce delivery times and carrier costs across the continent. But it requires the warehouse management system to assign the dispatch-country field dynamically at the order level, not statically at the product level. A seller whose OSS return assumes all dispatches originate from a single hub will produce a systematically incorrect return the moment a second warehouse node goes live. Configuring the data architecture for multi-node dispatch before expanding to a second location is the correct operational sequence.
Threshold Rule
Sales dispatched from foreign or multi-country 3PL nodes do not count toward the €10,000 annual threshold. Non-EU sellers using a centralized EU hub should assume destination-country VAT rates apply to every B2C transaction from the first sale.
Tax Point Rule
The VAT tax point is the confirmed dispatch event — the moment the parcel leaves the warehouse and a carrier tracking record is created. This field must be captured automatically at dispatch, not reconstructed from month-end carrier invoices or order exports.
Channel Separation Rule
Marketplace-facilitated sales covered by the deemed-supplier regime must be excluded from your OSS return. Direct webshop sales must be included. Mixing these two streams in the same data export produces a systematically incorrect quarterly filing that compounds across every reporting period.
What to Lock Before Your First EU Parcel Ships
The ViDA transposition, including Poland's Bill UC147, does not create new taxes for non-EU sellers. It clarifies and tightens the rules that already apply. For a UK, US, or Hong Kong brand using a European fulfillment hub to serve B2C customers across the continent, the practical effect is that the compliance infrastructure must be in place before the first parcel ships — not assembled reactively after the first quarterly filing deadline.
Three decisions determine whether your OSS compliance is manageable or fragile. First, confirm your registration category and initiate non-Union OSS registration in parallel with warehouse onboarding, not after it. Second, configure your fulfillment data architecture to capture dispatch country, destination country, product VAT category, and channel type at the order level for every outbound shipment. Third, establish a clear owner map: the marketplace handles deemed-supplier obligations for platform sales; your OSS registration covers direct webshop sales; your fulfillment partner's dispatch records are the source data for both.
Sellers who treat VAT compliance services as a tax-filing exercise rather than a data and operations discipline consistently encounter the same problem: the quarterly return cannot be filed accurately because the underlying dispatch data was never systematically captured. The fix is architectural, not administrative, and it is far easier to implement before go-live than to retrofit across a live operation.
If you are mapping out EU-wide B2C fulfillment and need a warehouse partner whose systems capture dispatch-country, destination-country, and order-channel data automatically at the point of shipment, speak with the FLEX. team about how our European fulfillment infrastructure supports your OSS compliance data requirements.
Verify your specific VAT registration obligations and filing requirements with a qualified EU tax adviser. FLEX. provides the operational and data layer — accurate dispatch records, multi-node inventory tracking, and B2C order fulfillment across the EU — that makes your tax adviser's job tractable.
