• Shopware Gold Partner & Shopify Partner
Shopware 6 update: process, test plan and the errors that really occur after updates

Shopware 6 update: process, test plan and the errors that really occur after updates

How Shopware releases versions

Shopware numbers versions with four digits, for example 6.7.16.0. Three kinds of releases matter for planning:

  • Major versions such as 6.6 or 6.7 contain breaking changes. Extensions and themes may stop working without adjustments.

  • Minor versions such as 6.7.15 to 6.7.16 appear roughly monthly. They bring features, bug fixes and security fixes, but no intentional breaks.

  • Patch versions in the fourth digit fix individual errors, sometimes at short notice when a minor release had a problem.

The current state of versions:

  • 6.7 has been the current major version with regular minor releases since June 2025.

  • 6.6 is the version in Extended Support. Shopware extended this support; it remains active until 6.8 is released.

  • 6.8 is announced for 2027. There is no exact date. Anyone planning with a fixed end date for 6.6 is planning with a figure Shopware does not give.

  • 6.5 and older no longer receive regular maintenance.

For older versions there is the free Shopware 6 Security Plugin. It backports known security fixes to existing installations without updating Shopware itself. It does not replace updates. It bridges the time until the next update.

How often to update? The honest answer

There is no frequency that is right for every shop. Every update takes time for testing, and testing costs budget. We advise how urgent an update is, and the merchant decides. Three rules still apply to every shop:

  • Security fixes immediately. At least through the Security Plugin, which for critical vulnerabilities is usually updated before the actual Shopware release.

  • Never fall out of the supported line. A version without support no longer receives security fixes, and every later update becomes a major project.

  • Plan major updates as a project. With budget, a test phase and coordination with every system connected to the shop.

When deciding when to apply a minor update, one question matters most: are ERP, PIM, payment providers, shipping interfaces and all extensions compatible with the new version? An update the shop survives but the inventory integration does not is not an update, it is a delayed outage.

What an update actually touches

Looking only at the Shopware version shows a fifth of the risk. An update touches five layers:

  1. The Shopware core: database migrations, changed interfaces, new behaviour in checkout or cache.

  2. Extensions: plugins and apps from the Store, from third parties and custom developments. Every single one must fit the new version.

  3. Theme and template customisations: every overridden Twig template is based on the version that was current when it was customised. If Shopware changes the original template, the customisation keeps running on the old state.

  4. Interfaces: ERP, PIM, payment providers, shipping, marketplaces, feeds. They often react to changed data structures not with an error but with wrong data.

  5. Infrastructure: PHP version, MySQL or MariaDB, Redis, OpenSearch, workers for the message queue and scheduled tasks. For major updates, PHP must first be brought to the required minimum version.

The three ways to update Shopware

Which route your agency chooses says a lot about the quality of its care.

Updating in the administration under Settings > System > Shopware Update. Shopware itself recommends this only for small installations, because it can fail on server time and memory limits. For a shop with significant revenue it is not the right way.

Updating via Composer in the project: raise the version constraint for shopware/core in composer.json, update dependencies, refresh configuration recipes, commit everything and roll it out through the normal deployment.

The Shopware CLI upgrade wizard: it runs read-only checks first, shows the planned changes, runs the Composer update and writes a report. With the dry-run option you can see beforehand which extensions block. For the compatibility check, extensions must be managed via Composer. In shops where plugins were uploaded as ZIP files, that is the first clean-up step.

On the live server, after the new code is deployed, the same order always applies: maintenance mode on for all sales channels (sales-channel:maintenance:enable --all), prepare the update (system:update:prepare), finish the update with the database migrations (system:update:finish), maintenance mode off. The update commands only run once the new code is actually on the server; otherwise migrations and code do not match.

How an update runs at arboro

  1. Inventory: current version, target version, list of all extensions with compatibility, list of all template customisations, list of all interfaces with contacts.

  2. Coordination with connected systems: ERP, PIM and payment providers confirm compatibility with the target version before a date is set.

  3. Backup of database, media and code, immediately before the update.

  4. Update on staging with a copy of live data. How the test system is built is covered in Shopware staging and backup.

  5. Template comparison: for every overridden template we check whether Shopware changed the original and carry the change over into the customisation.

  6. Work through the test plan, see below. With a log of what was checked and by whom.

  7. Merchant approval, scheduled at a low-revenue time.

  8. Live update with maintenance mode and a defined way back.

  9. Follow-up in the first hours and days: error logs, incoming orders, interface runs, load times.

The test plan after every update

Functionality

  • Home page, categories, filters, search, product pages with variants

  • Cart, vouchers, shipping costs, checkout with every active payment method, as a guest and with a customer account

  • Customer account, password reset, newsletter sign-up

  • Emails and documents: order confirmation, invoice, delivery note, cancellation invoice

  • Edge features that are rarely used and therefore noticed last: wishlist, product comparison, reviews, contact forms, B2B features

Technical SEO

  • Structured data for products, breadcrumbs and organisation, checked with the Rich Results Test

  • Canonical tags, hreflang in multilingual shops, meta robots on filter pages

  • Page titles and meta descriptions from the SEO templates

  • Sitemap, robots.txt, redirects and 404 pages

  • Load times and Core Web Vitals compared to before the update

Browsers and devices

  • Safari on iPhone, Chrome on Android, Chrome, Firefox and Edge on desktop

  • Especially: checkout, payment provider windows, cookie banner, mobile menu

Interfaces and background processes

  • Order export to ERP, stock and price sync, import from PIM

  • Payment provider notifications, shipping labels, tracking

  • Feeds for Google Shopping and price comparison sites

  • Message queue and scheduled tasks: are the workers running, is anything piling up?

What we find most often after updates in shops we take over

When we take over a shop from another agency, one of the first things we check is how the last updates went. Four patterns come up again and again:

The update was applied but not tested thoroughly. The shop runs, the home page loads, checkout works. What was visible at first glance was tested. Everything underneath was not.

Technical SEO errors under the hood. After an update, structured data is incomplete or faulty because a template was customised and the new version was not carried over. Canonicals or meta data no longer match on parts of the site. You see none of this in the shop. You see it weeks later in Search Console and the rich results, when stars and prices have disappeared from search results.

Template changes not carried over cleanly. Shopware changes storefront templates with every release. Anyone who overrode blocks must follow these changes in their own theme. If that does not happen, new features, accessibility improvements or bug fixes are missing exactly where the shop is customised, which is often in the most important places.

Browser errors from lack of testing, and plugin conflicts in edge features. Testing happened in one browser on one computer. On the iPhone a layout breaks or a payment window does not open. Add conflicts between two plugins that each work alone but together break an edge feature, such as a filter, a form or voucher logic. Such errors stay undiscovered for a long time because they only affect some customers.

Major update from 6.6 to 6.7: what is concretely different

A major update is not a big minor update but a project of its own. For 6.7 this mainly concerns:

  • Administration: it runs fully on Vue 3, the Vue 2 compatibility mode has been removed, and the build moved from Webpack to Vite. Plugins that extend the administration need a separate version for 6.7.

  • Storefront: global template variables were fundamentally reworked, and individual areas such as the service navigation were removed. Custom themes and template customisations must be checked and adapted.

  • Accessibility: in view of the European Accessibility Act, the improvements are active by default in 6.7. In 6.6, the changes involving breaking changes sit behind a feature flag and must be switched on actively.

  • System requirements: PHP 8.2 as minimum, tested with MySQL 8 and MariaDB 11.

If you are still on 6.6 you have time, but not unlimited time. Extended Support for 6.6 ends when 6.8 is released, expected in 2027. It makes sense to plan the move to 6.7 now rather than take two major versions at once later.

How to tell an update did not go cleanly

Fixing the errors is your agency's job. You should still recognise them, because many show up in the business first, not in the shop:

  • Orders come in but are not processed further. Order confirmations are missing, the ERP receives no orders, invoices are not created. Usually the background processes stopped running after the update. This is the most expensive error, because it only shows when customers ask.

  • Products are missing from categories or search. The indexes were not rebuilt after the update.

  • Stars, prices or availability disappear from Google results. The structured data has been faulty since the update. It only becomes visible weeks later in Search Console.

  • Conversion rate drops on certain devices. A layout or payment window no longer works in Safari on the iPhone, while desktop is fine.

  • A rarely used feature stops working. A filter, a form, voucher logic. Typical of conflicts between two plugins.

Every one of these belongs in the test plan before going live. If you only notice it in day-to-day business, testing was not thorough enough.

What a Shopware update costs, and why there is no flat price

A price range for "a Shopware update" would be so wide that it says nothing. The effort depends almost entirely on the complexity of the shop. Two examples from either end of the spectrum:

  • A simple shop with the standard theme, a swapped logo, two payment methods and two or three plugins. A minor update with a short test is done quickly here, and the risk is low.

  • A large shop with several hundred thousand euros in monthly revenue, around a hundred plugins, a custom theme with many template customisations, its own product configurators and connections to ERP, PIM and other systems. Here even a minor update is a small project, because every interface and every customisation has to be checked.

The cost drivers are therefore always the same:

  • Number and origin of extensions, especially custom developments

  • Number of overridden templates and how cleanly they are maintained

  • Connected systems such as ERP, PIM, payment providers, marketplaces and their compatibility

  • Custom features such as configurators, B2B logic or pricing rules

  • Scope of testing, and who takes on which part

  • Distance to the target version: skipping several versions means paying for all of them at once with the next update

You can save costs on testing yourself. Your team can take over the visual test, checking that pages, products and flows look right from a customer's point of view, using a checklist. The technical tests of interfaces, background processes and technical SEO stay with us.

For major updates we quote a fixed price after analysing the shop. For ongoing updates we agree with you, as part of our care and the SLA, how often and to what extent updates are applied.

What you should expect from your agency for updates

Five questions separate a professional update from an update on luck:

  • Is there a test system with current data, and is it updated there first?

  • Is there a written test plan and a log of what was tested? Including technical SEO, browsers and interfaces.

  • How are template customisations reconciled after updates? Shopware recommends versioning Twig blocks for this. It makes it possible to detect automatically after every update which overridden templates need to be updated. Ask whether your agency works this way.

  • What is the way back if something goes wrong?

  • Who monitors the shop after the update, and how quickly do they react? That belongs in the SLA.

If you do not get clear answers to these questions, that is a reason to look more closely.

Rollback: the way back must be settled beforehand

A Shopware update cannot be undone at the push of a button, because database migrations have run. The way back is a backup of database, media and code taken immediately before the update. Shopware only recommends a way back without restoring the database, for example via blue-green deployment, if only Shopware was updated and no extensions. Orders received between the update and the rollback must be secured separately. That is why the update appointment also includes deciding until when a rollback still makes sense.

Checklist: what a clean update looks like

  • Target version set, upgrade notes read

  • Compatibility of all extensions checked, blockers resolved

  • ERP, PIM, payment providers and shipping have confirmed compatibility

  • PHP and database at the required level

  • Backup of database, media and code immediately before the update

  • Update applied on staging with live data

  • Template customisations compared against changed original templates

  • Test plan completed: functionality, technical SEO, browsers, interfaces, queue

  • Merchant approval, scheduled at a low-revenue time

  • Live update with maintenance mode, way back defined

  • Follow-up over several days

How we do it at arboro

We advise when an update makes sense and what it costs, and you decide. We recommend security fixes immediately and apply them promptly once agreed. We test every update on staging against the test plan above, including technical SEO and interfaces, and only go live after your approval. arboro.PULSE then monitors the shop continuously: checkout, load times, errors and technical SEO down to the structured data on every page. To do this, PULSE crawls the shop more deeply than a classic SEO crawler such as Screaming Frog. That way an error after an update shows up before customers or Google notice it. More on arboro.PULSE and Shopware & Shopify support. If your shop has run for months without an update, or updates were applied without testing, that is a good reason to think about switching your Shopware agency.

How we check the technical SEO of a Shopware shop is described on Shopware SEO, and how we develop extensions and themes on Shopware & Shopify development.

Frequently asked questions

Security fixes immediately, at least through the Shopware Security Plugin. There is no minor-update rhythm that suits every shop. It depends on the budget for testing and on when ERP, PIM and extensions are compatible with the new version. What matters is never falling out of a supported version.

According to Shopware, Extended Support for 6.6 remains active until Shopware 6.8 is released. 6.8 is announced for 2027; there is no fixed date.

No. The Security Plugin closes known vulnerabilities in older versions. It does not replace updates and brings no bug fixes, features or compatibility with new extensions.

Only through a backup of database, media and code taken immediately before the update. A way back without restoring the database only makes sense if Shopware alone and no extensions were updated.

It depends almost entirely on the complexity of the shop: number of plugins, template customisations, connected systems such as ERP and PIM, custom features and scope of testing. A simple shop with few plugins is updated quickly; a large shop with many interfaces is a small project even for a minor update. For major updates we quote a fixed price after an analysis. Your team can take over the visual test and save costs.

Author

Florian Gronau

Florian Gronau

Head of Development / Authorised Signatory

Florian makes sure everything runs smoothly for our customers! He's got loads of experience in e-commerce and app development. As a certified IT specialist, he handles our clients' Shopware shops, plugins, and connects their shops with the ERP. With his friendly and communicative nature, he's the go-to for tech questions.

Support

Updates tested before they go live

We plan updates with you, test on staging including technical SEO and interfaces, and then monitor everything down to the structured data with arboro.PULSE.