OpenCart 3 vs 4: what to know before you upgrade

Search this and you get the same hedge on every page: both have their strengths, it depends on your needs. That is not an answer. We build and maintain OpenCart stores, so here is an actual recommendation, with the reasoning, and the one number that decides it for most people: how much you have invested in your current theme and extensions.

The short answer

If you have a running OpenCart 3 store that makes money, stay on 3 for now. Specifically 3.0.4.1, which is the current stable release and runs fine on PHP 8.1 through 8.4. If you are building something new from scratch in 2026, start on OpenCart 4. The pain is entirely in the middle: moving an established 3 store to 4 is a rebuild, not an upgrade, and most stores do not have a reason to pay that cost yet.

A version jump is also the moment payment extensions tend to break, so it pairs naturally with getting your OpenCart Stripe integration onto a maintained, webhook-driven setup rather than an abandoned free module.

What actually changed in 4

OpenCart 4 is a real modernization, not a reskin. It is built for PHP 8, the admin interface was redesigned, and the extension system moved to a cleaner install format. Under the hood the folder structure and the template engine changed, which matters more than it sounds, and page loads can be a little faster out of the box. None of that is the headline, though.

The headline is that the code structure changed enough that OpenCart 3 extensions and themes do not just drop into 4. They have to be ported. That single fact drives every real decision here.

Why a working store should usually wait

An OpenCart store is rarely vanilla. It is the core plus a theme you paid for and eight to fifteen extensions, often including your payment gateways handling shipping rules, payment gateways, SEO, currency, whatever the business needs. On version 3 that ecosystem is mature: years of bug fixes, wide extension compatibility, and a forum thread for every error you will ever hit.

Move to 4 and every one of those paid extensions needs a build that supports 4, and your theme needs a 4-compatible version or a rewrite. Some vendors have ported their work. Some have not and never will. We have priced OpenCart 3-to-4 moves where the licensing and porting of extensions cost more than the rest of the project combined, because two critical extensions had no version 4 and needed custom rebuilds. You do not find that out until you audit the list, which is the first thing to do before committing to anything.

Why a new store should start on 4

The math flips completely for a fresh build. There is no existing theme to rewrite, no paid extensions to re-license, no migration risk. You pick 4-native extensions from the start, you are on a version that will get security updates for years longer, and you are not launching on an engine that is already one major version behind. Starting a brand-new store on OpenCart 3 in 2026 means planning a migration you have not even launched yet. Skip it.

If you do decide to move 3 to 4

Treat it as a project, not a button. There is no reliable one-click upgrade from 3 to 4 that survives a customized store, whatever some tools claim. The honest path is a parallel build: stand up a clean OpenCart 4 install, port or replace the theme, install the 4-compatible extensions, migrate products, customers, and orders into it, and test checkout end to end before you switch domains. Your live 3 store keeps running the whole time. It is the same disciplined cutover any migration deserves, and the database move is the easy part. The theme and extensions are where the hours go.

The version that actually matters: are you patched

Here is the thing both camps miss while arguing about 3 versus 4. The number on the box matters far less than whether anyone is keeping it updated. An unpatched OpenCart 4 is more dangerous than a maintained OpenCart 3. Ecommerce is a constant target because there are card details and customer records behind the login, and abandoned admin panels are how stores get skimmed. Whichever version you land on, someone has to own the patching.

That is most of what we do for OpenCart clients. If you are weighing the move, our OpenCart support overview lays out what we run and maintain, and the full rebuild-and-migrate path is the OpenCart modernize bundle. If your store is on a version nobody has touched in a year, an OpenCart security audit is the fastest way to find out whether it has already been compromised, and OpenCart restoration is there for when it has.

Stay on 3.0.4.1 if you are running and earning. Start on 4 if you are building new. And if you are only on OpenCart because you are weighing a jump off a hosted platform, we laid out the case for moving from Shopify to OpenCart separately. Either way, the decision that actually protects your store is keeping it patched, not the major version on the badge.

Version jumps on other platforms follow the same shape: audit first, upgrade second. If you also run Drupal, our walkthrough of the Drupal 9 to 10 upgrade covers the module traps that stall it.