WooCommerce PHP 8.1 requirement: what your store must do before 11.6
The WooCommerce PHP 8.1 requirement is the new minimum: WooCommerce 11.6, planned for February 2027, will require PHP 8.1 or newer. Stores on PHP 7.4 or 8.0 will receive WooCommerce updates up to version 11.5 at most, and WordPress will normally not offer them anything newer. Moving to PHP 8.1 alone is not enough, though, because PHP 8.1 has not received even security fixes since 31 December 2025. Both WooCommerce and WordPress recommend PHP 8.3 or newer. In practice that means three steps: check your PHP version, test the change on a copy of the store and switch the live site during a quiet period.
We first wrote about this change while it was still a proposal, in our article on what is new in WooCommerce 11.1. Since then the decision has been confirmed and moved one version later. Below you will find the timeline, a PHP support table, a step-by-step upgrade process and what to do when something breaks on the new PHP. How to test changes safely on a copy of your site is covered in detail in our article on WordPress updates with staging and rollback. If you want a store that handles changes like this without stress, see how we build custom online stores.
WooCommerce PHP 8.1 requirement: what changes and when
From WooCommerce 11.6 the minimum will be PHP 8.1, and from version 11.3 WooCommerce will warn you about it.
The WooCommerce team proposed the change on 8 September 2026 for version 11.5, targeted for January 2027. After community feedback it confirmed it on 29 September 2026 and moved it to version 11.6, so stores can test after the peak selling season. According to the plugin page on WordPress.org, the current stable version is 11.1.2 and it still requires PHP 7.4 or newer.
| WooCommerce version | What it brings for PHP | What it means for a store on PHP 7.4 or 8.0 |
|---|---|---|
| 11.1.2 (current) | Minimum PHP 7.4 | Works, nothing changes yet |
| 11.3 | A dismissible notice in the admin | The store keeps working, the notice shows your PHP version and recommends contacting your host |
| 11.5 | Last planned version for PHP 7.4 and 8.0 | The highest version you can reach without changing PHP |
| 11.6 (planned: February 2027) | Minimum PHP 8.1 | WordPress will normally not offer the update until you change PHP |
What will not happen matters just as much. According to WooCommerce, the requirement change will not deactivate an existing installation, and it will not change PHP on your hosting either. A store on old PHP simply freezes on the last version its environment can handle. That is exactly the problem we get to below.

Why moving to PHP 8.1 alone is not enough
PHP 8.1 meets the WooCommerce 11.6 minimum, but it no longer receives security fixes itself, so aim straight for PHP 8.3 or 8.4.
According to the PHP project, each PHP branch gets two years of full support and then two more years of critical security fixes only. After that it reaches end of life. These are the dates from the official pages on supported PHP versions and unsupported branches:
| PHP version | Security fixes until | For WooCommerce 11.6 |
|---|---|---|
| 7.4 | ended 28 November 2022 | Not enough |
| 8.0 | ended 26 November 2023 | Not enough |
| 8.1 | ended 31 December 2025 | Meets the minimum, but without fixes |
| 8.2 | 31 December 2026 | Meets the minimum, support ends in less than three months |
| 8.3 | 31 December 2027 | Recommended minimum of WooCommerce and WordPress |
| 8.4 | 31 December 2028 | A good choice with a longer runway |
| 8.5 | 31 December 2029 | Newest branch, check extension compatibility separately |
According to its official requirements, WordPress still runs on PHP 7.4 but recommends PHP 8.3 or newer. WooCommerce sees it the same way: PHP 8.1 is the minimum, 8.3 or newer is its current recommendation. Its server recommendations page also states that WooCommerce is tested up to PHP 8.4. That is why we recommend PHP 8.3 or 8.4. Move to 8.5 only once your theme and every extension explicitly support it.
If you are changing PHP anyway, do it once and do it properly. Going from 7.4 to 8.1 and a year later to 8.3 means testing the same store twice. Jumping straight to 8.3 or 8.4 takes a similar effort and gives you a runway until the end of 2027 or 2028 respectively.
An online store that handles a new PHP version
If your store runs on old PHP and you do not know what the upgrade will break, see how we work on online stores and what we test before launch.
How to tell if the WooCommerce PHP 8.1 requirement affects you
You can find your PHP version in a minute, right in the WooCommerce admin.
- Open the system status: in the WordPress admin go to WooCommerce, then Status.
- Find the Server environment section: the PHP version row shows the version your store runs on.
- Compare it with the table above: 7.4 or 8.0 means the change affects you directly. With 8.1 and 8.2 your problem is not WooCommerce 11.6 but the end of security fixes.
- Note the WordPress and WooCommerce versions too: you will find them on the same page under WordPress environment, and you will need them for the test.
How common is old PHP? According to WooCommerce data, about 7% of tracked stores run PHP 7.4 and about 2% run PHP 8.0. Among stores that updated WooCommerce within the past year, the combined figure is closer to 6% and declining. Tracking is opt-in, so this is a sample, not a count of every store. Still, if you run old PHP, you belong to a shrinking group, and newer extension versions may no longer account for your environment.
How to upgrade PHP without losing orders
Back up and test on a copy of the store first, then change the live site and update WooCommerce.
WooCommerce recommends this sequence in its announcement. We added what we run into most often with online stores.
- Back up the whole store: database and files, stored off the server. We explain how in our article on WordPress backups with the 3-2-1 strategy.
- Copy of the store (staging): switch PHP to the target version there, ideally 8.3 or 8.4. Some hosts offer staging right in their control panel, otherwise it has to be set up by hand.
- Test the critical flows: checkout and every payment method, shipping and tax calculations, order management, scheduled jobs, the theme, extensions and custom code. On the copy, remember to turn off customer e-mails and live payments.
- Fix what you found: update extensions that throw errors on the new PHP and replace the ones nobody maintains any more. Have a developer review custom code.
- Change PHP on the live site: at the time with the fewest orders, with a ready way back to the original version.
- Check after the change: open WooCommerce, Status again and verify the PHP version. Then place a test order all the way to the confirmation e-mail.
- Update to WooCommerce 11.6: only once it is released and the live store runs on the new PHP without errors.

Timing matters more for an online store than for an ordinary website. If you can, do not change PHP during the pre-Christmas season, during sales or right before a campaign. The WooCommerce team reasoned the same way when it moved the mandatory change to February 2027. And if something does break after the change, you will find the diagnostic steps in our article on a site that stops working after a WordPress update.
What if your store breaks on the new PHP
You can stay on WooCommerce 11.5 for a while, but that is a delay, not a fix.
WooCommerce explicitly says you can remain on version 11.5 while you work through a hosting or extension constraint. It adds two caveats. Under its security patch support policy, only fixes for vulnerabilities rated CVSS 9 or higher are backported to older versions, within the last 21 major versions. Other fixes generally ship only for the latest version. The second caveat: PHP 7.4 and 8.0 themselves no longer receive security fixes, so no WooCommerce patch will address risks in PHP itself.
For paid extensions from the official marketplace the picture looks good. WooCommerce ran static analysis on all 1,357 extensions it sells in its marketplace and found potential PHP 8.1 issues in 0.22% of them. It also warns that such a screening cannot guarantee that every extension, theme or custom change will work on the new PHP in a particular store. Extensions from outside the marketplace and custom code were not part of this check.
| What the test showed | What to do |
|---|---|
| The extension has a newer version | Update it and repeat the test |
| Nobody maintains the extension any more | Find a replacement or have the feature rewritten |
| An error in custom code or a template override | A developer has to fix it |
| The host does not offer newer PHP | Ask for a different plan or consider changing hosts |
| The theme is old and unmaintained | Decide whether to fix the theme or rebuild the store |

What this looks like in practice
In our experience the problem is rarely WooCommerce itself, but old add-ons, custom code and a forgotten hosting plan.
With the stores we take over for maintenance or a redesign, a few patterns keep coming back:
- An old hosting plan: the store has run on the same package for years and nobody has changed the PHP version. Often it is enough to switch the version in the hosting control panel, sometimes you need a newer plan.
- Payment and shipping add-ons from smaller vendors: modules for local payment gateways, carriers or invoicing integrations sometimes lag behind new PHP versions. Test these first, because without them an order cannot be completed.
- Changes added straight into the theme: small tweaks to the cart, price calculation or order exports that someone once added to the functions.php file. On new PHP they may silently stop working or take the whole page down.
- Scheduled jobs: exports for price comparison sites, stock synchronisation and automatic e-mails run in the background. Errors in them are not visible right away, only when a customer does not get an e-mail or the stock levels do not match.
How we handle it at Denva: before every store launch we go through the whole purchase as a real customer, from adding to the cart through payment to the confirmation e-mail. After launch, if you want, we keep taking care of updates and monitoring.
If it turns out the store sits on an unmaintained theme and dozens of add-ons, it is a good moment to consider whether to keep patching it or rebuild it. You will find a platform comparison in our article WooCommerce vs Shoptet.
When you can do it yourself and when to bring us in
You can handle it yourself if:
- the store uses only actively maintained extensions and no custom code,
- your host offers staging and a one-click PHP version switch,
- after the test on the copy, checkout, payments, shipping and e-mails work without errors.
It is worth bringing us in if:
- the store contains custom changes or add-ons nobody maintains any more,
- the test on the copy showed errors in checkout, payments or the stock and invoicing integration,
- you have no staging and no clear way back if something goes wrong.
Conclusion
The WooCommerce PHP 8.1 requirement arrives with version 11.6 in February 2027, but the real reason to act is different: PHP 7.4, 8.0 and 8.1 no longer receive security fixes, and PHP 8.2 stops receiving them on 31 December 2026. Check your PHP version under WooCommerce, Status, test the move to PHP 8.3 or 8.4 on a copy of the store and switch the live site during a quiet period. Stay on WooCommerce 11.5 only until you have removed the obstacle. If you are unsure about the test or the fixes, write to us through the contact form and we will go through it with you.
Upgrade PHP without losing orders
Tell us what your store runs on and we will go through with you whether a PHP change, an add-on fix or a new store is the right move.
Frequently asked questions.
When will WooCommerce require PHP 8.1?
From WooCommerce 11.6, which WooCommerce plans for February 2027. Versions up to and including 11.5 still work on PHP 7.4 and 8.0, and from 11.3 you will see a notice about the change in the admin.
Will my store on PHP 7.4 stop working?
No, the existing installation will not be deactivated. But WordPress will normally not offer you the update to WooCommerce 11.6 and newer, so the store stays on an old version without most fixes and new features.
Which PHP version should I choose for WooCommerce?
PHP 8.3 or 8.4. PHP 8.1 meets the minimum, but it has not received security fixes since 31 December 2025. Both WooCommerce and WordPress recommend PHP 8.3 or newer.
Where do I find which PHP version my store uses?
In the WordPress admin under WooCommerce, Status. In the Server environment section you will find the PHP version row. Your host can also tell you.
Can I stay on WooCommerce 11.5?
Temporarily, yes, WooCommerce allows it as a delay. However, only fixes for vulnerabilities rated CVSS 9 or higher are backported to older versions, and PHP 7.4 and 8.0 themselves no longer receive fixes.