EU Consumer Right of Withdrawal: What the 14-Day Return Rule Means for Multi-Country Sellers
17.08.2026
Product Liability and the EU’s New Rules for Non-EU Manufacturers Selling Online
17.08.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 seller running storefronts on three EU marketplaces gets the same data request from each platform within a week: confirm tax ID, VAT number, and bank details, or risk a payout hold. It looks like a phishing attempt until it happens on the second and third marketplace too. It is not a scam. It is DAC7, the EU rule that requires digital platforms to collect seller information and report it to tax authorities every year. DAC7 does not create a new tax. It creates a reporting obligation for the platform, and that obligation only works if the seller's account data is complete. For a seller operating across multiple EU marketplaces, the practical question is not whether DAC7 applies but whether every platform account has the data needed to keep verification and payouts moving.
What DAC7 Actually Requires From the Platform, Not the Seller
DAC7 is the common name for Council Directive (EU) 2021/514, the seventh update to the EU's directive on administrative cooperation in taxation. It has applied to data collection since 1 January 2023, with the first annual reports filed by platforms in January 2024 covering 2023 activity. This is not a new 2026 rule; it is now an established annual cycle that repeats every reporting period.
The obligation sits with the platform, not directly with the seller. A marketplace facilitating sales or services involving EU sellers, or EU-located goods and property, must collect specified seller data and report annual earnings to the relevant tax authority. This applies to non-EU platforms too. A platform does not need to be headquartered inside the EU to fall under DAC7 marketplace reporting obligations if it has EU sellers using its marketplace.
For a seller, the practical consequence is a data request, not a tax bill. The platform is completing legally required seller due diligence for marketplaces, and it cannot report what it has not verified.
What the Platform Is Legally Required to Collect
Each marketplace account should have a complete identity and tax-residency file before the platform can consider due diligence closed. This typically includes a tax identification number (TIN), a VAT ID where the seller is VAT-registered, a verified address, and payment or transaction account details used for payouts.
Due diligence on new sellers is generally expected to be completed by year-end, which is why platforms often push data requests earlier in the year rather than waiting until December. A seller who joined three marketplaces in the same quarter may receive near-identical requests from each one, because each platform runs its own independent verification cycle and none of them can rely on another marketplace's records.
What Happens When the Data File Stays Incomplete
A platform that cannot complete due diligence on a seller account is not able to close its own compliance file with tax authorities. In practice, this shows up as account restrictions: held payouts, blocked withdrawals, or a verification flag that limits new listings until the missing field is submitted.
This is where multi-marketplace sellers run into a specific friction point. If a TIN or VAT ID request is ignored on one platform while it is answered on another, only the unresolved account gets restricted. The seller does not lose access everywhere, but cash flow tied to that one channel stalls, and the fix usually takes longer than the original request would have.
The Reporting Threshold: Why Some Sellers Are Excluded and Most Are Not
DAC7 includes a standard exclusion from reporting, but it only applies when a seller meets both conditions at once: fewer than 30 sales transactions during the reporting period, and no more than ā¬2,000 in total payments received in that same period. If a seller crosses either threshold, the exclusion no longer applies and the account becomes reportable.
This matters for multi-marketplace sellers because the threshold is assessed per platform, not combined across every marketplace a seller uses. A seller with low volume on one channel and high volume on another may be excluded on the first and reportable on the second, with each platform running its own count independently.
The annual reporting deadline follows a consistent structure: platforms must submit their report to the relevant tax authority by 31 January of the year following the reporting period. Activity from a given calendar year is reportable by 31 January of the next year. Because due diligence needs to be finished well before that deadline, data requests to sellers typically arrive months earlier, not in a last-minute scramble in January.
Data a platform is likely to request:
- Legal name and registered business name, if trading as a company
- Tax identification number (TIN) for the relevant jurisdiction
- VAT ID, where the seller is VAT-registered
- Registered business or residential address
- Bank account or payment provider details used for payouts
- Confirmation of tax residency, especially for sellers operating across borders
Situations that commonly trigger a fresh data request:
- Opening a new seller account on an additional EU marketplace
- Crossing the 30-transaction or ā¬2,000 threshold partway through the year
- A VAT ID change following a new country registration
- A bank account or payout method update
- An address change tied to a new warehouse, office, or return address in the EU
Checks a multi-marketplace seller should run internally:
- Confirm which marketplaces have completed due diligence and which are still pending
- Match the TIN and VAT ID submitted on each platform against current registrations
- Track transaction and payment totals per platform against the exclusion thresholds
- Flag any account with a payout hold linked to an unanswered data request
Ownership questions worth settling before the reporting deadline approaches:
- Who inside the business is responsible for responding to marketplace data requests
- Who tracks VAT registrations across the countries the business sells into
- Who reviews payout holds and escalates unresolved verification flags
- Who confirms bank and payment details stay current across every marketplace account
Treating DAC7 Requests as Routine Account Maintenance, Not a One-Off Task
The operational mistake most multi-marketplace sellers make is treating a DAC7 data request as a single event tied to one platform, rather than a recurring account-maintenance task that repeats across every marketplace they use. Because due diligence is assessed independently by each platform, a seller who updates VAT details on one marketplace but forgets a second or third one leaves an open verification gap that can surface as a payout hold months later.
A more reliable approach is to keep one internal reference file with current TIN, VAT ID, address, and payment details, and check it against each marketplace account whenever any of those details change. This does not require new software or a compliance department. It requires one person with clear ownership of the file, and a habit of updating every connected marketplace at the same time rather than one at a time as requests arrive.
The decision rule is simple: if a data request comes from a marketplace, respond with accurate information promptly, because the platform cannot complete its legal due diligence without it, and an unanswered request is far more likely to stall a payout than a completed one is to cause any problem.
Who Owns the Obligation
The platform, not the seller, is legally required to collect data and file the report. The seller's role is to respond accurately and promptly so the platform can complete its own due diligence file before the deadline.
What Gets Checked
TIN, VAT ID, address, and payment details form the core data file. Any change to VAT registration, bank details, or business address should trigger an update across every marketplace account, not just the one that flagged it.
When to Escalate
If a payout is held or an account is flagged after a data request, treat it as unresolved due diligence rather than a platform error. Resubmit the requested field promptly rather than waiting for a follow-up notice.
What This Means for a Seller Running Several EU Marketplaces at Once
DAC7 does not change what a seller owes in tax. It changes what a marketplace must collect and report, and it makes that collection a condition of keeping an account fully functional. For a seller on two, three, or four EU marketplaces, the practical decision is whether to treat data requests platform by platform as they arrive, or to keep one current reference file and update every account at once when a detail changes.
The second approach avoids the common failure pattern: a VAT update applied on one marketplace while a second marketplace still holds outdated information, which later surfaces as a blocked payout with no obvious cause. Reviewing which accounts have completed due diligence, and confirming TIN and VAT ID data matches current registrations, is a control worth running on a fixed schedule rather than only when a platform sends a warning.
None of this replaces a proper conversation with a tax advisor or accountant about specific obligations in each country of operation. What it does is separate the administrative task, keeping marketplace account data accurate, from the tax question itself, so one does not get mistaken for the other.
DAC7 compliance itself sits with tax authorities, platforms, and the seller's own tax advisor, and this article is not a substitute for that guidance. Where FLEX. can help is on the operational side: sellers running inventory and fulfillment across several EU marketplaces often need consistent address, entity, and shipping data across every channel, which is part of what supports smooth EU compliance for ecommerce sellers more broadly. Contact the FLEX. team if your logistics setup spans multiple countries and marketplaces ā sellers running inventory and fulfillment across several EU marketplaces often need consistent address, entity, and shipping data across every channel, and FLEX. can walk through how that fits into your current fulfillment and forwarding setup.
