WooCommerce has announced that version 11.6, planned for February 2027, will require PHP 8.1 or newer. Most of your team will never think about PHP, but it is the language your store runs on, and the version your server uses affects security, speed, and whether you can keep updating. If revenue flows through your WooCommerce store, this is worth a short conversation with whoever hosts and maintains it.

What Is Changing

PHP 7.4 and 8.0 have reached the end of upstream security support. WooCommerce is raising its minimum so it can stop testing and carrying code for those older versions. Version 11.3 will add a dismissible notice in the admin for stores on PHP 7.4 or 8.0, but it will keep working. Stores on those versions can keep updating WooCommerce up to version 11.5. After that, WordPress will not offer the next update until the server is upgraded. Your existing store will not switch off, but it will stop receiving new features and fixes.

WooCommerce’s own usage figures, which come from opt-in tracking and are only a sample, put roughly 7 percent of stores on PHP 7.4 and 2 percent on PHP 8.0. WooCommerce recommends PHP 8.3 or newer, not just the 8.1 minimum.

Why This Is Bigger Than a Version Number

The timing matters. This month the PHP project shipped a security release that fixed serious vulnerabilities, including ones that allow remote code execution. The fixes landed in the currently supported branches, and PHP 8.1 and older no longer receive them. A store on an unsupported PHP version can be fully up to date on WordPress, WooCommerce, and every plugin and still be exposed at the server level.

There is also a calendar issue. PHP 8.2 reaches end of life on December 31, 2026. If your host answers this question with “we are on 8.2,” that is better than 8.0, but it only buys you a few months. Moving straight to 8.3 or newer avoids doing this twice.

The Real Risk Is Plugins and Custom Code

Upgrading PHP is usually a setting your host can change. The harder part is confirming that everything running on top of it still works. Older themes, abandoned plugins, and custom code written years ago are where problems tend to appear, and checkout, payment, and shipping integrations are the places where a failure costs you orders. This is why the change should be tested on a staging copy first, not switched on a live store during a busy week.

Questions to Ask Your Host and Agency

• What PHP version is our store running right now? You can verify this yourself in the WordPress admin under WooCommerce, then Status, in the Server environment section.
• Who is responsible for upgrading it, and by when? Get a date, and make sure it falls well before February 2027.
• Will you test on a staging copy first? Ask which flows will be checked: checkout, payments, shipping rates, tax, emails, and any ERP or CRM connection.
• Which of our plugins, themes, or custom code are not compatible with PHP 8.3? Ask for a list, along with what it costs to replace or fix each one.
• What is the plan if something breaks after the change? A good answer includes a recent backup and a tested way to roll back.
• Is the work covered by our maintenance agreement? If not, find out the cost now rather than during a rush.

Schedule It Around Your Sales Calendar

WooCommerce deliberately set the requirement for after the peak selling season, and that is a useful cue for your own planning. If your busiest weeks are approaching, the sensible path is to check your current version now, test over the coming weeks, and make the change in a quiet period instead of waiting for the notice to turn into a deadline.

Where to Start

If you are not sure what your store is running, or whether your plugins will survive the move, I am glad to take a look and give you a plain answer. You can see what I build on my WooCommerce solutions page, and my managed hosting and maintenance plans include keeping your server software current and tested.