Hung Mac
DE Request a care proposal
Services Packages About Plugins Writing Request a care proposal
Services Shopware 6.7 Updates

Shopware updates with compatibility checks before production.

I plan and execute the update to the latest stable Shopware 6.7 patch available for your project. Before production, I review server and Composer requirements, custom plugins, apps, themes, integrations, checkout, the online revocation flow, scheduled tasks, queues, and rollback options.

Shopware 6.7 update Shopware update freelancer latest Shopware version Shopware 6.8 preparation Shopware MCP integration
Plan the 6.7 update
01 Best for
  • Stores still running an older Shopware 6 version
  • Teams that need current security and stability fixes
  • Stores with custom plugins, apps, themes, or integrations
  • Projects that want a controlled path toward Shopware 6.8
02 Deliverables
  • Version-by-version update path and technical risk map
  • Plugin, app, theme, and infrastructure compatibility matrix
  • Staging results for checkout, orders, revocation, jobs, and integrations
  • Production rollout, rollback, and post-update checklist
03 Process
  1. Inventory the current Shopware version, hosting stack, extensions, custom code, and deprecations
  2. Build the update path, update code where required, and validate the latest stable 6.7 release on staging
  3. Deploy in a planned maintenance window and verify the critical production flows
01

Why update to the latest Shopware 6.7 release?

Shopware 6.7 is the current major line for new improvements. Shopware 6.6 is in extended support and receives security updates, but no new features. The exact target patch is selected at project start so the shop receives the latest stable fixes without skipping compatibility checks.

The update is not only a version-number change. It gives the store a more current security and stability baseline, makes important storefront and administration improvements available, and creates a cleaner technical starting point for Shopware 6.8.

  • Current security, bug-fix, and stability updates instead of remaining on an older patch level.
  • Accessibility improvements enabled by default in Shopware 6.7, including more semantic storefront templates and a stronger foundation for EAA requirements.
  • The online revocation request flow: customers can use a “Revoke a contract” button in the footer and submit the request through a Shopping Experiences form.
  • Performance improvements through cache rework and more deliberate cache invalidation.
  • A modern extension foundation with Vue 3 compatibility, Pinia state management, Vite-based Administration builds, and updated core libraries.
02

Compatibility checks happen before production

A Shopware update can affect custom code far beyond Composer. The official 6.7 upgrade guide contains deprecations and behavior changes across the Administration, Storefront, DAL, cache, media, checkout, and extension APIs. I compare those changes with the actual shop instead of assuming every extension is ready.

The update is first completed on staging with a restorable backup and a documented rollback path. Production follows only after the relevant business flows have passed.

  • Check PHP, database, Redis, Elasticsearch or OpenSearch, Node, Composer, and hosting requirements.
  • Review installed plugins and apps, custom Symfony services, Storefront overrides, Administration extensions, and third-party integrations.
  • Test storefront navigation, customer login, cart, checkout, payment, shipping, orders, emails, documents, queues, scheduled tasks, and indexing.
  • Configure and verify the revocation CMS layout, footer button, validation, mail template, and request delivery when the store uses this feature.
  • Record database backup, maintenance window, deployment order, smoke tests, monitoring, and rollback decision points.
03

Prepared for Shopware 6.8 and AI integrations

I also review the official Shopware 6.8 upgrade guide while preparing the 6.7 update. This identifies deprecated APIs and configuration that should be removed early, plus upcoming behavior changes such as the cache rework becoming standard and explicit worker configuration for the dedicated webhook transport.

Shopware’s current 6.7 line already includes an experimental Model Context Protocol (MCP) server. It provides a standardized way for compatible AI clients to work with Shopware tools, prompts, and resources. This is an important foundation for the more AI-assisted Shopware ecosystem around 6.8, but it should be enabled deliberately rather than treated as a switch with no security review.

  • Assess custom extensions against the removals and breaking changes documented for Shopware 6.8.
  • Prepare cache, worker, webhook, and deployment configuration for the new defaults.
  • Evaluate MCP use cases such as controlled entity operations, system configuration, state transitions, cache management, and storefront product search.
  • Protect MCP access with dedicated integration credentials, least-privilege ACLs, capability allowlists, staging tests, and an audit-friendly rollout.
Hung Mac · Shopware 6 Freelancer
Hung Mac Shopware 6 Freelancer · Fullstack PHP Developer
Your Shopware developer · Former Shopware Core team member

Hi, I’m Hung Mac.

I’m a Fullstack PHP developer focused on Shopware 6 and Symfony, and I previously worked as a developer on Shopware’s Core team. I now work remotely from Vietnam with German Shopware agencies and merchants on ongoing care, hourly development, scoped projects, and dedicated part-time support.

  • Former member of Shopware’s Core team with public core contributions
  • 6+ years of Shopware and 10+ years of PHP experience
  • Shopware 6 Advanced Developer, Solutions Specialist, PaaS Specialist, and Frontend Developer certifications
  • Custom plugins, apps, updates, integrations, performance, and production debugging
View Shopware core contributions More about me
FAQ

Shopware 6.7 Updates

Update your store to the latest stable Shopware 6.7 release with extension compatibility checks, security updates, staging validation, revocation-flow testing, and Shopware 6.8 readiness.

Which Shopware 6.7 version will you install?

The target is the latest stable Shopware 6.7 patch available when the project starts, provided the hosting stack and required extensions pass compatibility checks. I do not hard-code an older patch level into the update plan.

Why should we update to Shopware 6.7 now?

The current 6.7 line provides the active stream of security, bug-fix, stability, accessibility, performance, and feature improvements. Shopware 6.6 is in extended support and no longer receives new features.

Does the update automatically configure the Widerrufsbutton?

Shopware 6.7 provides the online revocation request and the “Revoke a contract” footer option. The CMS layout, form fields, mail template, translations, and delivery still need to be configured and tested for the individual store.

Are you ready to prepare our store for Shopware 6.8?

Yes. The 6.7 update includes a review of the official 6.8 upgrade guide, current deprecations, custom extensions, cache behavior, workers, webhooks, and infrastructure so avoidable breaking changes can be handled early.

Can MCP be connected as part of the project?

Yes, as a separately agreed and security-reviewed step. Shopware currently marks its MCP server as experimental, so I first define the use case, credentials, ACL permissions, capability allowlist, data boundaries, and staging tests before enabling access.

Services
Shopware Freelancer Shopware Developer Shopware Audit Shopware Debugging Shopware Maintenance Shopware Performance Optimization Plugin & App Development Server, Hosting & Deployment Support