A WooCommerce plugin conflict happens when two plugins, or a plugin and your theme, try to change the same part of your store in incompatible ways. To find it safely, copy your store to staging, switch to a default theme, turn off everything except WooCommerce, then turn plugins back on one at a time until the problem returns.
Conflicts usually show up at the worst moment: right after an update, during a sale, or on the checkout page. This guide walks through how to spot one, read the logs, isolate the cause without disrupting customers, and fix it in a way that holds up after the next round of updates.
What is a WooCommerce plugin conflict?
A plugin conflict is a clash between pieces of code that each work on their own but break when they run together. Common causes are two plugins loading different versions of the same script, a plugin calling a function that another plugin or WooCommerce has changed, or a theme overriding WooCommerce templates that a plugin expects to be up to date.
The more plugins that touch the cart and checkout, the more places a conflict can appear.
What are the signs of a plugin conflict?
A conflict rarely announces itself. These are the symptoms that most often point to one, especially if they started after an update or a new install:
- The checkout spinner keeps loading, or the Place order button does nothing.
- A payment method disappears or returns an error at checkout.
- The site shows “There has been a critical error on this website” or a blank white page.
- Cart totals, coupons or shipping rates calculate incorrectly.
- Product pages, the cart or the mini cart lose their layout or stop updating.
- Admin screens such as Orders or Products fail to load or save.
- Order emails stop sending, or orders do not reach connected tools such as your ERP or email platform.
If you are seeing checkout failures specifically, our guide on fixing WooCommerce checkout errors covers related causes such as gateway settings and caching.
What should you do before you start troubleshooting?
Preparation keeps a small problem from becoming a bigger one. Before you change anything:
- Take a full backup of files and the database, and confirm you know how to restore it.
- Use a staging site if your host offers one. Troubleshooting on a copy means real customers never see a broken page.
- Write down what changed recently. Plugin, theme, WooCommerce, WordPress or PHP updates are the usual triggers.
- Record the exact steps that reproduce the problem, such as “add product X, apply coupon Y, pay by card”.
- Clear caches in your caching plugin, CDN and browser so you are testing current code.
WooCommerce’s own guide to testing for plugin and theme conflicts also recommends updating plugins and themes first, since a newer release may already fix the clash.
How do you check error logs for clues?
Logs often name the plugin at fault before you deactivate anything. Check these places:
- WooCommerce fatal error logs. Go to WooCommerce > Status > Logs and open any file starting with fatal-errors. WooCommerce records PHP fatal errors there, and the file path in each entry usually points to the plugin folder involved.
- WordPress debug log. If debugging is enabled and set to log to a file, errors are written to wp-content/debug.log. Turn debug logging off again when you are done.
- Recovery mode email. When WordPress hits a fatal error, Recovery Mode emails the site admin a special login link and pauses the failing plugin or theme for that admin session only.
- Browser console. For checkout or cart issues with no PHP error, open your browser’s developer tools and look for JavaScript errors in the Console tab while you reproduce the problem.
Note the plugin names and file paths that appear. They give you a short list to test first.
How do you find which plugin is causing the conflict?
Use a controlled process of elimination. Work through these steps on staging, testing the same action after every change:
- Reproduce the problem using the steps you recorded, so you know exactly what failure you are looking for.
- Switch to a default theme such as Storefront or a current default WordPress theme. If the problem disappears, your theme or its WooCommerce template overrides are the likely cause.
- Deactivate all plugins except WooCommerce and any extension directly involved, such as the payment gateway for a checkout issue.
- Test again. If the problem is gone, a conflict is confirmed. If it remains, the cause may be WooCommerce itself, a must-use plugin, server settings or custom code in your theme.
- Reactivate plugins one at a time, testing after each. With many plugins, turn on half at once, then narrow down within the half that brings the problem back.
- Confirm the pair. When the problem returns, check whether that plugin breaks things on its own or only alongside a specific other plugin or your theme.
What if you cannot use a staging site?
The free Health Check and Troubleshooting plugin lets you disable plugins and switch themes for your own browser session while visitors see the normal site. WooCommerce documents this in its Health Check troubleshooting guide. Two cautions from that guide: results can differ from truly disabling plugins, and troubleshooting mode does not put your payment gateway into test mode, so any order you place is a real charge.
How do you fix a plugin conflict once you find it?
Finding the plugin is half the job. Choose the fix that removes the clash without creating new risk:
- Update or roll back. If the conflict began with a new release, check whether a patch is out. If not, rolling back to the previous version can restore sales while the developer fixes it.
- Report it to the developer. Send the replication steps, the log entries, and your WordPress, WooCommerce, PHP and plugin versions. Clear reports get faster fixes.
- Remove overlap. Two plugins doing the same job, such as two caching or two checkout field plugins, are a common source of clashes. Keep one.
- Replace the plugin. If a plugin is abandoned or repeatedly breaks with WooCommerce updates, move to a maintained alternative.
- Add a compatibility fix. Sometimes a small code change, such as adjusting script loading order, lets both plugins run. Keep it in a child theme or a custom plugin so updates do not erase it.
When a fix needs custom code, our WooCommerce plugin development team can build and test it, and our guide on when to build vs buy a WooCommerce plugin can help you choose between a custom fix and a replacement.
Example: checkout stops working after an update
This is an illustrative scenario, not a specific client project. A store updates several plugins on a Monday. By the afternoon, customers report that the checkout spinner never stops.
- The fatal-errors log is empty, but the browser console shows a JavaScript error from a checkout field plugin.
- On staging, switching to Storefront does not help, which rules out the theme.
- With only WooCommerce and the payment gateway active, checkout works. The conflict is confirmed.
- Reactivating plugins in halves brings the error back when the checkout field plugin and an optimization plugin are both on.
- The optimization plugin was delaying the checkout field plugin’s script. Excluding that script from delay settings fixes checkout, and the change is noted in the store’s maintenance log.
How can you prevent plugin conflicts in the future?
You cannot remove every risk, but a few habits make conflicts rarer and easier to fix:
- Test updates on staging before applying them to the live store, especially for payment, shipping and checkout plugins.
- Update in small groups rather than all at once, so you know which change caused a problem.
- Read changelogs for major versions and check that each plugin supports your WooCommerce version.
- Remove unused plugins and avoid plugins with overlapping features.
- Avoid big updates in the days before a major sale, and keep a recent backup at all times.
- Place a test order after every update round and check that emails and connected tools still work.
For a structured routine, see our WooCommerce maintenance and support service, which covers staged updates, monitoring and fixes.
WooCommerce plugin conflict checklist
- Backup taken and restore process confirmed
- Staging copy created, or Health Check troubleshooting mode ready
- Recent changes and exact replication steps written down
- Caches cleared before testing
- WooCommerce fatal-errors log, debug.log and browser console checked
- Default theme tested
- All plugins except WooCommerce and the affected extension deactivated, then reactivated one at a time
- Conflicting plugin or pair confirmed
- Fix chosen: update, rollback, developer report, removal, replacement or compatibility code
- Test order placed and emails and integrations checked after the fix
Frequently asked questions
How do I know if a plugin conflict is breaking my WooCommerce store?
Look for problems that started right after an update or a new plugin: a checkout that spins or fails, a missing payment method, a “critical error” message, or broken layouts. Switching to a default theme and turning off other plugins on a staging copy will confirm whether a conflict is the cause.
Is it safe to deactivate plugins on a live WooCommerce store?
It is risky. Deactivating payment, shipping or tax plugins on a live store can break orders for real customers. Test on a staging copy instead, or use the Health Check plugin’s troubleshooting mode, which changes plugins only for your own logged-in session.
Where can I find WooCommerce error logs?
Go to WooCommerce > Status > Logs and open any file whose name starts with fatal-errors. If WordPress debugging is turned on and set to log to a file, you will also find a debug.log file in your wp-content folder.
Can a theme cause the same problems as a plugin conflict?
Yes. Themes can override WooCommerce templates and load their own scripts, so an outdated theme can break checkout or cart pages just like a plugin. That is why the standard test switches to Storefront or a default WordPress theme before checking plugins.
What should I do if two plugins I need conflict with each other?
Update both, then send each developer clear steps to reproduce the issue along with any log entries. If no fix arrives, look for an alternative plugin that does the same job, or have a developer write a small compatibility fix so both can run together.
Need help with a WooCommerce plugin conflict?
If a conflict is affecting your checkout or you would rather not test on your own store, we can help. EcomSupport360 provides reliable support for WooCommerce stores, from finding the cause to fixing it and keeping updates safe. Book a call and tell us what changed and what you are seeing.






