Shopware Cache Rework: Caching for Logged-In Customers
The storefront HTTP cache now works with login and a filled cart. How the sw-cache-hash works, what changes in invalidation and how to prepare extensions safely.
Insights on e-commerce, web development and digital solutions
The storefront HTTP cache now works with login and a filled cart. How the sw-cache-hash works, what changes in invalidation and how to prepare extensions safely.
From Shopware 6.7, Store API endpoints are cacheable. Avoid N+1 problems in Nuxt, set client caching correctly and use stale-while-revalidate.
Redis serves data with sub-millisecond latency and can cut Shopware load times by up to 40%. Learn to configure HTTP cache, object cache, and sessions, master invalidation and warmup, and optimize hit rate.
You decide which optional data processing to allow.
Our anonymous reach measurement runs without cookies and without IP storage — we do not ask for consent for it because none is legally required.
Strictly required: language preference, core site functions and storing your cookie choice. Without these the site does not work.
Stores your preferences in your browser's local storage (e.g. light/dark appearance, accessibility options). Improves comfort but is not strictly required.
Records your interactions (clicks, scrolling, inputs) pseudonymously so we can spot usability issues. Form field inputs are masked automatically before storage; your IP address is not saved with the recording. Served from our own domain, no external tool. Opt-in, revocable any time.
Allows measurement of advertising campaigns (internal UTM attribution, e.g. whether a visit came from an ad). No external advertising cookies.