WooCommerce Cart Is Empty After Adding a Product? What to Check
Troubleshoot an empty WooCommerce cart by checking page assignments, cache exclusions, session continuity, URLs and theme or plugin conflicts.
If the WooCommerce cart is empty after adding a product, check the actual cart page, caching and customer-session continuity before changing the design. A header badge showing a quantity does not prove the cart page has the same up-to-date state.
Begin with one product that is available for purchase and a fresh logged-out browser session. Record the product URL, the exact click, any message and the cart URL reached. This makes the fault reproducible rather than an occasional report.
Describe the failure precisely
Does the product appear briefly and then disappear? Does the mini-cart show it while the cart page stays empty? Does the issue affect only variations, only mobile visitors or only logged-out customers? Each pattern gives a different lead.
Test a simple product first. Then test a variable product with every required option selected. A product-selection error should not be confused with a cart that lost an item it had already accepted.
Confirm the cart page and header link
Check the cart page assigned in WooCommerce’s settings and verify that it contains the appropriate cart block or shortcode for your setup. Follow the header’s cart link and compare it with that assignment. A custom header may be linking to an old page or a duplicate created during a redesign.
If you have both an old cart layout and a newer block-based layout, establish which one customers should use. Avoid deleting either page until links and dependencies are understood.
Exclude personalised cart content from page caching
WooCommerce’s developer documentation says Cart, Checkout and My Account need to remain dynamic because they contain customer-specific information. It also describes cart and session cookies that caching systems need to account for. Check the WordPress cache, hosting cache and CDN, not only one plugin. Source: WooCommerce caching guidance.
After correcting the relevant rules, purge the affected cached pages and test a fresh session. Some tools already exclude these pages automatically; confirm the effective configuration rather than assuming the plugin name tells you the answer.
A fast cached product page can be useful. A shared cached copy of somebody’s personalised cart is not the experience a customer expects.
Keep the customer on one consistent site address
Follow the URLs from product page to cart to checkout. Look for unexpected changes between HTTP and HTTPS, different hostnames or a temporary migration domain. Record any redirect rather than changing the WordPress address as an experiment.
Check whether browser privacy settings, extensions or a consent configuration prevent the necessary session behaviour. Compare a clean supported browser. The aim is to identify the failing configuration, not to make every visitor disable their protections.
Isolate a theme or plugin conflict safely
Use a staging copy with a recoverable backup. Reproduce the same product-to-cart journey, then test the theme and cart-related extensions one at a time. Pay attention to custom add-to-cart scripts, product-options extensions, redirect tools and aggressive script optimisation.
Do not switch themes or disable payment plugins on a busy live store as the first troubleshooting step. A controlled test should tell you which change matters without interrupting real orders.
| Symptom | First area to investigate |
|---|---|
| Mini-cart and cart disagree | Cached page or stale interface state |
| Problem starts at a different hostname | Redirects and session continuity |
| Only variable products fail | Selections and product-option logic |
| Only logged-out visitors fail | Public caching and session behaviour |
| Problem began after an optimisation | The specific setting that changed |
Verify more than the cart count
After the fix, add two products, change a quantity, remove an item and revisit the cart. Test a valid coupon if your store supports coupons. Continue to checkout and confirm the correct items and totals remain present.
Use the store’s approved test-payment arrangement when checking an order; do not create unintended live charges. Test guest and signed-in journeys, desktop and mobile, and a new browser session. Record the result so the same journey can be checked after future updates.
If the fault appeared during a host move, review our WooCommerce migration guide. For recurring checks, use the maintenance checklist.
Need a cart repair? Send StartMyWeb a product URL and the exact failing steps, including whether the issue affects guests, mobile visitors or specific products.
When products stay in the cart but the next step fails, follow the WooCommerce checkout troubleshooting guide to separate order creation, payment and confirmation problems.
Editorial note: Prepared with AI assistance and checked against the official documentation linked above. Examples are illustrative; test changes on a recoverable copy before applying them to a live business website.
I can help with WooCommerce setup, fixes, migrations and store improvements when the project scope is clear.
Published by Lookman at Start My Web, an independent web and WordPress service working online from Bengaluru. Examples are illustrative; project scope and third-party product terms should be confirmed for your requirements.