Back to Community
Home / Community / Plugin → Jetpack

Troubleshooting Common Jetpack and WooCommerce Conflicts

20 threads Sep 16, 2025 Plugin → Jetpack

Content

Many WordPress site owners rely on both Jetpack and WooCommerce. However, updates to either plugin can sometimes introduce unexpected conflicts that break key functionality on your online store. Based on numerous community reports, this guide outlines the most common issues and provides steps to diagnose and resolve them.

Common Symptoms of Jetpack and WooCommerce Conflicts

Users have reported a range of problems that appear only when Jetpack is active, including:

  • Checkout page elements like "Apply Coupon" or "Returning Customer" login becoming unclickable.
  • JavaScript errors in the browser console, such as "Uncaught TypeError: Cannot read properties of undefined (reading 'addAction')".
  • Critical errors when adding products to the cart.
  • Payment method fields (e.g., Stripe) not loading or functioning correctly.
  • WooCommerce email previews failing to render in the admin area.
  • A general slowdown of the site or 503 errors.
  • Products not loading correctly on shop pages.

Why Do These Conflicts Happen?

These issues are typically not permanent flaws but are often caused by one of the following:

  • Plugin or Theme Conflicts: The most common cause. Another plugin or your theme may be loading scripts or styles that interfere with the interaction between Jetpack and WooCommerce.
  • Caching: Aggressive caching mechanisms can sometimes serve outdated JavaScript files, leading to errors.
  • Connection Issues: An unstable connection between your site and WordPress.com servers can cause unexpected behavior, especially with features that rely on this connection like the WooCommerce mobile app.
  • Deprecated Code: In rare cases, a recent update may deprecate a function that another plugin or theme was still using, throwing warnings or errors.

Step-by-Step Troubleshooting Guide

1. The Basic Checks

Always start with these simple steps:

  • Update Everything: Ensure WordPress core, WooCommerce, Jetpack, and your theme are all updated to their latest versions. A recent update may have already fixed the issue.
  • Clear Caches: Clear any server-side caching (e.g., object caching), plugin-based caching (e.g., WP Rocket, W3 Total Cache), and your browser cache.

2. Conflict Testing: The Most Important Step

To identify if another plugin or your theme is causing the problem, you need to perform a conflict test. The safest way to do this on a live site is using the free Health Check plugin.

  1. Install and activate the Health Check plugin.
  2. Go to Tools > Site Health > Troubleshooting and enable troubleshooting mode. This will deactivate plugins and switch to a default theme only for you, while your visitors see the site normally.
  3. In troubleshooting mode, enable only WooCommerce and Jetpack. Also, switch your theme to a default WordPress theme like Twenty Twenty-Four.
  4. Test if the problem persists (e.g., try to apply a coupon on the checkout page).
  5. If the issue is gone: The conflict is with another plugin or your theme. Reactivate your plugins one-by-one, testing after each activation, to find the culprit. Finally, reactivate your theme to test it.
  6. If the issue remains: With only WooCommerce, Jetpack, and a default theme active, the conflict may be more complex. Note any error messages and consider the next steps.

3. Investigate Error Messages

If you see a specific error message in your browser's console (like the common "addAction" error), this is a vital clue. Searching for the exact error message online can often lead to specific solutions or confirm it's a known issue being worked on.

4. Check and Repair the Jetpack Connection

Some issues, particularly those affecting the WooCommerce mobile app, can stem from a faulty connection.

  1. Go to Jetpack > Dashboard in your WordPress admin.
  2. Check if there are any connection errors reported.
  3. If needed, disconnect and then reconnect Jetpack to your WordPress.com account. You can find guides for this on the Jetpack support site.

5. Disable Specific Jetpack Modules

While not a permanent solution, temporarily disabling Jetpack modules can help pinpoint if a specific feature is causing the problem. Go to Jetpack > Settings and try deactivating modules like "Lazy Images" or "Custom CSS" to see if it resolves the issue.

What If the Problem is a Known Bug?

If your conflict testing confirms the issue occurs with only Jetpack and WooCommerce active, it may be a bug introduced in a recent update. The Jetpack team is generally responsive to these reports. If you suspect a bug:

  1. Perform the conflict test to confirm the issue is isolated.
  2. Note your WordPress, WooCommerce, and Jetpack versions.
  3. Note any specific error messages from your browser console or server logs.
  4. Temporarily rolling back to a previous version of Jetpack (e.g., 13.1.3) can serve as a workaround while a fix is developed. Always do this on a staging site first.

By methodically working through these steps, you can usually identify the root cause of conflicts between Jetpack and WooCommerce and restore full functionality to your online store.

Related Support Threads Support