WooCommerce 11.6 Will Require PHP 8.1 or Newer: What Store Owners Need to Do

On September 29, 2026, the WooCommerce team confirmed that WooCommerce 11.6, planned for February 2027, will require PHP 8.1 or newer. Stores whose servers still run PHP 7.4 or 8.0 will be able to update as far as WooCommerce 11.5 and no further until the server is upgraded.

PHP is the programming language that WordPress and WooCommerce run on, and its version is set at the hosting level, not inside the store's admin area. That is why this kind of change catches store owners out: the shop looks fine, updates quietly stop arriving, and nobody notices until a security fix or a payment extension needs a newer release. If your store was built some years ago and the hosting has not been reviewed since, this is a good prompt to check it, with help from your WordPress development team if needed.

What WooCommerce announced on September 29, 2026

The announcement was published on the WooCommerce developer blog under the title New Requirement for WooCommerce 11.6: PHP 8.1+. It states that WooCommerce 11.6 will require PHP 8.1 or newer, which makes WooCommerce 11.5 the last release that can run on PHP 7.4 or 8.0.

The decision followed a public consultation. On September 8, 2026, the team published a proposal to require PHP 8.1 that originally targeted WooCommerce 11.5 and asked hosts, extension developers and merchants for feedback. The confirmed plan moves the change one release later, to 11.6.

It is important to be clear about status. This is an announced future requirement, not something in effect today. According to the WooCommerce releases page, the current stable version at the time of writing is 11.1.2, released on September 22, 2026. The February 2027 date for 11.6 is described by WooCommerce as planned, so it could move.

Why WooCommerce is raising the minimum

The announcement gives two reasons. The first is security: it notes that PHP 7.4 and 8.0 have both reached the end of upstream security support. The earlier proposal puts dates on that, stating that PHP 7.4 reached end of life in November 2022 and PHP 8.0 in November 2023. A store on either version is running on a language runtime that has not received security fixes from the PHP project for years.

The second reason is engineering. The proposal explains that a higher minimum lets the WooCommerce team use newer PHP language features, adopt newer versions of the libraries WooCommerce depends on, drop compatibility code written for old versions, and test against fewer environments.

How many stores are affected

WooCommerce published its own usage figures. The announcement says that approximately 7 percent of tracked stores run PHP 7.4 and 2 percent run PHP 8.0. Among stores that have updated WooCommerce within the past year, it puts the combined figure closer to 6 percent and says that share has been declining steadily. The proposal adds a caveat that these figures come from stores that have opted in to usage tracking, so they are not a complete census.

On extensions, the announcement reports the result of a static analysis of the WooCommerce marketplace: of the 1,357 extensions available for purchase, 0.22 percent showed potential issues. That figure covers marketplace extensions only. It says nothing about plugins obtained elsewhere, themes, or custom code written for a specific store.

What happens to a store that stays on old PHP

The store does not break on the day 11.6 ships. The announcement explains that WordPress normally prevents an update to a plugin version when the server does not meet that version's declared PHP requirement. In practice, a store on PHP 7.4 or 8.0 would simply stop being offered 11.6 and later releases, and would stay on 11.5.

WooCommerce also says that WooCommerce 11.3 will add a dismissible admin notice for stores running PHP 7.4 or 8.0, so administrators should see a warning inside the dashboard before the cutoff.

Security fixes for older WooCommerce versions

Staying on 11.5 is not the same as staying fully patched. WooCommerce's security patch support policy says that when a fix warrants it, defined as a CVSS score of 9 or higher, patches are provided for the last 21 major versions, and that versions older than that window do not receive security patches. Lower-severity security fixes and ordinary bug fixes are outside that commitment, and the releases page states plainly that only the latest version of WooCommerce is considered fully secure.

The recommended version is higher than the minimum

PHP 8.1 is the new floor, not the target. The announcement says WooCommerce recommends PHP 8.3 or newer, and the WooCommerce server requirements page lists PHP 8.3 or greater as the recommended environment.

There is a further point that the minimum figure can obscure. The PHP project's own supported versions page currently lists only the 8.2, 8.3, 8.4 and 8.5 branches as supported. PHP 8.1 is not on that list. Moving a store from PHP 7.4 to 8.1 would satisfy WooCommerce 11.6, but it would still leave the store on a PHP version that the PHP project no longer maintains.

What this means for your business

What follows is our reading of the announcement, offered as guidance.

For a store on modern, managed hosting, this change probably requires nothing. Many hosts moved customers to PHP 8.2 or later some time ago. The businesses most likely to be affected are those with an older store on a server nobody has touched in years, or a store pinned to an old PHP version because a custom plugin or an abandoned extension breaks on anything newer.

That second group has the real work to do. The cost of a PHP upgrade is rarely the version switch itself, which is usually a setting in the hosting control panel. It is the testing and fixing of everything that runs on top: the theme, payment and shipping extensions, and any custom code. Older code can rely on behavior that newer PHP versions changed or removed, and those problems tend to surface in checkout, order emails or scheduled tasks.

The timing is also worth noting for retailers in both the US and UK. February 2027 falls after the holiday trading period, which leaves a window to test in the quieter weeks of the new year. Changing a store's PHP version in November or December, with peak traffic on the way, is a risk most merchants will want to avoid.

What to do next

The WooCommerce announcement sets out a sequence that suits most stores:

• Check the PHP version your store runs. WooCommerce says it is shown under WooCommerce, then Status, in the admin area.
• If it is 7.4 or 8.0, ask your hosting provider about moving to PHP 8.3 or newer.
• Take a backup and make the change on a staging copy of the store first.
• Test checkout, payments, shipping and each extension on staging, then repeat the checks after switching production.

We would add one step before all of that: list every plugin, theme and piece of custom code on the site and note when each was last updated. Anything that has not been maintained for a long time is the most likely source of trouble and may need to be replaced or rewritten, which is better planned than discovered. Developers who maintain their own extensions are asked by WooCommerce to test against PHP 8.1 and to make sure the PHP requirement they declare matches what the code actually needs.

Conclusion

WooCommerce 11.6, planned for February 2027, will stop supporting PHP 7.4 and 8.0, with WooCommerce 11.5 as the last release for those versions. Stores on old PHP will keep running but will fall behind on updates, and only the most severe security fixes are backported. Since WooCommerce recommends PHP 8.3 or newer, the sensible goal is a current, supported PHP version and not just the new minimum.

If your store depends on older extensions or custom code and you want help assessing or carrying out the upgrade, you can request a quote from Entrant Technologies.