Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsWooCommerce currently works with PHP 7.4 and newer, but PHP 8.3 or later is the sensible target for a store today. WooCommerce plans to enforce PHP 8.1 as its minimum with WooCommerce 11.6, currently planned for February 2027. That makes 8.1 a transition floor, not the version to choose for a new or recently upgraded store.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
The short answer
As of October 14, 2026, the official WooCommerce minimum is PHP 7.4. The WooCommerce documentation says the software “works with PHP 7.4 and above,” while its current recommendation is PHP 8.3 or greater. If your host offers it, select PHP 8.3 or a newer supported release rather than stopping at 7.4 or 8.1.
As an Amazon Associate I earn from qualifying purchases.
WooCommerce has announced a higher enforced floor: PHP 8.1 or newer is planned for WooCommerce 11.6, currently scheduled for February 2027. The date and release pairing have already changed once, so treat February as a plan rather than a guaranteed release day. The official developer post dated September 29, 2026 superseded an earlier September 8 proposal that targeted WooCommerce 11.5 in January 2027.
This distinction matters because three different answers are often mixed together:
#1 Best Overall
- Current enforced minimum: PHP 7.4.
- Announced future enforced minimum: PHP 8.1, with WooCommerce 11.6.
- Recommended operating version: PHP 8.3 or newer.
Current and planned PHP requirements at a glance
| PHP version | WooCommerce status today | Position under the announced 11.6 change | Practical decision |
|---|---|---|---|
| PHP 7.4 | Meets the current official floor. | Below the planned PHP 8.1 floor. | Use only as a temporary compatibility position while arranging an upgrade. |
| PHP 8.0 | Above today’s 7.4 floor. | Below the planned PHP 8.1 floor; stores on 8.0 receive the transition notice. | Plan an upgrade before WooCommerce 11.6. |
| PHP 8.1 | Above today’s floor. | Meets the announced minimum for WooCommerce 11.6. | Acceptable for clearing the future floor, but not WooCommerce’s recommended target. |
| PHP 8.3 or newer | Above today’s floor. | Above the announced 8.1 floor. | Preferred target because it matches the official recommendation. |
The table describes WooCommerce’s stated compatibility levels, not a promise that every extension, theme or custom integration will behave identically on every PHP release. Those components need to be checked as part of your own upgrade.
What “minimum PHP version” actually means
The enforced floor
A minimum version is the lowest PHP release WooCommerce is prepared to accept for that point in its support policy. Running at the floor can keep a store eligible for the current WooCommerce release, but it leaves no margin for the next policy change. PHP 7.4 is therefore a compatibility answer, not a recommendation for a new deployment.
Recommended Free Tools
The recommended runtime
A recommendation is the version WooCommerce wants store owners to select when their hosting environment and extensions support it. WooCommerce currently recommends PHP 8.3 or greater. Choosing that target gives a store distance from the announced 8.1 floor instead of requiring another change as soon as the new minimum takes effect.
The announced future floor
WooCommerce’s plan is to make PHP 8.1 the enforced minimum with version 11.6. The developer announcement currently places that release in February 2027, but it does not establish an exact day. The earlier proposal named WooCommerce 11.5 and January 2027; the later September 29 update changed both the WooCommerce version and the month.
Why PHP 8.3 is the better target than PHP 8.1
PHP 8.1 is important because it is the version named in WooCommerce’s upcoming enforcement plan. It is not the version WooCommerce recommends as the end state. If you move a store from 7.4 or 8.0 to 8.1 solely to satisfy the future floor, you meet the announced minimum but remain below the project’s 8.3 recommendation.
Rank #2
PHP 8.3 or newer is the cleaner target when your host presents it as an available, supported choice. It satisfies the current requirement, clears the planned 8.1 floor, and aligns with WooCommerce’s published guidance. The recommendation is conditional on the rest of your stack: confirm that your active theme, extensions and custom code support the selected PHP release before changing production.
There is no evidence in the supplied official material that a store must jump to a particular version newer than 8.3. “8.3 or greater” is the published recommendation, so use the newest option your host supports and your site has passed testing for rather than treating an untested version as automatically safe.
What happens to stores on PHP 7.4 or 8.0
The WooCommerce 11.3 notice
WooCommerce 11.3 adds a dismissible administrator notice for stores running PHP 7.4 or 8.0. The notice is a warning about the planned requirement; it is not an update lock. Dismissing it does not change the PHP version or remove the future compatibility issue.
Updates remain available through WooCommerce 11.5
The official announcement says stores on PHP 7.4 or 8.0 can continue updating through WooCommerce 11.5. That gives those stores a transition window, but it should not be read as permission to postpone indefinitely. The planned 11.6 floor is PHP 8.1, so the upgrade needs to be completed before installing a release that enforces it.
What the notice does not tell you
The announcement does not provide an exact date for when the 11.3 notice will first appear, nor does it give an exact WooCommerce 11.6 release day. If your dashboard shows the notice, record the PHP version, check your hosting control panel and schedule testing; do not wait for the notice to become a blocking error.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How to check your store’s PHP version
- Open the hosting control panel. Look for a PHP selector, runtime settings page or server software panel. The label varies by host.
- Record the active version. Write down the exact PHP version shown for the domain that runs WordPress and WooCommerce. A different staging domain or command-line environment may use another version.
- Check WordPress’s site information. In the WordPress administration area, open the Site Health screen and its information section, then locate the PHP version entry.
- Compare the result with the policy. PHP 7.4 is the current floor; 8.1 is the announced future floor; 8.3 or newer is the recommended target.
- Confirm what the host can offer. Some hosts expose a selector, while others require a support request. Make that check before a WooCommerce update forces the issue.
Do not infer the PHP version from your computer’s PHP installation. WooCommerce runs on the server that hosts WordPress, so the server-side setting is the one that controls the store.
A safe upgrade path to PHP 8.3 or newer
1. Inventory the parts that can break
List the active theme, WooCommerce extensions, payment integrations, snippets and custom plugins. Include anything that adds checkout fields, shipping logic, scheduled tasks or an external API connection. The PHP requirement applies to the WooCommerce runtime, but an extension can still impose its own compatibility condition.
2. Make a recoverable backup
Create a restorable copy of the WordPress files and database before changing the server runtime. Confirm that you know how to restore it, not merely that a backup job reports success. A PHP change can expose an error before you reach the WordPress dashboard, so keep the host’s rollback method available as well.
3. Test on staging first
Clone the store to a staging environment when your host provides one, switch staging to PHP 8.3 or the newer target, and exercise the actions that matter to your business: browsing products, adding items, applying coupons, checking shipping and taxes, placing test orders, issuing refunds and running scheduled jobs. Compare the results with the production site.
4. Inspect errors rather than guessing
Look for PHP fatal errors, warnings and failed background tasks in the staging logs. A blank page, a broken checkout step or a failed scheduled action is a reason to identify the responsible extension or custom code before touching production. Do not hide the symptom by repeatedly switching versions without finding the failing component.
Rank #4
5. Update incompatible components
Bring the theme and extensions to versions that explicitly support your selected PHP release, or ask their developers for guidance. If a custom integration has no maintained release, plan a code change or replacement before the PHP switch. WooCommerce’s minimum does not certify third-party code.
6. Change production during a controlled window
Use the host’s PHP selector or support process to change the production site. Record the previous setting so you can reverse it if necessary. Immediately check the storefront, checkout, order creation, administration screens and scheduled processing.
7. Monitor after the change
Review error logs and real orders after the switch. Keep the rollback path and backup accessible until the store has completed its normal order and scheduled-task cycle. If the host cannot provide the requested version or rollback, open a support ticket before attempting the change.
How the WooCommerce 11.6 change affects upgrade planning
Use the announced timeline as a deadline for preparation, not as a reason to install an untested release early. A store on PHP 7.4 or 8.0 has two separate tasks: move to a PHP version that clears 8.1, and verify that the WooCommerce version being installed still supports the site’s extensions and customizations.
If you are already on PHP 8.1, you satisfy the announced floor but remain below the 8.3 recommendation. Schedule a later move to 8.3 or newer if your host and codebase allow it. If you are on 8.3 or newer and testing is clean, no PHP change is required solely because of the 11.6 announcement.
Because the schedule moved from 11.5/January to 11.6/February within September 2026, check the current WooCommerce developer announcement and release documentation immediately before a major update. The month is a planning signal, not a substitute for the final release notes.
Common mistakes and how to avoid them
Treating PHP 7.4 as the recommended version
It is the current floor, not the target. Running at the floor maximizes the chance of postponing a server change today but leaves the store below the announced 8.1 requirement.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchStopping at PHP 8.1 because it is the future minimum
PHP 8.1 clears the planned enforcement threshold, but WooCommerce recommends 8.3 or greater. Choose 8.1 only when a documented compatibility constraint prevents the recommended target.
Assuming the dashboard notice blocks updates
The 11.3 notice is dismissible and does not block updates. Stores on 7.4 or 8.0 can update through 11.5, although they still need to move before the planned 11.6 enforcement.
Trusting an unqualified third-party requirement
Hosting and blog pages currently disagree: some report 7.4, some 8.1 and some 8.3 as the minimum. Those statements may describe different dates or policies. For the requirement itself, use the official WooCommerce documentation and developer announcements: 7.4 today, 8.1 planned for 11.6, and 8.3 or newer recommended.
Changing PHP without a rollback plan
A version selector makes the change easy to click, not necessarily easy to undo safely. Back up the database and files, test staging, document the old version and verify how your host restores it before changing production.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Decision guide for store owners
- On PHP 7.4: keep the store operating while you arrange testing and move to PHP 8.3 or newer. Do not plan around 7.4 surviving the 11.6 change.
- On PHP 8.0: treat the WooCommerce 11.3 notice as a prompt to upgrade. You remain able to update through 11.5, but 8.0 is below the announced 8.1 floor.
- On PHP 8.1: you meet the announced future minimum, yet you are not at WooCommerce’s recommended 8.3 target. Test a move to 8.3 or newer when your extensions permit it.
- On PHP 8.3 or newer: you match the published recommendation. Continue ordinary compatibility checks when changing WooCommerce, themes or extensions.
Bottom line for 2026
WooCommerce requires PHP 7.4 or newer today, but the practical answer to “which PHP version should I run?” is PHP 8.3 or greater. PHP 8.1 is the announced minimum for WooCommerce 11.6, planned for February 2027, not the preferred destination. If your store is on 7.4 or 8.0, the WooCommerce 11.3 notice is non-blocking and updates remain available through 11.5; use that transition period to test and schedule the move rather than waiting for enforcement.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
