Codewerk.
Get a quote

// Growth · Care

Keep your shop healthy and selling

Ongoing maintenance and support — monitoring, updates, backups, security and fast fixes — so your shop stays online and earning.

// What you get

What a maintenance plan covers

Monitoring & uptime

We watch availability and errors so problems are caught early.

Updates

Regular, tested core, plugin and composer updates on staging first.

Backups

Automated backups and a tested restore path for peace of mind.

Security

Security patches and hardening to protect shop and customer data.

Priority fixes

Fast response and fixes when something goes wrong in production.

Small changes

A monthly budget for the small adjustments every shop needs.

// Why it matters

A shop is never finished

An online shop needs ongoing care — updates, security, backups, monitoring and the steady stream of small changes every business needs. Codewerk Solutions offers Shopware maintenance and support on a clear monthly plan: we keep your shop updated, secure and backed up, watch for problems, and respond fast when something breaks.

Instead of scrambling when something goes wrong, you have a partner who already knows your shop and keeps it running — so you can focus on selling, not firefighting.

// In detail

Technology, performance and SEO

What we actually do under the hood — so you can judge the work, not just the promise.

Technology & architecture

A maintenance plan covers Shopware and plugin updates, PHP and dependency patches, backup verification (a backup you have never restored is a wish, not a backup), and a documented runbook so anyone on the team can act during an incident.

Monitoring & alerting

We alert on the only question that matters: are orders still being placed? Orders per hour compared to the same hour last week catches more real outages than every CPU graph combined. Every outbound integration gets its own heartbeat, because your ERP fails more often than your shop does.

Security & access

We track Shopware security advisories and plugin CVEs, apply critical patches out of cycle, keep an inventory of the exact versions you run, and check certificate expiry from outside — including on the API, staging and mail server, not just the shop.

// FAQ

Frequently asked questions

It depends on the plan. For a shop that is down, we agree a same-business-day response and usually much faster for flagged emergencies. The SLA is written down, not implied.

Yes, after a paid review of code, database, plugins and hosting. You get a written report with risks and a prioritised plan first — sometimes the honest recommendation is to fix three things before signing anything ongoing.

Updates, security patches, monitoring, backup verification and a defined number of support hours, reported transparently. Development of new features is quoted separately so the maintenance fee stays predictable.

It scales with what you actually run, not with your revenue. A lean shop on a current version with five well-known plugins is cheap to keep healthy. Thirty plugins, two of them abandoned by their vendor, plus a custom theme and an ERP integration, costs a multiple of that — because every update becomes a test cycle. We price it after the review, when we know which shop you have.

Security patches: as soon as they appear, out of cycle when the advisory is serious. Everything else: on a rhythm, roughly monthly, always on staging first. The dangerous strategy is the one that feels safest — never updating. Skip two years and you are no longer doing an update, you are doing a migration, at many times the cost and with plugins that no longer exist.

Ad-hoc work is possible, and for a small, stable shop it can be the rational choice — we would rather say that than sell you a plan you do not need. The trade-off is real: without a contract you queue behind the customers who have one, and nobody is watching your shop, so you hear about an outage from a customer instead of from us.

By email, to one address the whole team sees — that is our only support channel. It becomes a ticket with a timestamp, and urgent cases are flagged as such. We dropped phone and messenger support on purpose: a call leaves no trace, carries one person's version of the problem, and cannot be handed to whoever picks it up next. Written means reproducible.

Let's talk about your project

Send a short brief — we reply within one business day.