An international customer from Germany browses your US-based store. They see a price that correctly excludes local state sales tax. They leave the site, but when a local customer from California visits the exact same product page from a different computer, the store accidentally displays the German VAT structure or a cached tax price matrix, leading to either illegal overcharging or undercalculated profits.

This critical compliance bug is caused by an over-aggressive server-level object cache configuration. While page caching handles HTML documents, object caching tools like Redis or Memcached store raw database database queries—including calculated tax loops. If your tax configuration parameters fail to incorporate a unique caching token key for separate visitor geographical locations, the server serves the first compiled tax calculation to every single subsequently arriving visitor, regardless of their location.

The Solution

Resolving sticky tax calculations requires forcing WooCommerce to split its internal database queries using localization parameters.

  1. Activate Geolocation Cache Splitting: Navigate to WooCommerce > Settings > General. Find Default customer location and ensure it is set to Geolocate (with page caching support). This forces a unique URL hash tracking layer that separates cache structures.

  2. Configure Object Cache Group Exclusions: If you utilize a dedicated server with Redis object caching enabled, open your wp-config.php file and add the WooCommerce transients group to the non-persistent exclusion mapping array:

    PHP
     
    define('WP_REDIS_DISABLE_BANNERS', true);
wp_cache_add_non_persistent_groups(array('counts', 'wc_sessions', 'transients'));

  3. Flush Database Transients Safely: Go to WooCommerce > Status > Tools and execute Clear WooCommerce transients to completely destroy old, stale tax computation fragments stored inside your server's memory bank.