WooCommerce 10.8: What's New and What It Means for Your Store

WooCommerce 10.8 shipped on May 26, 2026, followed two days later by a 10.8.1 patch that fixed a regression blocking new merchants from finishing WooPayments setup. Rather than one headline feature, this release is a wide, practical set of changes: a few new merchant-facing tools, a round of performance work under the hood, and compatibility updates to match WordPress 7.0's redesigned admin.

If you're running a WooCommerce store, or managing several for clients, this covers what actually changed in 10.8, what to watch for before you update, and what the 10.8.1 patch fixed.

TL;DR

• WooCommerce 10.8.0 released May 26, 2026; 10.8.1 followed May 28, 2026, with a critical fix for a WooPayments onboarding regression.
• New merchant features include automated post-purchase review request emails, auto-generated coupon codes in email campaigns, email template sync and reset, and custom shipping providers with tracking URL templates.
• Performance work includes new database indexes for transaction lookups and stock reservations, cache priming for product archives and the Store API, and bounded caches to stop wp_options bloat.
• WooCommerce recommends updating WordPress and WooCommerce together, since 10.8 includes roughly 15 pull requests specifically to match WordPress 7.0's new admin styling.
• Back up and test on staging before updating: the release includes four automatic database migrations and a breaking change to how the Orders REST API handles non-order type updates.

Release Timeline

WooCommerce 10.8 followed its usual staged rollout:

• May 19, 2026 — Developer preview published, outlining API changes, performance work, and advisories for custom integrations.
• May 26, 2026 — WooCommerce 10.8.0 released, with 176 pull requests from 67 contributors.
• May 28, 2026 — WooCommerce 10.8.1 released as a fast-follow patch, specifically to fix the WooPayments onboarding issue below.

If your site auto-updates WooCommerce, it's worth confirming it landed on 10.8.1 rather than 10.8.0, given what that patch fixes.

What's New for Merchants

Customer Review Request Emails

WooCommerce 10.8 adds an automated email that invites customers to leave a review after a purchase, with accessible 5-star rating controls and verified-buyer badging on the resulting reviews. It's disabled by default, so stores that want it need to turn it on rather than opt out of it appearing unannounced.

Coupon Auto-Generation in Email Campaigns

Email blocks can now generate a unique coupon code at send time, rather than requiring a store owner to pre-create and manually assign codes for a campaign. This is aimed at personalized promotions, win-back emails, and similar campaigns where a shared code isn't ideal.

Email Template Sync and Reset

WooCommerce now tracks versioning on its default email templates and gives store owners a one-click way to restore a template to its default state. If you've customized a transactional email and it's drifted or broken, this removes the need to rebuild it from scratch.

Custom Shipping Providers

Stores can now define their own shipping carriers, complete with tracking URL templates and provider filtering, instead of being limited to whatever carriers a plugin has hardcoded. This mainly matters for stores using regional or specialty couriers that mainstream shipping plugins don't support out of the box.

Customer Account Dropdown Navigation

The Customer Account block gains an optional dropdown menu for account links, giving stores a more compact navigation option for account-related pages.

Offline Admin Awareness

The WordPress admin now shows a banner when the browser loses internet connectivity, and surfaces a notice when a save fails because of a network issue. It's a small change, but it replaces a confusing failure mode (a save that silently didn't happen) with a clear one.

Performance and Backend Improvements

10.8 continues WooCommerce's ongoing query-reduction work rather than introducing one big performance feature:

• New database indexes speed up transaction lookups and stock reservation checks, which matters most during high-traffic sales events when stock reservations happen rapidly.
• Cache priming was added across product archives, cart data, and the Store API, reducing repeated database work for common storefront requests.
• Coupon _used_by metadata is now lazy-loaded, preventing memory bloat on coupons with very high redemption counts.
• Layered navigation filter caches are now bounded (capped at 1,000 entries by default), protecting the wp_options table from unbounded growth on stores with large or highly filterable catalogs.
• HPOS (High-Performance Order Storage) meta table indexing was optimized for better write performance, a smaller but relevant change for stores that have already migrated to HPOS.

None of these are individually dramatic, but together they reduce baseline database load, which is the kind of improvement that shows up as fewer slow queries under real traffic rather than a headline benchmark number.

WordPress 7.0 Compatibility: Update Both Together

WordPress 7.0 changed how form controls, buttons, dropdowns, and notices look across wp-admin. WooCommerce 10.8 includes around 15 pull requests specifically to keep the WooCommerce admin visually consistent with that redesign: updated Select2 dropdowns, button styling, notice colors, and meta box design, plus hardcoded color values replaced with theme variables.

The practical implication: if you update WordPress to 7.0 without also updating WooCommerce to 10.8 or later (or the reverse), expect visual inconsistencies in the admin, like mismatched button styles or dropdowns that look out of place. It won't break functionality, but it will look unfinished. WooCommerce's own guidance is to update both together rather than staggering them.

10.8 also raised WooCommerce's minimum WordPress requirement to 6.9+, so very old, unmaintained WordPress installs will need a core update before they can take 10.8.

Security Fixes in 10.8

The 10.8 release patches a guest order data vulnerability related to guest fulfillment authorization and the exposure of sensitive order fields. WooCommerce didn't publish exhaustive technical detail on the exploit path in the consumer-facing release notes, which is standard practice for security fixes, but the advisory is enough reason on its own to prioritize this update over letting it sit in a "when I get to it" queue.

The 10.8.1 Patch: What It Fixed

10.8.1, released two days after 10.8.0, fixed a regression in WooPayments onboarding. An upgrade to the downshift package bundled in 10.8.0 broke the CustomSelectControl component, which in turn broke the legal entity type dropdown in the WooPayments setup flow. In practice, that meant new merchants trying to set up WooPayments for the first time could get stuck partway through onboarding.

If you're on 10.8.0, updating to 10.8.1 isn't optional if you have merchants (yourself or clients) setting up payments for the first time. Stores that completed WooPayments onboarding before the 10.8.0 upgrade weren't affected by this particular bug.

Developer Changes to Know About

A few changes in 10.8 are worth flagging specifically for anyone maintaining custom code, extensions, or integrations against a WooCommerce store:

• Orders REST API behavior change: the API now rejects type mismatches instead of silently coercing non-shop_order types. If a custom integration relies on the old, more permissive behavior, it will start failing on this update rather than quietly working around the mismatch. Test any custom order-related integrations before updating production.
• New product.published webhook topic, giving integrations a cleaner signal for publish-state changes instead of inferring it from a generic update event.
• extensionCartUpdate enhancements add more granular, per-address control options for extensions that modify cart behavior.
• Improved tax schema clarity in the Orders REST endpoints.
• Four automatic database migrations run on update: email template sync metadata backfilling, analytics import restoration, order meta indexing corrections, and review page creation. These run automatically, but on a large store, they're worth testing on staging first so you know roughly how long they take and confirm nothing unexpected happens.

How to Update to WooCommerce 10.8 Safely

1. Back up first, especially on stores with a large order history. The automatic database migrations in this release touch order meta and analytics data. MagicWP's on-demand backups let you take a full snapshot immediately before updating, so a rollback is a restore away if anything looks wrong.
2. Test on a staging copy, particularly if you run custom code against the Orders REST API or have a WooPayments onboarding flow that hasn't been touched since before this update. MagicWP's one-click staging tools let you clone a live store, apply the update, and check checkout, payments, and any custom integrations before touching production.
3. Update WordPress and WooCommerce together if you're moving to WordPress 7.0, to avoid the mismatched admin styling described above.
4. Confirm you land on 10.8.1, not 10.8.0, if you're setting up WooPayments for a new store or client during this period.
5. Check storefront and checkout performance after updating, not just before. The query and caching changes in this release generally help, but it's worth confirming on your own catalog size and traffic pattern. MagicWP's managed WordPress hosting with global edge caching and auto-scaling absorbs most of that variability automatically, but a quick check after any core commerce update is good practice regardless of host.

If you're reading this well after WooCommerce has moved past 10.8.x, the same update discipline applies: check the specific release notes for whatever version you're on, but back up, test on staging, and update WordPress and WooCommerce in step with each other regardless of version number.

Frequently Asked Questions

When was WooCommerce 10.8 released? WooCommerce 10.8.0 released on May 26, 2026, followed by the 10.8.1 patch on May 28, 2026.

Do I need to update to WooCommerce 10.8.1 specifically, or is 10.8.0 fine? Update to 10.8.1 if possible. It fixes a regression in 10.8.0 that broke the WooPayments onboarding flow for new merchants by breaking a dropdown component. Stores that already completed WooPayments setup before updating weren't affected, but there's no reason to stay on 10.8.0 once 10.8.1 is available.

Does WooCommerce 10.8 require a specific WordPress version? Yes. WooCommerce 10.8 raised the minimum required WordPress version to 6.9+. It's also specifically aligned with WordPress 7.0's admin redesign, and WooCommerce recommends updating both together.

Will WooCommerce 10.8 break my custom integrations? It might, specifically if your integration relies on the Orders REST API's previous, more permissive handling of non-shop_order type updates. That behavior now returns a rejection instead of silently coercing the type. Test custom order-related code on staging before updating production.

What does the review request email feature do, and is it on by default? It automatically emails customers after a purchase inviting them to leave a review, with accessible 5-star controls and verified-buyer badging. It's disabled by default, so it won't start sending unless you turn it on.

Does WooCommerce 10.8 change anything about HPOS (High-Performance Order Storage)? It includes one targeted improvement: optimized HPOS meta table indexing for better write performance. It doesn't change HPOS's migration process or make HPOS mandatory in this release.

Is the WooCommerce 10.8 update safe to run on a large store? Yes, but treat it like any release with automatic database migrations on a large store: back up first, and test on a staging copy so you know what the migration behavior looks like on your own order volume before it runs on production.

Conclusion

WooCommerce 10.8 isn't a flashy release, and that's largely the point: it's compatibility work for WordPress 7.0, a handful of genuinely useful merchant tools like review request emails and custom shipping providers, and a steady round of performance and security fixes. The one thing worth treating with real urgency is making sure you're on 10.8.1 rather than 10.8.0, given what the patch fixes for new merchant onboarding.

As with any WooCommerce update, back up before you touch a live store, and test on staging first if you run custom code against orders or checkout. The primary keyword here, WooCommerce 10.8, is really shorthand for what every release like it demands: careful, boring update hygiene, applied consistently.