Shopware Message Queue: Workers in Production
Late order mails, a stale search index, an outdated sitemap: how to move the Shopware message queue into production with CLI workers, separate queues and alerting.
Insights on e-commerce, web development and digital solutions
Late order mails, a stale search index, an outdated sitemap: how to move the Shopware message queue into production with CLI workers, separate queues and alerting.
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.
With 8.0.46, support for MySQL 8.0 ends. Why the EOL database under your shop is first an audit problem - and how the move to 8.4 LTS works.
A shop's largest attack surface is not the frontend, it is the build. How supply chain attacks via npm and Composer actually unfold, and which measures catch them beforehand.
As soon as a shop gets an AI advisor, a new attack surface opens up: language models do not separate instruction from data. What that means in practice and which layers hold.
67% of B2B buyers prefer a rep-free buying process (Gartner), yet 91% of B2B purchases stall along the way (Forrester). How an end-to-end RFQ workflow from quote cart to one-click order takes days out of the quoting process.
Filter and sort URLs turn a few thousand products into millions of pages - Google names faceted navigation as the single largest cause of crawling problems. A decision matrix instead of guesswork: which facets deserve a landing page, which belong out of the crawl, and why robots.txt and noindex are not interchangeable.
The CJEU requires every advertised price advantage to be calculated against the lowest price of the last 30 days. Here is how to couple price history, lowest price and discount badges properly.
Internal search is the highest purchase-intent path in the shop and usually the worst maintained. A working guide to relevance configuration of OpenSearch-based shop search: minimum_should_match, compound words, synonyms, product codes, autocomplete and variant search.
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.