Introduction
WooCommerce stores depend on many actions running without full page reloads. AJAX helps these actions work quietly in the background. Customers can add products, update carts, and change checkout details faster. When WooCommerce AJAX not working becomes an issue, these actions may stop. Buttons may stop responding, while cart totals remain unchanged. Checkout sections may also keep loading without showing updated information.
A WooCommerce AJAX error can have several possible causes. JavaScript, caching, plugins, themes, security rules, or hosting may interfere. Finding the exact failed request makes troubleshooting much easier. This first part explains AJAX and its common warning signs.
What Does “WooCommerce AJAX Not Working” Mean?
AJAX means Asynchronous JavaScript and XML. Modern AJAX requests can also exchange information using JSON data. AJAX lets a browser communicate with the server quietly. Customers can remain on the same page during this process.
For example, someone may click an Add to Cart button. The browser sends a background request to WooCommerce. WooCommerce processes it and sends the required response back. The page can then update without a complete browser refresh.
When this communication fails, a WooCommerce AJAX function not working issue appears. The button may respond visually but complete no action. Sometimes customers see a spinner that never stops loading.
A failed request may affect only one store feature. However, JavaScript errors can also break several interactive functions. A serious JavaScript error may even affect unrelated website scripts.
Where Does WooCommerce Use AJAX?
WooCommerce uses background requests across several customer-facing store areas. Add to Cart actions are one common example. Cart totals and checkout details can also update dynamically.
Shipping options may refresh after customers change their address. Payment methods can change when checkout conditions are updated. AJAX may also support product filters, searches, and mini-cart features.
The exact behavior depends on your theme and installed extensions. Newer WooCommerce blocks can also update cart information without reloads.
Therefore, WooCommerce AJAX issues may appear differently across stores. One store may have cart problems but normal checkout behavior. Another store may experience problems only during checkout.
If checkout is also affected, review WPCustomify’s guide about WooCommerce cart and checkout page problems. It explains related checkout failures and common troubleshooting areas.WooCommerce Cart & Checkout Page Is Not Working
Common Signs WooCommerce AJAX Is Not Working
A WooCommerce AJAX problem can appear in several store areas. The exact symptom depends on which request fails. WooCommerce recommends checking browser Network activity and JavaScript errors when dynamic store functions stop responding correctly.
1. AJAX Add to Cart Button Does Nothing
Customers click Add to Cart, but nothing happens afterward. The product does not enter the cart, and no confirmation appears. This often points toward blocked AJAX requests, JavaScript errors, theme conflicts, or scripts failing before WooCommerce completes the request.
2. Products Appear Only After Page Refresh
A product may enter the cart correctly on the server. However, the visible cart remains unchanged until refreshing the page. This behavior can indicate a failed frontend update, JavaScript conflict, caching problem, or incomplete AJAX response from WooCommerce.
3. Cart Count Does Not Update
The cart icon may continue showing an old item count. Customers successfully add products, but the displayed number remains unchanged. This symptom can involve cart refresh scripts, theme cart components, caching systems, or JavaScript that fails during frontend updates.
4. Mini Cart Does Not Refresh
The mini cart may continue displaying outdated products or totals. Newly added products may appear only after reloading the page. Theme customizations, cached dynamic content, JavaScript conflicts, and cart refresh behavior should be checked when this WooCommerce AJAX issue appears.
5. Cart Quantity or Totals Do Not Change
Customers may increase product quantities without seeing updated totals. Sometimes the quantity changes visually, while pricing remains unchanged. This may indicate failed background processing, JavaScript errors, caching interference, or another script preventing WooCommerce from applying the returned cart information.
6. Checkout Keeps Loading
An endless checkout spinner is an important AJAX warning sign. WooCommerce uses background requests for the order review area. URL mismatches, JavaScript conflicts, invalid responses, or insufficient memory can prevent these requests from completing correctly.
7. Shipping Methods Do Not Refresh
WooCommerce normally updates shipping options when relevant customer details change. If rates remain unchanged after entering another address, JavaScript or AJAX processing may have failed. Plugin conflicts, checkout customization, server errors, or invalid background responses can cause this behavior.
8. Payment Methods Do Not Update
Available payment options may depend on billing information and checkout conditions. When those options remain outdated, a WooCommerce AJAX request failed may be involved. JavaScript problems can prevent WooCommerce from loading the correct payment choices after customer information changes.
9. Checkout Order Review Does Not Update
The order review section should reflect products, taxes, shipping, and totals. If it remains outdated or displays a loading spinner, inspect the AJAX response. WooCommerce notes that unexpected HTML instead of expected JSON can break checkout updates.
10. Browser Shows 403, 404, or 500 AJAX Errors
Developer Tools may show failed requests with specific HTTP codes. A 403 indicates access restrictions, while 404 points toward an unavailable endpoint. A 500 generally indicates server-side processing failure. These codes help identify the WooCommerce AJAX error source.
11. AJAX Request Times Out
Some requests remain pending before eventually failing. This happens when the server takes too long to return a response. Heavy plugins, slow database queries, limited hosting resources, or complex processing can contribute to AJAX timeouts on WooCommerce stores.
12. JavaScript Console Shows Red Errors
Red JavaScript errors can reveal why a WooCommerce AJAX function not working issue occurs. One serious script error may interrupt other WooCommerce functions on the same page. Check the first meaningful Console error before changing several website settings.
How to Diagnose WooCommerce AJAX Not Working
When WooCommerce AJAX not working becomes a problem, avoid random fixes. First, find which request fails and where it fails. A careful diagnosis prevents unnecessary changes across your live store.
Browser tools, WooCommerce logs, and system checks provide useful evidence. These checks can separate JavaScript errors from server-side problems. They also help identify plugin, theme, or caching conflicts.
What to Do Before Troubleshooting WooCommerce AJAX
Create a complete website backup before making technical changes. Your backup should include website files and the database. Testing on a staging site is safer when available.
Next, record exactly when the WooCommerce AJAX error appears. Note the page, product, customer action, and visible message. Also note any recent plugin, theme, or server changes.
Clear your browser cache before starting deeper tests. You can also clear WordPress and server caches temporarily. However, avoid changing several settings at the same time. Otherwise, finding the actual cause becomes much harder.
If your problem affects cart or checkout functions, review relatedWooCommerce troubleshooting resources on WPCustomify. Comparing related symptoms may help narrow the affected store area.
Test the Store in an Incognito Window
Open your WooCommerce store using a private browser window. Then repeat the action that normally creates the problem.
Incognito testing removes many stored cookies and cached browser files. If AJAX works privately, browser cache may be involved. A browser extension can sometimes interfere with JavaScript requests too.
Also test another modern browser when possible. This simple comparison helps separate local browser problems from store-wide WooCommerce AJAX issues.
Check the Browser Console for JavaScript Errors
Chrome, Firefox, Edge, and Safari include developer tools. In Chrome, press F12 and open the Console tab.
Repeat the action causing the WooCommerce AJAX problem. Look for red JavaScript errors appearing during that action. WooCommerce notes that one JavaScript error can interrupt other page functions.
Pay attention to the file path shown beside errors. The path may reveal a plugin, theme, or custom script. This evidence can save time during later conflict testing.
Inspect AJAX Requests Using the Network Tab
The Network tab provides deeper information than visible error messages. Open Developer Tools and select the Network section. Filter requests using Fetch/XHR where supported.
Now reproduce the failing WooCommerce action. For example, add a product or update checkout details. Look for requests showing red status indicators or error codes.
Open the failed request and review its status code. Check the request URL, headers, response, and returned data. WooCommerce recommends this approach when diagnosing AJAX failures.
A 403 response can suggest blocking or permission problems. A 404 may point toward an unavailable endpoint. A 500 response usually requires checking server-side errors.
Check WooCommerce Status Information
Go to WooCommerce → Status inside your WordPress dashboard. Review warnings, outdated templates, database information, and environment details.
This area can reveal configuration problems affecting store behavior. WooCommerce also recommends checking Status when checkout keeps loading.
Do not assume every warning causes the AJAX failure. Instead, compare each warning with the affected feature.
Review WooCommerce and PHP Logs
WooCommerce includes logs for many store processes and extensions. Open the WooCommerce logging area and check recent errors.
You should also review PHP error logs from your host. Search for entries created when the WooCommerce AJAX request failed. Fatal PHP errors can end a request before WooCommerce returns valid data.
Record timestamps while testing. Matching request times with log entries makes diagnosis easier.
Enable WordPress Debug Logging Carefully
WordPress debugging can expose hidden PHP notices and errors. Enable logging on a staging site whenever possible. Avoid displaying raw errors to customers on production websites.
After enabling logs, reproduce the AJAX failure once. Then inspect the generated debug information for related errors.
This method is helpful when a WooCommerce AJAX function not working problem produces no visible browser message.
Identify the Exact WooCommerce AJAX Request
WooCommerce uses different background requests for different store actions. Common examples include wc-ajax=add_to_cart and wc-ajax=get_refreshed_fragments.
Checkout and shipping can use separate update requests. WooCommerce documentation recommends monitoring checkout-related AJAX requests through Developer Tools.
Finding the exact request tells you which store function failed. It also makes plugin and server troubleshooting more focused.
Find Whether the Problem Comes From Browser, Plugin, Theme, or Server
If one browser fails, test another browser and device. If every browser fails, investigate the website environment next.
Check Console errors for plugin or theme file paths. Then review failed requests and server response codes. A server error usually requires PHP logs or hosting checks.
This process provides evidence before you fix WooCommerce AJAX not working. Part 3 will cover the actual fixes for caching, JavaScript, plugins, themes, endpoints, security rules, and server errors.
How to Fix WooCommerce AJAX Not Working
When WooCommerce AJAX not working, begin with the failed store action. Do not change several settings at the same time. Apply one fix, clear caches, and test the function again.
The correct solution depends on the failed AJAX request. Add to Cart, cart updates, and checkout use different processes. Follow these steps in order to locate and repair the problem.
1. Check Whether AJAX Add to Cart Is Enabled
Start with the WooCommerce Add to Cart setting. Go to:
WooCommerce → Settings → Products → General
Find Enable AJAX add to cart buttons on archives. Enable this option and save your changes.
WooCommerce currently uses this setting for shop and archive pages. It allows products to enter the cart without reloading pages.
Now open your Shop or product category page. Add a simple product and watch the cart behavior.
Remember, this setting applies mainly to archive pages. A single product page can behave differently. Its AJAX behavior may depend on your theme, blocks, or extensions.
If this setting was disabled, enabling it may immediately fix WooCommerce AJAX not working on archive pages.
2. Find the Failed AJAX Request First
Press F12 in Chrome or Edge. Open Developer Tools → Network. Select the Fetch/XHR filter.
Now repeat the action causing the problem. For example, click Add to Cart again. You should see new background requests appear.
Open the failed request and check these areas:
Headers shows the requested URL and response status. Payload shows information sent to WooCommerce. Response shows what the server returned.
WooCommerce recommends checking Network requests when troubleshooting AJAX failures.
A successful request normally returns a valid response. A failed request usually shows 403, 404, 500, or timeout errors.
Knowing the status code prevents unnecessary troubleshooting.
3. Clear Every Cache Layer
Caching is a common cause of WooCommerce AJAX issues. Do not clear only your WordPress plugin cache.
Clear the browser cache first. Then clear your WordPress caching plugin. Also purge hosting, object, and CDN caches when enabled.
Make sure these dynamic pages remain excluded from page caching:
/cart/
/checkout/
/my-account/WooCommerce currently recommends excluding Cart, Checkout, and My Account. These pages contain customer-specific and session-based information.
If your caching system supports database exclusions, review WooCommerce session caching too. WooCommerce specifically documents _wc_session_ as important session data.
After changing cache rules, clear everything again. Then test Add to Cart and checkout.
4. Match the WordPress and Site URLs
Incorrect website URLs can break checkout AJAX communication.
Go to:
Settings → General
Check WordPress Address (URL) and Site Address (URL).
Both should use the same domain structure. For example, avoid one using http and another using https. Also avoid mixing www.example.com with example.com.
WooCommerce states that mismatched URLs can prevent checkout AJAX requests.
Correct the URLs carefully if they do not match. Then clear your cache and test checkout again.
This issue commonly appears after SSL changes or website migrations.
5. Fix JavaScript Errors Before Testing AJAX Again
JavaScript runs many WooCommerce frontend actions. One broken script can stop another WooCommerce function.
Open:
Developer Tools → Console
Reload the affected page and perform the failed action. Look for red errors appearing during the test.
Check the filename shown beside each error. A path containing a plugin folder often points toward that plugin. A theme path may indicate custom theme JavaScript.
WooCommerce confirms JavaScript problems can affect carts, checkout, variations, and AJAX Add to Cart.
If you use JavaScript optimization, temporarily disable these features:
JavaScript minification, script combining, delayed JavaScript, and aggressive defer settings.
WooCommerce’s caching guidance also recommends avoiding JavaScript file minification when troubleshooting compatibility.
Clear caches afterward and test the same action again.
6. Perform a Plugin Conflict Test
If the WooCommerce AJAX function not working problem remains, test plugins.
Create a backup and use staging whenever possible. Then disable every non-essential plugin except WooCommerce.
Test the affected function again.
If AJAX now works, another plugin caused the conflict. Reactivate plugins one at a time. Test the same WooCommerce action after every activation.
When the WooCommerce AJAX problem returns, you have identified the likely conflicting plugin.
Update that plugin first. If no compatible update exists, contact its developer or replace it.
WooCommerce also recommends this conflict-testing process for JavaScript and AJAX problems.
For related checkout failures, you can also review WPCustomify’sguide to WooCommerce order completion errors.
7. Test Your Active WooCommerce Theme
Themes can change WooCommerce templates, JavaScript, and frontend hooks.
Temporarily switch to a clean WooCommerce-compatible theme on staging. Then test the same Add to Cart or checkout action.
If the AJAX request succeeds, inspect your active theme. Check outdated template overrides and custom JavaScript first.
Also review modifications inside your child theme. Custom code may use old WooCommerce hooks or outdated frontend behavior.
Do not edit the parent theme directly. An update could remove those changes.
8. Fix WooCommerce AJAX 403 Errors
A 403 status means the server rejected the request. This often involves permissions, security rules, or authentication.
Check your security plugin’s blocked request logs. Then check your hosting firewall or Web Application Firewall.
If your host uses ModSecurity, ask them to inspect its logs. Give them the exact failed request URL and timestamp.
Do not permanently disable your firewall just to make AJAX work. Instead, identify the rule blocking the valid request.
WooCommerce lists plugin interference, hosting firewalls, and permissions among possible causes.
9. Fix WooCommerce AJAX 404 Errors
A 404 means the requested URL or endpoint was unavailable.
First, confirm the request uses your current website domain. Old URLs may remain after a website migration.
Next, go to:
Settings → Permalinks
Do not change anything yet. Click Save Changes to rebuild WordPress rewrite rules.
Clear every cache and test again.
If the request still returns 404, inspect custom AJAX code. Make sure it calls an available WooCommerce or WordPress endpoint.
10. Fix WooCommerce AJAX 500 Errors
A 500 error indicates server-side processing failed. Browser changes alone will not normally fix it.
Go to:
WooCommerce → Status → Logs
Check recent logs matching your test time. Also review your hosting PHP error log.
Look for fatal errors, uncaught exceptions, memory errors, or plugin filenames.
WooCommerce recommends checking server-side code and server logs for 500 responses.
Fix the reported PHP error before testing AJAX again. If a plugin appears in the error, disable that plugin temporarily.
11. Fix Invalid JSON and -1 AJAX Responses
Sometimes the request returns HTTP 200 but still fails. The response itself may be invalid.
Open Network → Failed Request → Response.
WooCommerce checkout normally expects correctly formatted response data. Unexpected HTML can prevent the order review from loading.
WooCommerce notes that an index.html file can sometimes override index.php. A cache system may also add unwanted HTML to AJAX responses.
If the response only shows -1, clear every cache layer. WooCommerce associates this response with failed security validation from a cached nonce.
Then reload the page and create a fresh session.
12. Check WordPress Memory and Server Resources
AJAX processes can fail when WordPress lacks enough memory.
Go to:
WooCommerce → Status
Find WP Memory Limit and review the current value. WooCommerce currently recommends at least 64 MB for checkout operation.
Busy stores may need more resources depending on installed extensions. Your host may also enforce a lower PHP memory ceiling.
Check PHP workers and execution limits when requests remain pending. A lack of available workers can delay background PHP requests.
If requests frequently timeout, send the failed request timestamp to your host. Ask them to review PHP and web server logs.
13. Check WooCommerce Status and System Tools
Open:
WooCommerce → Status
Review warnings about outdated templates, PHP settings, and database information.
Then visit:
WooCommerce → Status → Tools
WooCommerce provides built-in maintenance tools for supported cleanup and cache tasks.
Use only tools related to the problem you are investigating. Avoid clearing or rebuilding unrelated data without a backup.
After completing a tool action, clear caches and retest AJAX.
14. Test the Complete WooCommerce Purchase Flow
Do not stop after one button begins working.
Test a product from the Shop page first. Confirm the cart count updates without refreshing. Open the Cart page and change quantities.
Continue to Checkout. Enter a different shipping address and check rates. Change billing information and confirm payment options update.
Finally, place a test order using a safe test payment method.
Also repeat testing in an incognito browser window.
If every request returns normally, the WooCommerce AJAX request failed problem is resolved. Testing the full purchase flow also confirms that your fix did not break another store function.
How to Prevent WooCommerce AJAX Problems
Preventing WooCommerce AJAX issues is easier than repairing a broken checkout later. Regular maintenance, safe updates, correct caching, and proper testing can reduce AJAX failures. The following steps help keep WooCommerce background requests stable and responsive.
1. Keep WooCommerce, WordPress, and Plugins Updated
Keep WordPress, WooCommerce, themes, and extensions updated regularly. Outdated files may create JavaScript or PHP conflicts. Always review compatibility before updating important plugins. Test major updates on staging first, especially when your store uses custom checkout or cart features.
2. Test Every Update on a Staging Website
Use a staging website before changing your live store. Test Add to Cart, cart updates, shipping, payment methods, and checkout. This process can reveal a WooCommerce AJAX problem before customers experience broken buttons, loading errors, or failed requests.
3. Exclude Dynamic WooCommerce Pages From Caching
Avoid full-page caching for Cart, Checkout, and My Account pages. These areas contain customer-specific session data. Incorrect caching can display outdated information or break dynamic requests. Review your cache exclusions after installing a new performance or optimization plugin.
4. Avoid Aggressive JavaScript Optimization
JavaScript minification, combining, defer, and delay settings can change script order. This may cause a WooCommerce AJAX function not working issue. Enable optimization features carefully. After each change, test cart, checkout, product variations, and other interactive WooCommerce functions.
5. Monitor Browser Console and Network Errors
Check browser Developer Tools during routine store testing. Review Console errors and failed Fetch/XHR requests. Early JavaScript or AJAX warnings can reveal problems before customers notice them. Pay attention to repeated 403, 404, 500, timeout, or invalid response errors.
6. Review WooCommerce and PHP Logs Regularly
Check WooCommerce, WordPress, and PHP logs for repeated errors. Look for fatal errors, memory warnings, and plugin-related failures. Regular log reviews can help identify a developing WooCommerce AJAX error before it starts affecting Add to Cart or checkout requests.
7. Use Compatible Themes and Extensions
Choose themes and plugins that actively support current WooCommerce versions. Poorly maintained extensions may use outdated hooks or scripts. Remove unused plugins whenever possible. Fewer unnecessary extensions also reduce the chance of JavaScript conflicts and failed AJAX requests.
8. Maintain Enough Server Resources
WooCommerce AJAX requests depend on PHP and server resources. Low memory, limited PHP workers, or slow database queries can delay responses. Monitor memory, CPU usage, and execution time. Upgrade hosting resources when your store traffic or plugin load increases.
9. Configure Security Tools Carefully
Security plugins and server firewalls should protect your store without blocking valid requests. Review firewall logs for blocked WooCommerce traffic. Avoid broad restrictions on dynamic endpoints. Proper firewall rules can prevent unnecessary WooCommerce AJAX request failed errors.
10. Test Cart and Checkout Regularly
Perform regular customer-style testing across your store. Add products, change quantities, apply coupons, update addresses, select shipping, and test payments. This simple routine can detect WooCommerce AJAX not working problems before they directly affect customers and completed orders.
Conclusion
A WooCommerce AJAX not working issue can affect carts, checkout, shipping, and payment updates. Start by checking failed requests, JavaScript errors, caching, plugins, themes, and server logs. Apply one fix at a time and test the complete purchase process afterward. Regular updates, safe caching rules, and staging tests can prevent future WooCommerce AJAX issues. If the problem continues after troubleshooting, professional help may be useful. Visit WPCustomify for WooCommerce support and technical guidance. You can also call +1-(888) 602-0119 for assistance with persistent WooCommerce AJAX errors and other store-related problems.