Shopware 6 versions: update roadmap

The riskiest Shopware version is rarely the oldest. It’s the one that everyone in the team believes is still under support.

Take a shop running on 6.6.5. Shopware 6.6 is in extended support, so is everything fine? Unfortunately not. According to Shopware’s release policy, extended support only applies to the last minor version of a major cycle, which, for 6.6, means 6.6.10. All other 6.6 versions no longer receive patch releases, only security fixes via a plugin. And this plugin expressly does not cover vulnerabilities in Symfony or Twig.

This guide outlines the Shopware 6 versions: which one is current, how long 6.5, 6.6 and 6.7 will receive updates, what 6.8 will require in 2027, and the order in which you should update. All information is taken from Shopware’s release notes, version calendar, developer documentation and announcements, as of October 2026.

Which Shopware 6 version is current?

The current version is Shopware 6.7. The major release was released on 17 June 2025, following five release candidates between March and May. Since then, Shopware has been releasing a minor version every month with new features; the latest status is shown in the release notes. Shopware announced the next major version in November 2025 postponed from 2026 to 2027.

According to Shopware, the version number follows semantic versioning, with a leading 6 denoting the product generation. The second digit represents the major release, the third the minor release, and the fourth the patch. Version 6.6.10 therefore comprises major release 6.6 with minor release 10.

When it comes to planning, the difference between the types of update is important. Minor and patch updates introduce new features, bug fixes and security patches. According to Shopware, they do not require any special attention, as long as your extensions do not use internal or experimental APIs. Major updates are usually released once a year, clean up the codebase and introduce breaking changes. This is where plugins, themes and configurations break.

One detail helps to clarify this: major releases are not feature releases in Shopware. According to the manufacturer, they lay the technical foundations, with new features following in subsequent minor releases. According to Shopware, those who remain on the previous version will receive bug fixes and security updates as part of extended support, but no further new features.

Shopware 6 versions at a glance: Who gets support and for how long

Shopware distinguishes between four statuses in its version calendar. ‘Maintained’ is the current minor version of the current major release; it receives patch updates as required. ‘Extended Support’ is granted to the last minor version of a major release as soon as the next major release is published: selected bug fixes and security updates are provided as direct patches. “Security fixes only” means security fixes are now only available via the Security plugin. “End of Life” means no further support.

Shopware established this framework in February 2024 with the new release policy in February 2024: one year of extended support for the latest minor version, followed by a further year of security fixes via the plugin, totalling around two years. However, the calendar makes it clear that the transitions are tied to major releases and not to any fixed date. As 6.8 has been postponed to 2027, extended support for 6.6 will run until the release of 6.8.

The data in the fourth column is taken from the chart at version calendar and rounded to the nearest month. Treat these as planning figures with a buffer.

For 6.5, two Shopware sources appear to contradict each other. The calendar lists 6.5.8 is expected to receive security fixes via the plugin until the end of February 2027. The release notes, however, stated as early as May 2025 that this would be the last patch for the 6.5 series. Nevertheless, another one was released in June 2026, as an explicit exception for a security vulnerability in Twig.

Both points are consistent: there are no further patchreleases are no longer available for 6.5; until the end of the support period, the plugin will only fix vulnerabilities in the Shopware code. For planning purposes, this means: treat 6.5 as if support had already ended.

What has changed in Shopware 6.5, 6.6 and 6.7

If you skip major releases, you’ll have to deal with their breaking changes all at once. That’s why it’s worth taking a look at what has been changed in each release, especially where your own code is affected.

Shopware 6.5: Bootstrap 5 and a Storefront without jQuery

Shopware 6.5 was released on 3 May 2023. For retailers using their own theme, the most significant change was the storefront overhaul: an update to Bootstrap 5 and the removal of jQuery. Any theme or plugin script that still relied on jQuery had to be converted to vanilla JavaScript or include jQuery itself. In addition, there was a Symfony update featuring a new message queue, a new updater, the integration of OpenSearch with further support for Elasticsearch, and PHP 8.1 as the minimum version.

Shopware 6.6: Vue 3 in the administration

Shopware 6.6 followed on 21 March 2024 and upgraded the technology stack: Node 20, Vue 3, Webpack 5, Symfony 7, PHP 8.2, MariaDB 10.11 and Redis 7.0. The switch to Vue 3 affected all plugins with their own modules in the administration panel. Features that were previously hidden behind feature flags became standard.

According to Shopware, merchants benefited from faster storefront pages and faster indexing of multilingual shops. In Shopware’s own tests, the indexing of 25,000 products in six languages ran six times faster. Some accessibility improvements were already included in version 6.6, albeit behind a feature flag. Shopware has also backported individual accessibility updates to version 6.6.

Shopware 6.7: Accessibility, Vite and Pinia

Since version 6.7, the adaptations for the European Accessibility Act (EAA) have been active by default: optimised templates, adjusted font sizes, semantic HTML. For the administration, Shopware switched from Webpack to Vite. Plugins with admin components therefore require separate versions for 6.6 and 6.7. Vue 3 has been fully implemented, and state management has moved from Vuex to Pinia. In addition, there is a revised cache with delayed invalidation and new versions of key libraries, including DBAL 4 and PHPUnit 11.

With this update, accessibility is limited to the extent permitted by your theme. Shopware itself points out itself points out that custom themes will require further work. What this means in practice is set out in our BFSG checklist for Shopware 6.

One change in the 6.7 series concerns a reporting obligation that was already contractually in place. From April 2026, shops running version 6.7.8 or later will automatically report their Gross Merchandise Volume (GMV) to Shopware. This applies to Plan customers (Rise, Evolve, Beyond) and to Community Edition shops that are linked to a Shopware Account and the Extension Store. According to Shopware, only the aggregated GMV and the number of according to Shopware, only the aggregated GMV and the number of orders per day are transmitted.

This will be relevant for Community Edition shops with an annual GMV of more than one million euros: anyone wishing to continue using their Account and Store will then need one of the paid plans. You can find out how much the plans cost on our page on Shopware licence and operating costs.

Shopware 6.8: What to expect in 2027

Shopware 6.8 has been announced for 2027, though no specific date has yet been set. Shopware is continuously documenting the changes in the upgrade file on GitHub. This is a work-in-progress and may change before the release. As of October 2026, the following points, amongst others, are listed there:

• PHP 8.5 will become the minimum version; previously, it was 8.2. Shopware already supports PHP 8.5 from version 6.7.6 onwards and in the latest 6.6.10 builds, so you can make the switch earlier.
• The database requires at least MySQL 8.4 or MariaDB 11.4.
• Symfony 8 and Twig 4 are on the way. Symfony 8 no longer loads XML configuration files. Plugins that still include a services.xml will fail with an exception. XML files in the project’s config/ directory of the project are ignored without an error message. Shopware’s own formats, such as config.xml and custom-fields.xml, are not affected.
• Inline microdata is being removed from the storefront templates; structured data is now only available as JSON-LD. Any custom schema extensions in the theme must be moved.

In addition, the B2B Suite is being discontinued. From version 6.8 onwards, it will no longer supported, and Shopware advises a swift migration to the B2B Components. Our article on migrating from the B2B Suite to the B2B Components explains how the transition works.

In short: the upgrade to 6.8 is first and foremost an infrastructure update. PHP, the database and hosting must be compatible before the shop can be. It’s better to check whether your server can handle this now rather than in the month of the release. With Shopware hosting via nextlevels, we take care of deployments and updates for you.

As regards the schedule: with the release of 6.8, 6.6.10 enters a phase of security fixes only. From the 6.7 branch, only the latest minor version will then receive patch updates.

Shopware update: Roadmap by initial version

Shopware’s own recommendation on updates is simple: move from one major version to the next, and feel free to stay on a minor version for longer within a major version if you don’t need any new features. As for skipping entire major versions the documentation advises against, as long as the entire upgrade path has not been explicitly tested.

One sentence in Shopware’s updateguide: ultimately, the maintenance effort is the same, whether you wait a long time or update regularly. However, the risk is distributed differently. A major jump bundles all breaking changes into a single project, with a single go-live.

Shopware 5 is a special case. There is no update between Shopware 5 and 6, only a migration: the data is transferred via the Shopware Migration Assistant, whilst themes and plugins are recreated on Shopware 6. You can find out how to do this without losing your search engine rankings in our article on shop migration without SEO loss. Our page on Shopware migration outlines the process as a project.

With version 6.4, it’s worth doing the maths. Three major releases mean three rounds of breaking changes: jQuery out, Vue 3, Vite. A shop with lots of custom plugins may have accumulated so much technical debt that a clean rebuild to 6.7 may be cheaper than three consecutive updates. Work out the costs of both options before you run your first Composer update.

With version 6.6, the most important step is the smallest one. If your shop is running a version lower than 6.6.10, the minor update to 6.6.10 must be carried out before any discussion of 6.7. It brings you back into the scope of patch updates, and according to Shopware, minor updates are non-critical if there is no internal API usage. Shopware is also adding features to comply with new legal requirements: the notice regarding the statutory warranty, required by the new EU information obligations, is now also available in 6.6.10.

After that, plan for 6.7 with a buffer. Extended support for 6.6 ends with the release of 6.8, and the date has not yet been set. Anyone who only starts once the announcement has been made will be migrating under time pressure.

How a Shopware update works

A major update is a project with defined stages. Shopware describes the process in detail in the developer documentation; in practice, these six steps are key:

1. Take stock. Shopware version, PHP and database versions, all plugins with their source (Shopware, agency, custom-built) and the theme. The installed version is shown by composer show shopware/core. Extensions should be managed via Composer, otherwise the upgrade wizard will not be able to resolve them.
2. PHP first. Shopware always supports an overlapping PHP version. You can therefore switch to the minimum version of the target major release before the Shopware update.
3. Check compatibility. The Shopware CLI’s upgrade wizard checks the project and extensions in a test run without modifying any files.
4. Update and test on staging. Using a copy of the production data: work through UPGRADE.md, adapt plugins, then test checkout, login, payment methods and interfaces. Rector and the Codemods for the administration handle some of the adaptations.
5. Backup, maintenance mode, go-live. Back up the database and files, set sales channels to maintenance mode; after deployment, run bin/console system:update:prepare and bin/console system:update:finish, then exit maintenance mode.
6. Monitor after go-live. Check logs for new errors and deprecations, clear caches and rebuild assets if necessary.

The test run from step 3 looks like this:

shopware-cli project upgrade \
  --no-interaction \
  --target latest-patch \
  --dry-run

Shopware only recommends the Web Updater in the administration panel for small shops. The update runs in the browser there and may fail due to timeouts and memory limits on larger installations. Our page on shop maintenance explains how we roll out updates via a staging environment.

Security Plugin: A workaround, not a replacement for updates

The free Security Plugin from Shopware closes known vulnerabilities without you having to update Shopware itself. Version 4 covers 6.7, version 3 covers 6.6 and version 2 covers 6.5. Version 1 for 6.4 is no longer maintained. On a single server, you can install it via the Extension Store in the administration panel; in projects with CI deployment, use Composer:

composer require store.shopware.com/swagplatformsecurity
bin/console plugin:refresh
bin/console plugin:install --activate SwagPlatformSecurity
bin/console cache:clear

The limitation is summarised in a single sentence in the documentation: the plugin does not cover vulnerabilities in dependencies such as Symfony or Twig. To address these, you need to update the dependency or Shopware itself.

Just how real this is was demonstrated in June 2026. According to Shopware’s own statement, the plugin was unable to protect version 6.5 installations against a vulnerability in Twig; a Twig update was required. Shopware therefore an exceptional 6.5 patch. You shouldn’t rely on this for the next vulnerability. Our article on the OWASP Top 10 for Shopware.

How much a Shopware update costs

It’s impossible to give a reliable figure without looking at the shop. The effort involved depends on a few key factors:

• Skipped major releases: Each major release brings its own breaking changes, and these add up.
• Plugins: Store plugins require a compatible version from the manufacturer. Custom developments must be adapted by someone, either in-house or via a Shopware plugin development.
• Custom theme: jQuery legacy issues prior to 6.5, accessibility since 6.7, microdata with 6.8.
• Admin extensions: Vue 3 with 6.6, Vite and Pinia with 6.7.
• Interfaces: ERP, PIM and payment providers must be retested after every major release.
• Tests: Without automated tests, every run becomes manual work.

We have broken down the running costs for licences, hosting and agency fees on the page covering Shopware costs. To get the full picture, it’s worth taking a look at the Total Cost of Ownership. Delaying an update doesn’t save money; it simply shifts the costs into a larger, riskier block. This can be managed with a maintenance contract that keeps minor updates up to date, for example via our Shopware Support with SLA.

Conclusion: First check the version, then plan the update

First, check which minor version your shop is actually running on. If it’s on a 6.6 version below 6.6.10, updating to 6.6.10 is the step for this month. If it’s running on 6.6.10, the 6.7 update should be included in your planning for the coming months, before 6.8 is released.

If you’re already on 6.7, use the time until 2027 to prepare for PHP 8.5, the database, and the XML service and route configuration of your plugins. And if you’re still on 6.5 or older, this isn’t just an update– it’s a project.

Frequently asked questions about Shopware 6 versions

Which Shopware version is the latest?

Shopware 6.7, released on 17 June 2025. A minor release is issued every month; the release notes show which version is currently up to date. The next major version, 6.8, is planned for 2027.

How long will Shopware 6.6 continue to be supported?

The latest minor version, 6.6.10, will receive patch updates until Shopware 6.8 is released. After that, according to the release calendar, security fixes will be provided via the Security plugin until, as expected, the end of February 2028. Versions 6.6.0 to 6.6.9 are already receiving only security fixes via the plugin, expected to continue until the end of February 2027.

Can I update directly from Shopware 6.5 to 6.7?

Shopware advises against skipping major versions until the entire upgrade path has been tested. It is safer to go via 6.6: first upgrade to 6.6.10, test it, then upgrade to 6.7. Both steps can be combined into a single project once the staging environment is set up.

Do I have to install every monthly Shopware update?

No. According to Shopware, it is not necessary to update every month. However, you should always apply security fixes, either via the Security plugin or an update. It is crucial to be on the latest minor version before the next major release, as only this version receives extended support.

Is there a Shopware 7?

No, Shopware 7 has not been released. Shopware numbers the major versions within Shopware 6; the next major version, 6.8, is scheduled for 2027.