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
Here you find our articles about online shops, websites and web tech. We explain new rules, tools and good ways of working. You can filter the articles by topic. At the top of an article you find a short version in plain words. Ask us if something is still not clear.
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 served 99.76% of requests within one millisecond in the vendor benchmark and can cut Shopware load times. Learn to configure HTTP cache, object cache, and sessions, master invalidation and warmup, and optimize hit rate.
Larger targets, terms explained, input help, clear focus, no time limits
You decide which optional data processing to allow.
Our anonymous reach measurement runs without cookies and without IP storage, including campaign parameters in links – 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. Settings you choose yourself (light/dark appearance, accessibility) are kept in your browser's local storage only once you choose them; "Reset" in the accessibility settings removes them.
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.