JnK Plugins
WooCommerce 11.6 Needs PHP 8.1: What Happens If You Don’t Upgrade
Last updated 18 October 2026. Based on WooCommerce’s announcement of 29 September 2026 and WordPress.org’s public PHP statistics, read on 18 October.
WooCommerce will need PHP 8.1 or newer from version 11.6, planned for February 2027. If your store runs PHP 7.4 or 8.0, nothing breaks when that happens, but you’ll stop getting WooCommerce updates until you upgrade PHP. Here’s what changes, when, and how to check and fix it.
The change in three lines
- WooCommerce 11.3 (the next major version) adds a dismissible notice in wp-admin if your store runs PHP 7.4 or 8.0. It’s only a warning. Everything keeps working.
- WooCommerce 11.4 and 11.5 still work on PHP 7.4 and 8.0. 11.5 is the last planned version that does.
- WooCommerce 11.6, planned for February 2027, requires PHP 8.1 or newer.
Source: New Requirement for WooCommerce 11.6: PHP 8.1+. The original proposal on 8 September aimed for 11.5 in January. After feedback it was pushed one release later, so it doesn’t land in the middle of the holiday sales season.
What happens if I do nothing?
This is the part people get wrong, so here it is plainly.
- Your store won’t break. WooCommerce says the new requirement “will not deactivate an existing WooCommerce installation.”
- WordPress just won’t install 11.6. When a plugin update needs a newer PHP than your server has, WordPress doesn’t offer it. You’ll see “There is a new version of WooCommerce available, but it does not work with your version of PHP” on the Plugins screen, and automatic updates skip it too. We checked this in the WordPress core code.
- You’re stuck on 11.5. That’s fine for a while, but not forever. Under WooCommerce’s security policy, fixes for the most serious vulnerabilities (CVSS 9 or higher) are backported to older versions within a rolling window of 21 major release series. Other fixes generally only go into the latest version. So the longer you stay, the more you miss.
- Your extensions will move on too. Extension developers can start using PHP 8.1 features once WooCommerce does, so extension updates may stop installing on old PHP as well.
And there’s a bigger reason than WooCommerce. PHP 7.4 stopped getting security fixes from the PHP project in November 2022, and PHP 8.0 in November 2023. If your store is on either, the PHP itself is already unpatched.
How many stores does this affect?
WooCommerce’s own figures say about 7% of tracked stores run PHP 7.4 and 2% run PHP 8.0, and that among stores that updated WooCommerce in the past year it’s closer to 6% combined. That tracking is opt-in, so it’s a sample, not a count.
The wider WordPress world is further behind. Here’s what WordPress.org’s own stats showed for all WordPress sites on 18 October 2026:
| PHP version | Share of WordPress sites | OK for WooCommerce 11.6? |
|---|---|---|
| 7.3 or older | 5.7% | No (already too old for current WooCommerce) |
| 7.4 | 16.2% | No |
| 8.0 | 3.9% | No |
| 8.1 | 10.8% | Yes (the minimum) |
| 8.2 | 23.9% | Yes |
| 8.3 | 26.5% | Yes (WooCommerce’s recommendation) |
| 8.4 and newer | 13.0% | Yes |
Source: api.wordpress.org/stats/php/1.0. Figures rounded, so they may not add up to exactly 100.
So about 25.8% of all WordPress sites run PHP older than 8.1, against roughly 9% of the stores WooCommerce tracks. Part of the gap is who opts into tracking, and part is that stores tend to get more care than brochure sites. But it means if you look after a mix of sites, a quarter of them are likely to be on old PHP, and any of them that run WooCommerce will need sorting before February.
On extensions, WooCommerce says it scanned the 1,357 extensions sold on its marketplace for PHP 8.1 problems and 0.22% showed potential issues. That’s about three extensions. Free plugins, themes and custom code weren’t part of that check, and those are where problems usually turn up.
Step 1: Check your PHP version
Any of these will tell you:
- WooCommerce > Status, then look for “PHP version” under Server environment. This is the method WooCommerce itself recommends.
- Tools > Site Health > Info, then open the “Server” section.
- Your hosting control panel. Most hosts show the PHP version and let you change it, often per site.
If it says 8.1 or higher, you’re done. WooCommerce recommends 8.3 or newer, so if you’re on 8.1 or 8.2 it’s worth planning a move anyway, but there’s no deadline for that.
Step 2: Upgrade PHP safely
This follows WooCommerce’s own checklist, in plain words:
- Make a backup. Files and database, and know how to restore it.
- Make a staging copy. Many hosts have a one-click staging button. If yours doesn’t, ask them.
- Switch staging to the new PHP version. Aim for 8.3 if your host offers it. Going from 7.4 straight to 8.3 is normal, you don’t need to step through each version.
- Test the things that make you money. Add to cart, checkout with every payment method you offer, shipping and tax calculations, coupons, order emails, the order screens in wp-admin, and any scheduled jobs like subscription renewals.
- Click around the rest. Your theme’s main pages, contact forms, anything custom a developer built for you.
- Fix or replace what breaks. Update plugins and the theme first. That fixes most problems.
- Switch the live site, ideally at a quiet hour, and repeat the checkout test straight away.
Errors you might see after the upgrade
Most PHP upgrades go fine, especially if everything is up to date. When something does go wrong, it’s almost always an old plugin, theme or custom snippet, not WordPress or WooCommerce. Here’s what the common messages mean:
| You see something like | What it means | Will it break the site? |
|---|---|---|
| “Call to undefined function create_function()” or “each()” | Very old code using functions PHP 8.0 removed | Yes, fatal. Update or replace that plugin or theme |
| “Unsupported operand types” or “count(): Argument #1 must be of type Countable” | Code that PHP 7 let slide with a warning, but PHP 8 now stops | Yes, fatal on that page |
| “Passing null to parameter #1 … is deprecated” | A PHP 8.1 deprecation notice | No. It’s a warning for developers |
| “Creation of dynamic property … is deprecated” | A PHP 8.2 deprecation notice | No. Same, just a warning |
“Deprecated” messages are not errors. They’re PHP telling developers that something will stop working in a future version. On a live site they shouldn’t be shown to visitors at all, and they won’t stop your shop. If you see a white screen or “There has been a critical error on this website”, that’s a fatal error, and our guide to finding which plugin is causing a problem walks through tracking it down.
If you can’t upgrade yet
Sometimes an old extension or a custom integration really does need old PHP. WooCommerce’s answer is that you can stay on 11.5 while you sort it out, but it calls that “a temporary option”. Use the time to get the blocker replaced or updated, and push your host for a date.
If your host can’t offer PHP 8.1 or newer at all, that’s a good sign it’s time to move.
For more on why old PHP is becoming a bigger risk this year, we covered the jump in WordPress security releases in 2026 separately.
Frequently asked questions
When will WooCommerce require PHP 8.1?
From WooCommerce 11.6, planned for February 2027. WooCommerce 11.3 adds a warning notice for stores on PHP 7.4 or 8.0, and 11.5 is the last planned version that still runs on them.
Will my WooCommerce store stop working if I stay on PHP 7.4?
No. WordPress simply won’t offer you WooCommerce 11.6, so you stay on the last compatible version. The store keeps working, but you miss new features and most fixes, and PHP 7.4 itself has had no security fixes since November 2022.
Which PHP version should I use for WooCommerce?
PHP 8.3 or newer is what WooCommerce recommends. PHP 8.1 is the minimum from version 11.6. Test the change on a staging copy first, including checkout and payments.
