Customer messages and caching in Shopware
Customers must see the result of their actions even when the store uses page caching. FroggShop links the display of certain temporary messages to a policy excluding the relevant routes from the shared cache.
Keep feedback after an action
An account recovery request can end with a redirect and a confirmation message. The journey must display this feedback rather than leaving the customer without an indication.
The mechanism targets temporary customer journey messages, not marketing notifications or transactional emails.
Do not share a personal message
Routes designated for these messages follow a common rule: allowing message display means disabling HTTP caching for those routes.
The rest of the store can retain its cache strategy. The aim is not to make a personal message reusable between visitors.
Check new forms
The relevant routes are declared by the project. When a form or redirect is added, acceptance tests must check success and error messages.
This check must use the cache actually used in production: a correct page in development is not enough to validate the published journey.
What is the scope of your project?
Tell us about your needs and the tools you use. We can clarify the possibilities, conditions, alternatives and scope of work suited to your project.
Discuss your needs