WooCommerce VAT Registration and Filing Guide in Spain

Running a WooCommerce store that sells into Spain turns VAT (IVA) into an operational system, not a plugin toggle. Spain’s rules are highly structured and hinge on details that WooCommerce merchants control every day: where you ship to, how you price (VAT-inclusive vs. exclusive), how you classify products for the correct rate, and how cleanly your order data can be reconciled into filings.

From there, everything flows into your reporting lane and calendar. If you’re filing locally, Modelo 303 deadlines are strict; if OSS/IOSS applies, your reporting shifts to the one-stop-shop process with its own rules and recordkeeping requirements. This guide shows how to decide the right VAT lane, register correctly, configure WooCommerce so checkout VAT matches your obligations, and file with numbers you can defend.

In a nutshell:

• Spain VAT applies in the Peninsula + Balearic Islands, not the Canary Islands/Ceuta/Melilla.
• Spain VAT rates are 21% / 10% / 4% depending on what you sell.
• If you file local Spanish VAT, Modelo 303 deadlines are fixed (quarterly and monthly windows).
• Modelo 390 (annual summary) is filed in the first 30 calendar days of January.
• EU cross-border B2C “distance sales” include a €10,000 threshold rule, as Spain publishes.
• IOSS applies to certain imported distance sales and to the €150 low-value threshold Spain details in its VAT/e-commerce materials.
• Registering for OSS/IOSS in Spain uses Form 035, and the periodic return is Modelo 369.
• If you exceed €6,010,121.04 in turnover, Spain says you become a “Gran Empresa” starting the next year, affecting VAT cadence and SII obligations.

Why does the Spanish VAT get complicated on WooCommerce?

WooCommerce itself isn’t the problem; the complexity comes from the gap between how your store is configured and how Spain expects VAT to be applied and reported. When those two don’t match, you end up collecting the right-looking VAT in the wrong situations, or filing returns that don’t reconcile to what your store actually did.

• Spain VAT isn’t “one Spain.”

VAT applies in the Peninsula and the Balearic Islands, but not in the Canary Islands, Ceuta, or Melilla, so treating all Spanish addresses the same results in incorrect checkout tax and reporting.

• Multiple reporting lanes exist, and WooCommerce doesn’t pick one for you.

Local Spanish VAT returns (e.g., Modelo 303/390) and OSS/IOSS reporting are different compliance tracks with different “what goes where.” If you don’t define your lane first, your VAT collection and filings drift out of alignment.

• Product rates are legal classifications, not store categories.

Spain’s VAT rates are set in law (21% standard, 10%, and 4% reduced rates for qualifying supplies). If you rely on product category shortcuts, rate errors show up quickly at scale.

• Store totals don’t translate directly into VAT return totals.

Refunds, partial refunds, shipping treatment, discounts, and chargebacks can distort “sales reports” unless you build a VAT-ready export and reconciliation method.

• Deadlines force discipline.

Spain’s filing windows are fixed; if you wait until the end of the period to clean up data, VAT becomes a recurring fire drill instead of a routine process.

A practical decision map for WooCommerce sellers selling into Spain

VAT outcomes depend on three facts: where you’re established, where inventory sits, and where goods are dispatched from.

Scenario A: You’re established in Spain and sell to Spanish customers

You’re typically in local Spanish VAT compliance:

• Registration and local filing are usually part of normal operations.
• Modelo 303 and (where applicable) Modelo 390 become your baseline.

Scenario B: You’re established in the EU (not Spain) and ship B2C into Spain (no stock in Spain)

This is where OSS can simplify reporting if your facts fit the regime.

• Spain publishes the €10,000 threshold framework that shifts where VAT is due for certain cross-border B2C sales.
• The operational challenge is to maintain clear boundaries between “local” and “OSS” reporting.

Scenario C: You store inventory in Spain (3PL/warehouse)

Inventory in Spain is one of the most common practical triggers for local VAT compliance, given Spain-anchored supply chains and domestic supplies.

Scenario D: You’re outside the EU and ship into Spain

Imports change the VAT workflow (and the customer experience). Spain’s e-commerce/import materials explain how low-value import/distance sale rules and IOSS concepts fit into the picture.

When do you likely need Spanish VAT registration?

Spanish VAT registration isn’t triggered by “having Spanish customers.” It’s triggered by Spain-anchored activity, especially inventory, domestic supplies, and imports. You’re likely to need Spanish VAT registration if you:

• They are established in Spain and make taxable supplies there.
• Hold inventory in Spain and dispatch from Spain (warehouse/3PL).
• Import goods into Spain in your own name, creating Spain-side VAT and customs flows.

You may be able to avoid local Spanish VAT registration (depending on facts) if:

• You sell cross-border B2C into Spain from another EU country and report via OSS where appropriate (Spain publishes the €10,000 distance sales threshold framework).
• Your import model fits the IOSS-related rules, and you operate within the low-value framework Spain describes (including the €150 concept).

Spanish VAT return vs OSS vs IOSS: choosing the right reporting lane

Choose the reporting lane first, then configure WooCommerce to match it. Spain uses different forms depending on the lane.

• Local Spain VAT: Modelo 303 (periodic VAT self-assessment) and usually Modelo 390 (annual summary).
• OSS/IOSS regimes: Registration is via Form 035, and periodic declarations are submitted electronically via Modelo 369.

OSS vs IOSS 

VAT registration setup in Spain: what you apply for and where

Once you’ve confirmed you need Spanish VAT registration (or OSS/IOSS registration), the next step is getting the right forms and registrations in place with Spain’s tax agency before you start collecting VAT at scale. This section outlines what you typically need to file, where each registration occurs, and the key identifiers that make VAT filing in WooCommerce practical.

1) Local Spain VAT registration and census updates (Modelo 036)

Spain uses Modelo 036 for census registration (start/modify/end activities) in the census of entrepreneurs/professionals/withholders.

What to prepare before you start

• Legal entity details and fiscal address
• Activity description (eCommerce retail via WooCommerce)
• Whether you will do intra-EU operations (ROI)
• Whether you will use OSS/IOSS (Form 035)

Spain notes that in some cases, Modelo 036 must be accompanied by additional documentation, which must be provided within 10 business days of filing.

2) ROI / NIF-IVA for intra-EU operations (when applicable)

Spain’s guidance and tools cover identification for intra-EU operations (including ROI/VIES-related processes) and connect these to Modelo 036 and related procedures.

3) OSS/IOSS registration (Form 035)

Spain states that businesses can register for the “ventanilla única” regimes by submitting Form 035 electronically. Spain also maintains a dedicated e-commerce VAT area that links the Form 035 registration paths by regime.

How to configure WooCommerce VAT for Spain?

This section explains how to set up WooCommerce taxes so that Spanish VAT collection at checkout matches your actual compliance lane (local Spain VAT vs OSS/IOSS) and Spain VAT territory rules. The goal is simple: correct VAT at checkout, clean exports, and fewer reconciliation issues at filing time.

Step 1: Enable taxes in WooCommerce

WooCommerce’s documentation shows how to enable tax calculation in settings (WooCommerce → Settings → General → enable tax rates and calculations).

Step 2: Set the right tax basis and customer location logic

WooCommerce tax configuration is built around:

• Store base location
• Customer location (shipping/billing)
• Tax classes and rates

Practical setup choices that reduce VAT errors:

• Use shipping address as the driver for physical goods (so Spain mainland/Balearics vs excluded territories are treated correctly).
• Separate tax classes for standard vs reduced products, so you’re not stuck with one blunt rate.

Step 3: Build Spain tax rates (and treat non-VAT territories explicitly)

Spain mainland/Balearics rates should reflect your product’s VAT rate under Spanish law. Then make sure you have an intentional approach for Canary Islands/Ceuta/Melilla orders, since Spanish VAT does not apply there.

Step 4: If you sell digital products, set up digital VAT properly

WooCommerce provides guidance on configuring EU VAT rates for digital products and on structuring the tax setup for that category. (Use Spain’s VAT rules and your advisor’s classification to decide the correct VAT treatment. Don’t rely on generic plugin rate tables for legal classification.)

Step 5: If you ship imports, decide whether you’ll support IOSS-style flows

WooCommerce provides documentation for an IOSS-focused extension approach. The compliance point is bigger than the plugin: your shipping model, customs data, and reporting lane must align with Spain’s rules and the €150 low-value framework Spain describes.

Step 6: Make refunds VAT-aware (or your filings won’t reconcile)

Refunds and partial refunds are one of the biggest reasons WooCommerce VAT totals don’t match filings. Build a repeatable rule for:

• Full refund
• Partial refund
• Process the shipping refund and ensure your reporting export captures the tax adjustment.

VAT filing requirements in Spain: what you file and by when

Once you’re in Spanish VAT, compliance becomes a calendar discipline. Here are the core forms WooCommerce sellers most commonly encounter.

1. Modelo 303 (IVA self-assessment)

Spain’s tax authority states the filing windows for Modelo 303:

• Quarterly filers: 1–20 April/July/October; Q4: 1–30 January.
• Monthly filers: 1–30 of the following month; January can be filed up to the last day of February.

2. Modelo 390 (annual VAT summary)

Spain states that Modelo 390 is filed within the first 30 calendar days of January after the year is declared, and provides an explicit annual filing window example.

3. Modelo 349 (intra-EU recapitulative statement), when applicable

Spain states filing deadlines for Modelo 349, including monthly and quarterly rules, and the special timing for July and December.

4. Modelo 369 (OSS/IOSS periodic return)

Spain states that VAT declarations for the special one-stop shop regimes are made electronically by submitting Modelo 369.

Scaling trigger: “Gran Empresa” and SII

Spain states that exceeding €6,010,121.04 annual turnover makes you a “Gran Empresa” from the following year, with important tax effects. Spain also explains that under SII, the deadline for sending invoice record entries is generally 4 calendar days, and in any case, before the 16th of the following month.

What belongs in a Spanish VAT return (and what doesn’t) for WooCommerce sellers

A Spanish VAT return is not your WooCommerce revenue report. It only includes transactions that are Spain-reportable in the lane you’re filing, and Spain’s VAT territory rules make that boundary even more important.

Step 1: Start by separating orders by VAT territory

Before you even think about forms:

• Spain VAT territory (Península + Baleares): this is the core scope for Spanish VAT returns.
• Outside Spanish VAT territory (Canarias, Ceuta, Melilla): these should not be treated as standard Spanish VAT sales for Modelo 303 purposes.

Step 2: Bucket transactions by reporting lane (this prevents double reporting)

Use a simple bucket system so the same sale doesn’t end up in two places.

• Bucket A – Local Spain VAT return (Modelo 303)

Include: transactions you must report locally in Spain VAT territory (typically domestic supplies and Spain-anchored activity such as inventory-based supplies).

Exclude: sales you’re reporting under OSS/IOSS and sales outside the Spanish VAT territory.

• Bucket B – OSS/IOSS returns (Modelo 369)

Include: transactions that fall under the special one-stop shop regimes and must be declared via Modelo 369. Spain’s tax agency describes Modelo 369 as the periodic return for these regimes.

Exclude: local Spain VAT transactions that belong in Modelo 303.

• Bucket C – Outside Spain VAT scope

Include: orders shipped to the Canary Islands/Ceuta/Melilla (and any other transactions that are outside the Spanish VAT territory scope).

Exclude from: Modelo 303 “standard Spain VAT” totals.

Step 3: Use VAT return inputs that actually match the forms

What should you build your return from:

• Order-level taxable base and VAT lines (net amounts + VAT), tied to the shipping destination and product VAT rate.
• Refunds/credits linked back to the original order (including partial refunds), so VAT adjustments are consistent.

What you should not use as your primary return input:

• Payment deposits/payouts (they’re affected by payment timing, fees, chargebacks, and aren’t the VAT base).
• Top-line WooCommerce sales totals without adjustments (discounts, shipping treatment, cancellations, and refunds will distort them).

VAT recordkeeping for WooCommerce sellers in Spain: quick audit-ready checklist

Spain VAT filing is much easier to defend when your return figures can be traced back to clear, order-level evidence and a consistent transaction “bucketing” method. This quick checklist covers the minimum records WooCommerce sellers should keep each period, so reconciliations stay clean, and audit requests don’t become a scramble.

• Order-level export (taxable base, VAT rate, VAT amount, destination, shipping, discounts)
• Refund log tied to original orders (partial refunds included)
• Inventory/fulfillment evidence (especially if any stock sits in Spain)
• Lane memo (one page): what goes to Modelo 303 vs Modelo 369 vs outside VAT territory
• Invoice archive (kept for Spain’s 4-year retention baseline, and 10 years for OSS/IOSS records where applicable)

Common mistakes that trigger VAT problems for WooCommerce sellers in Spain

WooCommerce VAT problems in Spain usually aren’t caused by one big misunderstanding; they come from repeatable operational slip-ups, like charging VAT for the wrong Spanish territory, mixing reporting lanes, or building returns from store totals that don’t match the tax forms.

• Charging Spain VAT for Canary Islands/Ceuta/Melilla orders.
• Configuring WooCommerce taxes before choosing the correct reporting lane (Modelo 303 vs Modelo 369).
• Using one flat rate across all products without validating reduced/super-reduced eligibility under Spain’s VAT law.
• Mixing local Spain VAT and OSS/IOSS transactions in one reporting bucket (double reporting or omissions).
• Preparing Modelo 303 from “WooCommerce revenue” instead of taxable base + VAT lines (then wondering why it doesn’t reconcile).
• Treating shipping and discounts inconsistently across checkout, invoices, and filings.
• Missing deadlines for Modelo 303 / Modelo 390 because the VAT close wasn’t run early enough.
• Scaling into monthly/SII obligations without planning (Gran Empresa threshold and SII timelines).

How we help at Commenda

WooCommerce VAT in Spain tends to break when your operations evolve: a new 3PL, a new EU shipping route, a new product line with different VAT treatment, or a shift from local filings to OSS/IOSS (or the reverse). The risk isn’t just “wrong VAT.” It’s inconsistent VAT across checkout, invoices, and returns, followed by painful clean-up.

At Commenda, we make Spain VAT operational:

• We map your WooCommerce selling model to the right Spain VAT lane (Modelo 303 vs OSS/IOSS via Modelo 369 vs outside VAT territory), then document the boundaries so your team can run them consistently.
• We handle registration and setup sequencing so you don’t collect VAT without the correct registrations in place (Modelo 036 for local VAT, Form 035 for OSS/IOSS).
• We build a repeatable filing workflow that reconciles WooCommerce orders, refunds, shipping, and VAT calculations into filing-ready numbers without quarterly fire drills.

If your WooCommerce numbers don’t reconcile cleanly into Modelo 303/369, that’s a risk signal, not a “reporting annoyance.” Commenda will help you fix the structure, align your VAT lane, and build documentation that holds up when questions come.

Book a Demo! 

FAQs

1. Do I charge Spanish VAT for orders shipped to the Canary Islands?

In most cases, no, because Spanish VAT (IVA) applies in the Peninsula and the Balearic Islands and is excluded in the Canary Islands, Ceuta, and Melilla.
For a WooCommerce store, the practical takeaway is that these destinations should be treated as a separate tax/fulfillment flow, not as “standard Spain VAT at checkout.”

What to do operationally:

• Configure shipping/tax logic so Canary Islands/Ceuta/Melilla orders don’t inherit Peninsula/Balearics VAT rules.
• Expect different paperwork/indirect tax handling than mainland Spain (this is where many sellers get caught, because it’s not just a rate change, it’s a different scope).
  

2. If I use OSS/IOSS (Modelo 369), do I still need to file Modelo 303 in Spain?

Often, yes, if you have local Spanish VAT obligations. OSS/IOSS doesn’t automatically replace local filings when your business has Spain-anchored activity (for example, establishment or Spain-based inventory). Modelo 303 is Spain’s periodic VAT self-assessment return with strict filing windows.

How to keep this clean:

• Treat Modelo 303 and Modelo 369 as different “lanes” with different transaction sets. Spain’s tax agency describes Modelo 369 as the periodic return for the special eCommerce regimes.
• The key control is transaction bucketing: a sale should land in one lane only; you risk double reporting.
  

3. What’s the simplest way to keep WooCommerce VAT numbers reconcilable with Spanish filings?

Think in terms of a repeatable “VAT close,” not a one-off export. A practical method:

• Build VAT totals from order-level data (taxable base + VAT lines), not from payouts or “gross sales.”
• Separate by lane first (local Spain vs OSS/IOSS vs outside Spain VAT territory) before you total anything.
• Treat refunds as VAT adjustments tied back to the original order (especially partial refunds), so your period totals don’t drift.
• Keep a one-page bridge schedule that explains the difference between “WooCommerce sales” and “VATable sales reported,” so you can support the numbers if questioned.

This approach also helps you hit Spain’s fixed Modelo 303 windows without scrambling at the deadline.

4. Can I issue simplified invoices for WooCommerce sales in Spain?

Yes, in specific cases. Spain states that you can issue a simplified invoice when the invoice amount does not exceed €400 (VAT included) and in other defined situations (including corrective invoices).

Practical guidance for WooCommerce stores:

• Use simplified invoices mainly for lower-value B2C orders, where they reduce admin friction.
• If a customer needs an invoice for tax reasons (or if your supply type requires a more detailed invoice), be ready to issue a full invoice workflow as well.
  

5. How long should I keep VAT records for sales in Spain?

For standard VAT documentation, Spain’s tax agency states you must keep invoices and supporting documents related to tax obligations for the 4-year limitation period.

If you use OSS/IOSS:

• Spain’s official “Guía de la ventanilla única del IVA” states that the transaction records for the special regimes must be kept for 10 years from the end of the year in which the transaction took place.

Practical takeaway: keep two retention periods in mind: 4 years for general invoicing/VAT support docs and 10 years for OSS/IOSS regime records.