MagentoMenzzo
Furniture and home décor retail in Europe: a Magento platform connected to the business tools.
See our projectsMagento maintenance · Support · Adobe Commerce
Magento maintenance and support: a stable, secure store that keeps improving
Security patches, Magento 2 updates, bug fixes, feed monitoring and improvements: AXELITES provides maintenance and application support for your Magento Open Source, Adobe Commerce or MageOS store. A team that knows your catalogue and integrations, a shared tracking tool and a report every month.
A store that sells every day, securely
- 2012AXELITES founded
- 300+Projects delivered since 2012
- 3Editions: Open Source, Adobe Commerce, MageOS
- 1Point of contact and a report every month
Everything we take care of on your Magento store:
- Security patches
- 2.4 version upgrades
- Extension compatibility
- Bug fixes
- Support for your teams
- Monitoring and alerts
- Tested backups
- Performance and caching
- ERP, PIM and CRM feeds
- Payment and shipping
- Improvements and modules
- Monthly reporting
A Magento store cannot be maintained one ticket at a time.
Magento is a rich platform: dozens of extensions, scheduled tasks, a search engine, several caches and feeds to your business tools. Every security patch or version upgrade affects all of it. Our Magento maintenance takes care of everything that keeps the store running, with every change tested in a staging environment before production.
Ad hoc maintenance
- Security patches applied months late
- Extensions never updated, blocking the next release
- Fixes made directly in production
- ERP feeds that fail without anyone being alerted
- A provider who rediscovers the store at every incident
AXELITES Magento maintenance
- Security patches tracked, tested, then applied
- Extensions and dependencies kept current, upgrades planned
- Every change validated in staging, with a rollback plan
- Feeds, scheduled tasks and payments monitored
- A team that knows your catalogue, modules and integrations
What Magento maintenance covers for your store
Corrective, preventive and adaptive: Magento maintenance brings the three forms of maintenance together in one contract, with a team that knows your installation.
Corrective maintenance and support
A declined payment, a stuck order, a failed import: we reproduce the issue, measure its impact on sales, fix the root cause and document the intervention.
- Priority set by the impact on orders
- Diagnosis in the logs and the code
- Fix tested before production
- Help for your teams with the Magento admin
Security and Magento patches
We track the security patches released by Adobe and the versions of every component the store runs on. Each patch goes through staging first.
- Monitoring of Adobe security patches
- PHP, MySQL, OpenSearch and dependencies kept current
- Admin access and two-factor authentication reviewed
- Extensions and third-party scripts checked
Updates and version upgrades
Moving to a new 2.4 release affects the theme, extensions and custom modules. We check compatibility, adapt the code and replay the purchase journeys.
- Extension compatibility analysis
- Theme and custom module adaptation
- Catalogue, cart and checkout testing
- Scheduling outside peak trading periods
Improvements and development
A new payment method, a B2B pricing rule, a custom module or a Hyvä theme: your improvements are estimated, prioritized with you and delivered within the same framework as maintenance.
- An estimate before every improvement
- Custom Magento modules
- Amasty, Mageplaza… extension installs
- Hyvä integration and checkout
Integrations and business feeds
Stock, prices, orders and customers move between Magento and your ERP, PIM or CRM. We monitor these exchanges, handle errors and keep the connectors up to date.
- ERP: Sage X3, Divalto, SAP…
- Akeneo PIM and product data
- Payment, carriers and marketplaces
- Alerts when a synchronization fails
Performance, backups and hosting
Cache, indexes, scheduled tasks, search engine and server: we keep the store fast and available, and get it ready for sales and Black Friday peaks.
- Varnish, Redis and indexing checked
- Core Web Vitals tracked
- Verified, restorable backups
- Capacity reviewed before traffic peaks
From the first report to production, every change follows the same path
Whether a request comes from your customer service, a monitoring alert or a new need, it is tracked, qualified and validated before it reaches your customers.
Report
Your teams report an issue in the shared tracking tool, by email or by phone. A monitoring alert also opens a request.
Handled by: SupportQualification
We reproduce the problem and set its priority by impact: sales stopped, a degraded feature or a minor inconvenience.
Handled by: ManagementFix
The fix is developed on a copy of the store, never directly in production. The code is versioned and belongs to you.
Handled by: DevelopmentAcceptance
We replay the affected journeys: search, product page, cart, checkout and customer account. Your teams then sign off.
Handled by: QualityRelease
Backup first, a controlled deployment, caches flushed and indexes rebuilt when needed, with a rollback ready.
Handled by: SecurityFollow-up and reporting
The intervention joins the store’s history. The monthly report sums up requests, applied patches and the next priorities.
Handled by: Reporting
Priorities set by the impact on your sales
Not every request is equally urgent. These levels are the starting point: the response times attached to them are set in your contract, according to your trading hours.
Swipe to see more
| Criteria | CriticalSales have stopped | MajorA key feature is degraded | MinorLimited impact, workaround available | ImprovementA new need |
|---|---|---|---|---|
| Examples | Payment impossible, checkout error, store unreachable | Search or filters down, stock import failing, order emails stuck | Display glitch, wrong label, occasional admin slowness | New shipping method, pricing rule, module or page to build |
| Handling | Immediate response within agreed hours, fix or workaround as top priority | Fix scheduled as a priority after qualification | Fix bundled into a scheduled release | Estimate, your approval, then scheduling |
| Communication | Status updates until recovery, then a root-cause analysis | Tracked in the shared tool with an announced release date | Visible in the tracking tool and the monthly report | Costing sent before any work starts |
Pricing model: monthly retainer, bundle of hours or dedicated team, chosen according to the volume of requests and the pace of improvements. You remain the owner of the code, access and documentation. Request a proposal
Why maintaining a Magento store cannot wait
A Magento store relies on a stack of components: the Magento core, vendor extensions, custom modules, PHP, a MySQL database, an OpenSearch engine, caches and scheduled tasks. Each one evolves at its own pace. Without maintenance, the gap widens until an update turns into a project, or a known vulnerability stays open on a site that takes payments.
Adobe regularly releases security patches for the 2.4 versions still supported, and every version has an end-of-support date. If you take card payments, the PCI DSS standard also requires critical patches to be installed promptly. Preventive maintenance therefore avoids two risks: a security incident, and the technical debt that makes every improvement more expensive.
- A vulnerability exploited on an unpatched version
- An abandoned extension that blocks the next upgrade
- Payments or an ERP feed broken by an untested update
- A store slowed down by a poorly maintained cache or indexes
Magento 2 security patches and upgrades: our method
We distinguish three kinds of work. An isolated security patch fixes a vulnerability without changing the functional version: it is applied soon after release. A patch release (for example from 2.4.7-p1 to 2.4.7-p2) bundles security fixes and corrections. A version upgrade (from 2.4.6 to 2.4.7, for example) changes the compatible components and needs proper preparation.
In every case, the work starts in a staging environment: compatibility of extensions and custom modules, testing of purchase journeys, checks on business feeds. The production release is scheduled outside sales peaks, preceded by a backup, with a rollback procedure.
Taking over the maintenance of an existing Magento store
Was your store built by another agency, or has your provider stopped responding? A takeover starts with an audit: Magento version and edition, theme, extensions and licences, custom modules, hosting, access and deployment procedures. We identify overdue patches, weak spots and what needs stabilizing first.
For a smooth handover, gather these items before our first conversation if you can:
- Access to the admin, the server and the code repository
- The list of installed extensions and their licences
- Documentation of custom developments and feeds
- Known incidents and pending improvements
How much does Magento store maintenance cost?
The cost of Magento maintenance depends less on catalogue size than on how complex the installation is: number of extensions and custom modules, ERP or PIM integrations, starting version, volume of requests and the availability you expect. An up-to-date, documented store costs less to maintain than one several versions behind.
Three pricing models are available: a monthly retainer for a recurring volume of requests and checks, a bundle of hours used as needed, or a dedicated team when improvements are frequent. The proposal sets out the scope, priority levels, support hours and what remains out of scope: licences, hosting and third-party services.
The takeover audit prices any catch-up work separately. You can then tell one-off remediation, such as overdue patches or an extension to replace, apart from the monthly care of the store.
A Magento team between Paris and Tunis
Your store is looked after by an AXELITES team bringing together a project manager, back-end and front-end Magento developers, and operations skills. Project management relies on our Paris office and delivery on our Tunis office, zero to one hour from Paris time, working in French and English.
This nearshore model keeps people available during your teams’ working hours while keeping maintenance costs under control. The same team can also handle hosting, integrations and new projects, without multiplying providers.
Why entrust your Magento maintenance to AXELITES
One Magento team, from build to maintenance
The developers who maintain your store also build, migrate and integrate Magento stores. A major improvement does not force you to change provider.
Open Source, Adobe Commerce and MageOS
We work on all three editions and check, for each one, the versions, the services in use and how responsibilities are shared with the host and vendors.
Your integrations taken into account
ERP, PIM, CRM, payment, carriers: every fix is tested against the feeds that connect the store to your back office, not just the storefront.
Ownership and reversibility
The code, access and documentation belong to you. They are kept current during maintenance, which makes any future handover easier.
How we move forward together
Audit the store
Version, edition, extensions, custom modules, hosting and feeds: a written assessment, with the risks and the overdue patches.
Bring it up to date
Missing security patches, incompatible extensions, backups and monitoring: the store gets back on a healthy footing, priced separately.
Set up support
Tracking tool, priority levels, support hours, staging environment and points of contact are set up with you.
Maintain and improve
Fixes, updates, monthly checks and improvements continue within the same framework, with a report every month.
A takeover audit, a written scope and agreed priorities before the first intervention.
Every month
What we check on your Magento store.
A store can look fine while an index is out of date, a scheduled task keeps failing or a security patch has been waiting for weeks. These regular checks are part of our Magento maintenance and appear in the report, with the actions to plan.
- Available and applied security patches
- Scheduled tasks (cron), indexes and message queues
- Backups and restore tests
- Outdated extensions or ones abandoned by their vendor
- Response times, cache and disk space
The Magento stack we maintain
Editions, theme and the components every store depends on. Our Magento agency page presents the full expertise, from build to migration.
- Magento Open Source
- Adobe Commerce
- MageOS
- Hyvä
- PHP
- MySQL
- OpenSearch
- Redis
- Varnish
MagentoYour questions, our answers
Practical answers to help you make the right decisions before starting your project.
Discuss my projectMagento application maintenance means entrusting a provider with keeping a Magento store in good working order and improving it: bug fixes, security patches, updates, monitoring and new features. It is organized around a written scope, priority levels and regular reporting, rather than one-off interventions.
It sets out the scope covered (fixes, security, updates, improvements), priority levels and support hours, regular checks, reporting and the chosen pricing model. It also separates what depends on third parties: extension licences, the hosting provider or the vendors of connected software.
Corrective maintenance deals with issues that have occurred. Preventive maintenance anticipates: security patches, updates, backup and performance checks. Adaptive maintenance adds or changes features. Complete Magento maintenance brings all three together within one framework.
As soon as Adobe releases a patch that affects your version, after it has gone through staging. Critical patches are handled first, and version upgrades are planned so that you stay on a supported release. A store that takes card payments must also meet PCI DSS requirements on patching.
Yes. We start with an audit of the code, extensions, hosting and access, then define the takeover conditions and priority fixes. The handover should include environments, technical accounts and available documentation; if anything is missing, the audit flags it.
Yes. Maintenance covers Magento Open Source, Adobe Commerce and MageOS, a community distribution derived from Magento Open Source. For each store we check the versions, the services in use and how responsibilities are shared with Adobe, the host and extension vendors.
The price depends on the number of extensions and custom modules, integrations, the starting version, the volume of requests and support hours. After the takeover audit, we propose a pricing model (monthly retainer, bundle of hours or dedicated team) with a written estimate and a detailed scope.
They depend on the priority level: a store whose checkout has stopped working does not wait like a display glitch. Response times per level, covered hours and alert channels are written into the contract, according to your trading hours and key sales periods.
It can. We work on your existing hosting or offer managed hosting suited to Magento: caching, search engine, backups and monitoring. The contract states who does what between AXELITES, the hosting provider and your teams.
You remain the owner of the code, access and documentation, kept current during maintenance. A handover to another team relies on these items: the code repository, the list of extensions and their licences, deployment procedures and the history of interventions.
Let’s talk about your Magento store’s maintenance
Tell us your Magento version, your main extensions and the current pain points: we will propose a takeover audit and a suitable pricing model.