Shopware
Practical writing for Shopware 6 teams — interview prep, the DAL and plugin/app architecture, performance and caching, and how to plug modern AI into a Shopware storefront without rewriting the checkout.
What we cover
Shopware 6 is a different animal from Magento or Shopify: an API-first, Symfony-based platform where the Data Abstraction Layer sits between you and every entity, and where the split between plugins (running inside the shop) and apps (running outside it, over HTTP) decides most of your architecture up front. Most of what gets written about Shopware skips that distinction, so the guides here start with it.
The recurring themes are the ones that actually cost teams time in production: modelling entities and associations through the DAL without writing N+1 queries by accident, choosing between a plugin and an app for a given integration, keeping the HTTP cache and Elasticsearch honest as the catalog grows, and extending the Storefront and Administration without forking templates you will have to re-merge on the next minor.
Shopware and WisWes
WisWes runs on Shopware 6 through a native plugin — install it with Composer, click Install with WisWes in the admin, and the AI assistant reads your live catalog, stock and prices through the Store API. That means product answers, recommendations and cart actions come from the same data your storefront serves, not from a stale export. The Shopware install guide walks through the whole setup, and policy & FAQ answers covers how it grounds replies in your own docs rather than inventing them.
If you are weighing an AI assistant for a Shopware store, the pre-sales product Q&A and abandoned-cart recovery pages show what it does day to day, and pricing explains why we charge on win-backs instead of tokens.
