Shopware 6.6 to 6.7 Upgrade Guide: Breaking Changes, Test Plan, Release Checklist

Quick answers (so you don’t waste time)

• What breaks most? Plugins, admin extensions, custom storefront overrides, payment/shipping logic.
• What must be tested? Checkout end-to-end, order processing, indexing/jobs, ERP sync, SEO outputs.
• When should you delay? If a critical plugin is not compatible or you can’t test on staging properly.

Should you upgrade from Shopware 6.6 to 6.7 now?

Shopware 6.7 is a major step with a lot of core work under the hood. The release notes are useful to understand the direction and impact: Shopware 6.7.0.0 release notes .

You should treat this as a release project if you have any of the following: plugins beyond basics, custom storefront work, admin customizations, ERP/PIM/payment/shipping integrations, or complex B2B rules.

Upgrade now if:

• You can upgrade on staging with production-like data and configs.
• You can confirm extension compatibility (or replace unsupported plugins).
• You can monitor checkout and order processing during launch.

Delay the upgrade if:

• A revenue-critical plugin has no Shopware 6.7 compatible version.
• You are in peak season or running a major paid campaign.
• You don’t have time to test properly and prepare a rollback.

What usually breaks in a Shopware 6.6 to 6.7 upgrade

Most incidents come from dependencies. If you want the official “how to update” steps and extension compatibility notes, Shopware documents the update process here: Updating Shopware (docs) .

1) Plugin compatibility (the #1 cause of outages)

• Admin screens fail silently (product edit, rule builder, promotions).
• Indexing/scheduled tasks break, causing stale data and weird storefront behavior.
• Checkout issues triggered by payment/shipping plugins (the expensive kind).

Practical tip: create a “must-have plugins” list. If any of them is not confirmed compatible, you either replace it, postpone, or isolate it for a controlled mitigation plan. If you use many plugins, you’ll also want a structured compatibility review: Plugin compatibility audit .

2) Custom storefront themes and overrides

• Category filters, search UX, and JS storefront plugins regress (especially on mobile).
• Twig overrides produce broken markup in edge templates.
• Asset builds change and tracking scripts load incorrectly.

If performance matters to you (it should), treat the upgrade as a moment to re-check CWV and template weight. See: Shopware performance optimization .

3) Admin extensions and operational workflows

• Product creation/edit flows break (variants, properties, media).
• Rules/promotions behave inconsistently after upgrade.
• Custom admin modules fail to load or lose functionality.

4) Payments, shipping, ERP/PIM integrations

• Payment authorization/capture failures
• Shipping calculation errors
• ERP inventory/order sync delays or failures
• Tax edge cases (common in EU setups)

5) SEO stability (the silent revenue leak)

• Canonical output changes on key templates
• Sitemap output changes or missing URLs
• Robots rules / indexing signals drift
• Template overrides break metadata output

What to test before releasing Shopware 6.7

Your goal isn’t “no errors”. Your goal is: no checkout impact, no ops blockers, and no SEO instability.

Storefront revenue flows (must-pass)

• Homepage, category, PDP render correctly
• Search + filters + sorting + pagination
• Cart: quantities, promotions, vouchers, shipping/tax changes
• Checkout: end-to-end on desktop + mobile
• Order confirmation + emails

Admin workflows (operations must-pass)

• Create/edit products (variants, properties, pricing)
• Rules, promotions, vouchers
• Shopping Experiences (CMS) editing + publishing
• Order processing: status changes, refunds

Plugins and background processes

• Test each active plugin in its real use-case (not just “it installs”)
• Re-index and confirm jobs complete
• Check logs for repeating errors after cache warmup

SEO checks (minimum viable)

• Top 20 organic landing pages: canonicals, titles, meta descriptions, status codes
• Sitemap output and URL coverage
• Robots rules and noindex behavior
• Redirect behavior (if you changed routes)

Shopware 6.7 release checklist (pre-go-live)

If you can’t confidently confirm every item below, do not upgrade production yet.

• Backup verified: database + files (and you’ve tested restore).
• Staging parity: staging mirrors production plugins/configs/data shape.
• Extensions ready: all plugins updated/replaced; no unknowns left.
• Custom code validated: overrides rebuilt; key templates checked.
• Indexing completed: no stuck jobs; storefront data looks correct.
• Cache + assets rebuilt: clean build, no recurring console errors.
• Checkout proven: real payment method tested end-to-end.
• Shipping proven: shipping methods and pricing rules verified.
• SEO validated: key URLs + sitemap + canonicals checked.
• Monitoring ready: logs/alerts open during launch window.
• Rollback plan: steps documented and timeboxed.

What to monitor after upgrading to Shopware 6.7

The first 24 to 72 hours is where small bugs become expensive. Monitor what matters: checkout health, order flow, sync jobs, and SEO signals.

• Checkout conversion and payment failure rate
• Order exports, inventory sync, shipping label generation
• Logs: repeating errors after traffic ramps up
• Indexing/scheduled jobs stability
• Organic landing traffic anomalies and crawl/indexation issues

Final recommendation

A Shopware 6.6 to 6.7 upgrade is “safe” only when you treat it like a release: staging parity, compatibility checks, regression testing, and monitored go-live.

If you want a lower-risk path, MageSpark can run a compatibility audit, produce a store-specific test plan, and execute a controlled production release. Talk to our team.

For ongoing version tracking, Shopware’s changelog is a good reference point: Shopware changelog .