I have lost count of the client sites where I opened the ActionScheduler table and found 50,000+ pending tasks sitting there, dragging the database down with them. Almost every time, the analytics import logic was behind it. WooCommerce 10.5 goes after that bottleneck directly, which makes it worth a close look if you run a high-traffic store.
The death of ActionScheduler backlogs
WooCommerce has been handling analytics “fire and forget” style, with every order event spawning its own asynchronous job. That reads fine on a whiteboard. On a busy site it produced race conditions and database contention, and the server ended up spending more time managing the queue than processing orders.
WooCommerce 10.5 defaults to Scheduled Imports instead. Rather than thousands of separate tasks, it works through orders in batches of 100 every 12 hours. Bigger enterprise stores can hook into the new filters to change the frequency and the volume, and the admin dashboard finally shows the status of the import.
<?php
/**
* Tune the WooCommerce 10.5 analytics batch size for high-performance servers.
*/
add_filter( 'woocommerce_analytics_regenerate_batch_size', 'bbioon_increase_analytics_batch' );
function bbioon_increase_analytics_batch( $size ) {
return 250; // Process 250 orders per batch instead of 100
}
?>Experimental performance: REST API and object caching
My earlier take on WooCommerce REST API caching covered where this is heading: a more aggressive caching layer. WooCommerce 10.5 adds experimental Product Object Caching, which stops the same product data being pulled from the database several times inside one request.
That pays off on busy pages where several blocks or widgets all ask for the same product ID. I broke down the mechanics in a post on stopping redundant queries. The “experimental” label is worth taking seriously for now, but this is the direction a scalable WordPress backend is going.
A fix for the “Add to Cart” race condition
Everyone has hit this one: a shopper clicks “Add to Cart” on a variable product before the JavaScript has finished loading, and gets a broken submission or a “Please select product options” error even though they did select them. WooCommerce 10.5 now keeps the Add to Cart button disabled until the variation scripts are ready. It is a small change that takes real friction off mobile users on slow connections.
Customizing shipping tax logic
If you work in a messy tax jurisdiction like the EU, or the Netherlands in particular, the new woocommerce_shipping_tax_class filter is a relief. It lets you work out shipping tax from what is in the cart instead of leaning on one static setting.
<?php
/**
* Example: Use the highest tax rate in the cart for shipping.
*/
add_filter( 'woocommerce_shipping_tax_class', 'bbioon_dynamic_shipping_tax', 10, 2 );
function bbioon_dynamic_shipping_tax( $tax_class, $cart ) {
// Custom logic to determine tax class based on cart contents
return $tax_class;
}
?>If this WooCommerce 10.5 work is eating your dev hours, I can take it off your plate. I have been wrestling with WordPress since the 4.x days.
Final takeaway for developers
This release is not about shiny features. It pays down technical debt that has been sitting in WooCommerce Admin for years: Select2 styles are now scoped with :where() so they stop bleeding into the rest of the UI, and the SEO-friendly category permalinks got another pass. If you run a high-volume store, put it on staging with the Beta Tester plugin before the February 3, 2026 release.
