WooCommerce 11.6 makes PHP 8.1 mandatory for stores
On September 29, 2026 WooCommerce announced that PHP 8.1 becomes the minimum with version 11.6, which it plans to ship in February 2027. Stores still on PHP 7.4 or 8.0 will see a dismissible admin notice starting with WooCommerce 11.3 and can keep taking updates up to 11.5. WooCommerce's own recommendation is PHP 8.3 or newer.
The new floor moved back one release, to after the peak selling season
An advisory Brian Coords posted on the WooCommerce Developer Blog on September 29, 2026 sets out the timeline. WooCommerce 11.6, which the company plans to release in February 2027, raises the minimum PHP version to 8.1. Stores get a warning first: from version 11.3, any site still on PHP 7.4 or 8.0 will see an admin notice it can dismiss, flagging the upcoming change, while 11.3 itself continues to run on those older PHP versions.
The decision started as a proposal. A post on the same blog on September 8 suggested making 11.5, then targeted for January 2027, the first release to require PHP 8.1, and invited feedback from store owners, agencies, hosting providers and extension developers. According to the September 29 advisory, community feedback moved the requirement back to 11.6, so stores can test and upgrade once the busiest selling period is over. Until then, sites on PHP 7.4 or 8.0 can go on receiving WooCommerce updates for the remainder of the year, as far as release 11.5.
What the notice shows, and what staying on 11.5 really means
The 11.3 notice shows which PHP version the server is running and suggests asking the host about an upgrade. Nobody has to change PHP to keep running 11.3; the minimum only changes when 11.6 ships. WooCommerce lays out the order of work: look up the PHP version in WordPress admin under WooCommerce > Status, in the Server environment section; agree the change with the host; then back up the site and trial the PHP switch on a staging copy before touching the live store. The checks it lists for that copy cover the checkout and its payment methods, tax and shipping calculations, order handling, scheduled tasks, the theme, extensions and custom code, and once the live server is switched, the store's critical flows get run again. PHP 8.1 clears the new bar, but WooCommerce's current advice is to go to 8.3 or later.
Stores that need longer can hold at 11.5, the final planned version that still supports PHP 7.4 and 8.0. The advisory explains that WordPress usually blocks updating a plugin to a release whose declared PHP minimum the server cannot satisfy, and Brian Coords is explicit that "The PHP requirement change will not deactivate an existing WooCommerce installation." Staying put is still framed as temporary. Under WooCommerce's Security Patch Support Policy, flaws scored CVSS 9 or above have their fixes carried back to older affected releases, across a rolling set of 21 major release series, while other fixes generally land in the newest version alone. The advisory also cautions that a WooCommerce update may leave risks in the PHP runtime itself untouched.
A small share of stores, with security and old dependencies behind the move
The rationale starts with support. In Brian Coords' words, "PHP 7.4 and 8.0 have reached the end of upstream security support." The September 8 proposal gives the end-of-life dates: November 2022 for PHP 7.4 and November 2023 for PHP 8.0. Supporting them, the advisory says, keeps WooCommerce on older releases of its dependencies, adds extra code paths to maintain and widens the testing matrix for every release. Raising the baseline to 8.1 frees WooCommerce and extension authors to upgrade their dependencies and adopt newer language features. There is precedent: the proposal recalls that WooCommerce 8.2 raised the minimum to PHP 7.4, and that WordPress itself runs on PHP 7.4 or newer while recommending 8.3 or newer.
The affected share is small but not zero. In WooCommerce's most recent usage figures, about 7% of tracked stores run PHP 7.4 and 2% run PHP 8.0. For stores that updated WooCommerce in the last twelve months, the combined share of the two versions is nearer 6%, and it keeps shrinking. Stores choose whether to share this data, so the percentages describe a sample, not the whole store base. On the extension side, WooCommerce ran static analysis over the 1,357 extensions currently for sale in its marketplace and found potential PHP 8.1 issues in 0.22% of them, which it will review manually with the developers. WooCommerce also says the scan cannot promise that all the extensions, themes or custom integrations on any one store will survive a PHP upgrade. The marketplace scan is a useful signal, then, but it does not replace a store's own testing.
The sources say nothing about Türkiye, so this section is commentary
Neither source mentions Türkiye. There is no figure for which PHP versions WooCommerce stores in Türkiye run on, neither post names a single hosting company, and shared hosting in Türkiye is not discussed. What follows is therefore not a fact drawn from the sources but explicitly UNALSOFT commentary.
Our reading: for a store that does not manage its own server, the first step is to look up the PHP version under WooCommerce > Status and ask the host whether a move to 8.1 or 8.3 is available. Payment, shipping or invoicing plugins that are not currently sold in the WooCommerce marketplace fall outside the 1,357-extension scan, so testing them on a staging copy is the store's own job. The unknowns deserve the same clarity. The sources do not give: an exact release day for 11.6 (only the February 2027 plan), any release date for 11.3 or 11.5 in the September 29 advisory, an absolute number of affected stores, any data specific to Türkiye, or whether a dismissed notice comes back. We covered the WordPress 7.1.1 security release on September 19; that article is unrelated to this decision.
The UNALSOFT view
We read this advisory as a calendar. The February 2027 plan opens a concrete window to schedule a PHP upgrade without disrupting the peak selling season: find out which PHP version the server runs, talk to the host about moving to 8.3 or newer, then run checkout, shipping, tax and order flows on a staging copy. Aiming at the recommendation rather than the minimum is the sturdier target; WooCommerce itself frames 8.1 as only the floor and 8.3 or newer as its current recommendation. Staying on 11.5 works in the short run, but because fixes below CVSS 9 generally reach only the newest release, it is not a lasting answer. That is why, on the web design side, we treat the PHP version, the backup and the staging copy as separate items on a store's maintenance list. Because the sources carry no data about Türkiye, this article draws no conclusion about the local hosting market.
Which PHP version is your store running on?
A short conversation is enough to plan the PHP version, the backup and the staging test well before February 2027.