WooCommerce Is Dropping PHP 7.4: What Your Store Must Do Before January 2027

WooCommerce has proposed raising its minimum PHP requirement from 7.4 to 8.1, targeting the WooCommerce 11.5 release in January 2027. If your store runs an older PHP version, WordPress will simply stop offering you the update — no warning email, no broken site, just a store quietly frozen on an older WooCommerce release while everyone else moves on.

This guide covers who is affected, how to check your own store in under a minute, how to upgrade without breaking checkout — and one important detail that most coverage of this announcement has missed.

What WooCommerce actually proposed

In a developer blog post on 8 September 2026, the WooCommerce team proposed moving the minimum supported PHP version from 7.4 to 8.1, with WooCommerce 11.5 (January 2027) as the target release. The reasoning is straightforward: both PHP 7.4 and 8.0 “are no longer supported by the PHP project,” and continuing to support them means extra testing overhead and code that cannot use modern language features or current dependencies.

On the numbers, WooCommerce reports roughly 7% of tracked stores on PHP 7.4 and about 2% on PHP 8.0, with the combined figure nearer 6% among stores on recent WooCommerce versions and falling. The team adds an important caveat: “WooCommerce usage tracking is opt-in, so these figures do not represent every store, but a representative sample.”

The proposal is still open for feedback, so the exact version and date could move. The direction will not.

What actually happens if you do nothing

This is the part worth being precise about, because it is less dramatic — and more insidious — than people expect.

Your store will not break. WordPress checks a plugin’s declared PHP requirement before offering an update, so a store on PHP 7.4 simply will not be offered WooCommerce 11.5. You keep running 11.4 (or whatever you are on), and you keep receiving dot-release updates for that branch.

The problems arrive later and compound:

• You stop receiving new features and performance work.
• Extensions gradually raise their minimum WooCommerce version, and start dropping compatibility with yours.
• Security fixes for your branch eventually stop.
• Your PHP version is itself already unsupported, so the underlying language stops receiving security patches too.

A year later you are looking at a much larger, riskier jump made under pressure rather than a planned one made calmly.

Step 1: Check your PHP version

Three ways, easiest first.

Method A — WordPress Site Health (no plugins, 30 seconds)

1. In wp-admin, go to Tools → Site Health.
2. Open the Info tab.
3. Expand the Server section.
4. Read the PHP version row.

Site Health also flags an outdated PHP version on its Status tab with a recommendation, so if you have been ignoring a yellow notice there, this is probably it.

Method B — WooCommerce System Status

Go to WooCommerce → Status. The Server environment block shows PHP version alongside details this upgrade will also depend on: PHP post max size, max execution time, and the cURL and MySQL versions. Keep this page open when you upgrade — it is the fastest before/after comparison you have.

Method C — your hosting control panel

Most hosts expose a PHP version selector (cPanel’s “MultiPHP Manager,” or a PHP settings panel in managed WordPress hosts). This is where you will change the version, so it is worth locating now even if you check the version elsewhere.

The detail most coverage missed: don’t upgrade to 8.1

WooCommerce is proposing PHP 8.1 as a minimum. That is not a recommendation to run PHP 8.1.

PHP’s own release schedule is unambiguous. As of September 2026:

Upgrading from 7.4 to 8.1 means doing the work of a major PHP upgrade to land on a branch that has already stopped receiving security fixes — and you would be back for another upgrade almost immediately. PHP 8.3 is the sensible default for most WooCommerce stores today: broad extension compatibility, actively supported into late 2027. Choose 8.4 if your host offers it and your extensions are current.

The exposure is bigger than the telemetry suggests

WooCommerce’s figures come from opt-in usage tracking. WordPress.org publishes PHP version statistics across all WordPress installations that check in for updates, which is a far wider net — and the picture there is less comfortable.

As of September 2026, WordPress.org reports approximately 16.9% of WordPress sites on PHP 7.4, another 4.0% on PHP 8.0, and roughly 6% still on PHP 7.3 or older. That is close to 27% of the WordPress web sitting below the proposed WooCommerce minimum.

Add the 11.3% running PHP 8.1 — which clears the WooCommerce bar but is itself end of life — and around 38% of WordPress sites are running a PHP version with no security support at all.

Two practical conclusions. First, if you are on PHP 7.4 you are not an outlier and your host will have a well-trodden upgrade path. Second, the WooCommerce proposal is a deadline, not the actual risk — the actual risk is that you are running unpatched server software today, which belongs in the same conversation as the rest of your website security posture.

Step 2: Upgrade safely, in the right order

The mistake that causes downtime is switching PHP on a live store and finding out what breaks from customers. Do it in this order instead.

1. Update everything else first

Get WordPress core, WooCommerce and every plugin and theme onto current versions before touching PHP. A large share of PHP 8 errors come from abandoned plugins, and you want to discover that on your terms.

2. Take a full backup

Files and database, downloaded somewhere you control — not only your host’s snapshot. Verify you can actually restore it.

3. Clone to staging

Almost every managed WordPress host offers one-click staging. If yours does not, a local environment works. This step is not optional for a store that takes payments.

4. Switch PHP on staging and hunt for fatals

Set staging to PHP 8.3, then enable error logging in wp-config.php:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Errors will collect in wp-content/debug.log rather than appearing to visitors.

5. Walk the paths that make you money

Do not just load the homepage. Add to cart, apply a coupon, run a real checkout in test mode, trigger order emails, process a refund, run an export, and open every admin screen you use weekly. Then check debug.log again.

6. Fix or replace what breaks

Update the plugin first. If it is abandoned, replace it — a plugin that has not been updated for PHP 8 is a security problem independent of this deadline.

7. Switch production during your quietest hour

Then immediately re-run the checkout test on the live store, watch the error log for 24 hours, and keep the rollback path available. Most hosts let you revert the PHP version in a single click, which is your fastest recovery if something slipped through.

What actually breaks in PHP 8

For developers and anyone reading a debug.log for the first time, the majority of real-world WooCommerce breakage clusters into a handful of patterns.

• Passing null where a string is expected. Deprecated in 8.1 and extremely common in older code — trim( $maybe_null ) and similar. Noisy, usually not fatal, but it floods logs.
• Removed functions. create_function(), each() and the mysql_* family are gone. These are hard fatals.
• Stricter type juggling. PHP 8 changed how strings and numbers compare. Loose comparisons in pricing, tax or shipping logic can silently produce different results — this is the category that causes wrong numbers rather than error messages, so test calculations deliberately.
• Method signature and return type mismatches in classes that extend WooCommerce or WordPress core, which became fatal errors rather than warnings.
• Custom functions.php snippets. Code pasted in from tutorials years ago is rarely maintained by anyone and is a frequent culprit.

If you maintain extensions and are targeting WooCommerce 11.5, the same proposal notes you will be able to use newer PHP features — but that maintaining compatibility with older WooCommerce releases at the same time may require parallel code paths.

While you’re here: what shipped in WooCommerce 11.1

WooCommerce 11.1.0 landed on 1 September 2026 with 561 pull requests from 77 contributors, and it is backwards compatible with a database update required. The highlights worth knowing:

• Variation image galleries are now on by default for all stores, and the separate Additional Variation Images extension is being retired into core with automatic data migration.
• Store API and REST requests are 30–42% faster, through block registration that skips requests which do not render blocks. This is a meaningful win for headless stores and anything polling the API.
• Right of order withdrawal, the EU compliance feature letting customers submit withdrawal requests from My Account. It is disabled by default — we walked through what the EU withdrawal button means for WooCommerce stores separately.
• Video in product galleries as an experimental, disabled-by-default beta supporting locally uploaded video.
• Cleaner admin order screens for virtual products, and changes to order item deletion that prevent accidental removal.

Common mistakes

• Upgrading PHP before updating plugins. It turns one clear problem into several overlapping ones.
• Testing only the homepage. PHP errors in WooCommerce concentrate in cart, checkout, email and admin code paths that a homepage load never touches.
• Landing on PHP 8.1. It satisfies the requirement and is already end of life.
• Treating January 2027 as the deadline. Your PHP version stopped receiving security patches years ago if you are on 7.4. That is today’s problem.
• Leaving WP_DEBUG_DISPLAY on. On a live store this leaks file paths to customers and looks broken.

Frequently asked questions

Will my store break in January 2027?
No. WordPress will withhold the WooCommerce 11.5 update from stores that do not meet the PHP requirement. Your store keeps running; it just stops moving forward.

Is this confirmed or still a proposal?
It is a proposal published on 8 September 2026, with feedback open on the exact release date and minimum version. Plan for it regardless.

Which PHP version should I choose?
PHP 8.3 for most stores. PHP 8.4 if your host offers it and your extensions are actively maintained. Avoid 8.1 and 8.2 — 8.1 is end of life and 8.2 loses security support at the end of 2026.

How long does the upgrade take?
Changing the version is a one-click operation. The testing around it is the real work — budget a couple of hours for a simple store, and considerably more if you run custom code or a large extension stack.

Will PHP 8 make my store faster?
Usually, yes — PHP 8.x is significantly faster than 7.4 on typical WordPress workloads, and WooCommerce 11.1’s API improvements compound with it. Benchmark before and after with one of the website speed test tools so you know what you actually gained.

My host says they will upgrade me automatically. Do I still need to test?
Yes. An automatic upgrade does not test your checkout. Ask your host for the scheduled date and do your staging pass before it arrives.

What to do this week

Open Tools → Site Health → Info → Server and write down your PHP version. If it starts with 8.2, 8.3, 8.4 or 8.5, you are fine and this is a calendar note for later. If it starts with anything else, book an hour on staging in the next fortnight — you have four months before the deadline, and the upgrade is far cheaper done calmly than in January.