Skip to main content

OpenCart Maintenance

Keep your OpenCart store running as PHP and extensions move on

OpenCart is lightweight and economical, but much of a store's functionality lives in third-party extensions and code modifications. We keep them compatible, documented and secure as PHP and hosting change.

Checkout testedStore healthy

Business impact

The hidden fragility in many OpenCart stores

Many OpenCart stores were built years ago, extended piece by piece and then left alone. They work until a host upgrade, an extension conflict or a security issue exposes how much depends on unmaintained code.

Upgrades between major versions are not drop-in

Moving between OpenCart major versions changes templates, the extension structure and the admin, so many extensions must be replaced or rewritten. Stores often stay on old versions because of this.

PHP changes break older code

Extensions written for older PHP versions can produce errors or blank pages when the host upgrades PHP, sometimes affecting only checkout or the admin area.

Modifications are easy to lose

OCMOD and vQmod patch core files at runtime. When the modification cache is cleared or an extension is reinstalled, customisations can vanish or apply twice.

Common issues

Problems we regularly solve

Modification cache conflicts

Two OCMOD or vQmod files searching for the same line of code, so one silently fails and its feature disappears after the modification cache is refreshed.

Abandoned marketplace extensions

Payment, shipping and filter extensions whose developers have stopped releasing updates, leaving no compatible version for newer PHP or OpenCart releases.

Exposed admin and install folders

Default admin paths, leftover install directories and a storage folder inside the web root, all of which make attacks easier.

Direct core file edits

Changes made straight into core controller or model files instead of through modifications, which are overwritten during upgrades.

Session and cache bloat

Session tables, cache directories and logs growing unchecked, filling disk space and slowing the store and admin.

Payment module breakage

Gateway modules failing after a provider changes its API or authentication requirements, leaving orders stuck or customers unable to pay.

What's covered

What's included in OpenCart maintenance

OpenCart maintenance is designed to make a loosely documented store predictable: every extension and modification known, compatible and recoverable.

Extension and modification inventory

Documenting every installed extension, OCMOD and vQmod file, theme override and core edit, so changes can be made without guesswork.

PHP compatibility work

Testing the store on newer PHP versions in staging and fixing or replacing incompatible extensions before the host's deadline.

Patch and version maintenance

Applying OpenCart maintenance releases and security fixes, and planning major version upgrades with extension replacement mapped out in advance.

Admin and file hardening

Renaming the admin path, removing the install folder, moving storage outside the web root where possible, enforcing strong admin credentials and correcting file permissions.

Checkout and payment testing

Regular test orders through each payment and shipping method, plus checks on order notification emails.

Backups and housekeeping

Off-site file and database backups with restore testing, along with clearing stale sessions, logs and caches.

Maintenance activities

What we do, and how often

Exact frequencies depend on your plan and platform. This is a typical schedule.

Daily

  • Off-site database backups
  • Uptime and SSL monitoring

Weekly

  • Error log review
  • File change and malware scan
  • Test order through primary checkout path

Monthly

  • Extension update review and staged updates
  • Session, cache and log clean-up
  • Admin user review
  • Maintenance report

Quarterly

  • Test restore to staging
  • PHP and hosting compatibility review
  • Upgrade path assessment

Our methodology

How we work

01

Inventory the store

We record the OpenCart version, every extension and modification, theme overrides and any direct core edits, and check them against current PHP versions.

02

Secure the basics

We harden admin access, remove leftover install files, fix permissions and set up verified off-site backups.

03

Stage every change

Extension updates and modifications are applied on a staging copy, the modification cache is refreshed and the store is tested end to end before going live.

04

Plan the road ahead

We maintain a roadmap for PHP upgrades and major version moves, so the store does not become impossible to upgrade.

Business benefits

What you gain

A documented store

You know exactly which extensions and modifications your store depends on and why.

Fewer upgrade emergencies

PHP and hosting changes are tested and prepared for well before they are forced.

A harder target

Basic hardening removes the most common weaknesses in default OpenCart installations.

A realistic upgrade path

A clear plan for future versions, including which extensions will need replacing.

Technologies supported

  • OpenCart 3.x
  • OpenCart 4.x
  • OCMOD
  • vQmod
  • Twig templates
  • OpenCart Marketplace extensions
  • PHP
  • MySQL / MariaDB
  • Apache
  • Nginx
  • cPanel

Running something not listed? Ask us – we'll tell you honestly if it's a fit.

Who it's for

Who needs OpenCart maintenance?

Small and mid-sized retailers

Businesses that chose OpenCart for its simplicity and low running costs and want to keep it that way.

Stores with heavy customisation

Shops that depend on many extensions and modifications built by different developers over several years.

Owners facing a forced PHP upgrade

Stores whose host has announced the end of an older PHP version and need compatibility work done quickly and safely.

Industry guidance: E-commerce

FAQs

OpenCart Maintenance: common questions

Which OpenCart versions do you maintain?
We maintain OpenCart 3.x and 4.x stores and can stabilise older 2.x installations while planning an upgrade. The audit tells us how close your store is to a supported, upgradeable state.
Can you upgrade our store to the latest OpenCart version?
Yes, as a separately scoped project. Major version upgrades usually involve replacing or rewriting extensions and migrating the theme, so we map those changes before giving you a plan.
What if an extension we rely on is no longer supported?
We look for a maintained alternative first. If none suits, we can patch the existing extension for compatibility, explaining the long-term trade-offs of maintaining it ourselves.
How do you test changes to OCMOD or vQmod modifications?
On staging, by refreshing the modification cache, checking the modification log for failed search operations and then testing the affected pages and checkout.
What access do you need?
A dedicated OpenCart admin account, hosting control panel access and SFTP or SSH. We avoid sharing credentials and remove our access at the end of an engagement.
Is fixing a hacked OpenCart store covered?
Malware clean-up is handled as a separate piece of work before routine maintenance starts, because it needs investigation beyond normal upkeep. See malware detection and removal.

Get a clear picture of your OpenCart store

Our free website health check reviews your OpenCart version, PHP compatibility, SSL, backups and basic security, and highlights the most urgent risks.