WooCommerce Plans to Require PHP 8.1: How to Prepare Your Store

WooCommerce plans to require PHP 8.1 or newer starting with WooCommerce 11.5, which is currently targeted for January 2027. If your store runs PHP 7.4 or 8.0, it will stop receiving new WooCommerce feature releases at that point. As of 25 September 2026 this is still a proposal open for feedback, but you should plan as if it will ship, and move to PHP 8.3 or 8.4 rather than the bare minimum.

What exactly has WooCommerce announced?

On 8 September 2026 the WooCommerce engineering team published Proposed change: Requiring PHP 8.1 or newer for WooCommerce 11.5 and beyond on the official developer blog. The key points:

• Target version: WooCommerce 11.5.
• Target date: January 2027.
• What ends: support for PHP 7.4 and PHP 8.0 in future WooCommerce versions.
• Status: a proposal. The team says it will "review the feedback and usage data before confirming the target release and minimum PHP version", and promises advance notice before the release.

The post cites WooCommerce's opt-in usage data: about 7% of tracked stores run PHP 7.4 and about 2% run PHP 8.0. Among stores that updated WooCommerce within the last year, the combined share is closer to 6% and falling.

This is not the first bump. WooCommerce 8.2 raised the minimum to PHP 7.4 in 2023, with a similar advance notice (New Requirement for WooCommerce 8.2: PHP 7.4+).

Where are we in the release timeline?

The most recent release at the time of writing is WooCommerce 11.1.0, released on 3 September 2026. WooCommerce ships a new version roughly every five weeks, so 11.2, 11.3 and 11.4 should arrive before 11.5.

That gives most stores around three to four months. It sounds like a lot, but it overlaps with Black Friday and the holiday season, when most stores freeze changes. Realistically, your safe window to change PHP is October and early November 2026, or January 2027 after the peak.

What happens if my store stays on PHP 7.4 or 8.0?

Nothing breaks on the day 11.5 is released. According to the proposal:

• WooCommerce 11.5 would declare "Requires PHP: 8.1".
• WordPress would then not offer the update to stores that do not meet it.
• Your store keeps running its current WooCommerce version and still gets dot releases for that branch.
• WooCommerce will not change your PHP version or deactivate itself.

The real cost is slower and quieter. WooCommerce's security patch policy backports fixes to the last 21 major versions only when a vulnerability scores CVSS 9 or higher. Lower severity fixes land in new versions only. Extensions will also start requiring WooCommerce 11.5+ and PHP 8.1+, so you gradually lose updates for your payment gateway, shipping and tax plugins too.

And the PHP runtime itself is already unsupported. PHP 7.4 reached end of life on 28 November 2022 and PHP 8.0 on 26 November 2023 (php.net EOL list). No security fixes are published for either.

Which PHP version should you move to?

Do not stop at 8.1. PHP 8.1 reached end of life on 31 December 2025, so it is already unsupported. WooCommerce itself recommends PHP 8.3 or newer in both its server requirements and its PHP update guide.

PHP version	Security support ends	Meets WC 11.5 proposal?	Our view
7.4	Ended 28 Nov 2022	No	Upgrade now
8.0	Ended 26 Nov 2023	No	Upgrade now
8.1	Ended 31 Dec 2025	Yes	Too old to target
8.2	31 Dec 2026	Yes	Only as a short stop
8.3	31 Dec 2027	Yes	Safe default
8.4	31 Dec 2028	Yes	Good target if plugins support it
8.5	31 Dec 2029	Yes	Test carefully first

Dates are from php.net supported versions. WooCommerce's server requirements page lists PHP 8.3 or greater, "tested up to PHP 8.4", so 8.3 or 8.4 is the practical sweet spot for a production store today. Going 7.4 straight to 8.3 is one project, not three. The testing effort is almost the same as for 8.1.

How do you check your current PHP version?

There are two quick ways inside WordPress admin:

1. WooCommerce > Status, then scroll to Server environment and read the PHP version row. This is the path WooCommerce's own update guide uses.
2. Tools > Site Health > Info, then open the Server section.

Also check your hosting control panel. Some hosts run a different PHP version for the command line (WP-CLI, cron) than for the web server. If your scheduled actions or imports run through system cron, make sure both are upgraded.

How do you check plugin and theme compatibility?

This is where PHP upgrades actually fail. WooCommerce core has supported PHP 8.x for a long time. Your custom theme, an old extension or a snippet in functions.php usually has not been tested.

Step 1: Inventory everything that runs PHP

List every active plugin, the theme and child theme, mu-plugins, and custom code (functions.php, Code Snippets plugin entries, custom plugins). For each one, note the installed version, the latest available version, and the "Requires PHP" and "Tested up to" values from its readme or changelog.

Flag anything that has not been updated in over two years, anything bought from a vendor who has disappeared, and anything encoded with ionCube or similar loaders. Encoded files need a loader built for your target PHP version.

Step 2: Scan the code statically

PHPCompatibilityWP is a PHP_CodeSniffer ruleset made for WordPress projects. It flags functions and syntax that break on your target PHP version. Run it against wp-content on a copy of the site:

vendor/bin/phpcs -p wp-content/plugins wp-content/themes --standard=PHPCompatibilityWP --extensions=php --runtime-set testVersion 8.3-

Static scans produce false positives and miss runtime behaviour, so treat the output as a to-do list, not a verdict.

Step 3: Know the usual breaking changes

From our upgrade projects, the same few issues cause most PHP 7.4 to 8.x failures. All are documented in the official PHP migration guides:

• Removed functions in PHP 8.0, such as create_function(), each() and money_format(). Old plugins calling them cause a fatal error (PHP 8.0 incompatible changes).
• String to number comparison. In PHP 8.0, 0 == "foo" is now false. This quietly changes logic in old pricing, discount and form validation code.
• Warnings that became errors. Many internal functions now throw TypeError or ArgumentCountError instead of a warning. A checkout that "worked with warnings" on 7.4 can fatal on 8.x.
• Deprecations in 8.1. Passing null to non-nullable parameters of built-in functions is deprecated (PHP 8.1 deprecations). This is not fatal, but it floods logs and can hide real errors.

Step 4: Test on staging, with real flows

Clone production to staging, switch staging to the target PHP version, and turn on error logging. Then click through the flows that make you money.

Pre-upgrade checklist

Use this before you change PHP on production:

• Current PHP version confirmed in WooCommerce > Status, and the command line PHP version checked with your host.
• Target version chosen (8.3 or 8.4) and confirmed as available on your hosting plan.
• Full inventory of plugins, themes, mu-plugins and custom snippets.
• All plugins, theme and WooCommerce updated on staging first, on the current PHP version.
• Abandoned or encoded plugins identified, with a replacement plan.
• PHPCompatibilityWP scan done and findings fixed or accepted.
• Staging switched to target PHP with error logging enabled.
• Tested: product pages, cart, coupons, checkout with every payment method, refunds, subscriptions renewals if used, order emails, account pages.
• Tested background jobs: scheduled actions, stock sync, ERP or accounting exports, feeds.
• Logs in WooCommerce > Status > Logs checked for new fatal errors after testing.
• Fresh full backup (files and database) taken right before the production switch.
• Switch planned for a low traffic hour, outside sales campaigns, with someone watching orders for 24-48 hours.
• Rollback plan agreed: most hosts let you switch PHP back in one click, so know where that setting is.

What should agencies and extension developers do?

The proposal asks for feedback on what still blocks PHP 7.4 or 8.0 sites, including specific extensions and custom integrations. If you maintain client stores, now is the time to audit the whole portfolio and sort sites into three groups: ready, needs plugin updates, needs code work.

The post also notes that extensions supporting older WooCommerce versions may need compatibility layers. If you ship a custom plugin to clients, decide now whether you will keep a PHP 7.4 branch or move on with WooCommerce.

When to get help

If your store runs on PHP 7.4 or 8.0 and you have custom code or older extensions, the upgrade is usually a few days of careful staging work rather than a one-click change. Our WooCommerce upgrade service covers PHP and HPOS upgrades from $600, with a fixed scope agreed before we start. If you are not sure what state the store is in, the free WordPress health check is a good first step.