WooCommerce Proposes PHP 8.1 Minimum for Version 11.5

I have been in this game long enough to know that a proposed platform requirement is not a small memo. It is a bill you will eventually pay, either in a rushed hosting migration or in a quiet Sunday morning that you would rather have spent on anything else. This week WooCommerce filed one of those bills.

Brian Coords published a proposal on the WooCommerce developer blog on September 8, formally asking the community whether WooCommerce 11.5 — currently pencilled in for January 2027 — should drop PHP 7.4 and 8.0 and require PHP 8.1 or newer. It is a proposal, not a decision. But WooCommerce proposals of this shape have a strong tendency to ship.

If you run a Woo store, or you build them for other people, you have about four months to look at your fleet and decide what you are doing about it. Not eight. Not next year. Four.

What is actually new

The proposal is on the WooCommerce developer blog: raise the PHP floor to 8.1 starting with WooCommerce 11.5, which is scheduled for January 2027. That would end support for PHP 7.4 and PHP 8.0 in Woo core. Stores on older PHP would stay on the last compatible Woo release and would not receive automatic updates to 11.5 or beyond — WordPress already blocks the install path in that case, so nothing dramatic happens at the store level except that new versions simply do not appear.

The numbers the post cites for the current fleet are worth reading carefully. PHP 7.4 sits around seven percent of tracked stores. PHP 8.0 is roughly two percent. On recent WooCommerce versions the combined share is about six percent and declining. That is small, but seven percent of the WooCommerce install base is not a small number in absolute terms. It is a lot of stores whose owner may not read the developer blog.

The rationale in the proposal is the one you would expect. PHP 7.4 reached end-of-life in November 2022. PHP 8.0 reached end-of-life in November 2023. Neither version has received a security patch from the PHP project in years — any fixes on those branches now come from third parties, not from php.net. Moving the floor to 8.1 lets the core team use union types, attributes, null-safe operators, match expressions, named parameters, and readonly properties without polyfills. It also lets them adopt newer dependencies that already require 8.1+, and it cuts the CI matrix.

Two pieces of context that the proposal does not spell out but you should know. First, WooCommerce has always sat one step ahead of WordPress core on this. The last bump — 7.3 to 7.4, with WooCommerce 8.2 in October 2023 — followed the same playbook. Second, WordPress core currently requires PHP 7.4 as its floor and recommends PHP 8.3 or greater per the requirements page. WooCommerce today already recommends PHP 8.3 or newer in its server documentation. So the 8.1 minimum is not a jump ahead of Woo’s own recommended stack — it is Woo finally raising the hard floor to something below where it has been pointing site owners for a while.

One awkward wrinkle. PHP 8.1 itself is out of active support and, on the PHP project’s own schedule, security-only life ended at the end of 2025. That has already come up in the comments on Brian’s post, and it is a fair point. Choosing 8.1 as the new floor gets you the language features but does not put you on a supported PHP branch. If Woo is going to bother raising the floor, some contributors are arguing it should be 8.2 at minimum, or 8.3 in line with WordPress’s own recommendation. Watch that debate; it is the one that will shape the final decision.

Why it matters for WordPress and WooCommerce people

For agencies, the practical impact is not the language feature list. It is what happens on client sites between now and January.

If you run a portfolio of Woo stores on shared hosting in Turkey, Central Europe, or the UK, a non-trivial number of them are still on PHP 7.4 or 8.0. Not because anyone chose that — because the hosting control panel defaulted to it years ago and nobody changed it. When Woo 11.5 lands and those stores silently stop receiving updates, you will not get a phone call. You will get a support ticket six months later after a payment gateway release breaks compatibility with the stale Woo version, and the store owner will not connect the dots. You will.

For extension developers the calculation is different. If Woo core drops 7.4 and 8.0, you can drop them too on the next major of your extension without breaking WPCS compatibility rules. Union types in the codebase, readonly value objects, first-class callable syntax — the things that were awkward workarounds become idiomatic. Every extension author I know has been carrying a small pile of polyfills and defensive code for PHP 7.4. That pile can go in the bin.

For hosts, the interesting question is what the default PHP version in their control panel is on the day this ships. If your host is still shipping PHP 8.0 as the default for new WordPress installs — and some of them are — you have a bigger problem than one Woo release. You have a fleet full of stores that will fall off the update train through no fault of their owners.

What I would do (or not do) about it

Four things, in the order I would do them.

First, audit your fleet this week. Not next month. wp cli info on each site, or a one-liner that hits phpversion() via WP-CLI eval on every environment you own. Anything on 7.4 or 8.0 gets flagged. If you run twenty stores, this is an afternoon. If you run two hundred, it is a spreadsheet.

Second, do not upgrade straight to 8.1. If you have to move a store off 7.4, move it to 8.3. PHP 8.1 will be dead as a target long before the average site is due for its next maintenance window, and you do not want to do this migration twice. WordPress recommends 8.3 and WooCommerce’s own server documentation recommends 8.3. That is your target.

Third, test each store on a Playground or a staging environment before you flip the switch. Old themes and unmaintained plugins are where PHP upgrades bite. Deprecation notices in themes written for PHP 5.6 will happily throw warnings for hours. Run WP-CLI’s PHP compatibility scan first, then upgrade, then run the checkout end-to-end. Boring, disciplined, unglamorous — the way you avoid Monday morning calls.

Fourth, leave a comment on the proposal if you have skin in this game. Coords explicitly asks for community input on the timeline, on extension and theme dependencies, and on the choice of 8.1 versus something newer. Woo takes public feedback seriously on these threads. If you are running stores on hosts where the 8.1 upgrade is genuinely difficult, or if you would rather see the floor set at 8.2 or 8.3, say so on the record.

The bigger point is that platform floors move whether you plan for them or not. The only real choice is whether you move first, on your own schedule, or last, with someone else’s clock ticking.