Magento Developer Belgium

Three different shapes for three different Belgian shops:

• Shopify Plus, fast to launch, good for DTC fashion / cosmetics under €5M. Bancontact via Mollie / Stripe. Weaknesses: trilingual NL+FR+DE storefronts cost €2k+/mo in third-party apps, Peppol e-invoicing is unsolved out-of-box, B2B (KBC Payment Button, Net-60, BTW intracom) is third-party only.
• Lightspeed eCom (Belgian-Dutch-origin, HQ Amsterdam + Gent office), well-integrated for Belgian retail POS + e-commerce + Bancontact. Weaknesses: smaller theme + module ecosystem than Magento or Shopify, harder to do custom B2B flows or multi-region BE+NL+FR+DE.
• Magento 2 / Adobe Commerce, the right answer when you need multi-store (NL + FR + DE views with shared catalogue), real B2B (BTW intracom, KBC Payment Button, Net-30/60, Peppol), or cross-border to NL + FR + DE (80% of BE e-commerce is cross-border). Bancontact + Payconiq are native Magento modules, BTW trilingual templates are achievable, Peppol Access Point integration is straightforward via Hermes / Babelway / Pagero.

Most Belgian merchants €1M+ outgrow Shopify within 12-18 months. We migrate Shopify → Magento and Lightspeed → Magento regularly.

Bancontact is Belgium’s dominant local-pay scheme, 30%+ of all Belgian online checkouts (some segments push past 50%). It co-badges with Maestro on most Belgian debit cards, so without Bancontact acceptance, a huge slice of Belgian shoppers either bounce or pay with reluctance via Visa / Mastercard. Payconiq (a Bancontact sister product owned by Belgian banks) adds QR-code + push-to-phone mobile payments, ubiquitous in retail + restaurants, fast-growing in e-commerce.

To accept Bancontact + Payconiq in Magento 2, the simplest routes are:

• Mollie, the most-used PSP for Belgian e-commerce. Bancontact + Payconiq native, free Magento 2 module, KBC / Belfius / ING bank-wallets included.
• Stripe BE, Bancontact + Payconiq supported via the unified payment intent API. Good if you’re multi-country (BE + NL + FR + DE).
• Adyen, enterprise-grade, full BE rail coverage including KBC Payment Button.
• Worldline / Ingenico, legacy bank-direct route, used by big Belgian retailers + B2B.

We configure the PSP, enable Bancontact + Payconiq in checkout, and verify with BE-issued test cards (Bancontact issuer ranges from KBC / BNP Paribas Fortis / Belfius / ING).

Belgium has three official languages: Dutch (Vlaams, ~60% of the population, Flanders: Antwerpen / Gent / Brugge / Leuven), French (Wallon, ~40%, Wallonia + Brussels: Charleroi / Liège / Namur / Mons), and German (~1%, the East Cantons: Eupen / St. Vith / Malmedy). A serious Belgian e-commerce store needs all three.

Magento 2 architecture for this:

1. One Magento install, one website, three store views, be_nl, be_fr, be_de. Shared catalogue, currency (EUR), and customer base, but separate translations, URL prefixes (or country-coded paths like /nl/, /fr/, /de/), and per-store CMS pages.
2. URL routing, prefix-based is the cleanest. Add IP-geo + browser-language fallback (Belgian visitors hitting the root see Dutch by default if they’re in Flanders, French in Wallonia, with manual switcher).
3. hreflang, emit per-page nl-BE / fr-BE / de-BE tags. We use Panth_Hreflang module to manage this from DB.
4. Per-store catalogues, product names + descriptions + meta translated per store view. Attribute scope = store view for any localised text.
5. Per-store payment + shipping, same Bancontact / Payconiq stack on all three, but copy in the right language.

For Hyvä we ship a custom language-switcher that lives in the header without a full page reload.

Peppol (Pan-European Public Procurement OnLine) is the European e-invoicing network. Belgium adopted it as its national e-invoicing backbone via Hermes (the FOD BOSA / SPF BOSA Belgian government Access Point) and a growing list of certified private PDPs / Access Points (Babelway, Pagero, Basware, Esker, Codabox).

Belgian e-invoicing deadlines:

• From 1 March 2024, already required for B2G to federal entities above €3,000.
• From 1 January 2026, all B2G transactions must be Peppol-format e-invoices (no PDF, no paper).
• From 1 January 2028 (proposed, under finalisation), B2B e-invoicing mandatory between Belgian VAT-registered businesses.

Magento integration steps:

1. Choose a Peppol Access Point, Hermes (government, free for B2G), Babelway / Pagero / Basware (commercial, for B2B + cross-border + ERP integration).
2. Order/invoice generation must produce UBL 2.1 XML in Peppol BIS Billing 3.0 format (the EU-standard invoice schema).
3. Integrate Magento → Access Point via REST / SFTP / AS4. The Access Point delivers to the recipient’s ID (KBO / BCE company number + Peppol ID).
4. Inbound handling: receive supplier invoices via the same Access Point into Magento purchase orders or your ERP.

We’ve shipped this integration for BE merchants migrating from PDF-attached emails to full Peppol AS4.

Belgium calls VAT three things depending on the buyer’s language: BTW (Belasting over de Toegevoegde Waarde, Dutch), TVA (Taxe sur la Valeur Ajoutée, French), MwSt (Mehrwertsteuer, German). Rates:

• 21%, standard rate (most goods + services).
• 12%, reduced (some agriculture, social housing, restaurants).
• 6%, reduced (essential food, books, water, pharmaceuticals).
• 0%, B2B intra-EU sales with valid VIES BTW number (reverse charge); newspapers + journals.

Magento configuration:

1. Tax classes, create BTW-21, BTW-12, BTW-6, BTW-0 in Stores → Tax Zones & Rates.
2. Tax rules per rate, scoped to BE destination.
3. Invoice templates per store view, override the default sales email + PDF invoice template:
   • be_nl view → “BTW”, “Btw-nummer”, Dutch invoice copy.
   • be_fr view → “TVA”, “Numéro de TVA”, French invoice copy.
   • be_de view → “MwSt”, “USt-IdNr.”, German invoice copy.
4. Buyer-language fallback, if a Dutch-speaking buyer orders on the FR store, optionally send the invoice + auto-reply in their preferred language (configurable per customer).
5. BTW intracom validation on B2B checkout via VIES, required for 0% intra-EU reverse charge.

Belgian e-commerce is uniquely cross-border-heavy, ~80% of Belgian online shoppers buy from foreign stores (mostly NL, FR, DE), and many Belgian merchants serve those neighbours back. The Magento setup:

• Multi-region storefront, one Magento install, multiple websites or store views: be_nl / be_fr / be_de plus optionally nl_NL for Netherlands shoppers, fr_FR for France, de_DE for Germany. Shared catalogue, separate URLs (yourbrand.be / yourbrand.nl / yourbrand.fr / yourbrand.de).
• Per-country VAT, BE 21%, NL 21%, FR 20%, DE 19%. Each with its own reduced rates. OSS (One-Stop-Shop) for distance-selling thresholds.
• Per-country payments, BE: Bancontact / Payconiq / KBC. NL: iDEAL. FR: Cartes Bancaires (CB). DE: SEPA Direct Debit / Klarna / Sofort. We layer them per store via Mollie + Stripe + Adyen.
• Per-country shipping, bpost for BE, PostNL for NL, La Poste / Mondial Relay for FR, DHL / Hermes for DE. Mondial Relay also works BE + FR pickup-points.
• Per-country legal pages, Algemene Voorwaarden (NL), Conditions générales (FR), AGB (DE), and BE-equivalents per language.
• Currency, all EUR, no FX rebuild needed.

Belgium’s marketplace landscape is dominated by bol.com (the #1 BeNeLux marketplace, Dutch-owned but huge in Belgium, especially Flanders), Coolblue (Belgian-Dutch electronics specialist), and Vinted (second-hand fashion, fast-growing). Plus Amazon.fr / .de / .nl for cross-border.

Magento feed integration:

1. bol.com, use a Magento 2 bol.com connector (Channable, EffectConnect, or direct via the bol.com Retailer API). Push products, stock, price; pull orders + shipping labels. Bol.com supports both NL + BE shoppers in one feed.
2. Coolblue Marketplace, via Channable / Lengow / Mirakl integrations. Smaller catalogue control, stricter quality standards (Coolblue curates aggressively).
3. Vinted, B2C-only Pro accounts for second-hand fashion. Feed via Vinted Pro API or third-party (Channable supports it for some categories).
4. Amazon.fr / .de / .nl, standard Amazon Magento connector. Belgian merchants commonly list on Amazon.fr (closest geo) + Amazon.nl (BeNeLux).

We architect the feed flow so Magento stays the single source of truth for stock + price, everything else is a downstream sync.

Belgium’s three biggest banks each have their own checkout wallet that lets customers pay from their bank app, similar to iDEAL in the Netherlands but bank-branded:

• KBC Payment Button (also covers CBC, KBC’s Walloon brand), KBC is the #1 bank in Flanders. The Payment Button redirects to the KBC app, customer approves, money moves SEPA-instant.
• Belfius Direct Net, Belfius is a major BE-only bank. Similar app-redirect flow.
• ING Home’Pay, ING Belgium’s bank-wallet, same model.
• BNP Paribas Fortis Easy Banking, the #1 BE bank by deposits, supports payment via the BNPP Fortis app.

Magento integration: all four are available via Mollie, Adyen, or Worldline / Ingenico as PSP routes, you don’t integrate each bank directly. Enable them in your PSP dashboard, configure the Magento payment method to expose the bank picker at checkout, and customers see “Pay with my bank” with the 4 BE options + Bancontact + Payconiq + Klarna + Visa / MC. This is the BE equivalent of iDEAL bank selection.

GBA-APD is Belgium’s Data Protection Authority, Gegevensbeschermingsautoriteit (Dutch) / Autorité de Protection des Données (French). It enforces GDPR in Belgium plus the Belgian Data Protection Law (Loi du 30 juillet 2018 / Wet van 30 juli 2018).

Concrete Magento-checkout impacts:

• Cookie consent, GBA-APD aligns broadly with EDPB / CNIL guidance: granular opt-in, equally-prominent “Reject all” button, no pre-ticked checkboxes, no cookie walls for essential content. We ship Cookiebot / Didomi / Axeptio wired into Magento’s cookie API, trilingual NL+FR+DE banner copy reviewed against GBA-APD guidance.
• DSAR (Data Subject Access Requests), must be handled within 1 month, in the customer’s language (NL / FR / DE / EN). We add a self-service DSAR endpoint that exports the customer’s order + account data.
• Breach notification, 72-hour reporting to GBA-APD if a breach risks customer rights. Magento logs + monitoring must support evidence-gathering.
• Data-residency, GBA-APD doesn’t mandate EU-only hosting but strongly prefers it. Combell / Hostbasket / Nucleus / OVHcloud BE / AWS Frankfurt (eu-central-1) are all fine. US-region hosting is a red flag.
• Cross-border GDPR coordination, if you serve NL + FR + DE too, GBA-APD coordinates with AP (NL), CNIL (FR), BfDI / Landesdatenschutzbehörden (DE) via the EDPB.

Depends on your volume + budget + data-residency posture:

• Combell, the biggest Belgian hosting provider (Gent-headquartered, BE data centres). Strong on price (€30, €200/mo for small/medium Magento), Belgian support in NL + FR + DE, sovereign BE data residency. Less auto-scaling than AWS; more DevOps work needed for large stores.
• Hostbasket (now part of Combell group), SME-friendly Belgian hosting, similar profile.
• Nucleus (Antwerpen), high-performance Belgian managed hosting, well-known for Magento-specialised dedicated servers and ISO-certified BE data centres. Strong for €1M, €25M stores that want BE residency without going DIY.
• AWS Frankfurt (eu-central-1), if you want US-grade auto-scaling, RDS, ElastiCache, Fastly CDN. Not BE soil but GDPR-compliant. Cost-effective above €5M GMV.
• OVHcloud Belgium / France, French cloud giant with BE presence, mid-range pricing.
• Adobe Commerce Cloud (Frankfurt region), best if you’re already on Adobe Commerce. Auto-scaling, Fastly CDN, 24/7 Adobe support, < 30ms latency to Brussels / Antwerpen. Costs €25k+/yr.
• Hyvä Cloud / Cloudways Frankfurt, managed Magento, €200-800/mo, good middle ground.

For most Belgian merchants €500k, €5M, Nucleus or Combell is the sweet spot, BE residency, BE support, no AWS DevOps overhead.

Three tiers, all at $25/hr (the canonical rate, EUR equivalent on request):

• Audit, $499 (~€459 at current FX). ~20 hours @ $25/hr. Written audit covering Bancontact + Payconiq integration, trilingual NL+FR+DE store-view review, GBA-APD compliance, Peppol B2G readiness, Core Web Vitals. 30 / 60 / 90-day roadmap.
• Build, $4,999 (~€4,599 EUR). ~200 hours @ $25/hr. Full Magento build or rebuild, trilingual storefront, multi-rail BE checkout, BTW templates, Peppol Access Point, bol.com / Coolblue feeds, 14 days post-launch support. Most popular.
• Enterprise, Custom. Quoted per scope. Multi-region BE+NL+FR+DE, B2B with Peppol B2B 2028 prep, ERP integration (Odoo / Dynamics / SAP B1), 30 days post-launch + retainer.

Credentials: 8+ years on Magento 2 + Adobe Commerce, Adobe-Certified, 200+ stores shipped including BeNeLux + DACH builds. References available on request from Belgian + Dutch clients. We work with Belgian VAT (BTW BE0...) invoicing for tax-deductible B2B engagements.

Three common Belgian shapes, three different builds:

• Single-language Flemish boutique (e.g. an Antwerpen-based fashion store serving Flanders only), one Magento store view in Dutch, no FR / DE needed. Bancontact + Payconiq are mandatory, Mollie covers everything. BTW templates only in Dutch. bpost shipping. Combell or Hyvä Cloud hosting. Audit + Build €5k, €10k total.
• Wallon-French boutique (e.g. a Liège / Charleroi store serving Wallonia only), one store view in French. Same payment stack. Watch for cross-border France traffic spillover, some stores add a fr_FR view to court French buyers.
• Trilingual national retailer (e.g. a Brussels-headquartered home-goods chain serving all of Belgium), three store views (NL + FR + DE), Peppol B2G ready (likely sells to schools / hospitals / municipalities), KBC + Belfius + ING + Bancontact + Payconiq + Klarna full stack, bol.com feed live. Build cost €15k, €40k, Enterprise tier likely.
• Cross-border DACH-focused merchant (e.g. an Eupen / German-speaking East Cantons B2B selling into DE + AT + CH), German-first store plus DE + AT + CH multi-currency / multi-VAT. Klarna + Sofort + SEPA primary, Bancontact secondary. Different shape entirely, we’ve done this with Liechtenstein- and Luxembourg-adjacent BE merchants.

Architecture decided in the audit step, the wrong shape costs €10k+ to undo later.