Magento Developer Spain: 12 questions answered.

Spain has three mainland IVA rates plus a parallel system for the Canary Islands:

• 21%, standard (IVA general). Most goods + services.
• 10%, reduced (IVA reducido). Food, hospitality, transport, books-electronic since 2020.
• 4%, super-reduced (IVA superreducido). Bread, milk, fruit, vegetables, books-print, medicines, accessibility goods.
• IGIC (Impuesto General Indirecto Canario), Canary Islands replacement: 7% standard, 3% / 0% reduced. Geographically distinct, not part of EU VAT zone.
• IPSI (Ceuta / Melilla), another parallel system for those autonomous cities.

Magento configuration:

1. Create tax classes per rate (IVA-21, IVA-10, IVA-4, IGIC-7, IGIC-3, IPSI).
2. Create tax rules with geographic scope (mainland ES / Balearics / Canarias / Ceuta-Melilla / EU / RoW).
3. B2B reverse-charge, on intra-EU B2B sales with a valid VIES-validated EU VAT ID, IVA = 0% (recipient self-accounts). On Spanish-domestic B2B, IVA stays charged.
4. Inverted-charge on construction / scrap / electronics, specific Spanish reverse-charge rules apply to certain B2B categories per Ley 37/1992 art. 84.
5. IVA on invoice broken down per rate (mandatory).

Bizum is Spain’s dominant mobile payment, 45%+ of mobile checkouts, backed by every major Spanish bank (Santander, BBVA, CaixaBank, Sabadell, Bankinter). Without Bizum, you’re losing roughly half your mobile traffic at the payment step. Bizum is bank-to-bank instant payment, similar to UK Faster Payments or India UPI, with a phone-number identifier.

Magento integration paths:

• Redsys + Bizum, the canonical route. Redsys is the Spanish bank-acquirer rail (CaixaBank / Santander / BBVA « Servired » merger). Bizum is exposed as a tokenised payment method through your Redsys merchant account.
• Stripe ES + Bizum, Stripe added Bizum in 2024. Easier integration if you’re already on Stripe; Bizum appears as a payment-method option in the unified card form.
• Adyen + Bizum, for enterprise / multi-country merchants.
• Direct Bizum API, if you have a Spanish bank merchant agreement, you can integrate Bizum directly. More work, lower fees at volume.

We wire Bizum into Magento native checkout + Hyvä with the proper redirect / 3DS2 SCA flow, plus the “Bizum” button styled correctly (Bizum has brand guidelines, you can’t recolour it).

Three transparent tiers, all priced in USD with EUR parity quoted:

• Audit, $499 (~€459), ~20 hours @ $25/hr. A senior Adobe Certified Magento dev reviews your store for Bizum / Redsys / NIF-validation / LOPDGDD / multi-language / Core Web Vitals issues. Written report + presupuesto for any fixes.
• Build, $4,999 (~€4,599), ~200 hours @ $25/hr. Bizum + Redsys integration, NIF/NIE/CIF validation, multi-language store views (Castellano + Catalán + Euskera + Galego), IVA configuration, Veri*Factu / TicketBAI readiness, LOPDGDD-compliant cookie banner, Hyvä migration or Luma redesign. 2-3 week delivery typical.
• Custom, quoted, multi-Iberian (ES + PT + AND), full Veri*Factu / TicketBAI pipeline, marketplace feeds, ERP integration (Sage 200 / Holded / SAP / Microsoft Dynamics).

Why $25/hr? We’re based in Ahmedabad, India, same engineering quality as a Madrid / Barcelona agency at €75, €120/hr, without the Spanish payroll overhead. Credentials: Adobe Certified Magento Developer, ten years building Magento for B2B + DTC stores, 200+ stores shipped, including specific Iberian merchant builds. References available on request.

Three real Spanish-market scenarios we’ve shipped recently, and what changes per scenario:

• Andalusian artisan / small DTC (€100k, €500k GMV), Castellano-only storefront, Bizum + Redsys + PayPal, simple NIF validation, IVA 21% / 10% / 4%, LOPDGDD cookie banner, no marketplaces yet. Tier: Audit + small Build. Hosting: ARSYS or Cloudways. Focus on Core Web Vitals + organic SEO (Andalusian artisans win on local long-tail).
• Catalonia B2B wholesaler (€5M+ GMV), Catalan + Castellano storefront (Catalan required by Llei de Política Lingüística), NIF + CIF + VIES validation, Net-30/60, EU intra-community IVA reverse-charge, Veri*Factu mandatory 2026+, Sage 200 / Holded ERP integration, B2B trade catalogue with account-based pricing. Tier: Build → Custom. Hosting: AWS Madrid or Adobe Commerce Cloud.
• Multi-Iberian (ES + PT + AND, €10M+ GMV), Three storefronts on one Magento backend, Spain (Castellano + Catalán + Euskera + Galego), Portugal (Portuguese, EUR, separate SAF-T PT e-invoice), Andorra (Castellano, no EU IVA, sovereign tax system). Shared catalogue, per-country IVA + payment-method + shipping. Tier: Custom only. Hosting: Adobe Commerce Cloud Frankfurt for multi-region + 24/7 support.

Audit step identifies which scenario fits your store; we tailor scope + pricing accordingly.

Four practical options for Spanish data residency + low-latency Madrid / Barcelona / Valencia:

• AWS Madrid (eu-south-2), opened 2022, full availability zones in Madrid. Best if you need AWS-grade tooling (RDS, S3, CloudFront, ElastiCache) with FR / IT / PT low-latency too. Compliant with LOPDGDD + RGPD data-residency requirements.
• ARSYS, Spanish hosting giant (Logroño-based), part of 1&1 IONOS group. Strong on price, Spanish-language support, dedicated servers + managed Magento. AEPD-friendly, all data in Spanish data centres.
• OVHcloud Spain, OVH operates a data centre in Madrid since 2023. French sovereign cloud, ES data residency, lower prices than AWS for bare-metal.
• Adobe Commerce Cloud (Frankfurt), if you’re on Adobe Commerce, the closest region. ~30ms Madrid latency. Frankfurt is GDPR-compliant but technically German territory, some AEPD-strict clients prefer Spanish-region hosting for posture.
• Hyvä Cloud / Cloudways, managed Magento on AWS / DO, €200-800 /mo. Good middle ground for €500k, €5M stores.

Decision depends on whether you need Spanish-territory data residency (for AEPD-strict / public-sector clients) or just low-latency to Spain (for which Frankfurt or Paris is fine).

LOPDGDD (Ley Orgánica 3/2018, de Protección de Datos Personales y garantía de los derechos digitales) is the Spanish national law that implements RGPD (GDPR) plus adds Spain-specific rules. AEPD (Agencia Española de Protección de Datos) is the enforcement body, one of the most active regulators in the EU, levying multi-million-euro fines against Spanish + foreign companies.

Concrete Magento implications:

• Cookie consent, AEPD published explicit guidance (2020, updated 2023). Must be granular, per-purpose opt-in. No pre-ticked boxes. No “continued browsing = consent”. The “Reject all” button must be as prominent as “Accept all”. Cookie walls are banned (AEPD aligned with CNIL position).
• Data residency, for sensitive sectors (health, financial, public), AEPD prefers EU-region hosting; Spanish-territory hosting is the safe posture.
• Spanish-language DSAR, data-subject access requests must be answerable in Castellano (and Catalan/Euskera/Galego if your business operates there).
• Right-to-be-forgotten audit trail, Magento customer + order data with structured anonymisation pipeline (not just delete, anonymise for accounting retention).
• DPO appointment, mandatory for certain categories under LOPDGDD art. 34.

We ship Cookiebot / Axeptio / Didomi (Spanish-localised) wired into Magento’s cookie API, banner copy reviewed against AEPD guidance, and a structured DSAR / RTBF workflow.

Each platform has a Spanish-market sweet spot. Here’s the honest comparison:

• Magento 2 / Adobe Commerce, the answer when you need real multi-language (Castellano + Catalán + Euskera + Galego), multi-store (ES + PT + AND), B2B with NIF + VIES validation, or marketplace feeds at scale. Best ROI from €500k GMV upward.
• PrestaShop, dominant in the Spanish €100k, €2M segment because it’s cheap and has loud Spanish community modules. Hits walls on multi-store, B2B, and TicketBAI / Veri*Factu integration. Migration to Magento is common at €2M+.
• Logicommerce, Spanish SaaS (Barcelona-based), strong in B2B + omnichannel verticals, decent for €1M, €10M merchants who don’t want self-hosted ops. Limited customisation; you rent the platform.
• Shopify Plus, great for DTC fashion / beauty up to €5M but Bizum integration is weaker, Spanish-market apps are thinner, and Spanish accountancy / Veri*Factu integration is patchy. Strong if you’re cross-border-first.

We’ve migrated 30+ Spanish stores between these platforms. The audit step shows the real cost-vs-fit picture before you commit.

Selling-only-on-your-own-store is rare in Spain at scale. The Spanish marketplace mix matters:

• Amazon.es, ~35% of Spanish e-commerce by GMV. Magento → Amazon feed integration via Channable / Lengow / direct MWS API.
• El Corte Inglés Marketplace, ECI’s online marketplace (launched 2020 as « ECI Plus »). Premium DTC: fashion, beauty, home, gourmet. Strong margins, Spanish-only buyer base, paid placement. Strict catalog quality + Spanish-language metadata required.
• ManoMano, DIY / home / garden (French-founded but huge in ES). Magento integration via direct API. Strong B2C + emerging B2B (Pro) segment.
• Wallapop, Spanish C2C / circular-economy giant; B2B sellers can list as « Wallapop Pro ». Useful for resale / refurbished. Magento integration via custom API.
• Carrefour España Marketplace, groceries + general merchandise.
• Worten / MediaMarkt, electronics-vertical marketplaces.
• PcComponentes, Spanish electronics retail, opening marketplace gradually.

Magento implementation: pick 2-3 marketplaces that match your category, integrate via Channable or Lengow (both have native Magento connectors + Spanish-language onboarding), set up per-marketplace pricing + inventory split + return flow into Magento sales_order.

Spain has 4 co-official languages: Castellano (Spanish, all-Spain), Catalán (Catalonia, Valencia, Balearics), Euskera (Basque Country, Navarre), Galego (Galicia). For serious Iberian merchants this is non-negotiable:

• Catalonia, the Llei de Política Lingüística (1998) requires commerce operating in Catalonia to provide Catalan-language service. Barcelona retailers without Catalan storefronts lose conversion and risk Generalitat scrutiny.
• Basque Country, Euskera is the regional working language for > 30% of the population. Many Basque B2B buyers expect Euskera content.
• Galicia, Galego is universal in everyday commerce.

Magento implementation:

1. One website, four stores, Castellano default + Catalán + Euskera + Galego store views. Shared catalogue, per-store translated product_name / description / meta.
2. Locale-aware URLs, yourbrand.es (default), /ca/ (Catalan), /eu/ (Euskera), /gl/ (Galego). Or subdomain split if you prefer.
3. Hreflang tags, ca-ES, eu-ES, gl-ES, es-ES + x-default. Critical for Google to serve the right language to the right region.
4. Translation workflow, we connect Magento to professional ES→CA / ES→EU / ES→GL translators (Smartling / Phrase / native agencies) for product copy, not machine translation (which fails on Euskera grammar).

Spain has four different identifier formats and a Magento store touching B2B or invoicing needs to validate them correctly:

• DNI (Documento Nacional de Identidad), 8 digits + 1 letter (e.g. 12345678Z). Spanish citizens. Letter is checksum-derived from the digits.
• NIF (Número de Identificación Fiscal), for residents, the NIF = DNI. For foreigners, NIF can equal NIE.
• NIE (Número de Identidad de Extranjero), letter (X/Y/Z) + 7 digits + 1 letter (e.g. X1234567L). Foreign residents.
• CIF (Código de Identificación Fiscal), companies pre-2008. Letter + 7 digits + 1 control character (e.g. A12345674). Replaced by NIF-J / NIF-A for new SLs, but huge install base still uses CIF.
• VAT ID (NIF-IVA), ES + NIF/CIF for EU intra-community trade. Validated via VIES.

Magento integration:

1. Add identifier-type selector + value field to checkout + customer registration.
2. Apply the correct checksum algorithm per type (each is different, DNI uses mod-23, CIF uses a different control char calculation).
3. For B2B / VIES, on a valid VIES-validated ES+CIF, apply 0% IVA reverse-charge for intra-EU sales.
4. Print the validated identifier on every Magento invoice (mandatory under AEAT rules).

Real, daily, 3.5-4.5 hours of working overlap:

• India Standard Time = UTC+5:30
• Spain (mainland) = UTC+1 (CET, winter) or UTC+2 (CEST, summer)
• Overlap window: 12:30 PM, 5 PM IST = 9 AM, 1:30 PM CET (winter) or 9:30 AM, 2 PM CEST (summer).
• Canary Islands run on WET (UTC+0), adds an extra hour of overlap on Tenerife / Las Palmas projects.

This covers your Madrid / Barcelona morning standup, mid-morning review, and a clean lunchtime hand-off to async. Daily 4 PM CET review on staging is the typical cadence. Spanish merchants often work the long lunch (2 PM, 4 PM) plus late-day session (5 PM, 8 PM), we can flex 2-3 days/week to overlap the late session at the cost of a late evening from our end. Slack / WhatsApp async covers the rest. We’ve worked this way with Madrid, Barcelona, Valencia, Bilbao, and Sevilla clients for years.

Two parallel Spanish e-invoice mandates. They overlap but aren’t the same:

• TicketBAI, the Basque Country + Navarra mandate, already in force since 2022-2024 depending on province (Álava, Guipúzcoa, Vizcaya, Navarra each rolled out separately). Every invoice / ticket must include a TBAI-signed XML transmitted to the Hacienda Foral in real time, with a QR code and TBAI identifier printed on the customer receipt.
• Veri*Factu, the AEAT national mandate (Agencia Tributaria, all of Spain except Basque + Navarra). Approved via Real Decreto 1007/2023 + the Anti-Fraud Law. Mandatory from 1 January 2026 for most companies (entrepreneurs / SLs / SAs). Sends invoice records to AEAT in real time, with a QR + verification URL.

Magento integration:

1. Detect customer’s tax region at invoice generation. Basque / Navarra → TicketBAI flow. Rest of Spain → Veri*Factu flow.
2. Sign each invoice XML with a qualified electronic certificate (FNMT / Camerfirma).
3. POST to the right endpoint (AEAT Veri*Factu / Hacienda Foral TBAI).
4. Embed the QR + verification URL on the printed invoice / order email.
5. Cache responses for audit (mandatory 4-year retention).

We integrate with certified providers like Sage / Holded / Pennylane Spain or build the AEAT direct integration depending on scale.