Magento Developer UK FAQ
All 12 answers
How do you handle UK GDPR cookie consent in Magento?
Two layers: (1) UK GDPR + DPA 2018 for personal data, lawful basis, DSAR automation, retention rules in customer + sales_order. (2) PECR (Privacy and Electronic Communications Regulations) for cookies & marketing, ICO requires opt-in consent for non-essential cookies before they fire (no “continued use = consent” banners, no pre-ticked checkboxes). We ship a Cookiebot / Usercentrics / Klaro setup wired into Google Tag Manager & Magento’s native cookie API so analytics, ads, and chat widgets only load after consent. Banner copy reviewed against ICO guidance.
How does post-Brexit VAT work for my Magento store?
Post-1 January 2021 the UK left the EU VAT area, so:
- UK→UK B2C: standard 20% VAT, register at £90k turnover (2024+ threshold).
- UK→EU B2C: use the EU IOSS scheme for orders under €150 (one VAT registration covers all 27 countries) or register per-country above that.
- UK→EU B2B: zero-rated with VAT-number validation; reverse charge.
- EU→UK B2C: overseas sellers register for UK VAT below £135 thresholds.
We rebuild Magento’s tax engine with these rules, plug in EU-OSS / IOSS schemes, and validate VAT numbers via VIES (EU) + HMRC (UK). MTD invoicing wired into QuickBooks / Xero / Sage.
What is MTD (Making Tax Digital) and how do I comply in Magento?
MTD is HMRC’s mandatory digital VAT-record-keeping + e-submission rule. All VAT-registered businesses (regardless of turnover, since April 2022) must keep digital records and submit VAT returns via MTD-compatible software. Magento itself isn’t MTD software, it must feed compliant software:
- QuickBooks Online (most popular), we connect via the Magento ↔ QBO bridge.
- Xero, native Magento connector (e.g. A2X, Greenback).
- Sage Business Cloud / Sage 200, via Magento’s ERP-connector framework.
Every Magento order & credit-memo lands in your accounting software with VAT-rate breakdown, invoice number, and HMRC-compliant fields. No more month-end CSV exports.
How do I integrate BACS Direct Debit with Magento for B2B?
BACS Direct Debit is the UK’s preferred B2B rail, lower fees than cards (typically 0.5-1% vs 2-3%), better cash-flow control, and customer-friendly. The standard route is GoCardless, which has a mature Magento 2 module. We:
- Install + configure the GoCardless Magento module on your environment.
- Wire it into Magento’s B2B module (Adobe Commerce) or a custom company-account flow (Open Source).
- Add a Net-30 / Net-60 invoice flow with auto-collected mandates (signed online once, debited monthly).
- Reconcile in QuickBooks / Xero with VAT-rate awareness for MTD.
For Adobe Commerce B2B, this slots into company + sales_rule tables for customer-specific pricing and approval workflows.
What’s the difference between Worldpay, Opayo, Stripe and Adyen for UK Magento stores?
Pick by use case:
- Worldpay (FIS / Vantiv-owned), the legacy UK leader, best for established UK retailers with bank-direct relationships. Solid fraud tools.
- Opayo (formerly SagePay, now Elavon), very common with mid-market UK SMEs. Good for predictable monthly fees.
- Stripe, best developer experience, easiest scaling abroad (US / EU multi-currency), modern Strong Customer Authentication (SCA / 3DS2). Slightly higher base rate.
- Adyen, enterprise / multi-region. One contract for UK + EU + APAC, unified reporting, but minimum monthly volume.
We integrate any of them, many UK stores run Stripe + Klarna + BACS as a three-rail stack.
How do I add Klarna / Clearpay BNPL to my UK Magento store?
Klarna and Clearpay (UK-branded Afterpay) are both essential for UK fashion / DTC, ~30-40% of UK online shoppers under 35 expect a Pay-in-3 / Pay-in-4 option. Both have official Magento 2 modules:
- Klarna, Pay in 3, Pay in 30 days, financing. Strong UK + Nordic + DACH. Higher fees (3 to 6%); test its effect on AOV on your own store.
- Clearpay, Pay in 4 over 6 weeks. Big in UK / AU fashion. Slightly cheaper than Klarna.
We install, configure, and wire the on-site widgets (PDP price-line + cart + checkout). FCA-compliant disclosure copy reviewed. We also handle the FCA-required affordability check banner that came in May 2026.
How do you handle Royal Mail / DPD UK / Hermes / Evri in Magento?
Most UK stores need 2-3 carriers for cost optimisation:
- Royal Mail Tracked 24 / 48 + Special Delivery, cheapest for low-weight (< 2kg).
- DPD UK, best 1-hour delivery slot, premium retail. Native Magento module via DPD’s API.
- Evri (formerly Hermes), cheapest 2-5kg, weak tracking but good price.
- Yodel / ParcelForce, backup / regional use.
We integrate via ShipperHQ (rule engine) or direct carrier modules, rule-based routing by weight, postcode, value, and delivery promise. Booking labels auto-generated from Magento order grid; tracking webhooks update sales_order.
What’s the right setup for Highlands & Islands shipping?
Highlands & Islands (Scottish Highlands, Hebrides, Orkney, Shetland, Northern Ireland, Channel Islands, Isle of Man) are a known Magento gotcha, carriers charge surcharges of £5 to £25 that vanilla Magento doesn’t apply by default. We:
- Add a postcode-prefix matrix (IV, KW, PA, PH, ZE, BT, GY, JE, IM ranges) to
shipping_table_rate. - Wire ShipperHQ rules so only Royal Mail or specific premium carriers serve those postcodes, no DPD next-day promises that can’t be kept.
- Apply surcharges in checkout with clear copy (“£X surcharge for Highlands & Islands”) so customers don’t complain post-purchase.
- Optionally exclude express options for those regions to avoid late-delivery refunds.
I am available to UK stores for this setup, working remotely from Ahmedabad, India.
How do I split my store for UK + EU post-Brexit?
Three patterns, depending on volume:
- Single-store, geo-priced, one storefront with VAT calculated by destination. Cheapest. Good for small UK-first stores selling occasionally to EU.
- Two storefronts, shared catalogue,
storefor UK (GBP, UK VAT, Royal Mail) andstorefor EU (EUR, IOSS, DHL Europe). One Magento backend, one PIM, separate checkouts. Most popular pattern. - Two websites, two backends, legally separate UK Ltd + EU GmbH/BV. Best for £5M+ stores with EU fulfilment hub (Netherlands / Ireland). Magento
website-level split.
We architect, build, and migrate live data, including reroute + 301 from old single-store URLs.
What time-zone overlap can I expect working with you from India?
Real, daily, 4-6 hours of working overlap:
- India Standard Time = UTC+5:30
- UK = UTC+0 (GMT, winter) or UTC+1 (BST, summer)
- Overlap window: 1 PM to 7 PM IST = 8:30 AM to 2:30 PM GMT (winter) or 9:30 AM to 3:30 PM BST (summer).
That covers your morning standup, mid-morning review, and lunchtime hand-off. A daily review on staging is the typical cadence. Slack / WhatsApp async covers the rest. I am available to stores in London, Manchester, Edinburgh, and Bristol, working remotely from Ahmedabad, India.
Is Adobe Commerce Cloud (Dublin) better than UKFast for UK stores?
Depends on your volume + budget:
- Adobe Commerce Cloud (Dublin region), best if you’re already on Adobe Commerce. Auto-scaling, Fastly CDN, 24/7 Adobe support, < 30ms latency to most UK postcodes. Costs £25k+ /yr, locks you to Adobe.
- UKFast / Pulsant, UK-based managed Magento hosting. Cheaper (£5-15k /yr), excellent UK support, ISO 27001 accredited, data stays in UK (good for some UK GDPR / public-sector contracts). Less auto-scaling.
- Cloudways London / Linode London / Hyvä Cloud, good middle ground for £500k to £5M stores, £200-800 /mo.
We help benchmark + migrate, the right answer is rarely the most expensive one.
Should I migrate to Hyvä for my UK fashion store?
Almost certainly yes if you’re on Luma. UK fashion shoppers convert dramatically better on fast mobile experiences:
- Lighthouse 95+ on Hyvä vs typically 40-60 on Luma fashion themes, Google ranks fast pages higher for category/PDP queries.
- Hyvä Checkout loads in < 1s, which tends to lower bounce vs Magento Luma checkout, especially mobile.
- Klarna / Clearpay widgets render natively without the React/jQuery double-render Luma has.
- Royal Mail / DPD / Evri shipping pickers render instantly, no spinner-on-spinner.
The timeline is set in the written quote, after we agree the scope. A faster storefront usually helps conversion, so measure it on your own store over the first 90 days after launch; optimisation work then builds on it. See our Hyvä service page for what a build covers.
Related FAQ topics
All FAQ topics-
Magento Upgrade
Common questions about upgrading Adobe Commerce / Magento Open Source. -
Hyvä Development
Common questions about Hyvä theme development, migration from Luma, and Hyvä Checkout.
-
Magento Performance
Common questions about Magento performance optimization, Lighthouse... -
Emergency Bug Fixing
Common questions about emergency e-commerce bug fixing across... -
Hiring a Freelance Magento Developer
Questions about Magento project scope, quotes, start dates... -
Magento B2B Development
Common questions about Adobe Commerce B2B, Magento B2B development...