Pressidium EDGE uses WordPress-aware caching to accelerate public WooCommerce pages while automatically bypassing certain requests that must remain dynamic, including cart pages and detected logged-in sessions.

Most WooCommerce stores can start with this built-in behavior without configuring additional cache exclusions. However, custom checkout flows, translated URLs, WooCommerce extensions, or other functionality may require additional exclusions.

This guide explains which WooCommerce content can typically be cached, when additional exclusions may be necessary, and how to test your store’s caching behavior.

When additional exclusions may be needed

EDGE already bypasses certain dynamic requests by default. Before adding an exclusion, check whether the affected URL or session is being cached.

Additional exclusions may be necessary when:

  • Your store uses custom or translated cart, checkout, or account URLs.
  • A WooCommerce extension introduces customer-specific pages or endpoints.
  • Membership, subscription, booking, or payment functionality uses custom request behavior.
  • A page displays personalized information that should not be shared between visitors.
  • A custom WooCommerce integration relies on cookies that are not covered by the default caching behavior.

Only add exclusions when the existing caching behavior does not meet your store’s requirements. Unnecessary exclusions can reduce the performance benefits of EDGE.

Which WooCommerce pages can be cached?

Public WooCommerce pages can generally benefit from EDGE caching when they display the same content to all visitors.

Examples include:

  • Product pages
  • Product category pages
  • Shop archive pages
  • Public promotional and landing pages
  • Blog posts and other public content
  • Static assets such as images, CSS, and JavaScript

Typical URLs include:

/shop/
/product/example-product/
/product-category/shoes/
/sale/

Some stores display personalized prices, availability, recommendations, or other session-specific information on otherwise public pages. These cases may require different caching behavior.

Check how your store handles dynamic content before introducing custom exclusions.

Which WooCommerce requests should remain dynamic?

WooCommerce pages and requests containing customer-specific or transaction-specific information must not be served from a shared public cache.

Examples include:

  • Shopping carts and checkout pages
  • Customer account pages and order history
  • Order confirmation and payment pages
  • Subscription and membership management pages
  • Customer-specific wishlist or quote pages
  • Cart updates, checkout calculations, and other session-dependent requests
  • API or AJAX responses containing customer, cart, order, payment, or session data

Common URL paths include:

/cart/
/checkout/
/my-account/

EDGE already applies built-in cache bypass behavior for supported requests, including WooCommerce cart pages and detected WordPress login sessions.

Some stores use custom URLs, translated paths, or extensions that introduce additional dynamic functionality. Review those requests individually rather than assuming every store needs the same exclusions.

How to decide whether an exclusion is necessary

Before configuring additional cache exclusions:

  1. Check the affected request. Identify the exact URL and whether it displays public or customer-specific content.
  2. Review the default behavior. Confirm whether EDGE already bypasses the request.
  3. Identify any custom functionality. Check whether WooCommerce extensions, custom URLs, or cookies change how the request behaves.
  4. Choose the narrowest exclusion. If necessary, exclude only the affected URL path or cookie-based requests.
  5. Test the result. Confirm that customer-specific content remains dynamic and public pages continue to benefit from caching.

Avoid excluding broad public sections of the store, such as /shop/, unless there is a specific reason to do so.

If you determine that additional exclusions are necessary, you can configure them from the Pressidium Dashboard.

Go to Performance → Cache → Cache Exclusions for the affected website.

EDGE supports two exclusion methods:

  • URL path exclusions: Prevent specified URL paths and their child paths from being served from the Page Cache. For example, excluding /en/cart/ also excludes paths beneath it.
  • Cookie exclusions: Bypass the Page Cache when a request contains a matching cookie name. This can be useful for custom WooCommerce sessions or extensions.

Use the most specific exclusion possible. Broad URL or cookie exclusions can prevent otherwise public pages from benefiting from caching.

For complete instructions, configuration limitations, and examples, see Exclude URLs and cookies from cache.

After adding an exclusion, wait for the background operation to complete before testing the affected requests.

Test WooCommerce caching behavior

After configuring exclusions or making significant changes to WooCommerce, your theme, or related plugins, test the affected store functionality.

Test public pages

Using a logged-out browser session:

  1. Open a product page and a product category page.
  2. Confirm that product information, images, prices, and availability appear correctly.
  3. Check that public pages are being cached where appropriate.
  4. Verify that recently updated content appears as expected.

To inspect the cache status of a request, see Cache Analytics.

Test cart and checkout

  1. Add a product to the cart.
  2. Change the quantity and confirm the cart updates correctly.
  3. Proceed to checkout.
  4. Confirm that shipping, taxes, and payment options update correctly, where applicable.
  5. Complete a test order using a suitable test payment method.
  6. Confirm that the order confirmation displays the correct information.

Test customer-specific content

Use separate browser sessions or test customer accounts to confirm that:

  • Each customer sees only their own cart, orders, and account information.
  • Logged-in content is not shared with other visitors.
  • Customer-specific pages and requests bypass shared caching where required.

If customer-specific information appears in another visitor’s session, stop testing with real customer data and contact Pressidium Support.

Common issues and solutions

Cart contents are incorrect

If the cart displays outdated or incorrect products:

  1. Confirm the cart URL and check whether the request bypasses the Page Cache.
  2. Review any custom URL or cookie exclusions.
  3. Check whether WooCommerce extensions use custom cart endpoints.
  4. Test adding and removing products in a fresh browser session.

If the issue persists, contact Pressidium Support.

Checkout does not update correctly

If checkout calculations, shipping options, or payment steps behave unexpectedly:

  1. Confirm that checkout pages and customer-specific requests are not being served from shared cache.
  2. Check whether payment, shipping, or tax extensions introduce custom endpoints.
  3. Review any custom exclusions affecting those requests.
  4. Retest using a test order.

Product pages are not cached

If public product pages consistently bypass caching:

  1. Check whether the visitor is logged in or has an active WooCommerce session.
  2. Review URL exclusions that may match product paths.
  3. Check whether cookie exclusions also affect public requests.
  4. Verify whether custom plugins introduce personalized content.

Avoid removing exclusions until you understand why they were introduced.

Customer account content appears incorrect

If customers see outdated or another customer’s account information:

  1. Stop testing with real customer data.
  2. Identify the affected URL or request.
  3. Review the relevant cache exclusions and session behavior.
  4. Test with separate customer sessions.
  5. If another customer’s information is visible, temporarily disable the affected functionality or prevent access to the affected page, and contact Pressidium Support immediately.

For general caching issues, see Exclude URLs and cookies from cache.

Need help?

Contact Pressidium Support if WooCommerce content is being cached unexpectedly, cart or checkout functionality behaves incorrectly, or you are unsure whether a custom endpoint requires an exclusion.

When contacting Support, include:

  • The affected domain and URL
  • The expected and actual behavior
  • Any relevant URL or cookie exclusions
  • The WooCommerce extension involved, if applicable
  • Whether the issue affects logged-in or logged-out visitors
  • Screenshots and steps to reproduce the problem

Do not include customer payment information or other sensitive data.

Where to go next