Run a WooCommerce store with hundreds of variations and you eventually hit the variations wall. I have seen sites where get_variation_prices() alone accounted for close to half a second of latency. WooCommerce 10.5 finally refactors WooCommerce variation price caching, and the bottleneck it goes after has been sitting there for years.
WooCommerce already cached these prices in a transient, but the cache key was the problem. It serialized entire callback objects. So if a plugin modified prices through an object-oriented hook, any shift in that object’s state, down to a logger property nobody cares about, threw out the whole cache. On complicated setups that got expensive fast.
The shift to stable signatures
WooCommerce 10.5 adds a CallbackUtil class to deal with that. Rather than serializing the whole object, it builds a stable signature from the class and method names only. WooCommerce variation price caching then stays consistent between requests even when your object state wobbles.
The numbers back it up. In official testing with 800 variations, execution time fell from roughly 500ms to 40ms. That is the same direction as the WooCommerce 10.4 update, which was also mostly about performance.
What dynamic pricing developers need to do
This part matters if your extension changes variation prices based on something dynamic: user roles, time of day, cart contents. Leave those factors out of the cache hash and customers get served the wrong cached price. You now have to hook into woocommerce_get_variation_prices_hash.
<?php
/**
* Example: Adding User ID to the variation price cache hash.
* This ensures different users don't see each other's cached discounts.
*/
add_filter( 'woocommerce_get_variation_prices_hash', 'bbioon_add_user_to_variation_hash', 10, 3 );
function bbioon_add_user_to_variation_hash( $price_hash, $product, $for_display ) {
$price_hash[] = get_current_user_id();
return $price_hash;
}Legacy support and the WooCommerce 11.0 roadmap
The team is playing it safe. A new filter, woocommerce_use_legacy_get_variations_price_hash, defaults to true for now, so the old serialization behavior stays active until you opt out of it yourself. In WooCommerce 11.0 (August 2026) the default flips to false.
Test it early. Return false on that filter and you get the faster path today, as long as you have already checked that your dynamic pricing hooks are hash-aware. The official developer advisory has the rest of the detail.
If variation price caching is eating your dev hours, I can take it on. I have been working with WordPress since the 4.x days.
Summary for shop owners
If your variable product pages feel sluggish, this update is worth the upgrade on its own, since it cuts the server load needed to render prices. Have your developer look over any custom pricing logic before the 11.0 rollout so you do not end up showing stale prices.
