Magento & Adobe Commerce Maintenance
Magento rewards careful upkeep and punishes neglect
Magento 2 is powerful and complex: Composer dependencies, indexers, cron, search, caching and third-party extensions all have to work together. We keep that stack patched, consistent and documented.
Business impact
Why Magento stores need specialist maintenance
Security patches cannot wait
Magento has a history of serious vulnerabilities that attackers target to skim card details at checkout. Applying Adobe's security patches promptly is one of the most important protections a store has.
Upgrades get harder with time
Each skipped release widens the gap in PHP, OpenSearch, Composer and extension compatibility. Stores that fall well behind face a project rather than an update.
Background processes drive the storefront
Prices, stock, search results and catalogue changes depend on cron and indexers. When they stall, customers see wrong prices or missing products long before anyone reads a log.
Common issues
Problems we regularly solve
Stalled cron and invalid indexers
Cron jobs that stop running or overlap, leaving indexers marked invalid and product, price and stock changes stuck without reaching the storefront.
Search service problems
Elasticsearch or OpenSearch clusters running out of memory or disk, or version mismatches after an upgrade, breaking catalogue search and category pages.
Extension conflicts and rewrites
Third-party modules overriding the same classes through preferences and plugins, causing errors after upgrades or subtle checkout and pricing bugs.
Card-skimming injections
Malicious JavaScript inserted into the database, CMS blocks or design configuration to capture payment details, often going unnoticed for weeks.
Cache and full-page cache misses
Varnish or Redis misconfiguration, or blocks that are not cacheable, resulting in slow pages under load and high server usage.
Uncontrolled deployment practice
Changes made directly on production, missing static content deployment steps or the store left in developer mode, causing outages and slow pages.
What's covered
What's included in Magento maintenance
Security patching
Monitoring Adobe security bulletins and applying security patches and patch releases through Composer, tested on staging before production deployment.
Version upgrades
Planning and executing upgrades within Magento 2.4.x, including PHP, OpenSearch, MySQL or MariaDB, Redis and Composer requirements, plus extension compatibility.
Cron, indexer and queue health
Monitoring cron schedules, indexer status and message queue consumers, and resolving backlogs that stop catalogue and order changes flowing through.
Search and caching stack
Keeping Elasticsearch or OpenSearch, Varnish and Redis correctly sized, configured and compatible with your Magento version.
Extension management
Reviewing third-party modules for support status, known vulnerabilities and conflicts, and updating or replacing them as part of upgrade planning.
Integrity and malware checks
Scanning files and database content for injected scripts, reviewing admin users and enforcing two-factor authentication. See malware detection and removal.
Maintenance activities
What we do, and how often
Continuous
- Uptime, checkout and search availability monitoring
- Cron and indexer status monitoring
- OpenSearch or Elasticsearch cluster health checks
Daily
- Database and media backups
- Exception and system log review for new errors
- Message queue consumer checks
Monthly
- Security patch review and staging deployment
- Malware and injected-script scan
- Admin user and integration token review
- Maintenance report
Quarterly
- Upgrade path and PHP compatibility review
- Extension compatibility and support status audit
- Test restore and performance baseline review
Our methodology
How we work
- 1
Audit code and infrastructure
We review the Magento version, Composer dependencies, custom and third-party modules, core modifications, server stack and deployment process.
- 2
Establish a deployment pipeline
Changes move through version control and a staging environment, with a repeatable sequence of composer install, setup:upgrade, di:compile and static content deployment.
- 3
Patch and test on staging
Patches and upgrades are tested against catalogue, search, cart, checkout, payment and admin workflows before production.
- 4
Deploy with minimal downtime
Production deployments use maintenance mode for as short a window as possible, scheduled for low-traffic periods, with backups and a rollback route ready.
- 5
Monitor and plan ahead
Post-deployment checks, ongoing background process monitoring and a forward plan for the next upgrade keep the store from falling behind again.
Business benefits
What you gain
Patched promptly
Security patches are tracked and scheduled as soon as they are released, reducing the window in which your store is exposed.
Accurate storefront data
Healthy cron and indexers mean price, stock and catalogue changes reach customers when they should.
Upgrades as routine, not projects
Keeping close to current releases helps keep each upgrade smaller and more predictable.
Repeatable deployments
A documented deployment process reduces downtime and the risk of human error during releases.
Better performance under load
Correctly configured Varnish, Redis and search services help the store stay responsive during campaigns.
Technologies supported
- Magento Open Source
- Adobe Commerce
- Composer
- OpenSearch
- Elasticsearch
- Varnish
- Redis
- RabbitMQ
- PHP-FPM
- MySQL / MariaDB
- Nginx
- Magento CLI
- Git
Running something not listed? Ask us – we'll tell you honestly if it's a fit.
Who it's for
Who needs Magento maintenance?
Mid-market and enterprise retailers
Stores with large catalogues, multiple store views or complex pricing that need specialist Magento knowledge.
B2B merchants
Businesses using company accounts, quotes, shared catalogues and ERP integrations on Adobe Commerce.
Stores inherited from another agency
Retailers who have lost their original developer and need someone to take ownership of an unfamiliar codebase.
Magento 1 stores
Businesses still on an end-of-life Magento 1 installation who need to reduce risk while planning a replacement platform.
Industry guidance: E-commerce
Related services
Often combined with
Security Patch Management
Tracked, tested and staged security updates for operating systems, CMS platforms, plugins and libraries, with CVE monitoring and rollback plans.
Learn moreServer Performance Optimisation
Tuning PHP-FPM, Nginx, Apache or LiteSpeed, OPcache and MySQL so your server generates pages quickly and stays stable when traffic rises.
Learn moreDatabase Optimisation
Slow query analysis, indexing, table clean-up and configuration tuning for MySQL and MariaDB databases behind websites, stores and applications.
Learn moreWebsite Migration
Planned hosting, domain and platform migrations with redirect mapping, DNS and email continuity, data validation and a tested rollback plan.
Learn moreFAQs
Magento Maintenance: common questions
Do you support both Magento Open Source and Adobe Commerce?
How quickly are Magento security patches applied?
What access do you need?
We are on Magento 1. Can you still help?
Are version upgrades included in maintenance?
Do you need to put the store into maintenance mode?
Where can I read more about common Magento issues?
Know exactly how far behind your Magento store is
Request a technical audit covering your Magento version, outstanding patches, extensions, cron and indexers, search and caching configuration.