WooCommerce 3.6 Released with New Product Blocks and Major Performance Improvements

WooCommerce 3.6 was released this week after six months in development. Store owners with sites running on WordPress 5.0+ will now have access to eight new product blocks, including hand picked products, featured products, products by category/attribute, sale products, new products, top rated, products, and best selling products.

These blocks were previously available as a feature plugin but have now been rolled into WooCommerce core. The plugin now requires WooCommerce 3.6 and will continue to be used for iterating and exploring future WooCommerce block editor features.

Performance improvements were one of the major focuses for this version, which introduces product data lookup tables. WooCommerce core developers’ long term plan is to move post meta to custom tables and a feature plugin is currently in development towards this goal. In the meantime, lookup tables provide a structured index for product data that speeds up querying. This version also brings improvements to transient invalidation, changes to REST API initialization, caching improvements, and more.

WooCommerce developer Timmy Crawford highlighted a few frontend performance improvements in the 3.6 release post:

  • A 62% improvement in the load time when ordering and filtering products
  • Reduced overall load time by bypassing inactive webhooks
  • Reduced the load time for pages with category or product attribute lists
  • Reduced load time of product pages with attributes

This release also includes the controversial new marketplace suggestions that advertise official extensions inside the WooCommerce admin. The setting for turning them off can be found under the “Accounts & Privacy” section of the admin.

For the full list of additional enhancements in 3.6, check out the release post or view the plugin’s changelog. The release should be backwards compatible with sites running WooCommerce 3.0+, but testing how the update affects themes and extensions is highly recommended before updating. Version 3.6.1 was released today to fix some issues 3.6.0 had with certain hosting environments.

Would you like to write for WP Tavern? We are always accepting guest posts from the community and are looking for new contributors. Get in touch with us and let's discuss your ideas.


  1. Beware of this update. We ran it on a site and then I was not able to add an item to the cart. We reverted back to 3.5.8.


    1. A few kinks being worked out. 3.6.2 is just around the corner, and addresses the cart issue.

      Overall, 3.6 is a huge improvement.


      1. Do they even test?!

        An update for a shopping plugin which renders the shopping cart useless is not an improvement at all, sorry.


  2. I am looking forward having all meta data in custom tables where WooCommerce does not make use of _posts and _postmeta any longer. This will make continuous developing and staging on separate servers and websites much easier than it is now.

    This release is a good step forward to that goal.

    Congrats to all contributors.


  3. Why the WooCommerce 3.6 first included an option to either enable or disable usage tracking and then suddenly 3.6.1 and it’s no more there?

    I have upgraded to WooCommerce 3.6.1 a day ago. I have found that the Usage Tracking feature, which was earlier released with 3.6, has been removed (ref: https://www.cloudways.com/blog/woocommerce-3-6-features/).


    1. In WooCommerce 3.6.1 usage tracking and marketplace suggestions settings can be found from
      WooCommerce > Settings > Advanced > WooCommerce.com


  4. Hi, I did update to 3.6.1 and it gave me so many problems, I had to go back. Emails were not being sent for orders. Login created problems and what not. Took around 2-3 hours to restore dB and files. But now happy that everything works. Please don’t upgrade now. Upgrade after 15 days or so.


  5. WooCommcerce wishlist plugin auto change product title to wishlist title after WooCommer upgrades, we have to deactivate wishlist.


    1. That issue has existed on previous versions of the plugin.


Comments are closed.