How your store stays online during updates
An update without downtime takes three things. If you update straight in the live store and hope for the best, you are testing with real customers.
- 01
A copy first
The update is applied to a copy of the store and tested there through to a test order.
- 02
A fresh backup
Files and database are backed up right before the live update.
- 03
A clear way back
How the previous state comes back is settled and tried out in advance.
The Shopware 6 release model
Shopware 6 uses a four-part version scheme. The leading 6 stands for the product generation. 6.7.0.0 was a major version, 6.7.1.0 a minor version, 6.7.1.1 would be a patch.
Patch
Low riskUrgent bug fixes and security fixes.
Minor
Medium riskNew features and improvements, according to Shopware without breaking existing extensions.
Major
A project of its ownTechnical overhauls with so-called breaking changes.
Shopware had announced yearly major versions. 6.7 came out in June 2025, and 6.8 has since been announced for 2027. There is no fixed date yet.
Only the latest minor version of the current major version regularly receives patches. The last minor version of the previous major version gets extended support for a while, older versions only the security plugin. If you skip updates for years, you end up without security updates.
Why extensions and themes break during updates
A Shopware store rarely consists of Shopware alone. There are payment and shipping plugins, Store extensions, a theme and often custom development on top. Each part hooks into Shopware at specific points.
Major updates
change these points on purposeShopware updates frameworks such as Symfony or Vue.js, removes deprecated interfaces and often requires a newer PHP version. Extensions that have not been adapted stop working afterwards.
Minor and patch updates
are not supposed to break anythingAccording to Shopware, rare exceptions come with security patches. Still, some plugins rely on internal behavior, or a theme overrides a template that has changed. Then a button, a checkout field or a payment method is missing.
Plugin updates
bring their own bugsEven without a Shopware update, an updated extension can cause errors.
Many of these errors do not show up on the homepage. They only appear in the cart, with a payment method or in the order confirmation.
Checklist for a safe Shopware update
Twelve points in three phases. The first two phases happen on the copy, only the third touches the live store.
Before the update
- Read the changelog. What changes? For major versions this includes the upgrade documentation, along with the minimum requirements for PHP and the database.
- Check extension compatibility. For every extension, find out whether a fitting version exists, for example with a dry run of the Shopware CLI. Plugins that are no longer maintained are a warning sign.
- Create a copy of the live store. Real products, categories and settings, but anonymized customer and order data.
- Plan the backup. Back up the database and files right before the live update, and know how restoring works.
Test on the copy
- The right order. For major updates, raise PHP first, then update Shopware and the extensions together. Composer resolves both in one step.
- Clear the cache, rebuild the indexes. Otherwise the Storefront and search show old or incomplete data.
- Test the checkout thoroughly. One order per payment method in test mode, plus discount codes, shipping costs, guest checkout, customer account and order confirmation.
- Check the other features. Search, filters, Shopping Experiences, forms, the Administration, the handover to your ERP or inventory system, and the error logs.
Go live
- Pick the timing. A time with few orders, not right before a promotion and not on a Friday evening.
- Take a backup, apply the update. Roll out the tested version. For larger database changes, switch the sales channels into maintenance mode beforehand (sales-channel:maintenance:enable --all); only the web updater does this on its own.
- Check right afterwards. A test or real order, homepage, category, product page, login.
- Keep the rollback ready. Better to restore the previous state than to hunt for the error under time pressure. Save the orders placed in between.
A small project of their own
Patch and minor updates fit into a fixed maintenance schedule with the checklist. A major update such as 6.6 to 6.7 needs more lead time.
Shopware publishes a release candidate before every major version so developers can adapt their extensions. Even so, it often takes weeks until every Store plugin in your store has a compatible version.
- 01
Make an inventory early
Which extensions are installed, which already exist for the new version, and which are still needed?
- 02
Plan for custom code
Your own plugins and theme customizations have to be adapted to the breaking changes. That is development work, not configuration.
- 03
Prepare the server
New major versions often require a newer PHP version. Check in good time whether your hosting offers it.
Do not switch on day one.
The previous major version keeps receiving security updates for a while. Waiting for the first patches is usually the calmer choice.
Typical problems after an update
Almost all of them can be found on a copy with one complete test order, before a customer notices.
- Problem 01
Payment method missing
no longer appears in checkout - Problem 02
No confirmation
the order confirmation is not sent - Problem 03
Wrong amounts
prices or shipping costs are calculated wrong - Problem 04
Search has gaps
new products are not found - Problem 05
Admin stuck
a single page of the Administration does not load
Why the live store should not be your test system
Many stores are updated directly in production with the update button in the Administration. That often works. When it does not, the error happens exactly where it costs the most.
Update button in the live store
- Customers abandon their purchase, payments go nowhere.
- Troubleshooting under time pressure while the store is selling.
- An update changes the database. Copying old files back is not enough, and without a backup from right before, it gets difficult.
- The button checks neither payment methods nor how the theme displays.
Update on a copy
- If an update fails on the copy, it costs nothing.
- The error gets fixed calmly.
- Only the working state goes live.
- The risk sits where mistakes are allowed.
I compare the options, from your host’s staging area to a managed solution, in the guide to staging environments.
How I handle this with the Doppelgänger
I have worked with Shopware 5 for more than six years and with Shopware 6 for more than four. The checklist above applies to every store I look after. With the Doppelgänger for Shopware, every update follows this pattern:
-
Tested through to checkout
Shopware, extensions and theme go onto an exact copy on a dedicated server in Germany first, tested through to a completed order. Customer data anonymized. -
Publishing without downtime
Automated publishing brings the checked state live within a few minutes. Security updates usually within 24 to 48 hours. -
A test order every morning
Automatically through the live store up to payment. If checkout fails, I notice before your customers do. -
Rollback in seconds
Every release is a version of its own. The previous state is restored in seconds.
Still on Shopware 5? Then you face a different task, more on that in the guide to migrating from Shopware 5 to 6.
From a client: For JuCad I have handled the Shopware updates since 2020, look after the connection to their ERP system and keep building new features.
Since 2020 Julian has been our go-to person for the store, and he knows it inside out: every interface, the connection to our ERP system and custom features like the Trolley-finder, the Trolley comparison and the product FAQs. So we never have to explain at length what we need. We check in every week, and what we discuss is usually done by the next meeting. Updates are simply no longer something we have to think about.
Quick answers.
How often should I update Shopware 6?
Security updates should be applied promptly, ideally within a few days of release and after a test. Minor versions come out monthly, and it is often enough to apply them bundled on a fixed schedule. What matters is not falling too far behind, because only the latest minor version of the current major version regularly receives patches.
What is the difference between a minor and a major Shopware update?
Minor updates bring new features and improvements but are not supposed to break existing extensions. Major updates change the technical foundation, such as framework versions and interfaces, and usually require updated plugins, an updated theme and often a newer PHP version.
Can I undo a Shopware update?
Yes, but only if you prepared for it. An update changes the database as well as the files, so a rollback needs a backup of both, taken right before the update. If you restore the database, orders placed after the update have to be saved separately.
Why does my plugin stop working after a Shopware update?
Usually the plugin is not yet compatible with the new Shopware version or was not updated at the same time. Before updating, check whether the vendor offers a compatible version. Custom plugins and theme customizations need their code adapted.
Does my store have to go offline during an update?
Not necessarily. With an update that has been prepared and tested on a copy, the actual switch on the live server often takes only minutes. For large database changes, for example in major updates, a short maintenance window can make sense, and you can schedule it for a time with few orders.