EU Packaging Waste Rules Under Pressure: What Amazon.fr Sellers Must Prepare Before Q4
26.06.2026
Amazon.fr vs Cdiscount vs ManoMano: How French Marketplace Algorithm Differences Should Shape Your Fulfillment Priorities
27.06.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.
Most multi-market EU sellers already know DAC7 placed reporting obligations on platform operators. What is less understood is that the broader DAC recast extends automatic exchange of information to cover seller-level transaction data, cross-border inventory movements, and VAT registration triggers that many operators have not yet mapped. If your business moves stock between EU member states ā whether through marketplace fulfilment, third-party logistics, or pre-Amazon storage buffers ā your transaction records are now part of a wider data-sharing framework between tax authorities. The practical question is not whether you are affected. It is whether your intrastat reporting, EC Sales Lists, and OSS reconciliation are aligned before a cross-border audit request arrives simultaneously in two or more jurisdictions.
What the DAC Recast Adds Beyond DAC7
DAC7, which came into force for platform operators across the EU, required digital marketplaces to collect and report seller data ā revenue, transaction counts, bank details ā to the tax authority of the platform's home member state, which then shares that data automatically with other relevant member states. The DAC recast goes further. It broadens the scope of automatic exchange to include additional financial account data, cross-border arrangements, and ā critically for ecommerce sellers ā transaction-level information that can be cross-referenced against VAT compliance services filings and intrastat reporting submissions. For sellers operating pan-EU fulfilment models, this means tax authorities in France, Germany, the Netherlands, and Belgium may now receive correlated data from multiple sources simultaneously. A mismatch between your OSS registration declarations and the transaction data reported by a marketplace creates a reconciliation gap that is visible to more than one authority at once.
Transaction Data You Must Control Before Goods Move
Before inventory crosses an EU internal border ā whether from a French fulfilment centre to a Belgian distribution point, or from a German warehouse to an Amazon FC in another member state ā several data points must be confirmed and recorded. Intrastat reporting thresholds vary by member state, and the obligation to file can be triggered by the value or volume of dispatches and arrivals independently. Sellers using EU VAT compliance services should confirm whether their provider captures the commodity code, country of dispatch, country of destination, and statistical value for each movement. EC Sales Lists require separate confirmation that the receiving entity holds a valid VAT number in the destination member state. Failing to record these at the point of movement, rather than reconstructing them from carrier invoices later, is the most common data gap that creates audit exposure across Francophone Europe and Benelux markets.
What Breaks When Reporting Responsibility Is Unclear
The most operationally damaging scenario is not a seller who ignores DAC recast obligations entirely ā it is a seller who assumes their marketplace or 3PL is handling the reporting layer when it is not. Platform operators report seller-level aggregated data under DAC7. They do not file your intrastat reporting declarations, your EC Sales Lists, or your OSS reconciliation. Those remain seller obligations. When a tax authority in France or Belgium receives DAC7 data showing significant cross-border transaction volumes and then finds no corresponding intrastat filing or OSS registration for the same period, the gap triggers a compliance review. At that point, the seller faces potential back-filing requirements across multiple jurisdictions simultaneously ā not a single-country correction. The cost and complexity of resolving a multi-jurisdiction gap is substantially higher than maintaining aligned filings from the outset.
OSS Reconciliation and the Multi-Market Alignment Problem
OSS registration simplifies VAT reporting for B2C cross-border sales by allowing sellers to file a single quarterly return covering all EU member states where they sell. However, OSS does not replace intrastat reporting for goods movements, and it does not cover B2B transactions, which still require local VAT registration in the destination member state in many cases. For sellers operating across France, Belgium, the Netherlands, and Luxembourg ā the core Francophone Europe and Benelux footprint ā the interaction between OSS declarations, EC Sales Lists, and intrastat reporting creates three separate data streams that must reconcile. Under the DAC recast framework, tax authorities can now cross-reference these streams more effectively. A seller whose OSS return shows sales into Belgium but whose intrastat reporting shows no corresponding goods dispatch from France may face questions about the physical supply chain that require warehouse-level documentation to answer. Maintaining EU VAT for international sellers requires treating these three reporting layers as a single coordinated data obligation, not three separate administrative tasks.
Intrastat and EC Sales List Checks
- Confirm intrastat thresholds for each member state where you dispatch or receive goods ā thresholds differ by country and direction
- Record commodity code, statistical value, country of dispatch, and country of destination at the point of each movement
- Verify EC Sales List filing frequency matches your transaction volume in each destination market
- Confirm that VAT numbers of receiving entities are validated before each B2B cross-border transaction is recorded
- Reconcile intrastat dispatch data against carrier proof-of-delivery records quarterly
OSS Registration and Filing Checks
- Confirm OSS registration covers all B2C destination member states where you have sales above the EU-wide distance selling threshold
- Separate B2B and B2C transaction streams before filing ā OSS does not apply to B2B supplies requiring local VAT registration
- Reconcile OSS quarterly return totals against marketplace-reported transaction data before submission
- Flag any member state where local VAT registration may be required independently of OSS ā particularly where you hold stock
- Retain OSS filing records for the period required by your member state of identification
DAC7 and Platform Data Alignment
- Request your DAC7 data summary from each marketplace platform where you sell ā this is the data already shared with tax authorities
- Compare platform-reported revenue figures against your own VAT compliance services records for the same period
- Identify any transaction categories the platform may have excluded or categorised differently from your own records
- Confirm that your bank account details registered with each platform match the entity holding your VAT registrations
- Document any discrepancies between platform data and your own filings before an authority raises them
Multi-Jurisdiction Risk Monitoring
- Map which member states have received DAC7 data about your business and confirm you have active filings in each
- Assign a named owner for each reporting obligation ā intrastat, EC Sales Lists, OSS, local VAT ā to avoid assumption gaps
- Set a quarterly review date to reconcile all three data streams before each OSS filing deadline
- Flag any new EU member state where inventory movements begin, and confirm reporting obligations before the first dispatch
- Retain warehouse movement records and carrier documentation as supporting evidence for intrastat and OSS positions
Mapping Your Cross-Border Data Obligations Before the Recast Window Closes
The practical sequence for a multi-market EU seller is to start with the data you already generate ā carrier manifests, warehouse dispatch records, marketplace transaction reports ā and map each data point to the reporting obligation it feeds. Intrastat reporting draws on goods movement data. EC Sales Lists draw on B2B invoice data. OSS draws on B2C sales data by destination member state. DAC7 draws on platform-aggregated revenue data. Under the DAC recast, these four streams will be cross-referenced by tax authorities with greater frequency and precision than before. Sellers operating pre-Amazon storage in France or Benelux fulfilment centres should confirm that every stock transfer between locations is captured in intrastat records, not only in internal warehouse management systems. The gap between what your WMS records and what your intrastat filing declares is exactly the gap that a cross-border audit will examine first. Global VAT compliance for EU operations is not a single filing ā it is a data architecture decision that should be made before inventory moves, not after a query arrives.
Obligation Owner
Intrastat reporting, EC Sales Lists, and OSS filings are seller obligations. Platforms report aggregated seller data under DAC7 ā they do not file on your behalf for these three streams.
Data Checkpoint
Each cross-border stock movement requires commodity code, statistical value, dispatch country, and destination country recorded at the point of movement ā not reconstructed later from carrier invoices.
Escalation Rule
If DAC7 platform data and your own OSS or intrastat filings show different figures for the same period, resolve the discrepancy proactively before filing ā do not wait for an authority query.
The Decision Every Multi-Market Seller Needs to Make Now
The DAC recast does not create entirely new obligations for most sellers ā it creates new visibility for obligations that already exist. The practical risk is not ignorance of the rules. It is operating with three separate reporting streams ā intrastat reporting, EC Sales Lists, and OSS reconciliation ā that are managed by different people, on different schedules, without a reconciliation step that confirms they tell the same story. For sellers with inventory across France, Belgium, the Netherlands, or Luxembourg, the Francophone Europe and Benelux footprint is exactly the multi-jurisdiction profile that cross-border data exchange is designed to surface. The decision to make now is whether your EU VAT for international sellers setup treats these obligations as a single data architecture or as separate administrative tasks. Sellers who map the full obligation set before the recast implementation window closes are in a materially better position when a multi-jurisdiction query arrives. Verify your legal and tax obligations with a qualified adviser ā the operational logistics layer is where FLEX. can support.
If your cross-border EU operations involve pre-Amazon storage, Benelux fulfilment routing, or multi-market inventory movements, the logistics layer ā warehouse records, carrier documentation, stock transfer data ā is the foundation your tax filings depend on. FLEX. supports sellers operating across Francophone Europe and Benelux with the operational infrastructure that keeps your compliance data clean at source. Speak with the FLEX. team about how your current fulfilment setup maps to your intrastat and OSS reporting obligations ā before a cross-border query makes that conversation urgent.
