Nothing is more frustrating than waking up to find your WooCommerce store no longer working and showing errors on the website. This was the case for one of our clients back in 2025 when their web hosting company upgraded the PHP version. The web host did send notices ahead of time, but the client never took action on them, and since everything was currently working, they didn’t see a reason to update. That’s where the problem started.
PHP updates happen from time to time, and they weren’t the problem. Heck, WooCommerce and WordPress themselves were perfectly fine on the new PHP version too. The problem was a plugin used in the store that wasn’t compatible with the new PHP version.
When WordPress sites break after a server or software update, the problem is often not WordPress core itself. It is an outdated plugin, theme, or piece of custom code that was never updated to support the newer environment.
That situation is worth thinking about again now because the WooCommerce development team has proposed making PHP 8.1 the minimum requirement starting with WooCommerce 11.5. That version is currently expected in January 2027, so stores still running PHP 7.4 or PHP 8.0 need to start paying attention now.
TL;DR – Key Takeaways
- WooCommerce is proposing PHP 8.1 as the minimum starting with version 11.5, which prevents stores on PHP 7.4 or PHP 8.0 from upgrading to newer WooCommerce releases.
- PHP 8.1 reached end of life in December 2025, which raises the question of why WooCommerce would make an unsupported PHP version its new minimum instead of targeting PHP 8.3 or PHP 8.4.
- Your store is not going to suddenly stop working when WooCommerce 11.5 is released, but staying on an older PHP version can eventually leave WooCommerce and its extensions stuck on older releases.
- Testing your plugins, theme, custom code, payment gateways, shipping tools, subscriptions, and integrations needs to happen before changing PHP on a live store.
What WooCommerce Is Actually Proposing
WooCommerce 11.5 currently proposes setting the minimum PHP version to PHP 8.1, which means users still running PHP 7.4 and PHP 8.0 would not be able to upgrade WooCommerce until they upgrade their server software.
Supporting older PHP versions means WooCommerce developers have to keep testing and maintaining compatibility with older dependencies. Raising the minimum version also gives developers access to newer PHP features and libraries without having to code scenarios for versions that have been out of date for years. That reduces development overhead and can also improve performance.
According to w3tech.com, they’re showing that about 20% of sites using PHP are running the older PHP 7.4 version and about 6% are using PHP 8.0. WooCommerce’s own tracking currently puts PHP 7.4 at around 7% of tracked stores and PHP 8.0 at roughly 2%.
That may be a relatively small percentage of WooCommerce stores, but the sites still running these older PHP versions may also be the ones that are harder to upgrade because of older plugins, custom development, hosting limitations, or other dependencies.
The change is still in the proposal stage. WooCommerce is actively asking developers, web hosts, agencies, and store owners what might prevent them from moving away from PHP 7.4 and 8.0 before they finalize the requirement. If this change would affect your store or clients, WooCommerce is currently asking for feedback.
Your Store Is Not Going to Suddenly Break in January
If WooCommerce 11.5 ships with PHP 8.1 as its minimum and your site is still running PHP 7.4, WooCommerce won’t deactivate itself or suddenly stop working. WordPress checks a plugin’s PHP requirement before installing an update, so you would normally remain on the newest WooCommerce release that still supports your current PHP version.
Your hosting company won’t change PHP just because WooCommerce releases a new version either; they have other reasons for updates. The real problem is that your store can eventually become stuck on an older WooCommerce release.
At first, that may not seem like a major issue. But over time, newer versions of payment gateways, shipping extensions, subscription plugins, and other integrations may require newer WooCommerce releases. Once one part of the store needs to move forward, staying frozen on an older version can become increasingly difficult.
WooCommerce still provides security updates and support for older releases, so it is not as though the previous version becomes abandoned the day 11.5 appears. There will eventually be a point where older releases are no longer supported, but that transition doesn’t happen overnight.
For many WordPress blog sites, they’re treated more like informational sites, and sitting on older versions of software doesn’t usually create an update crisis. But an online store is completely different. Your online store will be processing payments, storing customer information, handling subscriptions, taxes, and possibly a fulfillment company. Running old software in those environments carries real risk, and it’s not the type of website I would intentionally delay updates for.
PHP 8.1 Is Already End of Life
This is the part of the proposal I have a problem with. PHP 8.1 is no longer being maintained, even for security releases. That stopped in December 2025! Even PHP 8.2 is going to expire in December 2026, which is the month before WooCommerce 11.5 is set to release!
| PHP Version | Initial Release | Active Support Expires | Security Support Expires |
|---|---|---|---|
| PHP 8.2 | December 8, 2022 | December 31, 2024 | December 31, 2026 |
| PHP 8.3 | November 23, 2023 | December 31, 2025 | December 31, 2027 |
| PHP 8.4 | November 21, 2024 | December 31, 2026 | December 31, 2028 |
| PHP 8.5 | November 20, 2025 | December 31, 2027 | December 31, 2029 |
PHP 8.3 will continue to receive support through December 31, 2027, and PHP 8.4 is supported through December 31, 2028. Those are more realistic minimum numbers in my book. Skip the 8.1 minimum and go right for 8.3.
Some hosting companies and server management providers continue to support older PHP versions well past the security expiration, but those are outliers. So for most WordPress site owners, the official PHP support schedule is the better target to follow.
WordPress and WooCommerce currently both recommend using PHP 8.3 or newer, and certainly, with any of the client projects we’re recommending, that they’re on PHP 8.4 or PHP 8.5. Besides, there’s a speed boost in some of the PHP execution.
But again, the problem with the newer versions is plugin and theme compatibility. The number of patches that we’ve had to create for users still running plugins that were released on PHP 7.4 and never fully updated to 8.x is insane. We are still talking about the _load_textdomain_just_in_time error giving Loading Triggered Too Early. This is an issue that started back in November 2024 with WordPress 6.7, and you can still find developers not fixing the error/notice today in September 2026!
If you’re already going through the work of moving an older WooCommerce store off PHP 7.4 or PHP 8.0, the biggest investment is not changing the PHP setting itself. It is testing the plugins, theme, custom code, and integrations to make sure they still work correctly.
Since you are doing compatibility work anyway, it makes more sense to target a PHP version with a longer support lifetime rather than stopping at PHP 8.1 just because it meets WooCommerce’s proposed minimum.
Changing PHP Is Easy. Knowing What Will Break Is Not.
One of the comments described upgrading PHP as a five-minute job in a hosting control panel. This is technically true for most hosting companies. Click a button, click refresh, and PHP is now running the latest version.
The important part is what happens after you change it.
WooCommerce core is generally not the first place I would expect problems, even on an older store. I would start with custom code added to the theme or functions.php file, then work through the plugins installed on the site. Older payment gateways, shipping extensions, custom plugins, and integrations are usually where compatibility problems start to surface. This is also where experienced WooCommerce development and support becomes valuable, especially on stores with custom functionality or years of accumulated changes.
The situation gets more complicated when an outside service changes its API. A payment processor, shipping provider, or other integration may require you to install a newer version of its plugin. That newer plugin may require a newer version of PHP or WooCommerce, and suddenly one necessary update forces several other parts of the site to move forward at the same time.
When PHP 8.0 was released, they introduced a number of backward-incompatible changes. Then, when PHP 8.1 came out, it deprecated additional behaviors such as passing NULL in built-in functions that expect a non-nullable value. Some functions used for years, such as create_function(), were completely removed, which breaks older themes, plugins, and custom code.
For a deeper look at some of the incompatibilities and examples of what changed between PHP 7.x and PHP 8.x, check out our post about upgrading PHP on WordPress and checking for compatibility issues.
WooCommerce makes essentially the same point in its proposal. Raising the minimum PHP version does not automatically make every WooCommerce extension, theme, or custom snippet compatible with it.
That is why testing is more important than the PHP setting itself.
How to Check Which PHP Version Your Store Is Running
You can find your PHP version inside WordPress without installing anything.
Go to WooCommerce > Status and look under the Server Environment section. You can also go to Tools > Site Health > Info > Server.
Finding the PHP version takes a few seconds. The plugin list is where the useful part of the audit starts.
Look for plugins that have not been updated in a long time, extensions with expired licenses, custom plugins nobody recognizes, and anything tied directly to checkout, payments, shipping, subscriptions, tax calculations, or order processing. Those are the parts of the store I would want to understand before changing the live site’s PHP version.
Test the Store Before You Change Production
For an active WooCommerce store, don’t just change the PHP version and hope for the best. Clone the site to a staging environment and make the PHP change there so you can test everything safely.
Be especially careful with subscriptions, memberships, automatic payments, emails, fulfillment systems, and third-party integrations. Your staging site should be configured so that it is not able to charge customers, send production emails, create live shipments, or push test orders into outside systems.
On your staging site, turn on WordPress debug logging and display errors on your site, then test the store functionality. Add products to the cart, complete checkout, test payment gateways appropriately, process a refund, confirm customer emails are being generated, and work through the admin order screens.
Before changing PHP on the production site, make sure you have a current backup and know how to switch back to the previous PHP version if something unexpected happens. If the store has a serious problem after the change, rolling PHP back is often the fastest way to get it operational again while you troubleshoot.
Once you’ve completed your testing, you can now implement it on the production server. I still recommend turning on debug logging but not displaying errors to visitors. You can set it to display for admin users, but logging is usually enough. Now test everything again to make sure nothing breaks.
Keep in mind, a WooCommerce store can load perfectly well on the front end while something important is quietly failing in the background. Test everything!
Do Not Pick the Worst Possible Time to Do It
One point from the Reddit discussion that I completely agree with was the timing. Nobody needs to be experimenting with major server changes immediately before the busiest part of the ecommerce year.
For a lot of stores, November and December are terrible times to discover that an old shipping plugin does not like the new PHP version.
There is still plenty of time before WooCommerce 11.5 is expected in January 2027. If your store is running PHP 7.4 or PHP 8.0, now is a good time to start figuring out what is keeping it there.
That does not mean changing production immediately. Use a staging environment to identify compatibility problems, fix what surfaces, and then schedule the live change for a quieter period when somebody is available to monitor the store afterward.
The Reddit Reaction Was Not What I Expected
When I opened the Reddit discussion, I expected at least some of the reaction to come from store owners unhappy that WooCommerce was forcing another technical change on them. But reading through the threads, that really wasn’t the tone of the discussion.
Most of the comments I saw were saying the opposite: the PHP 8.1 version was too conservative, and WooCommerce should move the minimum to PHP 8.3 instead. That was pretty close to my own reaction when I first read the proposal too.
The stores still running PHP 7.x in 2026 may also be the ones least likely to be actively maintained. Some may depend on older paid plugins, custom development from years ago, or code nobody wants to touch because nobody is sure what will break. Those are the stores where a PHP upgrade can turn from a five-minute hosting change into a much larger compatibility project.
Not Sure What Will Break?
If you are running a WooCommerce store on an older PHP version and you are not sure what is going to happen when it changes, Kim and I can take a look before you touch the live site.
That usually starts with reviewing the plugins, theme, custom code, hosting environment, and any integrations that are important to the store. From there, we can test the PHP change in a staging environment and work through any compatibility problems before anything is changed on the live site.
When you contact Big Red SEO, you are talking directly to Kim or Conor. There is no account manager passing the question to somebody else and no support queue where the details get lost. We are the same people who will actually look at the website, work through the problem, and explain what we found.
If you want us to take a look before WooCommerce’s PHP requirements change, call us at (402) 522-6468 or fill out our contact form. We can help you figure out what needs to be updated or fixed before you change PHP on the live store.
