Shopware 6.7 – What You Need to Know

Shopware 6.7 is on the verge of release – the next major update could arrive as early as Wednesday. In this article, we’ll give you an early look at the most important changes in the storefront and explain what you should prepare for as a store owner – and how best to do it.

Shopware 6.7

As with the updates to versions 6.5 and 6.6, Shopware has once again introduced extensive changes. In this article, we would like to give you an early overview of the upcoming adjustments.

You can find all information about the changes and features in Shopware 6.7 directly on the official Shopware website.

Shopware 6 Changelog

https://www.shopware.com/en/changelog/

https://github.com/shopware/shopware/releases

Shopware 6 Blog

Major 6.7 – when and why to upgrade

Introducing Shopware 6.7: Get ready for the next major release

Important changes in the storefront with Shopware 6.7

With the update to Shopware 6.7, extensive changes have been made to the storefront and its underlying architecture. These changes particularly affect the development of themes. Below is a summary of the most important updates:

Template Architecture & Storefront Behavior

Limitations Due to Changed Template Variables

Mit Shopware 6.7 wurde die Struktur der globalen Template-Variablen grundlegend überarbeitet. Zentrale Variablen wurden entfernt oder stehen nur noch eingeschränkt bzw. über Workarounds zur Verfügung.

Dies hat direkte Auswirkungen auf die Storefront-Gestaltung – beispielsweise auf den Header-Bereich:

Service Navigation No Longer Available in the Header

Die "Service-Navigation" wurde vollständig entfernt. Diese muss nun manuell über individuelle Template-Anpassungen oder Erweiterungen wieder integriert werden.

Hinweis: Als Theme-Hersteller werden wir dadurch leider erheblich eingeschränkt. Inhalte, die zuvor standardmäßig verfügbar waren – wie die "Service-Navigation" oder "Zahlungsarten auf der Produktseite" – lassen sich im Standard nicht mehr ohne Weiteres nutzen. Zwar verfolgt Shopware mit dieser Umstellung ein performanteres Architekturmodell, allerdings gehen dadurch bewährte und etablierte Funktionen verloren, was zusätzlichen Anpassungsaufwand notwendig macht.

Accessibility Compliance

Significant accessibility improvements are being implemented to comply with the European Accessibility Act (EAA).

Top Navigation Flyout

As part of the accessibility improvements, the top navigation flyout has been revised and more closely integrated with the main navigation.

Note: The flyout is now narrower but more accessible for screen readers and keyboard users.

Cache Overhaul

Shopware 6.7 introduces new caching mechanisms aimed at significantly improving both performance and efficiency:

• New caching mechanisms improve performance and efficiency
• Store API caching layer has been removed
• Cache invalidation is now delayed
• Lower memory usage with higher cache hit rates

Technical Modernizations

Migration from Webpack to Vite

The switch to Vite as the build tool marks a significant step forward in modernization.

Note: Extensions with admin components will now require separate versions for Shopware 6.6 and 6.7.

This transition greatly improves build times and the overall developer experience.

Improvements in Vue.js

• Migration to Vue 3 (fully adopted, no longer using compatibility mode)
• Transition from Vuex to Pinia for state management, enabling more modern and efficient patterns

Updates to Key Libraries

• Upgrade to Doctrine DBAL 4.0 to ensure long-term support and access to new features
• Updates to core libraries including:
  • PHPUnit 11
  • League OAuth2 Server
  • DomPDF

System requirements

The following versions are required for version 6.7:

• Node.js 20 or higher

  PHP 8.2, 8.3 and 8.4

• Redis 7.0 or higher

• MySQL 8.0.17 (problematic versions: 8.0.20, 8.0.21) or higher

• Maria DB 10.11 (problematic versions: 10.11.5 & 11.0.3) or higher

Notes on the Shopware update

Preparations

As major releases (6.6 > 6.7) of Shopware can lead to incompatibilities with extensions (plugins/apps/themes) due to "breaking changes", we recommend waiting a few weeks before updating.

As with all Shopware releases, we recommend performing the update in advance in a test system or a staging environment and testing it extensively.

It is also important to create a complete backup of your shop before the Shopware update.

Shopware update

• Assign the Shopware default theme to your Sales Channel(s) before performing the Shopware update.
• Start the Shopware update wizard. This will inform you about "incompatible" extensions.
  • Important: Deactivate "incompatible" extensions before the Shopware update in the Extension Management and perform the Shopware update to version 6.7 afterwards!

• After the Shopware update, please update all extensions (plugins/apps/themes) to the latest version (e.g. ThemeWare® version 4.x).
• Check whether all extensions are compatible with Shopware 6.7 and work without issues.
  • Important: Do not activate the respective extension or theme until you are certain both conditions are met!
• Finally, reassign your theme (e.g. ThemeWare® theme) to the desired Sales Channel(s).

After the update

As the latest major releases of Shopware have shown, there are some extensions that were not compatible with the Shopware release and caused errors. Therefore, check your storefront for any JavaScript errors after the update.

If you have made individual customisations to the storefront, check and update them so that they do not lead to any errors.

In addition, new or changed features of Shopware can of course result in changes to the storefront.

Conclusion

Most of these changes affect the core of Shopware or the theme and extensions used. Therefore, you don't have to do or consider much yourself.

However, if you use customised HTML/CSS code or have made individual customisations (e.g. Twig, JS, SCSS), you must of course check these.

Best regards, the ThemeWare® Team