Yes, caching can absolutely cause problems with dynamic pages if it is not configured correctly. The most common mistake is caching cart, checkout, my account, or logged-in pages the same way as normal blog posts.

For WooCommerce, those pages should be excluded from full-page cache. You can still cache static assets and use object cache, but user-specific pages need special handling.

I had this happen once with a membership site. Some logged-in pages looked stale because the cache plugin was too aggressive. Nothing private was exposed, but users were confused because account changes were not showing right away.

After that, I started excluding logged-in users from page cache and only caching public pages. That solved it.

The safest setup is to cache product pages, category pages, blog posts, and landing pages, but exclude cart and checkout. Most good caching plugins and managed hosts already have WooCommerce exclusions, but I still check them manually.

Test it like a customer: add a product to cart, update quantity, apply coupon, log in, and complete a test checkout.

Caching is not bad for dynamic sites, but lazy setup is bad. A WooCommerce store can still benefit from object caching, browser caching, CDN, and optimized database queries.

The trick is knowing what not to cache. Anything personalized, session-based, or checkout-related needs to be excluded or handled carefully.