WooCommerce 11.6 is scheduled for February 2027, and it will require PHP 8.1 or newer. Stores still running PHP 7.4 or 8.0 have time to prepare, but this is not a change to make five minutes before opening orders for the day. PHP sits underneath WordPress, WooCommerce, the theme, payment gateways, shipping tools, and custom code. A careful upgrade tests the whole selling system, not just the homepage.

WooCommerce plans to show a dismissible warning in version 11.3 for affected stores. That warning is advance notice, not a shutdown message: WooCommerce 11.3 will continue working on PHP 7.4 and 8.0. The actual minimum changes with WooCommerce 11.6. Here is what store owners should check now so the deadline becomes routine maintenance instead of an emergency.

What is changing in WooCommerce 11.6?

WooCommerce currently runs on PHP 7.4 and newer, while recommending PHP 8.3 or newer for an updated hosting environment. With WooCommerce 11.6, the declared minimum will become PHP 8.1.

The schedule matters:

• WooCommerce 11.3: stores using PHP 7.4 or 8.0 should begin seeing an admin notice that identifies the current server version and recommends contacting the host.
• WooCommerce 11.5: this is planned to be the final release that remains compatible with PHP 7.4 and 8.0.
• WooCommerce 11.6: planned for February 2027, this release requires PHP 8.1 or newer.

WordPress normally blocks a plugin update when the server does not meet the plugin’s declared PHP requirement. WooCommerce says the change will not automatically deactivate an existing installation. That avoids one kind of failure, but staying frozen on an older release is not a healthy long-term maintenance plan.

Why WooCommerce is raising the PHP minimum

PHP is the programming language that runs WordPress and WooCommerce on the server. Older PHP branches eventually stop receiving upstream security fixes. PHP 7.4 and 8.0 are already past upstream security support, which means the PHP project no longer issues supported fixes for newly discovered problems in those branches.

Supporting older runtimes also keeps WooCommerce and extension developers tied to older dependencies and additional compatibility paths. Raising the floor gives developers access to newer language features and a smaller test matrix.

WooCommerce reports that about 7% of tracked stores use PHP 7.4 and 2% use PHP 8.0. Among stores that updated WooCommerce during the prior year, the combined share is closer to 6%. Those figures come from opt-in usage tracking, so they are a sample rather than a count of every store.

How to check your store’s PHP version

In WordPress admin, go to WooCommerce > Status. Under Server environment, find the PHP version row. You can also look under Tools > Site Health > Info > Server.

If the version begins with 7.4 or 8.0, the store needs a plan before WooCommerce 11.6. If it shows 8.1, the site meets the announced minimum, but that does not mean every theme and extension is current or that the environment is the best available choice. WooCommerce currently recommends PHP 8.3 or newer when the site’s software supports it.

Do not confuse WordPress, WooCommerce, and PHP versions

These are separate layers. WordPress might be version 7.x, WooCommerce might be version 11.x, and PHP might be version 8.x. Updating one does not automatically update the others. The hosting provider controls the available PHP versions, while WordPress and WooCommerce are managed as software inside the hosting account.

A safe WooCommerce PHP upgrade checklist

1. Make an inventory before changing the server

Record the active WordPress theme, child theme, plugins, payment gateways, shipping integrations, tax tools, subscriptions, memberships, product add-ons, analytics connections, and custom code. Note who maintains each item and whether a current update is available.

This is also the right time to remove inactive plugins and abandoned tools. Old code does not become safer because it is switched off in the WordPress dashboard, and unused extensions make compatibility reviews harder.

2. Confirm that a restorable backup exists

Create a fresh backup of both files and the database. Confirm where it is stored, when it completed, and how it would be restored. A backup icon in a hosting panel is not the same as a tested recovery plan.

For an active store, think about orders that may arrive between the backup and a rollback. Restoring yesterday’s database can remove today’s orders, customer records, stock changes, and subscription activity. Plan the maintenance window and rollback method around live commerce data.

3. Clone the store to staging

A staging site lets you change PHP without risking the public checkout. It should resemble production closely enough to expose real compatibility problems, including the same theme, extensions, PHP modules, and representative settings.

Keep staging private and prevent it from sending real customer emails, charging payment methods, publishing product feeds, or competing with the live site in search results.

4. Update supported software first

Bring WordPress, WooCommerce, the theme, and maintained extensions to versions that support the target PHP release. Read changelogs for payment, subscription, shipping, tax, and checkout extensions rather than assuming every green update badge means the same thing.

If a critical plugin has no current release, no support response, or an unclear PHP requirement, resolve that dependency before changing production. The deadline may be months away, but replacing a business-critical extension can take longer than expected.

5. Change PHP on staging

Ask the host to move the staging site to the target version, or use the hosting panel if the process is documented and reversible. PHP 8.1 meets the announced WooCommerce 11.6 minimum. PHP 8.3 or newer is WooCommerce’s current recommendation, but the right target depends on the compatibility of the complete site.

After the change, review the PHP error log, WordPress Site Health, WooCommerce status report, scheduled actions, and browser console. A page that appears normal can still hide failed background jobs or deprecation warnings.

6. Test the buying journey, not just page loads

A reliable test follows the paths that produce revenue and customer service work:

• Open simple and variable products, select variations, and confirm prices and stock.
• Add, update, and remove cart items; test coupons, fees, and taxes.
• Complete checkout with each important payment method in test mode.
• Verify shipping rates, local pickup, address validation, and delivery estimates.
• Confirm order emails, customer accounts, refunds, cancellations, and status changes.
• Test subscriptions, renewals, bookings, memberships, bundles, and custom product fields if the store uses them.
• Check mobile navigation, product galleries, forms, search, and account pages.

Also review integrations outside WordPress: accounting exports, fulfillment systems, CRM updates, email marketing, webhooks, product feeds, and analytics events.

7. Schedule production with monitoring

Choose a lower-traffic window, take another current backup, document the previous PHP version, and make sure someone can reverse the change. After switching production, clear server and page caches and repeat a short critical-flow test.

Watch error logs, payment failures, scheduled actions, incoming orders, form submissions, and customer messages after launch. “The homepage loaded” is not enough evidence that an ecommerce upgrade succeeded.

What if an extension breaks on newer PHP?

Capture the exact error, PHP version, WooCommerce version, extension version, and steps that reproduce the problem. Check the extension’s documentation and changelog, then contact its developer with that information.

Do not permanently hide errors and assume the problem is solved. Displaying errors to shoppers should normally be disabled on production, but the underlying error log still needs review. If an abandoned plugin blocks the upgrade, compare replacement options and plan a controlled migration.

Can a store stay on WooCommerce 11.5?

Temporarily, yes. WooCommerce says stores can remain on 11.5 while resolving hosting or extension constraints. Its security policy backports the most severe vulnerabilities across a rolling set of release series, but other fixes generally ship only in the latest release. An older WooCommerce branch also cannot repair vulnerabilities inside an unsupported PHP runtime.

Treat 11.5 as breathing room, not the destination. Record why the upgrade is blocked, who owns the fix, and the date for another test.

A practical timeline for store owners

1. This week: check the live PHP version and save the WooCommerce status report.
2. This month: inventory the theme, extensions, integrations, and custom code; remove abandoned dependencies.
3. Before peak sales: build or refresh staging, verify backups, and test the target PHP version without rushing production.
4. After peak sales: resolve compatibility issues and schedule the live PHP change with a rollback plan.
5. Before WooCommerce 11.6: confirm production runs a supported PHP version and repeat the critical checkout test.

WooCommerce PHP 8.1 requirement FAQ

When will WooCommerce require PHP 8.1?

WooCommerce says version 11.6, planned for February 2027, will require PHP 8.1 or newer.

Will the warning in WooCommerce 11.3 break my store?

No. The planned notice is an advance warning for stores on PHP 7.4 or 8.0. WooCommerce 11.3 will continue working on those versions.

Should every store move directly to PHP 8.3?

WooCommerce recommends PHP 8.3 or newer, while PHP 8.1 is the announced minimum for version 11.6. Test the target version against the site’s theme, extensions, integrations, and custom code before production.

Can the host change PHP for me?

Usually, yes. The host controls the server environment. Ask for the available PHP versions, staging options, backup process, rollback method, and any compatibility scan they provide.

CodeForce can help with WooCommerce and WordPress maintenance, connected business systems, website recovery planning, and a cleaner customer journey with Checkout Clarity Pro.

Sources

• WooCommerce Developer Blog: New requirement for WooCommerce 11.6
• WooCommerce server recommendations
• WooCommerce guide to updating PHP and WordPress
• PHP supported versions
• WooCommerce security patch support policy

Not sure whether an old plugin, custom checkout, or hosting setup will survive the PHP change? Book a CodeForce intro call before the upgrade becomes urgent.