Magento and Adobe Commerce support and maintenance.

Senior engineers answerable for your store every month, ad hoc or on a retainer.

Support and maintenance for Magento Open Source, Adobe Commerce and Mage-OS stores: fixes, small changes, patching, housekeeping and advice from senior engineers. For merchants of every size who want someone answerable for the store. Work with us ad hoc, invoiced at the end of each month, or on a monthly retainer.

For
Trading Magento stores that need someone answerable every month
What it is
Fixes, changes, patching and advice from senior engineers
Price
Ad hoc, invoiced monthly, or a set monthly retainer
First step
The free health check, then we agree what the store needs

Is support at your store like this?

The three complaints we hear most from merchants changing support provider.

  • We pay a monthly retainer and still get a quote every time something breaks.

    What it usually means

    That retainer buys availability, not work. Ours is spent on the work your store needs, and the invoice shows you each piece of it.

  • When the store went down on a Saturday, it took until Tuesday to get an answer.

    What it usually means

    Nobody agreed a response time for a store that cannot take orders. It belongs in writing, before you sign.

  • We have no idea whether anyone is patching the store.

    What it usually means

    Housekeeping is invisible until it is missed. Patches and checks should be reported to you like any other work.

What support covers.

Anything the store needs from a senior engineer, month in, month out.

  • Requests triaged on arrival

    A store that cannot take orders comes first; most other requests are answered the same morning.

  • Fixes and small changes

    Bugs, errors, payment methods misbehaving, stopped imports, banners due by Friday.

  • Patching and housekeeping

    Adobe patches, PHP and packages in support, indexers, cron, backups, disk and logs.

  • A senior engineer to ask

    An extension you are being sold, a quote from someone else, a log line you cannot read.

  • Uptime and error alerting

    Where in scope, alerts for downtime and the errors that precede it, read by an engineer.

  • One itemised invoice a month

    Each piece of work listed with its own price, and a note of what we recommend next.

The same store, with and without us.

Without us
  • A retainer fee, and a separate quote for every fix
  • No answer when the store is down at the weekend
  • Patching left until someone asks
  • Invoices you cannot trace to work
  • A new freelancer each time, learning the store again
  • Notice periods that make leaving hard
With Refined Commerce
  • A retainer spent on the work your store needs
  • Email support every day of the year
  • Patches and housekeeping done and reported
  • An invoice that lists each piece of work
  • The same senior engineers, who know the store
  • Ad hoc or monthly, with fair notice in writing

How a month of support works.

Agreed once, then simple: you ask, we do, and the invoice lists it.

  1. Step 1: The free health check

    Send us the store address. A senior engineer reads its release, support status, PHP, headers, hosting and any sign of a hijack.

    Within two working days
    Access we need
    None. Publicly served pages only; nothing is tested.
    What you receive
    One page by email, with no obligation.
  2. Step 2: We look at the store, then agree the arrangement

    Release, hosting, integrations and how often things change tell us what the store needs. We suggest ad hoc or a retainer, and you choose.

    Before anything is agreed
    Access we need
    Read access to the repository, server and an admin account.
    What you receive
    A written proposal you can adjust.
  3. Step 3: You email us; we raise things too

    Anything you need comes to us by email. Patches, housekeeping and anything we spot in the logs are raised with you in the same way.

    Every day of the year
    Access we need
    Deployment access to staging and live.
    What you receive
    A reply, normally the same morning, with a time for the work.
  4. Step 4: The work is done on staging first

    Where a task touches code it is done and tested on a copy of the store, then deployed at a suitable time.

    In order of priority
    What you receive
    Written confirmation when each request is finished.
  5. Step 5: One invoice at the end of the month

    Each piece of work listed with its own price, with what we recommend for the month ahead.

    Monthly
    What you receive
    One itemised invoice.

Do we need support, a security retainer, or both?

Three ways to have us answerable for your store each month. They fit together, and we will tell you plainly which you need.

  • Support and maintenance

    Fixes, changes, patching, housekeeping and advice from senior engineers, ad hoc or on a monthly retainer.

    • Requests triaged on arrival
    • Email support every day of the year
    • One itemised invoice a month
    • Ad hoc or a monthly retainer
    This page
  • Security retainer

    Monitoring, patching within an agreed window of each Adobe security release, a hardened edge and incident response.

    • Every Adobe bulletin read on the day
    • Monitoring a person reads
    • Incident response included
    • A set monthly figure
    About the security retainer
  • Both together

    The security retainer keeps the store patched and watched; support keeps everything else moving. One invoice and one point of contact.

    • The right choice for most trading stores
    • Proposed together, in writing
    Ask us which fits

We price the work, not the clock.

This service
A set monthly figure, agreed once we have examined the store.
How you pay
Monthly, with one itemised invoice.
Our rate
£80 an hour plus VAT, the same for every merchant.
Never charged
Account management, or the first look at your store.

Ad hoc or a monthly retainer: your choice.

We are flexible about how you pay. Work with us ad hoc and everything you ask for in a month is itemised on one invoice at the end of it, then the next month starts afresh. Or agree a monthly maintenance retainer, a development retainer or both, sized to the store once we have looked at it. There is no account-management fee either way.

  • Ad hoc: pay only for what you ask for
  • Retainer: a set monthly figure and priority
  • Change from one to the other as the store changes
What happens first
  1. We move any open issues into a list and agree the order with you.
  2. Release, patch level, cron and indexers are checked, and anything urgent is raised.
  3. You get a short written list of what we would look at first.
How our pricing works

Proof, from real stores.

Supadance: a category page of the live store on desktop
Supadance on a phone
Dance shoes, handmade in EnglandMagento 2 and Hyvä

Supadance

Design and Hyvä build for a British dance-shoe maker selling worldwide, with ongoing development and support.

Passes Core Web Vitals on mobile
  • LCP1.3 s
  • INP112 ms
  • CLS0.01

Core Web Vitals, real-user data (Chrome UX Report), mobile, 28 days to 31st October 2026. Marks show Google's thresholds.

Rowan built our new web site a short while ago, and has helped with the any upgrades and issues since, he's always quick to respond and gives a clear message without technical jargon. Highly Recommended Magento Web site developer.

Andrew ErringtonGoogle review

Is this the right service for your store?

This is for you if

  • Your Magento store trades every day, whatever its size
  • You want quick answers from people who know the store
  • You would rather have one senior team than a series of freelancers
  • You are on Magento Open Source, Adobe Commerce, Mage-OS or Magento 1

If your situation is different

Why merchants bring this work to us.

About Refined Commerce
  • 2008

    On Magento since its early releases

    Decades of collective experience across Magento 1, Magento 2, Adobe Commerce, Hyvä and Shopify. Very little about your store will be new to us.

  • 1

    Point of contact, and senior engineers only

    You deal directly with the founder. No juniors learning on your store and no account managers between you and the people doing the work.

  • 5.0

    On Google, from 23 merchant reviews

    Small stores and large ones, described in their owners' words. The reviews are quoted on this site word for word.

Questions merchants ask about this.

What does a Magento support retainer include?

Fixes, small changes, security patching, housekeeping and advice from senior engineers, for a set monthly figure agreed once we have looked at the store. A quiet catalogue and a busy multi-store estate need different things, so the retainer is sized to yours and reviewed as the store changes.

Do we have to take a retainer?

No. Many merchants work with us ad hoc: you ask for what you need, and everything requested that month is itemised on one invoice at the end of it. Some months that is a little, others more. A retainer suits stores that change every month and want priority; ad hoc suits stores that mostly need us now and then.

How quickly do you respond?

Support is by email, every day of the year. Each request is triaged on arrival: a problem that stops the store trading is dealt with first, normally the same day, and most other requests get a reply the same morning with a time agreed for the work.

What happens out of hours?

A critical fault out of hours goes to your host's 24-hour team, who can restore service at the server, with us copied in. We pick it up as soon as we see it, which in practice is usually straight away.

Is this the same as the security retainer?

No, though they fit together. The security retainer covers patching within an agreed window, monitoring, a hardened edge and incident response. Support covers everything else the store needs month to month. Many merchants have both; we will say which you need.

How do we see what was done?

Every request is confirmed in writing when it is finished, and the monthly invoice lists each piece of work with its own price. Nothing appears on an invoice that you did not ask for or agree to.

Do we have to be on a supported release?

No. We support stores on unsupported releases, Magento 1 included, and many come to us that way. We are straight about what it means: Adobe no longer ships fixes, so security patches have to be backported, and the upgrade belongs on a dated plan.

Can you take over support from another agency?

Yes, and most of our clients came to us that way. We start with a read-only look at the code, the hosting and the patch level, tell you in writing what we found, and agree the handover with you and, where it helps, with the outgoing agency.

Can we leave?

Yes. The notice period is in the written agreement, the code is in your repository and the hosting is in your name. We would rather keep you by being useful than by making it difficult to go.

See where the store stands before you decide on support.

Give us the address and we will read what the store already shows the world: release, support status, PHP, headers, hosting and any sign of a hijack. One page, by email, within two working days. Nothing is accessed or tested.

  • Magento Open Source, Adobe Commerce and Mage-OS stores
  • No login, no access, no obligation
  • Written by a person, not a scanner
Free store health checkOne page, by email

5.0 from 23 Google reviews

Free, with no obligation. We read only what your store serves publicly; nothing is accessed or tested, and it is not a security guarantee. Privacy notice.
What you receive
Example report
Magento Security and Upgrade Health Check
example-store.co.ukNeeds attention
Platform
Magento Open Source 2.4.4-p3
Adobe support
ended 12th April 2025
PHP
8.1, end of life 31st Dec 2025
Frontend
Luma
Security headers
2 of 6 present
Hijack indicators
none found

What we would do first. Apply the outstanding security fixes, then plan the upgrade to a supported release.

Free health check