Updating Shopware isn’t just about installing a newer version. Every release introduces changes to core packages, Symfony components, Composer dependencies, and plugin compatibility. If you update without planning for those changes, even a routine upgrade can quickly turn into hours of troubleshooting.
One of the most common mistakes developers make is running a standard composer update on an existing Shopware installation and letting Composer execute every script automatically. That works on some stores, but on customized installations or projects with multiple plugins, it’s often where dependency conflicts, incomplete recipe installations, and broken storefronts begin.
This guide walks through that workflow step by step. It’s intended for Shopware stores installed with shopware-installer.phar.php and managed through Composer with SSH access.
Whether you’re upgrading from Shopware 6.5 to 6.6, moving to Shopware 6.7, or installing another supported release, these steps will help you perform the update more safely while avoiding many of the issues developers commonly encounter during Composer-based upgrades.
Why Keeping Shopware 6 Updated Matters?
Keeping your Shopware 6 store updated is essential for maintaining a secure, high-performing, and future-ready eCommerce platform. Every release includes important improvements that help your store run smoothly while reducing technical risks.
Here are the key benefits of updating Shopware 6 regularly:
- Protect your store with the latest security patches that fix known vulnerabilities and reduce the risk of cyber threats.
- Improve website performance through speed enhancements, bug fixes, and backend optimizations.
- Maintain compatibility with the latest versions of PHP, Symfony, Composer packages, and Shopware core components.
- Ensure third-party integrations continue working with payment gateways, shipping providers, CRM systems, and ERP platforms.
- Reduce plugin compatibility issues by staying on versions actively supported by extension developers.
- Avoid problems caused by deprecated APIs that can break custom plugins or integrations on older installations.
- Simplify future upgrades by applying smaller, incremental updates instead of managing a large version jump.
- Lower long-term maintenance costs by resolving compatibility changes gradually rather than all at once.
- Keep custom themes and plugins easier to maintain, especially for stores with complex business logic.
- Minimize downtime and unexpected errors through regular maintenance and compatibility updates.
- Deliver a better customer experience with a faster, more reliable, and stable online store.
- Stay eligible for official Shopware support and benefit from the latest platform improvements and fixes.
Shopware 6 Update Prerequisites
Before making any changes, verify that your server and project are ready for the target Shopware version.
A typical Composer-based Shopware update assumes that you have:
- SSH access to the server
- Composer installed and working correctly
- Git or another version control system
- Administrator access to Shopware
- A complete database backup
- A backup of the project files
- Sufficient disk space for Composer packages
- The PHP version required by the target Shopware release
It’s also worth reviewing the release notes for your destination version before updating. Shopware occasionally removes deprecated packages, introduces new framework requirements, or changes configuration files that may affect customized projects.
If your store uses commercial Shopware plugins or custom Shopware extensions, check that compatible versions are available before starting the upgrade. A plugin that hasn’t been updated for the target Shopware release can block the Composer update or cause unexpected errors after deployment.
Before Starting Your Shopware 6 Update
Never perform a Shopware update directly on a live production store without first testing it in a staging environment.
you can get help of Shopware Software Specialist or Certified Showpare 6 agency in germany like iCreative Technologies , those are top Shopaware Development Partner for B2B and B2C also.
Need Help Upgrading Your Shopware 6 Store?
Upgrade your Shopware store safely with expert assistance from iCreative Technologies.
A staging server gives you the opportunity to identify dependency conflicts, plugin compatibility issues, theme problems, or deployment errors before customers are affected. Even if the Composer update completes successfully, problems sometimes don’t appear until caches are rebuilt or themes are compiled.
Before running a single command, create fresh backups of both:
- the complete Shopware project directory
- the production database
If something unexpected happens during the Shopware 6 upgrade, restoring a verified backup is considerably faster than trying to repair a partially updated installation.
It’s also a good practice to commit your current project to version control before modifying composer.json. Having a clean Git commit makes it much easier to review dependency changes or roll back specific modifications if needed.
Finally, verify the target Shopware version’s PHP requirements.
How to Safely Upgrade Shopware 6 Using Composer
Step 1: Prepare Your Shopware 6 Store for the Upgrade
Once you’ve confirmed your backups are in place and your environment meets the target version’s requirements, the first step is preparing Shopware for the update.
Run the following command from your project root:
bin/console system:update:prepare
This command puts Shopware into an update-ready state by performing a series of internal checks before any Composer packages are modified.
Running it first helps prevent issues that can occur when the application is updated while background processes or pending update tasks are still present.
Tips : If the command returns any warnings or errors, resolve them before moving forward. Ignoring them usually leads to bigger problems later in the upgrade process.
Step 2: Verify Composer Dependencies Before Updating Shopware 6
One of the biggest causes of failed Shopware upgrades is assuming that changing only the shopware/core version is enough.
It rarely is.
Each Shopware release is built against a specific set of Composer package versions. Those versions include Symfony components, Doctrine libraries, Shopware packages, and several third-party dependencies that need to work together.
Before editing your project, visit the Shopware Production Template repository on GitHub and switch to the Git tag that matches the version you’re upgrading to. Review its composer.json file and compare it with your own project.
Pay particular attention to:
- Shopware packages
- Symfony components
- Required PHP version
- Composer plugins
- Additional framework packages
If your project contains packages that differ significantly from the official Showpware templates, determine whether those differences are intentional before changing anything. Many stores include custom integrations or third-party packages that should remain untouched.
Tips : Taking a few minutes to compare dependency versions now can save hours of troubleshooting later.
Step 3: Update Your composer.json
Once you’ve reviewed the official template, update your project’s composer.json.
Start by changing the Shopware version constraint to the version you want to Shopware install.
After that, review the remaining packages listed in the require section and align them with the versions expected by your target Shopware release wherever appropriate.
If your store installs plugins through Composer instead of the Shopware Store, review those version constraints as well.
Avoid making unnecessary changes outside of the required packages. The goal is to bring your project in line with the target Shopware version without introducing unrelated dependency changes.
Why Use composer update –no-scripts?
This is the approach that makes the biggest difference during a Shopware 6 upgrade.
A standard Composer update doesn’t just download new packages. It also executes various Composer scripts while dependencies are still being installed and replaced.
On a clean project, those scripts often complete without any issues.
On a production Shopware store with multiple plugins, custom code, or modified dependencies, they can fail halfway through the process.
When that happens, Composer may leave the project in a partially updated state where some packages belong to the old version while others belong to the new one. Recovering from that situation is rarely straightforward.
Running Composer with the –no-scripts option changes the workflow.
Composer installs and updates dependencies first, allowing you to complete the remaining Shopware update steps separately. This staged approach simplifies troubleshooting, reduces update risks, and provides greater control, especially for stores with custom plugins or complex integrations.
Step 4: Upgrade Shopware 6 Using Composer
After updating your composer.json, run the following command:
composer update --no-scriptsComposer will now begin resolving every dependency based on the constraints defined in your project.
Depending on your internet connection, server resources, and the number of installed packages, this step may take several minutes.
Some of the issues developers commonly encounter include:
Symfony Version Conflicts
When upgrading between major Shopware releases, Symfony package requirements often change.
For example, upgrading from Shopware 6.5 to 6.6 may require updating packages such as symfony/runtime to match the newer framework requirements.
Trying to force older Symfony versions usually creates additional dependency conflicts later in the installation.
PHP Version Mismatches
Composer validates your current PHP version against the requirements of every package being installed.
If your server is running an older PHP version than the target Shopware release supports, Composer will stop before installing anything.
Always verify PHP compatibility before beginning the upgrade rather than after dependency resolution fails.
Plugin Dependency Conflicts
Plugins installed through Composer frequently specify version constraints for Shopware or Symfony packages.
If one of those plugins doesn’t yet support your target Shopware version, Composer won’t be able to complete dependency resolution.
In most cases you’ll need to:
- update the plugin to a compatible version
- temporarily remove the package if it’s no longer maintained
- postpone the Shopware upgrade until the plugin supports the newer release
Once composer update –no-scripts finishes successfully without conflicts, you’re ready to rebuild the Shopware bootstrap files and complete the remainder of the upgrade process.
How to Fix Common Shopware 6 Update Errors
Even when the Composer update completes successfully, you may run into a few issues while finishing the Shopware 6 upgrade.
Most of these errors are related to dependency mismatches, incomplete Composer recipes, or outdated packages. Below are the most common problems and their solutions.
Health Check Errors After the Update
If the Shopware health check reports errors immediately after the upgrade, don’t panic. This often happens because the cache hasn’t been fully rebuilt.
Close the browser tab and run:
bin/console cache:clear
Reload the Admin panel and run the health check again. In most cases, the warnings disappear.
Fix “Attempted to Load Class HttpKernel”
This error usually indicates that Composer didn’t complete the dependency installation correctly or the Composer recipes weren’t fully restored.
Review the earlier upgrade steps and make sure you’ve completed:
- Updating
composer.json - Running
composer update --no-scripts - Reinstalling Composer recipes
- Clearing the cache
If any of these steps were skipped or interrupted, rerun them before continuing.
Fix “Attempted to Load Class SensioFrameworkExtraBundle”
Some older Shopware installations still include legacy Symfony packages that conflict with newer Shopware versions.
Refresh those packages by running:
composer require sensio/framework-extra-bundle enqueue/enqueue-bundle sroze/messenger-enqueue-transport
composer remove sensio/framework-extra-bundle enqueue/enqueue-bundle sroze/messenger-enqueue-transport
This forces Composer to rebuild the affected dependencies and usually resolves the issue.
Fix “Key Provided Is Shorter Than 2048 Bits”
If you’re upgrading a Shopware version earlier than 6.7, regenerate the JWT secret:
bin/console system:generate-jwt-secret --force
Note: This command is no longer available in Shopware 6.7 and later.
Fix JWT Key Errors in Shopware 6.7+
Starting with Shopware 6.7, the platform uses APP_SECRET instead of the legacy JWT key.
Generate a new application secret:
bin/console system:generate-app-secret
APP_SECRET=your_generated_key
Generate a new application secret:
Save the file and clear the cache before logging back into the Shopware Admin.
Final Thoughts
A successful Shopware 6 update starts with proper planning. Back up your store, review your dependencies, and complete each upgrade step carefully instead of rushing the process.
Using composer update –no-scripts gives you greater control over the upgrade and makes it easier to resolve dependency issues before running Shopware’s post-update tasks. Combined with plugin compatibility checks and testing on a staging environment, it helps ensure a smoother and more reliable upgrade.
Following these best practices will help keep your Shopware store secure, stable, and ready for future releases.
FAQs for Shopware Upgrade
The safest approach is to back up your store, test the upgrade on a staging environment, update your composer.json, and run composer update --no-scripts before completing the remaining Shopware update commands.
Using --no-scripts updates Composer dependencies without executing Shopware's post-update scripts immediately. This gives you more control over the upgrade process and makes it easier to troubleshoot dependency conflicts.
Yes. Always back up both your database and project files before starting a Shopware 6 update. A recent backup allows you to restore your store quickly if the upgrade doesn't go as planned.
Yes. Once the Shopware core update is complete, update your plugins and apps to compatible versions, then clear the cache and recompile your theme to ensure everything works correctly.
Clear the cache, install assets, dump bundles, and recompile the theme. In many cases, missing assets or an outdated theme cache are the cause of frontend issues after an upgrade.
Check that you can access the Shopware Admin, browse the storefront, test the checkout process, verify your plugins are working, and confirm there are no errors in the system health check.
