Magento development in the UK: costs, hosting and when it’s worth it

Magento is worth it for a UK retailer when the shop is genuinely complex: tens of thousands of SKUs, several storefronts or currencies from one stock pool, trade customers with their own price lists, or an ERP that has to stay in step with the website every few minutes. If none of that describes you, Magento will cost you more to build, host and keep patched than WooCommerce or Shopify, and you will not feel the benefit. As a rough guide, a well-built Magento Open Source shop from a UK agency starts in the low five figures, needs specialist hosting from around £100 a month, and needs regular developer time for security patches.

That is the short answer. The rest of this guide explains the two editions, what a build really involves, what it costs to run for three years, and how to tell whether your business has outgrown simpler platforms. We build on Magento, WooCommerce and PrestaShop, so we have no reason to push you towards the most expensive option.

Magento Open Source, Adobe Commerce and Mage-OS

Adobe bought Magento in 2018. Today there are three things people mean when they say “Magento”.

Magento Open Source is the free edition. You download it, host it wherever you like and pay developers to build and maintain it. It already includes the serious retail features: configurable products, multiple websites and store views from one admin, customer groups, tiered pricing, cart price rules, layered navigation and a mature REST and GraphQL API. Most small and mid-sized Magento shops in the UK run this edition.

Adobe Commerce is the licensed edition, sold on-premise, on Adobe’s managed cloud, or as a newer SaaS-style service. It adds a full B2B suite (company accounts with buyers and approvers, shared catalogues, quote requests, purchase orders and credit limits), content staging and scheduling, customer segments and Adobe’s support. Adobe does not publish list prices. Licences are quoted individually and generally scale with your gross merchandise value; figures reported by UK merchants and agencies usually start in the tens of thousands of pounds a year. For a business turning over a few hundred thousand pounds online, that alone rules it out.

Mage-OS is a community-led distribution of Magento Open Source, maintained by developers and agencies who wanted a release cycle not tied entirely to Adobe. It stays compatible with Open Source extensions. It is a sensible choice for some projects, though for most UK shops plain Open Source remains the default.

When Magento earns its cost

We recommend Magento when a business ticks at least two or three of these boxes. One on its own is rarely enough.

• A large or awkward catalogue. Ten thousand products or more, configurable products with many attributes, bundles, kits, or a catalogue fed from a PIM.
• Several storefronts from one stock pool. A retail site and a trade site, two brands, or a UK store plus an EU store in euros, all managed from one admin.
• Real B2B trading. Customer-specific prices, tiered quantity breaks, account customers who pay on terms, quick order by SKU, reorder from history.
• Heavy integrations. Sage, Microsoft Dynamics, NetSuite or a warehouse management system that needs stock, orders and prices synchronised all day.
• Ongoing development budget. Magento rewards a business that keeps a developer on retainer. It punishes one that builds a site and walks away.

Picture a trade supplier in Leeds with 15,000 SKUs, separate trade and retail price lists, and stock held in an ERP. Magento’s customer groups, shared stock and API make that tidy. Doing the same in WooCommerce is possible, but it means stitching together several plugins, and the database starts to strain once order volumes climb.

When it is the wrong choice

We usually steer people away from Magento if:

• You have fewer than a couple of thousand products and one storefront.
• Your online turnover is under roughly £500k a year and you have no plans for complex B2B or multi-store selling.
• Content matters as much as products. Magento’s CMS is basic, and blogging on it is clumsy.
• You want to make most changes yourself without a developer.
• You cannot budget for maintenance every month, not just at launch.

In those cases WooCommerce is usually the better fit, and we explain why in our WooCommerce vs Magento vs PrestaShop comparison. If you want Shopify’s convenience, that is a valid choice too, with the trade-off that you rent the platform rather than own it.

What a Magento build costs in the UK

Agency quotes for Magento vary widely, and you will see anything from £10,000 to well over £100,000. The spread comes from three things: how much custom design you need, how many integrations there are, and how much data has to be migrated and cleaned.

Here is how we would price a typical mid-sized project on our hourly model. Our e-commerce development rate is £65 an hour, and blocks of 100 hours or more carry a 25 % discount, which brings it to £48.75 an hour. Prices exclude VAT at 20 %.

Those are estimates for scoping, not a fixed quote. The biggest cost swing is usually the integration with your back-office system, because the quality of its API and data is outside our control. A clean, documented API saves weeks; an old desktop accounting package that only exports CSV adds them.

Why we build on Hyvä

The default Magento front end (Luma) is heavy, and it is hard to get a Luma store to pass Core Web Vitals on a mid-range phone. Hyvä is an alternative theme built on Alpine.js and Tailwind CSS that strips out most of that weight. It became free and open source in late 2024, which removed the licence fee that used to put smaller shops off. On a new build we use Hyvä by default and aim for the same Lighthouse 95+ target we set on every other site. Some older extensions need a Hyvä compatibility module, so we check the extension list before we commit.

Hosting: where most Magento shops go wrong

Magento will not run well on cheap shared hosting. A production store needs PHP 8.x tuned for Magento, MySQL or MariaDB, OpenSearch for catalogue search, Redis for cache and sessions, Varnish for full-page caching, and ideally a CDN such as Cloudflare in front. You also want a staging server that mirrors production, so patches are tested before they go live.

These are typical market ranges in 2026, not quotes from any particular provider. The single most common performance problem we see on inherited Magento stores is not the code; it is a server without Varnish or Redis configured, or with OpenSearch starved of memory. Black Friday then exposes it.

Running costs: the three-year view

The build is the visible cost. Running it is where budgets go wrong. Adobe releases security patches for Magento several times a year, and each supported 2.4.x release has a published end-of-support date on Adobe’s lifecycle policy page. In practice each release gets around three years of security fixes, so a store you launch today will need at least one significant upgrade within that period.

Here is a worked comparison for a hypothetical UK shop turning over £600k a year online, with 4,000 products and one ERP link. Figures exclude VAT.

On those assumptions Magento costs about £16,500 more over three years. That gap is worth paying if Magento removes manual work: if your staff spend two days a week rekeying trade orders or reconciling stock between systems, automating that is worth far more than £16,500. If it does not remove work, you are paying for capacity you do not use.

Monthly support on our hourly model is straightforward. A block of 10 hours at our e-commerce rate is £650 less 5 %, so £617.50, or £741 with VAT, and unused hours never expire. You can book hours online and use them for patches, upgrades and changes as needed.

Payments, VAT and UK-specific setup

Magento handles UK VAT properly once configured: tax classes for standard, reduced and zero-rated goods, prices entered including or excluding VAT, and VAT shown correctly on invoices. A few UK points we always check:

• Payments. Stripe, Adyen, PayPal, Opayo and Worldpay all have Magento integrations. We usually recommend Stripe for a new store; its UK card fees are around 1.5 % plus 20p for standard UK cards at the time of writing, and its hosted payment fields keep your PCI DSS scope small. See our Stripe vs PayPal vs GoCardless guide for the full comparison.
• PCI DSS 4.0. Since March 2025 the standard asks merchants to control and monitor scripts on payment pages. On Magento that means a content security policy, an inventory of third-party scripts, and not loading marketing tags on checkout.
• Selling to the EU. Since Brexit, B2C sales of low-value goods into the EU usually go through the Import One-Stop Shop (IOSS), and Northern Ireland follows EU rules for goods under the Windsor Framework. Magento’s multi-store setup makes a separate euro storefront straightforward, but get your accountant to confirm your VAT position before you build it.
• Delivery. Royal Mail, DPD, Evri and ParcelForce integrations exist, usually through a shipping platform such as ShipStation or a carrier module.

Upgrading or replatforming an existing Magento store

Many UK businesses come to us with a Magento store that was built some years ago and has drifted: an old 2.4 release, a Luma theme with a dozen overrides, and extensions that nobody has updated. The choice is between an upgrade and a replatform.

Upgrade if the catalogue and business rules still need Magento, and the custom code is reasonable. A typical upgrade from an older 2.4 release to the current one, with a Hyvä front end, is a fraction of the cost of a new build.

Replatform to WooCommerce if the store is mostly simple retail and the Magento complexity is costing you more than it gives back. We have a separate guide to WooCommerce development for UK shops that covers what that build involves. Either way, the order history, customer accounts and every old URL need to come across, with 301 redirects so you keep your search rankings.

Our Magento health-check checklist

When we take over a store, this is what we look at in the first week:

1. Magento version and whether it still receives security patches.
2. PHP, MySQL, OpenSearch and Redis versions against Adobe’s system requirements.
3. Varnish and full-page cache hit rate.
4. Extension list: who maintains each one, when it was last updated, and whether it is still needed.
5. Overrides and plugins in custom modules that will break on upgrade.
6. Cron jobs and indexers, which are behind a surprising number of “stock is wrong” complaints.
7. Admin users, two-factor authentication and the admin URL.
8. Checkout scripts and their PCI DSS 4.0 status.
9. Core Web Vitals on real mobile devices, from the Chrome UX Report data in Search Console.
10. Backups, and whether anyone has ever restored one.

Our recommendation

If your business has a large catalogue, several storefronts, trade pricing or a demanding ERP link, Magento Open Source on good hosting with a Hyvä front end is a strong, long-lived platform, and we are happy to scope it. If you are a growing retailer with a few hundred or a couple of thousand products, WooCommerce will do the job for considerably less, and you can revisit Magento if you outgrow it. For businesses whose requirements fit neither, a bespoke e-commerce build is the third option.

We are based in St Albans and work with retailers across the UK, remotely or in person in London. If you want a straight answer on whether Magento suits your shop, get in touch with your product count, turnover band and the systems you need to connect, and we will tell you what we would do. Integrations are a large part of most Magento projects; our API development and integration team handles ERP, PIM and warehouse links.

Photo: Alberto Rodríguez via Unsplash