Shopware 6

Shopware 6 is a comprehensive, API-first eCommerce platform. The Community Edition is open-source and free to use under the MIT license. There are also paid tiers providing additional features.

We have been working with Shopware 6 since 2019. In the three years since our last Tech Radar update, the platform has released two major versions—6.6 (April 2024) and 6.7 (June 2025). Each major version introduced a significant number of improvements, breaking changes and tech stack upgrades.

Tech stack evolution

Each major release has brought significant dependency upgrades. Shopware 6.6 moved to Symfony 7, PHP 8.2, and upgraded the Administration to Vue 3, while keeping a Vue 2 compatibility layer to ease the transition. Shopware 6.7 removed that compatibility layer entirely, requiring all components to use Vue 3 APIs. On top of that, the Administration build system switched from Webpack to Vite, state management migrated from Vuex to Pinia, and DBAL was upgraded to version 4. For shops with custom plugins, each major release requires a migration effort, as multiple breaking changes across the Storefront, Administration components, and core Shopware classes often land at once.

In recent years, Shopware followed an annual major release cadence with a clearly defined Release Policy. The last minor version of a major cycle transitions to extended support, receiving security updates. After that it moves to security fixes only, where patches are delivered via a security plugin rather than direct updates. For example, Shopware 6.6.10 will receive security patches at least until the end of 2028.

While the security updates window is quite long, we don't recommend postponing major upgrades for too long. Each major release introduces breaking changes, and it's better to resolve them before they pile up. In our experience, each major release comes with a significant number of improvements, be it performance, accessibility, or new features in the Administration panel. It's better to upgrade regularly and benefit from it. Often, it's possible to partially prepare for the upcoming upgrade by using feature flags provided by Shopware. For instance, we were able to prepare for the upcoming accessibility improvements by enabling ACCESSIBILITY_TWEAKS ahead of time.

Storefront and frontend performance

Shopware 6.6 introduced asynchronous JavaScript plugin loading for the Storefront. This allowed to only load the JavaScript code that is really needed on a given page, instead of loading one big all.js everywhere. This noticeably improved the frontend performance, especially for shops with a lot of plugins installed.

Shopware 6.7 significantly improved the accessibility of the default Storefront—semantic HTML, correct ARIA attributes, and base font size reset to browser standard—providing a solid base for European Accessibility Act (EAA) compliance. For context, back on Shopware 6.5 we conducted an accessibility audit for one of our clients, and had to fix a large number of issues manually, patching Twig templates and implementing custom JavaScript accessibility plugins. With 6.7, we were able to remove most of that custom code, as the fixes are now part of the core.

Starting from Shopware 6.7, the header and footer are now loaded via ESI (Edge Side Includes). This improves cache hit rates, by allowing to cache header and footer separately from the rest of the page.

Administration

The Administration remains based on Vue.js. Since 6.7, the Vue 2 compatibility layer has been fully removed, so all components must use Vue 3-compatible code. The build tooling now uses Vite instead of Webpack. Shopware 6.7 adopted the Meteor component library across the Administration, renaming core components (e.g. sw-button → mt-button). The user interface is intuitive and extending it by adding custom components or using the Shopware Component Library remains straightforward. However, implementing custom CMS blocks still requires adding multiple boilerplate files across both Administration and Storefront.

AI features

With the recent versions, Shopware continues to put a strong emphasis on AI capabilities of the framework. Most notably, Shopware introduced Shopware Copilot, available on paid plans from 6.7 onwards. It covers content generation (product descriptions, translations), image keyword suggestions, product review summarization, and natural language data querying. Shopware has also announced an agentic commerce initiative for AI-driven purchasing flows, though this is still early-stage. These capabilities remain restricted to the higher-tier plans.

B2B capabilities

When we first started working with Shopware 6, the B2B Suite plugin was essentially a port of the old Shopware 5 B2B plugin. It didn't follow the new practices and patterns introduced in Shopware 6, making it difficult to extend and customize. Since then, the B2B component has matured considerably. The old B2B Suite plugin has been replaced by B2B Components, a modular framework that follows Shopware 6 conventions and is much easier to customize and use with other Shopware features such as Flow and Rule Builder.

The list of B2B features is long: Quick orders, Quote Management, Employee Management, Order Approvals, or Shopping Lists to name some of them. On top of that, Shopware 6.7 introduced additional B2B capabilities.

Organization unit support The ability to map a B2B customer's internal structure (departments, teams, locations) with per-unit payment methods, shipping addresses, and product catalogs.

Advanced Product Catalogs Enable or disable specific product categories per organizational unit, giving precise control over which products employees can see and order in the Storefront.

Budget management Allows setting spending limits per organizational unit, enforcing company purchasing policies directly in the ordering process.

If you're interested in how we leverage these capabilities for our clients, check out our B2B solutions page.

Ongoing limitations

The Rule Builder and event system characteristics we described previously remain relevant. The event-heavy architecture can still create performance problems when processing large datasets—something to keep in mind for integrations that need to access thousands of products at once. The maximum number of rules displayed in the Administration is still hardcoded, which remains a sign that the rule system was probably not designed to be used on a very large scale.

Headless option

For projects requiring highly customized frontends, Shopware now provides first-party headless support via Shopware Frontends, a Vue/Nuxt-based toolkit that is actively maintained alongside the default Twig Storefront. You can read more about our experience with it in our Shopware Frontends blog post.

Summary

Overall, Shopware 6 continues to be a well-maintained, actively evolving platform. The ecosystem is mature, the plugin marketplace is broad, and the tech stack stays up-to-date with the PHP and JavaScript ecosystems. We continue to recommend it for clients looking for an eCommerce solution for small to medium online stores, with the caveat that custom extensions require ongoing investment to keep up with the major release cycle.

Interested in building your shop with Shopware 6? Visit our Shopware Development page to see how we can help you!

Shopware 6 is a comprehensive, API-first eCommerce platform. The Community Edition is open-source and free to use under the MIT license. There are also three paid tiers, providing additional features.

We have been working with Shopware 6 since 2019 and have observed a lot of improvements both in the ecosystem and around the framework. For example, the developer documentation that used to be poor and incomplete is now much more detailed and contains a lot of useful examples.

There are many ready-to-use plugins for integrating the shop with external systems like ERPs, PIMs, or CRMs available in the Shopware Store. If a given integration is missing, it is relatively easy to implement it thanks to the API-first architecture of Shopware.

The Storefront is built with Twig templates and Bootstrap with the addition of Vanilla Javascript for interactive elements. The core templates are reasonably divided into blocks, making the necessary extensions or overrides easy. What’s worth mentioning is the theme inheritance system, which can be very powerful if you e.g. need to build multiple brand-specific stores based on a common theme.

Shopware Administration is based on Vue.js and Twig.js. The interface is intuitive and can be easily extended by adding your own component or using one from the Shopware Component library.

One of the features that distinguish Shopware 6 from other eCommerce platforms is the Rule Builder. It can be used to personalize the shipping and payment options, create marketing strategies and product discounts, without writing any code. We also used the Rule Builder system as the base for implementing a custom price list system, with each customer group having personalized product prices. It was a good foundation that allowed for relatively quick development of such functionality, but we ran into some limitations. For example, the maximum number of rules to be displayed in Shopware Administration is hardcoded to 500. While this particular issue only affects the Administration UI, it may also be a sign that the rule system was not really designed to be used on such a large scale.

Shopware 6 makes extensive use of its event system. It’s very easy to customize or add certain features by subscribing to the events emitted by Shopware. While this is a powerful mechanism, it sometimes comes at the cost of decreased performance, because virtually any operation on any entity triggers some sort of events. It becomes a real problem if you need to access the data of thousands of products at once to e.g. generate a price list.

With the release of Shopware 6.5, we’ve seen further improvements, both in terms of performance and new functionalities. We think Shopware became mature enough to be a viable option to run a small to medium online store. Therefore, we recommend it to clients looking for an eCommerce solution and move it to the “Adopt” ring.

Shopware 6 is all new, comparing to its predecessor, completely redesigned e-commerce platform.

The architecture is API-driven and consists of three elements:

• Core system - PHP and Symfony 4 based, with the API;
• Storefront - PHP and Symfony 4 based, with Twig templates;
• Administration panel written in Javascript, based on Vue.js framework.

OAuth2 server is used to authorize the access to the API.

Community Edition is fully open source. Professional Editon and Enterprise Edition are not available yet.

Shopware 6 comes with Docker configuration files and one-command bootstrap. The current “developer preview” version covers basic requirements needed to setup an online store. However, the vendors have been working on the new versions on their plugins. They should be soon available via the Shopware Store.

Shopware 6 is a really promising product and we are going to asses it further once the first stable version is rolled out.