Quick answer: If your Zen Cart store is still on version 1.5.x, upgrading to Zen Cart 2.2.x is the best way to run on a modern, supported PHP, get the bundled PayPal REST integration and close known security gaps. Zen Cart 2.2.x is designed for PHP 8.2 to 8.5, with MySQL 5.7.8 or MariaDB 10.2.7 and above. The safe route is to check your current version, audit every plugin and template customisation, back up the files and database, rehearse the upgrade on a staging copy, fix what breaks, test checkout and payments properly, and only then go live with a rollback plan. Most stores can do this in a few weeks, and it is much easier to plan it now than to react after a host changes your PHP version or a security problem appears.
Why upgrade now?
Many Australian Zen Cart stores have been running reliably for years, which is exactly why they are easy to neglect. But the platform and the web around it have moved on. These are the main reasons to act:
- Modern PHP support. Zen Cart 2.2.x is designed to run on PHP 8.2 to 8.5. Older 1.5.x releases were built for much older PHP versions, and running on unsupported PHP means no security fixes. Zen Cart 2.2.1 also improved compatibility with PHP 8.4, although some plugins may need updating to run without warnings.
- Security. The Zen Cart project told everyone running 1.5.7x and 1.5.8x to install its April 2024 address security patch as soon as possible, and users of 1.5.8x on PHP 8 or newer are advised to apply a fix for an IntlException error. Upgrading to a current release is the cleanest way to be covered. For more on protecting your store, read our Zen Cart security guide for Australian stores.
- PayPal. Zen Cart 2.2.1 and higher bundle a modern PayPal REST integration, and the project released a plugin in March 2026 to maintain it. If you still use older PayPal modules, now is the time to plan the switch.
- A better admin experience. Release 2.2.1 improved the admin area, including a configuration screen that lets you update all the values in a group at once, and payment, shipping and order total modules grouped by status and sort order.
- Your host may force the issue. Hosting providers retire old PHP versions on their own schedule. A forced PHP change can break an unprepared store overnight, often at the worst possible time.
- The next release is on its way. The project has reported that it is preparing Zen Cart 2.3.0, and a future 3.0 is in development, designed for PHP 8.3 to 8.5. Getting to a current 2.2.x release now puts you in a much better position for what comes next.
If you want the PHP side of this in more detail, see our guide to Zen Cart PHP upgrades. This article focuses on the Zen Cart version upgrade itself.
Which version are you running?
Zen Cart’s recent release history looks like this:
| Version | Released |
|---|---|
| 1.5.7 | June 2020 |
| 1.5.8 | October 2022 |
| 1.5.8a | March 2023 |
| 2.0.0 | April 2024 |
| 2.0.1 | May 2024 |
| 2.1.0 | November 2024 |
| 2.2.1 | March 2026 |
| 2.2.2 | April 2026 |
To find your version, log in to the admin area and check the footer or the Server and Version Info page under Tools. Also note your PHP version (your hosting control panel or the same Server Info page will show it) and your database version.
As a rough guide:
- On 2.2.x: you are on the current branch. Make sure you are on the latest patch release.
- On 2.0.x or 2.1.x: a smaller jump, and usually simpler.
- On 1.5.7x or 1.5.8x: a bigger jump, with more to check, but well worth planning.
- On 1.5.6 or older, or 1.3.x: consider this a larger project, and ask whether a fresh build on the current version is a better option than upgrading in place.
Plan your approach: standard upgrade, database-only upgrade or rebuild?
The Zen Cart documentation distinguishes between two main routes, and the right one depends on how far behind you are and how much your store has been modified.
- Standard site upgrade. The normal route when you are upgrading from the previous release. You replace the files with the new version and run the upgrade process to update the database.
- Database-only upgrade. The documentation suggests considering this when you are upgrading from a release older than the prior release. You install a clean copy of the new version, then upgrade your existing database to match and reapply your customisations carefully.
- Rebuild or migrate. For very old or heavily modified stores, sometimes the cleanest option is a fresh install on the current version, with your products, customers and orders moved across. Others decide it is time to move platforms entirely. Our Zen Cart vs Shopify vs WooCommerce comparison can help with that decision.
Whichever route you choose, always read the release-specific upgrade notes for the version you are going to, and for every release back to the one you are on.
The step-by-step upgrade plan
Step 1: Record exactly what you have
Before you change anything, document:
- Zen Cart version and PHP version
- Database type and version
- Hosting setup, and who manages the server
- Installed plugins and their versions
- Your template name, and whether it is a built-in, purchased or custom template
- Payment, shipping and tax modules in use
- Any scheduled tasks, feeds or integrations (accounting, inventory, marketplaces, email marketing)
Step 2: Audit your plugins and template
This is where upgrades usually succeed or fail. Zen Cart has a helpful override system that lets you keep customisations in folders named after your template, so core files stay clean. The problem arises when someone edited core files directly. Check for:
- Plugins. For each one, check its support thread on the Zen Cart forum for a version that supports your target Zen Cart and PHP version. The documentation specifically reminds upgraders to check whether a new plugin version has been released since the one they installed.
- Core file modifications. Any change made directly to a core file has to be identified and reapplied to the new version of that file.
- Template overrides. The upgrade notes tell you to update both the default template files and your custom templates, so check which changes affect you. The built-in Responsive Classic and Bootstrap templates are good candidates if you want a modern, maintained base.
- Custom modules and auto-loaded files. Look for custom code in the extra functions, extra datafiles and module override folders.
- Abandoned plugins. If a plugin has not been updated for years and has no PHP 8 version, plan to replace it or remove the feature.
Our customisation and performance guide explains how to keep customisations upgrade-friendly.
Step 3: Take a full backup, and test it
Back up both parts of your store:
- The database, with a full dump
- The files, including images, the admin folder, configuration files, plugins and your template
Store a copy off the server and practise restoring it. A backup you have never restored is only a hope.
Step 4: Create a staging copy, and switch off live behaviour
Build a staging site with the same PHP and database versions you plan to use in production, and restore your backup onto it. Before you test, make sure the staging copy cannot affect real customers or real money:
- Switch payment modules to test or sandbox mode
- Turn off or redirect outgoing email, so test orders do not email real customers
- Disable feeds, marketplace syncs and accounting integrations that could push data out
- Block search engines from the staging site
If your host offers a one-click clone and update tool, it can speed up this step, but check the result carefully.
Step 4a: Upgrade PHP and the database, if needed
Move staging to a PHP version your target Zen Cart release supports, and one that still receives security fixes. Check the support dates on php.net and the compatibility notes for each of your plugins, because a version that Zen Cart supports is not necessarily one that all your plugins are ready for. Doing this as its own step makes it easier to tell whether a problem came from PHP or from Zen Cart.
Step 5: Run the Zen Cart upgrade on staging
Follow the official upgrade instructions for your route and starting version. In outline:
- Download the current release from the official Zen Cart site, and only from there.
- Put the new files in place, keeping your template, plugins and configuration files as the documentation instructs.
- Run the upgrade process in the installer to update the database.
- Complete the post-upgrade steps, such as removing the installer folder, checking file permissions and confirming your admin folder is renamed to something non-obvious.
The documentation also notes that the release notes list every changed file, which is useful for working out which of your customisations need to be reapplied.
Step 6: Fix and reapply
Work through the list from your audit:
- Update plugins, or replace those that don’t work on your target PHP version
- Reapply core and template customisations to the new files, moving them into the override system where possible
- Check logs for PHP warnings and errors, and fix them properly instead of hiding them
- Clear caches and regenerate anything that is compiled
Step 7: Switch to PayPal REST
If you take PayPal payments, use the upgrade to move to the PayPal REST integration that is bundled with Zen Cart 2.2.1 and higher. You will need a PayPal Business account and REST app credentials, and you should test thoroughly in PayPal’s sandbox before going live. Also check PayPal’s own developer notices about older integration methods, so you know how long the old modules will keep working. Our guide to payment gateway setup for Australian Zen Cart stores covers the other options, such as Stripe, eWAY and SecurePay, and our article on adding Buy Now, Pay Later covers Afterpay and Zip.
Step 8: Test like a customer, and like an administrator
Place complete test orders, and check:
- Browsing, search, filters and product options
- Cart, coupons, gift certificates and discounts
- GST calculation on products, shipping and discounts, and correct tax display
- Shipping quotes for metro, regional and remote Australia (Australia Post, Sendle, StarTrack and any others you use)
- Every payment method, including PayPal REST, cards and BNPL
- Customer accounts, registration and password reset
- Order confirmation emails and admin notification emails
- Admin order management, invoices, packing slips and any order editing plugin
- Stock and inventory updates
- Product feeds, sitemap and redirects
- Mobile layout and page speed
- SSL and secure checkout
Have someone who works with the store every day test it too, because they will spot things a developer won’t.
Step 9: Go live carefully
Choose a quiet period, and avoid the weeks around your biggest sales. Then:
- Put the store into maintenance mode, and take a fresh full backup.
- Repeat the upgrade on production, or switch over to the tested environment.
- Switch live payment modes and integrations back on one at a time.
- Place a real low-value test order and refund it.
- Keep the old version and backup for a few days in case you need to roll back.
Step 10: Monitor after launch
For the first week, watch error logs, order volume, payment success rates, emails and server performance. Small problems, such as a missing confirmation email, are easiest to fix early.
How long does it take?
The time depends on how far behind the store is, how much customisation it has and how many plugins it uses. As a rough guide:
| Situation | What it looks like | Typical effort |
|---|---|---|
| Light | Recent version, few plugins, standard template | A few days |
| Moderate | 1.5.7 or 1.5.8, several plugins, light template customisation | One to three weeks |
| Heavy | Much older version, modified core files, custom modules, many integrations | Several weeks or more, often in stages |
These are general estimates, not quotes. An assessment will give you a realistic plan for your own store.
Australian considerations
- Privacy Act 1988. Businesses covered by the Act must take reasonable steps to protect the personal information they hold. Running an outdated store with known security gaps makes that harder to demonstrate, and a data breach may trigger notification obligations.
- Card payments. If you take card payments, your payment provider will expect you to meet PCI DSS requirements for merchants, which include keeping software patched. Check what applies to your set-up with your provider.
- ACSC Essential Eight. Patching applications and avoiding unsupported software are core recommendations from the Australian Cyber Security Centre.
- GST and pricing. Make sure tax settings, price display and any promotional claims continue to comply with Australian rules after the upgrade.
- Cyber insurance. Insurers increasingly ask about patching and software support, and unsupported systems can complicate a claim or renewal.
This is general information, not legal advice. Check your obligations with your legal or compliance advisers.
Common mistakes to avoid
- Upgrading production first. Always rehearse on staging.
- Leaving payment and email switched on in staging. This can charge or email real customers.
- Changing PHP and Zen Cart at the same time. Do them separately so you can find the cause of any problem.
- Ignoring plugin compatibility. One unsupported plugin can stop checkout working.
- Overwriting customisations. Document and reapply them, and move them into the override system.
- Downloading Zen Cart or plugins from unofficial sources. This is a common way for malware to reach a store.
- Skipping the post-upgrade clean-up. Remove the installer folder, check permissions and rename the admin folder.
- Upgrading just before a big sale. Schedule it for a quiet period.
Upgrade checklist
- Zen Cart, PHP and database versions recorded
- Upgrade route chosen (standard, database-only or rebuild)
- Release-specific upgrade notes read for every version between yours and the target
- Plugins audited, with compatible versions identified
- Core file changes and template overrides documented
- Full database and file backup taken and test-restored
- Staging environment built, with payments in test mode and email redirected
- PHP and database prepared on staging
- Upgrade completed on staging
- Plugins and customisations fixed and reapplied
- PayPal REST configured and tested in sandbox
- GST, shipping, coupons and emails tested
- Full checkout tested for every payment method
- Go-live window and rollback plan agreed
- Live payments re-enabled, with a real test order completed
- Logs and orders monitored for at least a week
- Installer removed, admin folder renamed and permissions checked
DIY or get a Zen Cart specialist?
If your store is on a recent version, uses few plugins and you have a technically confident administrator, you can do much of this yourself with the official documentation. Bring in a specialist when your store is several versions behind, has many plugins or modified core files, takes a lot of revenue, uses custom integrations, or when you simply cannot afford downtime.
A good Zen Cart partner will assess your store, give you a clear plan, handle staging, testing and the cutover, and leave your store cleaner and easier to maintain. Learn more about our Zen Cart maintenance, support and optimisation, customisation and theme design and website development services.
Frequently asked questions
What is the latest version of Zen Cart?
The 2.2.x branch is the current release line, with Zen Cart 2.2.1 released in March 2026 and 2.2.2 in April 2026. The project has reported that it is preparing Zen Cart 2.3.0, so check the official Zen Cart site for the latest release before you start.
Which PHP version does Zen Cart 2.2 need?
Zen Cart 2.2.x is designed for PHP 8.2 to 8.5, with MySQL 5.7.8 or higher, or MariaDB 10.2.7 or higher. Choose a PHP version that your plugins also support and that still receives security updates.
Is Zen Cart 1.5.8 still safe to use?
It can be, but only if you have applied the April 2024 address security patch and any other fixes, and you are running a supported PHP version. Older versions miss improvements for modern PHP, so upgrading is the safer long-term choice.
Will my plugins work after upgrading?
Not automatically. Each plugin needs a version that supports your new Zen Cart and PHP versions. Check each plugin’s support thread on the Zen Cart forum, and replace any that have been abandoned.
Can I upgrade directly from 1.5.x to 2.2?
The documentation suggests considering a database-only upgrade when you are coming from a release older than the prior one. Always read the release-specific upgrade notes for each version between yours and the target, and rehearse on staging first.
Do I need to change my PayPal integration?
If you use older PayPal modules, you should plan to move to the PayPal REST integration bundled with Zen Cart 2.2.1 and above. Test it in PayPal’s sandbox first, and check PayPal’s developer notices for timelines on older methods.
Will I lose my orders and customers during the upgrade?
Not if you back up properly, test the restore, rehearse on staging and keep a rollback plan. The main risk comes from skipping those steps.
How much downtime should I expect?
If the upgrade is rehearsed on staging, the live cutover can often be done in a short maintenance window, such as out of hours. Heavier stores need a longer window, which is why planning matters.
How much does a Zen Cart upgrade cost?
Costs depend on how far behind the store is, how many plugins and customisations it has and how many integrations are involved. A light upgrade is quick and affordable, while a heavily modified store takes longer. An assessment will give you a clear estimate.
Need help upgrading your Zen Cart store?
Zencart Professionals helps Australian online stores upgrade, secure and maintain their Zen Cart websites. We can assess your current version, audit your plugins and customisations, move you to Zen Cart 2.2.x on a supported PHP version, set up PayPal REST, and manage the testing and go-live so your store keeps trading.
Contact us to book a Zen Cart upgrade assessment.
