Skip to main content
Back to Blog
Security
October 27, 2026
5 min read

WooCommerce and PHP 8.1: Is Your Store Ready?

WooCommerce stores run on PHP, and PHP 8.1 is already unsupported. Here is how to check your store, what to test, and how to move to a current version safely.

PHPWooCommerceWordPressE-commerce
WooCommerce and PHP 8.1: Is Your Store Ready?

Does WooCommerce require PHP 8.1?

WooCommerce publishes its own minimum PHP version on its official requirements page, and that number changes between releases, so check it there rather than trusting a blog post. What matters more is that PHP 8.1 itself is already unsupported, so a store should be on a newer line regardless of the minimum.

Is PHP 8.1 still supported for my store?

No. The PHP team states that "PHP 8.1 and older no longer receive updates" on its 2026 news page. Its supported versions list now shows only 8.2 through 8.5, per the PHP supported versions page. That applies to every WordPress site, including stores.

A store that takes payments carries more risk than a brochure site, because it handles customer data and orders. For more on 8.1, read Is PHP 8.1 Still Supported?.

Which PHP version should a WooCommerce store run?

Aim for PHP 8.3 or 8.4 unless a key extension blocks you. Both are supported for years: 8.3 until December 31, 2027 and 8.4 until December 31, 2028, per the supported versions page. PHP 8.2 works today but loses security fixes on December 31, 2026.

PHP versionSecurity fixes endFit for a store
8.1 or olderAlready endedNo, plan an upgrade now
8.2December 31, 2026Short-term only
8.3December 31, 2027Good, mature
8.4December 31, 2028Good, test extensions first
8.5December 31, 2029Newest, test carefully

Why does PHP matter more for a store than a blog?

A store takes real money and holds customer details, so downtime and breaches cost more. php2shell, announced October 21, 2026, lets an attacker run commands on the server without a password. CISA added both flaws to its exploited list on October 26, per the CISA KEV feed.

If you take card payments, your card processor may also expect timely patching. Details differ, so check with your processor or compliance advisor. Our php2shell explainer covers the flaw.

Which parts of a WooCommerce store break on a new PHP version?

Usually the extensions, not WooCommerce itself. Payment gateways, shipping calculators, subscription tools, booking add-ons and custom checkout fields are the usual suspects. A store with many extensions has more to test, so list every one you run before you start. The checklist below covers the main areas.

  • • Payment gateways. Run a real test order.
  • • Shipping and tax plugins. Check rates at checkout.
  • • Subscriptions and memberships. Test renewals.
  • • Email templates. Confirm order emails still send.
  • • Custom theme code. Look for errors in the log.

If something breaks, read My Site Broke After a PHP Upgrade.

How do I check which PHP version my store runs?

Use the free PHP version checker or, inside WordPress, open Tools, then Site Health, then Info, then Server. The tool reads what your site reveals to visitors, and some hosts hide it, so the Site Health screen is more reliable.

Write down the exact number. You will need it for your host and for any quote.

How do I upgrade a WooCommerce store without losing orders?

Never test on the live store. Work on a staging copy, and avoid changes during busy sales hours. Orders placed on the live site while you test on a copy do not carry over, so the final switch should happen during a quiet window.

  • • Back up files and database, then confirm the restore works.
  • • Create a staging copy on the new PHP version.
  • • Place test orders with each payment method.
  • • Fix or replace any failing extension.
  • • Switch live at a quiet hour with the rollback ready.
  • • Recheck orders, emails and stock for a day.

What does a WooCommerce PHP upgrade cost?

Our WooCommerce / Complex WP Upgrade is $4,500 fixed, with a 30-day fix of regressions. It covers checkout, payment and email flow testing plus a staged cutover, usually in one to two weeks. If you are unsure how complex your store is, start with the $295 PHP Health Check.

We cannot promise every extension will work on a new PHP. We will tell you which will not before the live switch. For other price points, see How Much Does a PHP Upgrade Cost?.

Should I wait for WooCommerce to force the change?

No. Waiting means the change happens on someone else's schedule, often at a bad time such as a holiday sale. A planned upgrade on a staging copy costs less and risks less than an emergency fix on a live store with a broken checkout.

PHP 8.1 is already past its support window, so the reason to move exists today, whatever any single plugin requires. Pick a quiet week, not the weeks before a big promotion.

What is the next step?

Check your PHP version, open WooCommerce's own requirements page, and plan the move before December. Book a call and tell us your host, your extensions and your current PHP version. We will tell you which package fits your store and how long the work should take.

Before the switch, take a full backup and test checkout, payment and shipping on a copy of the store. Orders keep arriving while you work, so pick a quiet hour for the final change and check a test order afterward.

This article is general information, not legal or compliance advice. Written by Eliran Yihye, founder of Cuanto Labs, on October 27, 2026.

Eliran Yihye, founder of Cuanto Labs

Cuanto Labs

Related articles

What we build

Cuanto Labs is a software team in Fort Lauderdale, Florida. We build custom web apps, AI agents and Shopify stores at a fixed price, with the timelines and prices published up front.

Working in South Florida? See how we run projects in Miami, Fort Lauderdale and Aventura, or across the rest of the region.

Ready to start your project?

Let's discuss how Cuanto Labs can help your business grow with custom software, AI solutions, and more.

Get in Touch
Book a free call