Skip to content
Available for new work
A tower of orange circuitry rising from a dark plinth. AI-generated image.AI-generated
Adobe Commerce

Magento stores, built and brought back.

Upgrades
2.4.x, patch by patch
Hyvä
Themes that load fast
Extensions
Written, or untangled
Integrations
ERP, PIM, payments

Magento 2.4.8 upgrades, and stores several versions behind

An upgrade is rarely hard because of Magento itself. It's hard because of everything installed on top of it. Each release moves the versions of PHP, the database and search it supports, and extensions written for an earlier release may not survive the jump. That is why stores sit on old versions for years: the upgrade keeps being quoted as a small job and keeps turning into a large one.

  1. List everything installed

    Every extension, its vendor, whether it is still maintained, and whether a compatible release exists. Abandoned ones are replaced or rewritten before the upgrade, not during it.

  2. Scan the custom code

    Adobe's Upgrade Compatibility Tool compares your own modules against the target version and lists what will break. It's a starting point, not a verdict.

  3. Upgrade a copy, never the live store

    The work happens on a staging copy with real catalogue data, and the checkout, account and admin paths are tested end to end.

  4. Plan the release

    A deployment that keeps the store taking orders, with a rollback ready if anything unexpected turns up in the first hours.

Being on an unsupported version doesn't mean the store stops taking orders. It means Adobe no longer ships security fixes for it, so every newly disclosed vulnerability stays open on your site. The StyleSmuggler zero-day showed how quickly that becomes real.

Hyvä theme development

Hyvä is a replacement for Magento's standard Luma frontend. Luma loads a large stack of older JavaScript libraries on every page. Hyvä swaps them for a much lighter set, Alpine.js and Tailwind CSS, so pages have far less to download before a shopper can use them.

Every extension with its own frontend needs a Hyvä-compatible version, so a Hyvä move is scoped extension by extension, like a rebuild of the frontend. I'll tell you up front what your set of extensions involves.

It's worth it when the current theme is slow and hard to change and you plan to stay on Magento for years. My own development tooling, Keel, starts new Magento projects on Hyvä by default.

Magento Open Source or Adobe Commerce

I’m DC, a freelance Magento developer. I upgrade stores that have fallen behind, move them onto Hyvä, write the custom modules a store needs, and fix the ones that have been patched until nobody wants to touch them. Both editions are the same platform at heart. I work on both. The development work is largely the same; what changes is where the store is hosted and how releases reach it.

Adobe Commerce

The licensed edition: B2B tools, the option of Adobe's own cloud hosting, and a licence fee to match.

Magento Open Source

Free to run on your own hosting.

Open SourceAdobe Commerce

If you are unsure which one you are on, the admin panel will say, and so will your last invoice from Adobe.

Magento work, by job

Custom modules, rescues, security and integrations

Upgrades and Hyvä are the most asked-for Magento jobs. These are the rest, and most stores need at least two of them.

Jump to a section
  1. Custom Magento modules, written to be owned
  2. Fixing a Magento store that has been patched for years
  3. Malware, card skimmers and security patches
  4. Magento and the systems around it
  5. Certified in three months, because the job needed it

Custom Magento modules

Custom Magento modules, written to be owned

When no extension does what the store needs, or the one that does brings ten things you don’t, a custom module is the cleaner answer. I write them to Magento’s own conventions, with tests, and hand over the code so the module is yours.

Two of my modules are public, so you can read the code before you hire me: a catalog infinite scroll module under the MIT licence, and a Page Builder hero banner slider. Both were installed and tested on a real Magento 2.4.7 store before release, because some faults never show in static checks: an admin page missing its access rule that sent even a full administrator back to the dashboard, and a layout file in the wrong folder that Magento ignored without an error.

Magento support and repairs

Fixing a Magento store that has been patched for years

Much of my Magento work is on stores I didn’t build. The common problems are a slow storefront failing Core Web Vitals, dozens of extensions that overlap, a checkout that errors for a slice of customers, and releases that break something new every time. Most stores still carry decisions made several versions ago, and knowing why they were made is most of the work of undoing them safely.

Magento security

Malware, card skimmers and security patches

I trained in digital forensics before I worked in ecommerce, and I still use those manual techniques to find malicious code injected into Magento stores, including card-skimming scripts that sit in a theme file or a database field for months without anyone noticing. Clean-ups go with the security patches that let the attacker in, so it doesn’t happen again.

Magento integrations

Magento and the systems around it

Klaviyo on Magento 2, including Hyvä stores where the standard integration needs extra work. ERP, order management and PIM connections that keep stock, prices and product data in step. Marketplaces such as Amazon and eBay through M2E Pro or a built connection, and new payment gateways. Each has its own page under Integrations.

Background

Certified in three months, because the job needed it

A small agency moved me from PHP and WordPress work straight into Magento builds and the servers underneath them. I learned the platform on live client work and passed the Magento 1 certification first time, three months in. After that I joined a multi-brand agency for the Magento 2 launch and spent years on the platform across agencies large and small.

How a Magento job starts

Scoped, priced, then built, and where I’m the wrong choice

What it covers

  • A free thirty-minute call: the version, the extensions you know about and what is going wrong
  • A £500 health check first, if you know the store underperforms but not why
  • A written scope and a price before work starts; upgrades are priced after the extension list is reviewed, because that is where the cost hides
  • Remote from North Wales, with any time on site and travel in the price before you agree it

What it does not

  • A replatform that needs a large team working in parallel from week one
  • Contracts that require an accredited Adobe Solution Partner
  • An upgrade to a store you should really be moving off, which I’ll point out rather than price

Before you ask

Magento questions

Cost

How much does a freelance Magento developer cost?

Each job is priced on its own, on the scope and the value it brings, rather than billed by the hour, and you agree the price before anything starts. The one fixed figure I publish is the entry point: a health check from £500.

Available for new work

UK based · PHP · Python · JS · TS. Every first call is free.