Core files edited
Changes made directly to controller and model files instead of through OCMOD or events, silently lost or conflicting on every update.
[ E-commerce ]
OpenCart Development Services
OpenCart stores that are fixed properly, not patched again.
OpenCart is lean and cheap to run, which is why a lot of stores have been on it for ten years. The problems usually come from that history: a stack of marketplace extensions, core files edited by hand, and a version that no longer runs cleanly on a current PHP release.
Free store review · Fixed-price upgrades · Staging copy first
3.x & 4.xOpenCart versions
Freecode and security review
Fixedprice for defined work
$20/hrfor small fixes
[ What goes wrong with OpenCart ]
Why the store keeps breaking.
Almost every OpenCart issue I am asked to fix traces back to how extensions were installed and how the core was modified.
Modification conflicts
Two OCMOD or vQmod files searching for the same line, so one fails and the modification cache was never refreshed.
PHP version errors
A 2.x or early 3.0 store throwing deprecation errors or white screens after the host moved to PHP 8.
Security gaps
Default admin path, the install folder left on the server, storage inside the web root, and extensions with known SQL injection flaws.
Outdated payment modules
Payment extensions built on deprecated PayPal or Stripe APIs that start failing when the provider retires the old endpoint.
Slow on a small server
Unindexed database tables, uncached category counts and uncompressed images making a modest catalog feel heavy.
[ How it works ]
Review, fix, verify.
01 — Days 1–3
Review
Version, PHP compatibility, installed extensions and modifications, core file changes against a clean copy, and security basics. You get a written list of what is broken, risky or slow.
02 — Week 1+
Fix on staging
Work done on a staging copy of the store with real data, core edits moved into OCMOD or events, and every change kept in Git.
03 — Go live
Deploy & verify
Deployed with a full backup ready to restore, then checkout, payments, shipping rates and admin re-tested on the live store.
[ What actually changes ]
What I work on.
I work on OpenCart 2.x, 3.0.x and 4.x, including stores that have been customized by several different developers over the years.
Development & upgrades
- Custom extensions and modules — built with OCMOD and the event system, not by editing core files, so they survive updates.
- OCMOD and vQmod fixes — conflicting modifications traced, rewritten and the modification cache rebuilt cleanly.
- OpenCart 3 to 4 upgrades — data migrated, extensions replaced or rewritten for 4.x, which packages and loads extensions differently.
- PHP 8 compatibility — older stores fixed or moved to a release that runs on a supported PHP version.
- Theme customization — Twig templates in a proper custom theme, responsive fixes and layout changes without touching the default theme.
Integrations, speed & security
- Payment gateways — Stripe, PayPal, Square, Klarna, Mollie and others, on current APIs with proper webhook handling.
- Shipping integrations — live rates and labels for UPS, FedEx, USPS, DHL, Royal Mail or Australia Post.
- Speed optimization — database indexes, caching, image compression and a CDN in front of the store.
- Security hardening — admin renamed and protected, storage moved out of the web root, files checked for injected card skimmers.
- Migration off OpenCart — to WooCommerce, Shopify, BigCommerce or Magento, with products, customers, orders and 301 redirects.
[ Example engagement ]
Core edits moved out, upgrade finally possible.
A 3.0 store with around forty hand-edited core files and several overlapping modifications. Changes moved into OCMOD and events, dead extensions removed, then updated to run on PHP 8.
Illustrative example of a typical engagement. Figures vary with the state of your systems and are not a guarantee of a specific outcome.
~40core edits moved to OCMOD
7unused extensions removed
PHP 8from an unsupported PHP 7
0.9sfaster product pages
[ Free · 48 hours ]
Get a store review.
Send me your store URL and OpenCart version. You get a written review of extensions, modifications, PHP compatibility and security, with the fixes ranked by risk.
[ Pricing ]
Straightforward pricing. $20/hour or fixed.
Tell me the number you have to work with. I'll tell you honestly what's achievable within it — and if it isn't enough, I'll say so before we start rather than halfway through.
Hourly rate $20/hoursmall jobs and ongoing work · fixed price for defined projects
Fixed project price
Scope agreed in writing, price agreed in writing, before any work starts. No hourly creep and no invoice you haven't already approved.
Monthly retainer
For ongoing work — maintenance, monitoring, updates and small changes. Month to month, cancel whenever, no minimum term.
$20/hour for small jobs
For a single bug, a short task or ongoing tweaks, where writing a full scope would cost more than simply doing the work. Billed in real time, reported in writing.
Budget too tight for the whole thing? I'll often suggest doing the highest-value part first and the rest later, rather than doing all of it badly.
[ Questions ]
Common questions.
How much does an OpenCart developer cost?
$20 an hour for small fixes, extension conflicts and hourly work, billed for time actually spent. Anything with a defined outcome — an upgrade, a migration, a speed project — gets a fixed price agreed in writing before I start, so the number does not move halfway through.
Should we upgrade from OpenCart 3 to 4?
Not automatically. OpenCart 4 changes how extensions and themes are built, so most 3.x extensions need replacing or rewriting. If your 3.0 store runs on a supported PHP version and your extensions are maintained, staying on 3.0 for now can be the sensible choice. I will tell you what the upgrade really involves before you decide.
Can you fix a white screen or error after a PHP update?
Yes, this is one of the most common requests. I turn on error logging, find the exact files failing on the new PHP version, and fix or replace them rather than rolling PHP back.
Can you build a custom extension?
Yes, for anything the marketplace does not cover well. It is built with OCMOD or events, documented, and installable through the extension installer like any other module.
Our store was hacked. Can you clean it?
Yes. I compare the files against a clean OpenCart copy, remove injected code, check the database and admin users, rotate credentials, and then close whatever let the attacker in.
Should we move off OpenCart?
Sometimes. If you keep paying for workarounds, need B2B features or want less server maintenance, Shopify or BigCommerce may cost less over time. If the store works and is maintained, staying is fine. I build on all of them, so I have no reason to push a migration.
Can you make our OpenCart store faster?
Usually by quite a lot without a redesign: database indexes, caching, image compression, fewer third-party scripts and a CDN. I measure before and after so you can see what changed.
[ Related services ]
Related e-commerce work.
Shopify DevelopmentTheme work, custom apps and checkout that converts.Magento DevelopmentUpgrades, speed, extensions and security patches for Magento 2.BigCommerce DevelopmentStencil themes, headless storefronts, apps and integrations.WordPress DevelopmentCustom themes, plugins and integrations built to be maintained.Server Security HardeningLock down SSH, firewall, patching and access before it costs you.Cloudflare SetupDNS, SSL, WAF and caching on Cloudflare, configured properly.
[ Guides on this topic ]
From the blog.
OpenCart 4 Upgrade: Moving from OpenCart 3 SafelyOpenCart 4 upgrade guide: why going from 3 to 4 is really a migration, how to audit extensions, move data, keep SEO URLs and test checkout before going live.OpenCart Hacked? Clean, Upgrade and Secure Your StoreOpenCart hacked? How I remove card skimmers and backdoors, check OCMOD modifications and the database, patch the store and lock it down so it stays clean.
[ Let's talk ]
Tell me about your store.
Send the store URL, OpenCart version and what is going wrong. You'll get a straight answer on scope, cost and timeline — same working day, from the person who'd actually fix it.