WooCommerce 10.9.4 Released: Key Fixes for VAT Exemption
If you're running WooCommerce with VAT-exempt customers and block checkout, you've likely been bleeding sales without knowing it.
The Block Checkout VAT Bug: What Was Broken
The issue hit specifically during block checkout for authenticated users who should have been exempt from VAT. If your store serves B2B customers or operates in regions where certain buyers carry valid exemptions, the checkout flow was either miscalculating tax or failing to apply the exemption correctly. For logged-in users who've already verified their status, seeing unexpected tax charges at the final step is the kind of friction that sends carts straight to abandonment.
Block checkout — the newer, React-based checkout experience WooCommerce has been pushing — was the affected flow. If you're still on legacy checkout, this particular bug wouldn't have touched you. But WooCommerce is clearly steering toward block checkout as the default path, so staying on legacy indefinitely isn't a viable long-term strategy.
Why This Matters for Your Store's Bottom Line
Think about the scenario: a repeat B2B customer logs in, adds products to cart, reaches checkout, and suddenly sees VAT applied when it shouldn't be. They don't file a support ticket. They don't email you. They close the tab and buy from a competitor who gets checkout right. That lost revenue is invisible unless you're actively monitoring cart abandonment analytics segmented by user role.
VAT exemption logic is one of those "set it and forget it" configurations that store owners rarely audit. But when it breaks, the financial impact compounds silently across every exempt transaction. WooCommerce 10.9.4 patches this before it becomes a pattern of lost trust with your most valuable repeat buyers.
What You Should Do Right Now
Update to 10.9.4 immediately if you're using block checkout and have any VAT-exempt customer roles. This is a targeted patch release, not a feature update — the risk of regression is low, and the fix directly protects revenue.
After updating, run a quick audit: log in as a test account with VAT exemption applied, add items to cart, and walk through block checkout. Confirm the exemption displays correctly and the order total reflects zero or reduced VAT as expected. If you're using a third-party VAT plugin, verify it still plays nice after the update — plugin conflicts are rare in patch releases, but five minutes of testing beats a day of customer complaints.
The Bigger Picture: Block Checkout Is the Future
WooCommerce's developer blog also announced that settings pages are transitioning from legacy PHP to React, with a new Settings UI available for testing. This signals the platform's direction: React-based interfaces are replacing PHP-driven admin pages, and block checkout is part of that same architectural shift.
If you've been deferring the move to block checkout, this VAT fix is another data point that WooCommerce is actively maintaining and improving that experience. Legacy checkout still works, but the engineering investment is flowing toward blocks. Staying current — both on core updates and on testing block checkout — keeps you ahead of the curve rather than scrambling when legacy gets deprecated.
The takeaway is straightforward: update, test your VAT exemption flow, and stop leaving money on the table at checkout. Every friction point between "Add to Cart" and "Place Order" is a potential lost sale — and this one was entirely fixable.