Shopware maintenance: updated every month, every update measured
A webshop does not become slow or vulnerable overnight. It happens update by update, plugin by plugin, image by image. With our maintenance package we keep Shopware and your plugins up to date every month, measure what every update does to your shop, and tell you each month what changed and what could be better.
.png)
Why a webshop wears down
At go-live a Shopware webshop is as good as it will ever be: everything has just been tested, the versions are current and the speed has been measured. Then the wear begins. Shopware ships a new version almost every month, plugins get updates, marketing adds new banners and a script arrives for a campaign. Each change is small. Added together, they decide whether your shop is still as fast and secure a year from now as on launch day.
What we see most often is postponement. An update gets pushed back because it is busy, then another, until a year of versions sits between the shop and the current Shopware. At that point updating is no longer routine but a project with risk. And because nobody measures what happens in between, nobody notices that the product page has slowly become half a second slower on mobile.
Our maintenance package turns that around. Update every month, measure after every update, and have one conversation each month about what we saw. That keeps your shop current, and it gives you something most webshops lack: a fixed moment when someone takes a critical look at your shop.
What happens every month
Updating Shopware
Every month to the latest release within your major version, so you get security updates and improvements straight away.
Updating plugins
All installed plugins move along, so they keep working with the new Shopware version.
Measuring after every update
After every update we check RUMvision and Tideways: what your visitor notices, what the server does.
Continuous monitoring
Between updates we also keep an eye on the speed and technical behaviour of your shop.
Monthly report
At least once a month you hear what changed and what we saw.
A concrete improvement proposal
Every month a proposal to make your shop better. If there is nothing to improve, we tell you that too.
One fixed amount
€750 per month, excluding VAT. You know in advance what maintenance costs you.
What we come across in practice
Monthly measuring mostly surfaces things nobody caused on purpose. A few examples of what we find in webshops:
Oversized uploaded images. A new banner or product photo is uploaded straight from the camera or design tool, several megabytes in size. The page looks fine in the office, but on mobile your visitor waits for an image many times heavier than it needs to be. RUMvision shows on which pages the load time of the largest element is climbing; after that the cause is usually found quickly.
Plugin processes that ask too much. A plugin that runs an extra query on every page view, or a background job that keeps the database busy at night while your international customers are still ordering. Tideways shows per transaction which query, template or plugin is eating the time, and therefore where we need to step in.
An update that quietly slows your shop down. Most updates make your shop better. Sometimes a new plugin version makes one page slower. Because we check RUMvision and Tideways after every update, you see it within hours rather than weeks later in Google Search Console.
Versions falling behind. The longer an update waits, the bigger the jump becomes and the longer known security issues stay open. Updating monthly keeps every step small.
More on the speed thieves we find most often and how to track them down is on Making your webshop faster and keeping it fast.
.png)
Why monthly, and not once a year
Shopware works with small, regular releases within a major version, and a new major version roughly once a year or less. The next major version, Shopware 6.8, is planned for 2027 according to Shopware's roadmap. If you move along every month, you take small steps whose effect is easy to measure. If you wait a year, you get all the changes at once and can no longer tell which one caused a problem.
Your plugins follow the same cycle. A plugin three versions behind is harder to update than one that always runs the latest version. Monthly maintenance stops maintenance from piling up into a migration. How a bigger jump, such as from 6.6 to 6.7 or to 6.8 later on, is handled is explained on Updating and upgrading Shopware.
What it costs and which conditions apply
The maintenance package costs €750 per month, excluding VAT. For that we update Shopware and your installed plugins every month, monitor your shop with RUMvision and Tideways, check the data in both tools after every update, and send you an overview of the changes with an improvement proposal at least once a month.
The most important condition: your shop runs on the latest Shopware version. The package is designed to keep you current, not to catch up a backlog. If your shop is behind, we first bring it up to date in a separate project with its own quote. Then the monthly rhythm starts. That way you pay for catching up once, and the package holds from then on.
What is not in the package: new functionality. Maintenance keeps your existing shop current, fast and secure. A new integration, an extra sales channel or a redesigned checkout is further development, which we discuss and estimate separately. The monthly improvement proposal can be the reason to start it.
Also separate: moving to a new major version. The monthly updates within your major version are in the package. Moving to a new major version, such as Shopware 6.8 in 2027, takes more work on plugins and custom code, and we estimate that separately per client. That way you know in advance what the step costs, and the monthly price stays the same. How such an upgrade runs is explained on Updating and upgrading Shopware.
Why we always show maintenance and development as two separate items is explained on the costs page.
Proof: why Memo can do this
We measure every update with two tools. Memo is a partner of RUMvision and Tideways, and the maintenance package uses both. RUMvision shows what your real visitors experience, Tideways what happens inside the application. With every update we see the impact on page speed and on technical behaviour, on a single timeline. How that measurement around a release works is described in our blog on release monitoring with RUMvision and Tideways.
Measuring first works. For Kempers.de we tackled performance without migrating the shop, together with hosting partner Hypernode. After those changes the load time was three times faster. Read the Memo and Hypernode case study.
We keep our own extensions current with every new version. As a Shopware Extension Partner we have six extensions in the official Shopware Store, including the official PostNL plugin for Shopware 6. They have to keep working with every new Shopware version, in shops we have never seen. We apply the same discipline to your shop. More on how we build plugins that survive updates is on plugin and extension development.
For the full picture of what Memo does around Shopware, see the Shopware hub.
Is your shop running the latest Shopware version?
Book an introduction and tell us which version and which plugins you run today. We will let you know whether you can join the maintenance package straight away, or what needs to happen first.
Frequently asked questions
What does webshop maintenance involve?
In our maintenance package it means we update Shopware and all installed plugins to the latest release within your major version every month, monitor your shop continuously with RUMvision and Tideways, check after every update what that update did, and tell you at least once a month what changed, with a concrete improvement proposal.
What does maintaining a Shopware webshop cost?
The maintenance package costs €750 per month, excluding VAT. New functionality and the move to a new major version are not included: we estimate those separately. The costs page explains how maintenance and development relate to the build cost.
My shop is not on the latest Shopware version. Can I still join?
Yes, but not straight away. The condition for the package is that your shop runs on the latest Shopware version. If it is behind, we first update it in a separate project with its own quote. Then monthly maintenance starts. How such a project runs is described on Updating and upgrading Shopware.
What happens if an update makes my shop slower?
We see it quickly, because we check the data in RUMvision and Tideways after every update. Tideways compares performance after a release with the period before it, and RUMvision shows what real visitors experience. If the update is the cause, we fix it or roll it back before it costs you weeks of conversion.
What is the difference between maintenance and development?
Maintenance keeps your existing shop current, fast and secure: updates, monitoring and fixing what we find along the way. Development adds something new, such as an integration, a sales channel or a new feature. The first is in the package, the second we discuss separately, often prompted by the monthly improvement proposal.