WooCommerce PHP 8.1 Requirement: What Changed and What to Do

WooCommerce is dropping PHP 7.4 and 8.0: version 11.6, due in February 2027, needs PHP 8.1 or newer. The requirement does not switch off a running store, but a store that stays on the old runtime stops receiving new WooCommerce releases after 11.5. Check the runtime and test the extensions now, not in February.

What changed in the WooCommerce PHP 8.1 requirement

WooCommerce 11.6 is the first release that needs PHP 8.1, and 11.5 is the last planned release for PHP 7.4 and 8.0.

The official WooCommerce developer announcement sets the steps. WooCommerce 11.3 adds a dismissible admin notice for stores on PHP 7.4 or 8.0. The notice shows the server's PHP version and recommends talking to the host, and 11.3 keeps working on those versions. Stores on the older runtimes can keep updating through 11.5 while they prepare.

Based on community feedback, the team pushed the requirement to 11.6 so stores have time to test and upgrade after the peak selling season. Use that window rather than wait for the last month.

The reasoning is security and maintenance. PHP 7.4 and 8.0 have reached the end of upstream security support. Supporting them also keeps WooCommerce tied to older dependency versions, extra code paths and a wider test matrix for every release.

Who does the PHP runtime deprecation affect?

It affects stores and extension authors still on PHP 7.4 or 8.0. Stores already on 8.3 or newer only need routine regression testing; 8.1 and 8.2 meet the minimum but are at or near end of life.

WooCommerce's own opt-in usage figures show about 7% of tracked stores on PHP 7.4 and 2% on PHP 8.0. The share is lower among stores that updated WooCommerce in the past year.

The marketplace scan found few issues; custom code was not scanned. A static analysis of the 1,357 extensions for sale flagged potential PHP 8.1 issues in 0.22% of them. WooCommerce adds that the screening cannot guarantee every extension, theme or custom integration on a given store will work. Custom plugins, older themes and one-off integrations are outside that scan. Code written for an older PHP can fail with a fatal error at checkout or in a background job. Test in this order: custom plugins and themes first, then marketplace extensions that have not had an update in a long time, then everything else.

Extension developers and agencies get their own instructions in the announcement: test on PHP 8.1 and on the PHP version you recommend, and check the declared PHP requirement and dependency constraints against the code you ship. Report compatibility issues on GitHub with the PHP and WooCommerce versions and steps to reproduce.

What actions must engineering teams take before version 11.6?

Find the PHP version on every environment, test the full store on PHP 8.1 or newer in staging, then upgrade production and only then update to 11.6.

Start when the 11.3 notice appears rather than in February. WooCommerce recommends PHP 8.3 or newer, with 8.1 as the minimum for 11.6. Aim for 8.3 rather than the bare minimum: the PHP project's unsupported branches list shows PHP 8.1 itself reached end of life on 31 Dec 2025. Treat the change with the same discipline as an ecommerce platform migration checklist: a written list of flows, a staging copy and a rollback plan. If the audit turns up a long list of broken plugins, that is also a signal the store may have outgrown its plugin stack.

How to test your store stack for PHP 8.1 compatibility

Scan the code, copy the store to staging on the new PHP version, and walk the flows the announcement lists before touching production.

The WordPress requirements page covers the platform itself; extensions and custom code are yours to test. Follow these steps:

1. Check the runtime. In WordPress admin, open WooCommerce > Status and read the PHP version under Server environment; run php -v on the server for the command-line version.
2. Scan the code. Run the PHPCompatibility 10.x ruleset for PHP_CodeSniffer against wp-content/plugins and wp-content/themes, targeting PHP 8.1. The project notes its PHP 8.1 coverage is incomplete, so a clean scan does not replace the staging run.
3. Build a staging copy. Back up the store and copy the database, media and plugins to a staging site running the new PHP version.
4. Walk the critical flows. Test checkout and payment methods, shipping and tax calculations, order management, scheduled jobs, the theme, extensions and custom code, as the announcement recommends.
5. Read the logs. Turn on WP_DEBUG_LOG on staging, trigger the Action Scheduler jobs, and check wp-content/debug.log for fatal errors and deprecation warnings before switching production.

Running the compatibility scan in GitHub Actions CI/CD workflows helps stop new code from bringing old syntax back after the upgrade.

Why WooCommerce needs a newer PHP baseline

A PHP 8.1 floor lets WooCommerce and extension developers update dependencies and use newer PHP features without keeping older code paths alive.

Some newer tooling already assumes it: the WooCommerce Dual API documentation lists PHP 8.1+ as a requirement. Extensions built on such tooling cannot run on PHP below 8.1.

Deployment details beyond the announcement

The announcement covers updates through WordPress admin; deployments that bypass it and the command-line runtime need their own checks.

WordPress normally refuses to update a plugin when the server does not meet its declared PHP requirement, and the change will not deactivate an existing WooCommerce install. Deployments that install plugins with Composer or scripts bypass that check. Set the PHP version in Composer's platform config and pin WooCommerce below 11.6 until the runtime is upgraded.

The announcement also does not say whether the 11.3 notice checks the command-line PHP that cron jobs and deployment scripts use, which is why the checklist above covers both runtimes.

Staying on 11.5 has a security cost. Under WooCommerce's Security Patch Support Policy, fixes for vulnerabilities rated CVSS 9 or higher are backported within a rolling window of 21 major release series. Other fixes generally ship only in the latest release, and the announcement warns that a WooCommerce patch may not address risks in a PHP runtime that no longer gets upstream security updates. Staying on 11.5 is not worth it beyond the time the upgrade needs.

What to do next

This week, open WooCommerce > Status on production and note the PHP version. If it reports PHP 7.4 or 8.0, or anything below the recommended 8.3, ask your host for PHP 8.3 on a staging copy and run the compatibility scan across custom themes and plugins. Work through the critical flows on staging, fix what breaks, then upgrade production and repeat the same checks before updating to 11.6. If a hosting or extension constraint needs more time, stay on 11.5 knowingly and put a date on the upgrade. If your team cannot fit the audit and fixes alongside regular work, our WooCommerce development team can run the compatibility audit and staging verification before WooCommerce 11.6 ships.