DAC7 WooCommerce 2026: US & EU Marketplace Seller Reporting — Complete Compliance Guide

You run a WooCommerce marketplace — Dokan, WCFM, WC Vendors, or a custom stack with third-party sellers. Your vendors are in the US, Europe, or both. Commissions work. Stripe payouts flow. Vendor dashboards hum. Then the compliance questions start hitting your inbox: "Do I need to report my sellers to the IRS? To the EU? What about DAC7? Is that like 1099-K?"

You are not alone. Every week, US-based marketplace operators discover that selling into the European Union triggers DAC7 — an EU reporting directive with January 31 deadlines, €2,000 thresholds, and 22 data points per seller. Meanwhile, the IRS is lowering the Form 1099-K threshold to $600 for 2026. If you operate a marketplace with international sellers, you may now face two reporting regimes, not one.

This guide exists because most US marketplace founders know about 1099-K but have never heard of DAC7. The difference matters: DAC7 requires proactive seller data collection throughout the year, not just a January mailing of tax forms. Miss both deadlines and you face penalties on both sides of the Atlantic.

Why read this article? You will understand what DAC7 means for US-operated marketplaces, how it compares to IRS Form 1099-K, which 22 fields you must collect per seller, how €2,000 / 30 transaction thresholds apply to non-EU platforms, what penalties await on each side, and how to reach compliance in 7 phased steps without rebuilding your vendor onboarding.

What you'll learn: DAC7 for US audiences · DAC7 vs 1099-K side-by-side · platform operator test · 22 seller data points · annual aggregation · 4 Dokan/WCFM/WC Vendors/Generic presets · US/EU penalty comparison · real case studies · synergy with Factur-X France · stack audit with Plugin Usage Detector · sync debug with Debug Tracker · TaxBit vs Volade vs manual comparison.

Take a breath. DAC7 is serious, 1099-K is changing, and your WooCommerce marketplace can handle both. Let's start where US readers need to start.

Who this guide is for — the US marketplace operator

You are in scope if you run a WooCommerce marketplace from the US (or globally) where third-party sellers transact, you collect commissions, and any of these describe you:

• You have EU-resident sellers on your platform — DAC7 applies even if your company is US-based.
• You accept payments from EU buyers and distribute to EU sellers — the "platform operator" definition is functional, not geographic.
• Your accountant mentioned both 1099-K and DAC7 — many US marketplaces expanding into Europe are dual-obligated.
• You use Dokan, WCFM, WC Vendors, or a custom vendor role and want to prepare before your fiscal year ends.

Typically out of scope for DAC7: pure US-domestic marketplace with no EU seller presence and no EU payment facilitation (but 1099-K may still apply). Single-seller stores are excluded from both regimes.

The scenario we see weekly: a US-based outdoor gear marketplace built on Dokan, 120 sellers (15 in Germany, 5 in France, rest in the US). They file 1099-K for US sellers. They have never heard of DAC7. In January 2026, a French seller's tax authority inquiry triggers the discovery — and they have 30 days to produce a structured seller report. DAC7 Compliance by Volade does not replace a cross-border tax attorney — it structures WooCommerce data for both 1099-K and DAC7 reporting.

What is DAC7 — explained for a US audience

If you know IRS Form 1099-K, you already understand the concept: tax authorities want marketplace platforms to report seller income so they can verify tax compliance. DAC7 (Directive on Administrative Cooperation 7) is the European Union's version — but with significant differences in scope, thresholds, and data requirements.

The core concept

DAC7 amends EU Directive 2011/16 on administrative cooperation. It requires platform operators — defined as any entity that makes a digital platform available to sellers — to collect, verify, and annually report seller data to EU tax authorities. The key insight for US readers: DAC7 applies to the platform, not the platform's location. A US LLC operating a WooCommerce marketplace where German artisans sell furniture is a DAC7-reportable platform operator.

Why this matters for US marketplaces in 2026

Three converging trends make DAC7 unavoidable for US WooCommerce operators:

1. IRS 1099-K threshold dropping to $600 — more US sellers will receive forms, and platforms must collect TINs more aggressively.
2. EU tax enforcement tightening — DAC7 audits and penalty enforcement began ramping up in 2025-2026.
3. Cross-border WooCommerce growth — US-based marketplaces selling digital goods, handmade items, or B2B services into the EU are common.

If you have EU-resident sellers or process EUR-denominated payments, DAC7 applies. Period.

The calendar that matters

Both deadlines fall on January 31 — a coincidence that simplifies calendar management but concentrates your compliance work in Q4.

"Am I affected?" — 5 signs for US marketplace operators

1. You use Dokan, WCFM Marketplace, WC Vendors, or a custom seller / vendor role with third-party vendors.
2. You have any sellers resident in the EU (even one) — or you route payments through an EU entity.
3. Your sellers have a dashboard and receive payouts (Stripe Connect, PayPal, manual transfer).
4. You take a commission on each sale — even a small one — which establishes "platform remuneration."
5. A tax advisor or investor mentioned DAC7, P2B regulation, or "cross-border tax reporting."

If two apply: read on this week, not in December. Incomplete vendor profiles do not get finished in 48 hours when 150 sellers must respond across time zones.

DAC7 vs IRS Form 1099-K — the US vs EU comparison

This is the section most US readers need. If you already handle 1099-K, you are halfway there — but DAC7 adds layers you have not dealt with.

Side-by-side comparison

Key differences that matter operationally

1. IBAN and birth data: DAC7 requires bank account (IBAN) and birth date/place for individual sellers. 1099-K does not. This means your vendor onboarding form must collect more data for EU-reportable sellers.

2. Quarterly breakdown: DAC7 requires revenue split by quarter (Q1–Q4). 1099-K only requires annual totals. Your aggregation system must support time-windowed queries.

3. Seller residency: 1099-K applies to US payees. DAC7 applies based on seller activity, not residency — a US citizen selling on your platform from Germany could trigger DAC7 if they are EU-resident.

4. Verification burden: DAC7 requires "reasonable measures" to verify seller data (TIN validation, address checks). 1099-K relies on IRS name/TIN matching but the burden is lighter.

Practical overlap — when you must file both

What this means for your WooCommerce setup

Your WooCommerce marketplace likely has a single vendor registration form. If you have mixed US/EU sellers, you now need:

• For US sellers: TIN/EIN, address, payout details (existing 1099-K data)
• For EU sellers: All of the above plus IBAN, birth data (if individual), EU VAT number, permanent establishment info

The Volade plugin handles this distinction through conditional field requirements based on seller country.

Am I a DAC7 platform operator?

Now that you understand the what and the why, let's confirm the who. Under DAC7, a "platform operator" is defined functionally:

3 simplified criteria (2-minute test)

All three yes: you are very likely an operator. Two yes: consult your tax advisor — often yes for Dokan/WCFM/WC Vendors. One yes (e.g. directory without payment): grayer area.

WooCommerce setups — in or out

Reporting thresholds — dual regime reference

Real example — the California marketplace with EU sellers

A WooCommerce + WCFM marketplace (organic skincare, 90 sellers: 70 US, 15 Germany, 5 France) discovers DAC7 in Q3 2025 through an EU seller's tax inquiry. They file 1099-K for US sellers annually but have no structured data for EU sellers — no TIN, no IBAN, no birth dates. Diagnosis: WCFM preset applied, conditional onboarding (US fields vs EU fields), vendor sync, Q4 onboarding campaign, pilot JSON export for 2025 EU sellers. January 2026 reporting completed for both regimes. Cost of ignorance avoided: dual penalties and a French tax audit.

The 22 data points explained — what EU and US authorities expect

The heart of DAC7 is a structured seller dossier with precise fields. DAC7 Compliance by Volade models 22 fields in the seller table — plus transaction aggregation at export time. 1099-K requires a subset of these; DAC7 requires the full set for EU-reportable sellers.

Overview — 4 blocks

DAC7 seller profile
├── Legal identity (name, trading name, entity type)
├── Address & tax residence
├── Tax identifiers (TIN, VAT, EIN/SIREN, company registration)
├── Personal data (birth — if individual)
├── Financial account (IBAN, account holder)
├── Contact (email, phone)
└── Onboarding status (complete / incomplete / pending)

The 22 fields — where to find them in WooCommerce

Minimum required fields (plugin validation)

To reach complete status, these cannot be empty:

• legal_name, address_line1, postal_code, city, country_code, tin, email

For EU sellers, these additional fields are required at filing time:

• vat_number (if applicable), iban, account_holder
• birth_date, birth_place, birth_country (if individual)
• entity_type, registration_number (if company)

Transaction data (annual aggregation)

Beyond profile fields, export includes per reportable seller:

What WooCommerce already provides (and what is missing)

Plugin comparison — DAC7 Compliance by Volade vs TaxBit vs manual

Not every marketplace has the same vendor volume, geography mix, or compliance budget. Here is an honest comparison for US operators specifically.

Comparison table — DAC7 & 1099-K reporting solutions

When to choose what — US operator scenarios

TaxBit specific notes for US readers

TaxBit is a leading US tax compliance platform used by major crypto and marketplace companies. It handles 1099-K, 1099-B, and DAC7 reporting. However:

• WooCommerce integration is not native — you typically export orders and upload to TaxBit.
• It is priced for enterprise volumes (think 1,000+ sellers).
• For a WooCommerce marketplace with 20–200 sellers and mixed US/EU geography, TaxBit may be overkill — especially if your core data lives in WooCommerce meta tables.

Volade's approach: stay on WooCommerce for data collection, use Volade for DAC7 structuring and export, and feed data to TaxBit (or your existing 1099-K processor) for US filings.

Complementary Volade stack

Compliance workflow — 7 phases for dual-regime readiness

This section is the central tutorial for US operators. Block one full day on staging with test vendors. Do not go to prod before tax advisor validation.

Phase 1 — Marketplace audit and dual-regime scope (45 min)

1. List active vendor count over 12 months, split by country of residence
2. Identify your marketplace plugin (Dokan, WCFM, WC Vendors, custom)
3. Verify payment flow: Stripe Connect, manual, PayPal? EUR and USD handling?
4. Export a sample of vendor profiles — which tax fields already exist (EIN, TIN)?
5. Estimate how many vendors exceed $600 (1099-K) or €2,000 / 30 tx (DAC7)
6. Audit the stack with Plugin Usage Detector

Phase 2 — Configure the platform operator (30 min)

Whether you operate from the US, EU, or both, the platform operator entity must be declared.

1. Set platform_name — legal name of your platform company (US LLC, SAS, etc.)
2. Add platform_tin — EIN (for US) or SIREN/SIRET (for EU)
3. Complete platform_vat — EU VAT number if you have one (not required for US-only operators)
4. Set reporting_year — in July 2026, often 2025 for the next filing
5. Verify reporting_country — the EU member state where you first register as operator
6. Confirm dual thresholds: €2,000 / 30 tx (DAC7) and note $600 (1099-K) for reference

Phase 3 — Install DAC7 Compliance by Volade (15 min)

1. Install DAC7 Compliance by Volade on staging
2. Open Volade → DAC7 Compliance
3. Check access badge: Free — no account is enough to start
4. Enable conditional field collection: collect_birth_data for EU individuals, collect_iban for EU-reportable sellers
5. Run Site Health test — platform TIN, incomplete profiles, and unregistered operator status surface here

❝Without a Volade account: seller profiles, marketplace sync, annual aggregation, JSON export work. Free account: TIN/VAT/IBAN validation, CSV export, onboarding reminders. V+ Premium: DAC7 XML export, multi-country, multisite central, bulk onboarding.

Phase 4 — Choose and apply a marketplace preset

Click Apply on the matching preset — thresholds and require_onboarding prefill.

Phase 5 — Sync vendors and complete onboarding (2–3 h)

1. Click Sync vendors from marketplace
2. Review summary cards: total profiles, complete, reportable, split by US and EU
3. Filter pending or incomplete vendors
4. Send country-specific reminder emails: different fields for US vs EU sellers
5. Manually complete the 2–3 strategic top vendors in admin
6. Target 100% complete on all reportable before December

Phase 6 — Generate and validate a pilot export (1.5 h)

1. Select reporting year (e.g. 2025)
2. Click Export JSON — download the file
3. Verify: reportable vendor count matches your estimate for both regimes?
4. Manually check 5 vendors: totals = WooCommerce? Country fields correct?
5. Send JSON to your tax advisor with a note: "Which regime applies to each?"
6. If V+: test Export XML (DAC7) for EU schema validation
7. For 1099-K: export CSV for your accounting team or 1099-K filing service

Phase 7 — Production, filing, and annual cycle (ongoing)

1. Replicate config on prod after advisor validation
2. Integrate DAC7 onboarding into vendor signup workflow with country-based field logic
3. Schedule quarterly review: new vendors, incomplete profiles, regime changes
4. Calendar: October → send onboarding reminders; December → validate data; January → file
5. Archive JSON/XML (DAC7) + 1099-K CSVs + proof of seller notification
6. If B2B invoicing to EU vendors: pair with Factur-X France

"

Marketplaces that validate a pilot export with their tax advisor before December sleep better than those syncing 200 vendors on January 28. With dual US/EU deadlines, start your compliance process in October.

— Volade support team

Penalties & risks — US vs EU non-compliance

Understanding penalties helps prioritize. Here is what you face on each side.

US penalties (1099-K)

DAC7 penalties vary by EU member state. Here are estimates for key countries where US operators commonly have sellers:

Why penalties differ

1099-K penalties are per-form, making them calculable. DAC7 penalties are per-violation with wider discretion — and can include public naming of non-compliant platforms. The reputational risk for US platforms operating in the EU is significant.

Real penalty scenario

A US WooCommerce marketplace (50 EU sellers, 200 US sellers) fails to file DAC7 for 2024. The French tax authority, tipped by a seller inquiry, issues a notice:

• 1099-K impact: late filing penalty on 200 US forms = ~$22,000 (assuming 30-day late group)
• DAC7 impact: €15,000 fine from French authority + mandatory compliance audit
• Total hard cost: ~$40,000 + legal fees
• Reputational cost: flagged as non-compliant platform, EU sellers notified

The plugin cost to prevent this: $0 (free tier) to $199/year (V+). The time investment: one week of setup.

Real US and EU case studies

These anonymized examples are based on actual WooCommerce marketplace compliance projects handled by Volade and partner agencies.

Case 1: US handmade marketplace, caught by surprise (Austin, TX)

Setup: Dokan marketplace, 200 sellers, 90% US, 10% EU (France, Germany, Italy). $1.2M GMV. No DAC7 knowledge.

Trigger: French tax authority requested seller data from the platform in March 2026 after a French seller declared income inconsistent with platform activity.

Response: Volade installed on staging, WCFM preset applied (they had migrated from WCFM to Dokan 6 months prior without updating preset), 22 EU seller profiles completed in 3 days. JSON export generated. Tax advisor confirmed no penalties due to proactive response.

Lesson: Platform was 6 months late on DAC7 compliance. Only avoided penalties because they cooperated immediately. Cost: $3,500 in expedited agency work + Volade V+ subscription. Preventable cost: $0 with awareness.

Case 2: EU marketplace with US expansion (Berlin, Germany)

Setup: WC Vendors marketplace, 85 sellers (70 EU, 15 US). €800K GMV. Compliant with DAC7 for EU sellers since 2023.

Challenge: US expansion required 1099-K filing for US sellers. No existing US TIN collection on vendor forms.

Response: Condition fields added to vendor registration — US sellers see EIN/ZIP fields, EU sellers see TIN/IBAN/VAT. Dual export pipeline: DAC7 XML for EU, CSV for 1099-K processor.

Result: Full dual-regime compliance in 4 weeks. Cost: €2,000 for Volade V+ + 5 hours of agency setup.

Case 3: US agency managing 12 marketplace clients (Chicago, IL)

Setup: Agency running 12 WooCommerce marketplaces for clients — mix of Dokan, WCFM, custom stacks. Client sellers span US, Canada, UK, and EU.

Challenge: Each client has different seller geography, threshold configurations, and filing requirements. Manual per-client compliance was impossible.

Response: Volade V+ Agency plan deployed across all 12 sites. WP-CLI used for bulk sync and export. Standardized 48-hour runbook per client.

Result: Average 3 hours per client per year for DAC7 compliance. Revenue: $1,200–$2,500 per-client compliance fee. Agency tooling cost: $99/month.

Case 4: US B2B parts marketplace with no EU sellers — 1099-K only (Detroit, MI)

Setup: Dokan marketplace, 300 sellers, all US-based. B2B industrial parts. No EU presence.

DAC7 status: Not in scope (no EU sellers, no EU payments).

Action: Confirmed exclusion with tax advisor. Focused on 1099-K compliance only. Volade not needed for this client — but they use Factur-X France for B2B e-invoicing to US vendors who request structured invoices.

Lesson: Not every WooCommerce marketplace needs DAC7. Confirm scope first.

FAQ — questions US marketplace operators ask most

Does DAC7 apply to my US-based WooCommerce marketplace if all my sellers are in the US?

No. DAC7 only applies if you have sellers resident in the EU or facilitation of EU payments. For US-only seller bases, 1099-K is your concern. However, if one US seller relocates to Germany and continues selling, they become an EU-resident seller under DAC7 — monitor seller addresses annually.

I already file 1099-K. What does DAC7 add that I do not already do?

Six things: (1) IBAN collection, (2) birth date/place for individual sellers, (3) quarterly transaction breakdown, (4) EU VAT number, (5) permanent establishment field, (6) DAC7-specific XML schema. Your 1099-K workflow covers about half of what DAC7 requires. The Volade plugin fills the gap.

What if I have just one seller in France? Do I really need to register?

Yes, probably. One EU-resident seller who is reportable (€2,000 or 30 transactions) triggers your obligation to register as a platform operator in an EU member state. The cost of non-compliance (up to €20,000 in France) far exceeds the setup cost. Consult a cross-border tax attorney.

How do I handle sellers who refuse to provide their TIN or IBAN?

You cannot report them completely — non-compliance risk. Update your terms of service: selling on the platform requires legal and tax data. For reportable sellers who refuse: suspend the account. For US sellers under 1099-K, backup withholding may apply. For DAC7, the platform bears the penalty for incomplete data.

What is the cheapest way to become DAC7-compliant for a small US marketplace (< 20 sellers)?

Volade free tier + manual JSON export + tax advisor review. No account needed for basic seller profiles, sync, aggregation, and JSON export. Send the export to an EU tax advisor for validation. Estimated cost: $500–1,000 for the advisor review. V+ upgrade only needed when you scale or require XML schema.

Can I use the same plugin for both 1099-K and DAC7?

The DAC7 Compliance by Volade plugin handles DAC7 seller profiles, aggregation, and exports. For 1099-K filing, you still need a 1099-K filing service (TaxBit, QuickBooks, etc.) — but the plugin's CSV export can feed into those systems. Think of Volade as your WooCommerce-native data collection layer for both regimes, with DAC7-specific formatting built in.

What happens if I ignore DAC7 entirely as a US company?

Risk profile: EU tax authorities can request seller data through mutual legal assistance treaties and administrative cooperation channels. If a seller in an EU country under-reports income, the EU authority investigates the platform. Penalties (€10k–€50k+) + mandatory compliance + potential cross-border audit. Reputational damage with EU sellers who may view your platform as non-compliant. And if you ever seek EU investment or acquisition, DAC7 compliance will appear in due diligence.

How do I register as a platform operator for DAC7?

Registration depends on the EU member state. Generally: (1) Identify the member state where your first reportable seller resides, (2) register with that country's tax authority for DAC7 purposes, (3) submit annual returns by January 31. Some countries allow online registration; others require a physical form. Your EU tax advisor handles this — budget €1,000–3,000 for initial registration plus ongoing advisory.

What about marketplaces with only B2B sellers?

B2B marketplaces are not exempt from DAC7. The directive covers any platform where sellers offer goods or services — B2B and B2C alike. However, B2B sellers are typically companies, so birth data fields are not required. Entity type, registration number, and VAT become the priority fields. If your B2B marketplace involves EU sellers, DAC7 applies.

Are digital goods / services marketplaces covered differently?

No. DAC7 covers: (1) sale of goods, (2) provision of services, (3) rental of immovable property, (4) rental of transport, (5) personal services (gig economy). A WooCommerce marketplace selling digital downloads with EU-resident sellers is in scope.

Conclusion — your WooCommerce marketplace can handle both regimes

DAC7 is not a punishment against WooCommerce or US marketplaces selling globally. It is the operational reality of cross-border e-commerce in 2026: the EU wants to see what you already see in your admin — who sells, how much, and where tax applies. The IRS wants the same, with a different form.

You already run Dokan, WCFM, or WC Vendors. You already handle commissions and payouts. Adding DAC7 compliance is not a rebuild — it is a structured data layer on top of your existing vendor profiles. And if you also file 1099-K, the incremental work for DAC7 is mainly field expansion: IBAN, birth data, quarterly splits, and XML formatting.

Our final recommendation for US marketplace operators:

1. This week: count your sellers by country. Know who is US and who is EU.
2. Confirm with a tax advisor: are you a DAC7 platform operator?
3. Install DAC7 Compliance by Volade on staging, apply your preset, run a sync.
4. Generate one JSON export. Send it to your advisor.
5. If you have EU sellers: register as a platform operator in the relevant member state.
6. Set your calendar: October reminders → December validation → January filing.

You built a marketplace on WooCommerce because it gives you control without enterprise lock-in. DAC7 compliance should work the same way — structured, transparent, and inside your existing stack.

If you choose Volade: welcome. We build these tools because marketplace operators — whether in the US, Europe, or anywhere — deserve to stay on WooCommerce without fearing January 31.

Good compliance. Your sellers, your tax advisor, and your cross-border future will thank you.

---

Article updated July 13, 2026. Sources: DAC7 directive (EU 2021/514), IRS Publication 1220, US Treasury 1099-K final regulations (2023–2026), French DGFiP documentation, German BZSt guidance, tax advisor feedback, and Volade field tests on Dokan, WCFM, and WC Vendors across US and EU seller configurations.