← Update Watch

Update Watch: the WooCommerce 11.2.0 update that cleared addresses at checkout

Update Watch · Published 19 October 2026 · 5 min read

Update Watch looks at real WordPress and WooCommerce updates that broke something, using public sources only. The point isn't to blame plugin developers, who usually fix things fast. It's that even well-run plugins ship changes that surprise some shops, and your process has to allow for that.

What happened

A store owner posted on the WooCommerce support forum that after updating from WooCommerce 11.1.2 to 11.2.0, a shipping method stopped showing correctly at the classic (shortcode) checkout. The same setup had worked on 11.1.2.

A WooCommerce team member first tried to reproduce it on a clean test store, where 11.2.0 worked, and asked for a system report and plugin list. The store owner then tracked the cause to a small piece of code in their theme that removed some billing fields from checkout. The team confirmed what had changed: in 11.2.0, fields removed that way were sent to the server as empty values. That could blank the customer's address, which in turn hid the shipping options that depend on it. The reply said the team planned to restore the old behaviour.

They did. The changelog for WooCommerce 11.2.1, released on 9 October 2026, says the classic checkout's order review and coupon requests were restored so that fields removed with checkout field filters are no longer sent as empty values.

Why it matters

This wasn't a crash, and it didn't affect every shop. A clean test store worked fine. It hit shops with a particular, common customisation: removing checkout fields with code.

The store owner worked around it by hiding the fields with CSS instead of removing them in code, which is a workaround worth knowing. We're only relaying what's in the public thread, and we don't know how many shops were affected.

How you'd catch it

  1. Test the checkout on your real shop right after the update, not on a staging copy that doesn't have your customisations. Add a product, go to checkout, fill in an address, and confirm shipping and payment options appear.
  2. Include the customised parts in the test. If you've removed, reordered or added checkout fields, check that address entry still works end to end.
  3. Update WooCommerce on its own, so a broken checkout points straight at the update that caused it. Our checkout testing checklist covers the steps.
  4. Keep the previous version to hand. The store owner confirmed the same setup worked normally on 11.1.2; rolling back one plugin takes minutes if you have its files ready.
  5. Watch the forum after big releases. A quick look at the support threads a day or two after a release shows whether others are reporting the same thing.

An uptime monitor can't do any of this, because it never goes through the checkout. We explain why in why uptime monitoring misses broken WooCommerce checkouts.

This is the kind of failure PatchSure is being built to catch. The plan: after every update, PatchSure runs a checkout test on each WooCommerce shop. If checkout stops working, it rolls back the update that caused it and tells you in plain English. PatchSure is still in development; join the list to hear when the private beta opens.

Join the early-access list

Summary

Sources