Run a Shopware updatewithout stallingthe checkout

Release cycle

How often is there a Shopware update, and which version is current?

A Shopware update comes in three sizes, and each has its own rhythm. According to the release strategy there is one major version a year, minor versions arrive on the first Monday of every month, and patches come whenever they are needed. So the small steps can become as ordinary as closing the books at month end, while the big step once a year is really a project of its own, with a budget and a date you put in the calendar well ahead.

Only the newest minor version of the current cycle is actively maintained. Once the next major version is out, the last minor version of the old cycle moves into extended support and receives selected bug fixes and security updates. Anything older only gets security fixes through the Shopware Security Plugin.

The current release is Shopware 6.7.15.0, published on 30 September 2026 (as of October 2026), and the 6.6 branch stands at 6.6.10.28. If you are still on an early 6.7, you have quite a bit to catch up on. That rarely happens on purpose. Updates just pile up because the shop is selling and something in day-to-day business always feels more urgent.

Version scheme

Which kinds of Shopware 6 update are there, and which ones affect your extensions?

The version number tells you what kind of Shopware 6 update you are looking at, because it follows the scheme 6.Major.Minor.Patch. The six at the front is the generation, followed by major, minor and patch. Going from 6.7.14.0 to 6.7.15.0 is a minor update, going from 6.6 to 6.7 is a major one.

For your extensions that difference matters a lot. According to Shopware, minor versions usually bring nothing that breaks existing code. Breaking changes are part of the deal with major versions, though, and every extension has to declare which Shopware versions it supports. A plugin released for 6.6 will not simply carry on running under 6.7.

How much work a custom extension causes on a major jump depends heavily on how it was built. Our guide to Shopware plugin development explains how to set plugins up so that updates stay predictable.

Shopware 6.7

What changed with Shopware 6.7?

Shopware 6.7 is the major version of 2025, and most of what it renewed sits underneath the Administration. The build now runs on Vite instead of Webpack, the Administration runs entirely on Vue 3 (without the compatibility mode), and state is handled by Pinia where Vuex used to be. Caching was reworked as well; the Store API's own cache layer is gone.

In everyday shop operations you notice this mainly in one place: plugins with their own part in the Administration need separate versions for 6.6 and 6.7. Further down, other building blocks were renewed too, such as the database layer DBAL, now on version 4. And if you run a custom theme, be aware that key template variables were removed or are only available in a limited form.

Your server has to keep up as well. Shopware 6.7 requires PHP 8.2, 8.3 or 8.4, MySQL 8.0.17 or later or MariaDB 10.11 or later, and Node.js 20 or later. Check this with your host before you plan anything else, because if the server cannot meet these requirements, all the other preparation is wasted.

Incidentally, 6.7 itself shows how little a release date tells you about a major version: Shopware's announcement named 14 May 2025, while the endoflife.date directory lists 17 June 2025. For your plan that is a side issue. What counts is the day your extensions are released for it.

Outlook

What is officially known about Shopware 7?

There is no official announcement and no date for Shopware 7 so far (as of October 2026). What Shopware has announced is the next major version, 6.8, which is now planned for 2027 after originally being scheduled for 2026.

Along with that delay, Shopware extended the extended support for 6.6, which now runs until 6.8 is released. If you are still on 6.6, there is no need to rush. You should still plan the move to 6.7, though, because new features and most extensions are concentrated there.

So if you read about specific features or even a launch date for Shopware 7 somewhere, we would be cautious. The release strategy is what you can rely on, and according to it the next big version up to 2027 is simply 6.8.

Preparation

How do you prepare a Shopware update without putting the live shop at risk?

You prepare a Shopware update in four steps: set up a test system, take a backup, check your extensions, and fix a date for the live run. The test system (staging) is a copy of your shop with the same code and the same extensions, ideally with reasonably current data, and that copy is where the update runs first.

The backup covers both the database and the files. Shopware explicitly recommends one before installing any update, so that you can restore the shop if something goes wrong. Please try restoring it at least once before you need it for real, because a backup that cannot be restored in the end is just a reassuring file sitting on the server.

The Administration itself helps with the extensions. Under Settings, System, Shopware Update, Shopware shows for every active extension whether it is already compatible, whether a compatible version is available for the new release, or whether it remains incompatible. If it says incompatible, sort that out with the vendor or your developer before the update. When your own plugins are affected, it is a good moment to look at Shopware development at Scalableloops; we test our extensions on 6.6 and 6.7.

For the live run there is a maintenance mode per sales channel. While it is active, the storefront only shows a maintenance page, and orders cannot land in a half-updated shop. Pick a window with little revenue. And not Friday evening, however tempting it looks.

Running it

Shopware update via the Administration or the command line?

For a Shopware update in a small shop the Administration is enough, while for larger shops the command line is the more stable route. The web updater under Settings, System, Shopware Update takes you from the compatibility check through to installation. Shopware itself, however, only recommends it for small instances, because it can fail on the server's time limits and resources.

The second route goes through Composer. You set the target version in the project file and pull it in with composer update, then run bin/console system:update:prepare and bin/console system:update:finish on the server, and finally switch maintenance mode off again. The advantage is that the process is versioned, can be repeated exactly on the test system and does not break off because of a browser time limit.

If your shop runs in the Shopware Cloud as SaaS, the question does not come up, because Shopware takes care of hosting and updates there. With self-hosted shops and PaaS, the update is down to you or your service provider.

Testing

What should you check after a Shopware update before customers order?

After a Shopware update, check the path that earns you money first: home page, category, product page, cart and checkout. Shopware lists the Administration, the storefront, the extensions and the error logs for the check afterwards. We add two things that never show up in a log, namely payment methods and tracking.

A test order with each active payment method shows whether the connection to the payment provider still holds after the update. For tracking, looking at the source code is not enough. Trigger a purchase and check in your ad account or in your tag manager's debug mode whether the purchase event arrives with a value, for example via Google Tag Manager for Shopware. This is the one people tend to miss: an update that leaves the checkout intact but loses the purchase event often goes unnoticed for days, until the campaigns suddenly look worse even though nothing has changed in sales.

If you also want to compare loading times, you will find measuring points in our guide to Shopware performance.

1. Check 1StorefrontHome page, category, product page, search: click through layout, prices, images and filters on a phone and on a desktop.
2. Check 2Cart and checkoutAdd an item to the cart, redeem a voucher, choose a shipping method, complete the order, check the order confirmation.
3. Check 3Payment methodsOne test order per active payment method, then check the payment status in the Administration.
4. Check 4Tracking and consentCookie banner, purchase event with value and order number, confirmed in the ad account or in debug mode.
5. Check 5Administration and extensionsAll extensions active and up to date, orders and products can be edited, interfaces to ERP and shipping are running.
6. Check 6LogsRead the error logs in the first hours after the update, not only when the first complaint comes in.

When it has to wait

What can you do when a Shopware update is not possible right now?

If you have to postpone a Shopware update, for example because the Christmas season is in full swing, close security gaps with the Shopware Security Plugin. It is meant for versions that no longer receive direct patches and delivers the fixes without you having to change version.

It is not a permanent solution, though, more of a bridge. The longer a shop stays on an old version, the bigger the jump becomes later and the more extensions have to move at the same time. Shopware 5 is a separate topic, by the way, because getting from there to 6 means switching systems. Our guide to the migration from Shopware 5 to 6 walks through it.

Whether a Store extension or a custom solution makes updates easier is compared in Shopware plugin: buy or build.

Before your next update

How to plan your next Shopware update

1. 01Check version and requirementsThe version is shown in the Administration, and your host knows the PHP and database versions. If PHP is below 8.2, that is the first thing to fix.
2. 02List your extensionsA simple list is enough: every active extension, who supplies it and whether it has been released for the target version. As long as anything says incompatible, we would not set a date.
3. 03Prepare staging and backupRun the update on the copy and work through the checks above. While you are at it, restore the backup once, so you know it works when it matters.
4. 04Set the live windowIdeally a quiet hour with few orders, maintenance mode on, and the time for testing afterwards planned in from the start. If you would like support, there is our free Shopware consultation.