Every year, we see the same pattern: a Shopware shop grows steadily, marketing plans a big campaign, and suddenly the platform that “worked fine” becomes the bottleneck. The difference between shops that survive peak traffic and shops that fail is rarely hardware. It is architecture.
Where Shopware platforms actually break
In our experience, Shopware 6 performance problems concentrate in a few predictable areas:
- The cart and checkout path. Product listings can be cached aggressively; the checkout cannot. Every architectural weakness surfaces here first, because these requests always hit PHP, the database and often external services.
- Uncontrolled plugin behavior. Third-party plugins subscribing to core events can multiply database queries invisibly. One plugin adding two queries per line item turns a 50-item B2B cart into a hundred extra queries.
- Synchronous work in the request path. ERP lookups, stock checks and emails executed inline block the customer while external systems respond — or fail to.
The decisions that matter
1. Decide what is allowed to be slow
Not everything needs sub-100ms responses. Define explicit performance budgets per route: storefront listings, product detail, cart operations, checkout submission. Budgets turn “the shop feels slow” into an engineering conversation.
2. Move work out of the request
Shopware’s message queue exists for a reason. Order confirmations, ERP synchronization, search index updates and stock propagation belong in asynchronous consumers, not in the customer’s request. The checkout should do one thing synchronously: persist the order.
3. Design the cache layers deliberately
HTTP cache, object cache and the database each have a role. The most common mistake we see is relying on full-page caching to hide backend problems — which works until a campaign brings thousands of logged-in or cart-carrying users who bypass it.
4. Load-test the uncacheable path
Testing the home page tells you little. Test the cart-to-order flow with realistic baskets and realistic plugin configurations. That is the path that decides whether your campaign succeeds.
Takeaway
Scaling Shopware is not about bigger servers. It is about deciding — deliberately — what happens synchronously, what gets cached, and what the platform does under pressure. Those decisions are cheap to make early and expensive to retrofit during an outage.
