What Developers Need to Know About the Shopware 6.7 Update

Shopware 6.7 is a major release packed with significant changes, especially relevant for developers. This article provides a structured overview of the most important new features, technical changes, and migration tips so you can upgrade your Shopware project successfully.

New Features and Improvements in Shopware 6.7

• Accessibility Compliance: Shopware 6.7 fully implements the European Accessibility Act (EAA) requirements with comprehensive accessibility updates now enabled by default. For developers, this means your themes and plugins must now comply with stricter accessibility standards, including enforced UI adjustments.

• Modernized Frontend Toolchain (Webpack → Vite): The admin frontend build system has been switched from Webpack to Vite, speeding up builds and improving development cycles.
  Developers with admin UI plugins will need to migrate from webpack.config.js to vite.config.js.

• Vue 3 and Pinia: Shopware 6.7 now runs fully on Vue 3. The legacy Vue 2 "migration build" has been removed.
  All admin UIs and extensions must be compatible with Vue 3.
  Additionally, the state management system has shifted from Vuex to Pinia.

• Improved Caching System: Caching has been optimized to enhance performance and scalability.
  Cache invalidations now happen asynchronously (every 5 minutes by scheduled task).
  The separate Store API cache layer has been removed.

• Updated Tech Stack Requirements: Shopware 6.7 now requires PHP 8.2+ and Node.js 20+. Core libraries like PHPUnit, Doctrine DBAL, and OAuth2 have been updated.

• New Migration Toolkit: Shopware provides a developer tool to assist with plugin migration, capable of linting, auto-fixing, and formatting code.

Key Technical and Breaking Changes

• Vite Frontend Build: Any plugins using Webpack must migrate to Vite. Shopware provides migration guides for creating vite.config.js.

• Removal of Vue 2 Migration Mode: Legacy compatibility with Vue 2 is gone. All admin code must now use Vue 3 APIs and patterns.

• Switch from Vuex to Pinia: Store definitions must be rewritten for Pinia. Access patterns shift from this.$store to Pinia store instances.

• New Meteor Admin Components: Admin UI now uses Meteor Components aligned with the Shopware Design System. Use the deprecated attribute to temporarily fallback to legacy components.

• Removed Legacy Systems: Deprecated templates and PHP methods have been removed, e.g., legacy product detail page templates.

• OAuth2 Token API Strictness: The /api/oauth/token endpoint now requires RFC-compliant requests only.

• Plugin Uninstall Behavior: Plugins must ensure they clean up their database artifacts when keepUserData = false.

Migration Guide for Developers (Upgrading to 6.7)

1. System Requirements:

   • PHP 8.2+
   • Node.js 20+
   • Update your environment and test on staging first.

2. Check Theme Compatibility:

   • Shopware’s premium themes won't be updated for 6.7.
   • Review custom themes for deprecated structures.

3. Frontend Changes for Accessibility:

   • Update themes to meet new accessibility rules.
   • Adjust template structure where needed.

4. Update Admin Plugins:

   • Migrate to vite.config.js
   • Use Vue 3 + Composition API
   • Replace Vuex with Pinia
   • Update UI components to Meteor versions

5. Test All API Integrations:

   • Ensure OAuth requests are RFC-compliant
   • Review response changes and endpoints

6. Use the Plugin Migration Tool:

   • Automate detection and correction of deprecated code.

7. Test Everything Thoroughly:

   • Run the upgrade on a staging site
   • Validate frontend, admin, plugins, and integrations

---

🚀 Need help upgrading to Shopware 6.7?

Whether you need migration support, plugin refactoring, or help reviewing your custom themes – I’m happy to assist as a technical partner or consultant.

👉 Message me here on dev.to or visit my website to learn more.