Why Upgrade to Shopware 6.7?
Shopware 6.7 is more than a version bump—it’s a technical clean-up that prepares the platform for the next wave of features. Key highlights introduced on 17 June 2025:
- Performance boost thanks to a re-engineered cache layer with delayed invalidation.
- Modern developer tooling: Admin build pipeline moves from Webpack to Vite for faster HMR and smaller bundles.
- Vue 3 & Pinia out of the box—the legacy Vue 2 compatibility layer is gone.
- Full EAA accessibility compliance baked into the core storefront.
- 200+ bug fixes and security hardening.
⚠ Extended support for 6.7 lasts until at least mid-2028, making it the safest long-term branch.
System Requirements & Hosting Checklist
| Component | Minimum for 6.7 | Recommended | Notes |
| PHP | 8.2 (8.2, 8.3, 8.4) | 8.3 | Ensure all extensions support 8.2+ |
| Node.js | 20 | LTS 20 | Needed for admin asset build |
| MySQL | 8.0.17+ (avoid 8.0.20-21) | 8.0.36 | MariaDB ≥ 10.11 also supported |
| Redis | 7.0+ | 7.2 | Session & cache backend |
| Varnish | Required with XKeys module | Latest 7.x | For HTTP caching |
| OS | Linux (Ubuntu 22.04 LTS) | — | Windows hosting not recommended |
Breaking Changes Developers Must Know
- Webpack → Vite migration: replace `webpack.config.js` with `vite.config.js`.
- Vue 2 layer removed: update all admin components to Vue 3 Composition API.
- Vuex → Pinia: rewrite state stores and switch helpers (`mapState` → `mapVuexState`).
- Meteor Component Library: legacy `sw-*` UI parts replaced with `mt-*`.
- Removed deprecated APIs: e.g., `CreateSchemaCommand`, `AuthController::authorize`, various cart & sitemap methods.
- Manifest version bump for Apps: check your `manifest.xml`.
Pre-Upgrade Compatibility Audit
- Plugin inventory: export a list of all installed plugins & apps. Check vendor changelogs for 6.7 support.
- Custom themes: scan Twig templates for removed classes (`alert-has-icon`, `sw-dashboard-statistics`).
- 3rd-party integrations: verify OAuth token flows under stricter RFC compliance.
- Server readiness: stage servers must match the new PHP & Node versions.
Step-by-Step Upgrade Procedure
- Create a staging clone of production including database & `files/`.
- Increase disk & memory limits—build processes are heavier during first run.
- Run composer update to fetch `shopware/core:~6.7` & compatible plugins.
- Execute database migrations: `bin/console database:migrate –all`.
- Build admin & storefront assets: `bin/console theme:compile` (now Vite).
- Smoke-test staging: functional checkout, admin login, plugin features.
- Schedule production downtime window (~15 min for DB schema update).
- Repeat steps 3-5 on live, clear CDN & Varnish cache.
- Monitor logs & metrics for 24 h (slow queries, PHP errors, 500s).
Post-Upgrade QA & Monitoring
- Run Lighthouse audits to confirm improved Core Web Vitals.
- Validate WCAG 2.1 AA compliance if you maintain custom theme overrides.
- Set up delayed cache invalidation interval via scheduled task for optimal hit ratio.
FAQs on Shopware 6.7
Q: Is Shopware 6.6 still supported?
A: 6.6 moves to extended support until 2027, but only receives security patches. New features land exclusively in 6.7+.
Q: Can I skip directly from Shopware 6.4 or 6.5 to 6.7?
A: Yes, but you must run each database migration step in sequence (6.5 → 6.6 → 6.7). Always update your plugins between jumps.
Q: Which plugins are incompatible?
A: Any plugin that still relies on Webpack, Vue 2, or Vuex without providing a 6.7-ready branch. Check the developer’s changelog or contact them.
Need Help Upgrading?
Our certified Shopware developers can audit your shop, patch plugins, and migrate your stack with zero downtime.