A quick product page is useful only if customer-specific journeys remain correct.
Begin with the store's actual routes
WooCommerce's guidance says Cart, Checkout and My Account must remain dynamic because their content is customer-specific. Some caching systems already exclude them. Verify your configured page URLs and the behavior of your host and CDN as well as the plugin. A renamed checkout route should not be assumed to match a default exclusion.
Prepare two independent sessions
Use two separate browser profiles or devices on a staging store. Set up a test gateway and test customers; avoid real charges. In session A, add one product. In session B, add a different product. Record the quantities and totals you expect in each. Keeping separate profiles avoids accidentally sharing a private session through multiple tabs.
Follow the whole cart journey
In both sessions, open a product, add an item, view the cart, change quantity and remove the item. Then add it again and move to checkout. Check the mini-cart as well as the full cart page. A correct total on one screen does not prove every component is updating correctly. Record the exact step where a discrepancy begins.
Include pricing and account variations
If the store uses coupons, customer pricing, location-dependent shipping or multiple currencies, select a representative example for each enabled feature. Compare the expected and displayed values in both sessions. Sign in and out using test accounts and inspect account information. Stop the experiment if one session displays another customer's data; restore the previous configuration and investigate the relevant cache layer.
Keep a reproducible handoff
Save the exclusion settings, the tested routes and the completed checklist. After changing a host, CDN or checkout extension, rerun the same scenarios. This is a baseline verification workflow, not certification of every payment method or integration. Give a developer the URL, session state, expected result and exact reproduction steps when a problem needs escalation.
Put it into practice
- Verify actual cart, checkout and account routes.
- Use two isolated sessions and a test gateway.
- Test mini-cart, totals, quantities and coupons.
- Check signed-in and signed-out states.
- Repeat after changing a caching layer or store integration.
AI-assisted educational content prepared for the Velonic resource library. How these guides are prepared.