OutPerformerz
BACK TO SIGNALS
INFRASTRUCTURE#18

Shopware 6 update checklist: how to update without losing sales

Nov 19, 2026 · 7 min read

A Shopware 6 update rarely fails because of the core. It fails because of plugins, the theme, payment methods and tracking. This checklist covers what to prepare, how to run the update and what to check afterwards.

Why a Shopware update can cost you sales

For most stores, updating Shopware 6 is routine. When it goes wrong, the core is rarely the problem. The trouble comes from everything attached to it: plugins, a customised theme, payment integrations, tracking scripts and background processes. If one of those breaks, you may not notice right away. The homepage loads, product pages look fine, but the PayPal button is missing at checkout or order confirmation emails stop going out.

Typical consequences of an unprepared update:

  • A plugin is not compatible with the new version and gets deactivated or throws errors.
  • Template overrides in your theme no longer match changed storefront templates.
  • A payment method disappears or fails at the final step.
  • The purchase event stops reaching your analytics, so campaigns are steered on wrong data.
  • Background workers keep running old code because nobody restarted them.

The good news: with a fixed sequence of steps, you can catch most of this before the update or spot it right after.

Before the update: prepare staging and backups

Test every update on a staging system first. That is a copy of your live store on a separate server or subdomain. Keep it as close to production as possible: same PHP version, same plugins in the same versions, a recent database copy and the same theme.

What matters on staging:

  • Catch outgoing email. Otherwise real customers receive test emails. A mail catcher or disabled mail delivery prevents that.
  • Payment providers in test mode. PayPal, Klarna, card processors and others offer sandbox accounts. Live credentials do not belong on staging, partly because some integrations register webhooks for the current domain when you save the settings.
  • Restrict access. Password protection keeps search engines and customers away from the copy.

Before the live update you need a complete backup that you can actually restore. That means a database dump, media and files (for example public/media and files), configuration (.env, JWT keys) and the code, including custom/plugins. A backup you have never restored is a hope, not a plan. Restore it on staging at least once so you know how long it takes.

Check plugin compatibility and your theme

Plugins are the most common source of trouble after an update. Go through the list of installed plugins before you start:

  1. Is there a version of each plugin that its vendor declares compatible with the target Shopware version?
  2. Which plugins are installed but no longer used? Remove them cleanly before the update instead of carrying them along.
  3. Which plugins touch the checkout, cart or payment? These get extra attention during testing.

Minor and patch releases usually keep the extension interfaces stable. A major release, meaning a jump in the second version number such as 6.5 to 6.6, deliberately changes interfaces and removes deprecated features. Read Shopware's upgrade notes for it and check whether the PHP or database requirements change.

Review custom code and theme changes together with your agency or developer. Overridden Twig templates and custom storefront JavaScript plugins are fragile when the underlying templates change. On staging this usually shows quickly: missing elements, broken layouts or errors in the browser console.

Pick the right time and follow a fixed routine on the day

Choose a time with few orders. Your own order data tells you which hours those are; generic advice does not. Avoid days with running promotions, newsletter sends or big campaigns, and make sure someone has time to check things afterwards. Updating late on a Friday with nobody available the next day is asking for trouble.

A routine that works:

  1. Take a fresh backup right before the update.
  2. Switch the sales channels to maintenance mode and allow your own IP so you can keep testing.
  3. Run the update, either through the Administration or via Composer followed by bin/console system:update:finish, depending on how the store is installed.
  4. Update plugins, recompile the theme and clear the cache.
  5. Restart message queue workers and scheduled tasks so they pick up the new code.
  6. Run a quick functional test from your allowed IP, then end maintenance mode.

Decide in advance at what point you will abort and restore the backup. That decision is hard to make under pressure if you have not prepared it.

After the update: test purchases with every payment method, then tracking

The most important test after an update is a real purchase with every active payment method. A test order paid by bank transfer tells you nothing about PayPal, Klarna or cards, because each method has its own integration with its own scripts, redirects and callbacks.

For each payment method, check:

  • Does it appear at checkout, for guests and on mobile?
  • Does the redirect to the provider and back to the confirmation page work?
  • Does the order get the right payment status in the Administration?
  • Does the order confirmation email arrive?

Cancel and refund the test orders afterwards so they do not distort stock and reports.

Then check tracking. Open the store in Google Tag Manager preview mode or with your browser's developer tools and confirm that the consent banner appears, that tags fire only after consent and that the thank-you page sends a purchase event with transaction_id and value. Customised templates are a frequent cause of missing events, because tracking code often lives exactly there.

Monitor the store for several days after the update

Some problems never show up in a test purchase. They appear only under real traffic: an error that hits certain shipping countries, a plugin that fails on large carts, a payment method that hangs in one particular browser. So in the first days, watch closely:

  • Orders per hour and per day compared with the same weekday in previous weeks.
  • Share of each payment method. If one method drops to zero while total orders look normal, that is a clear signal.
  • Error logs in var/log plus web server and PHP logs. New errors that start at the time of the update deserve a close look.
  • Load times of key page types, since a disabled cache or a faulty plugin can slow the store down noticeably.
  • Gaps between store and analytics. If orders in Shopware are stable but GA4 purchases drop, the problem is tracking, not revenue.

Write down the date and time of the update. Whoever investigates a drop later saves a lot of time when it is clear what changed and when.

Shopware 6 update checklist

Before the update:

  • Staging is current, email is caught, payments run in sandbox mode
  • Compatible versions confirmed for all plugins, unused plugins removed
  • Upgrade notes and system requirements read, especially for major releases
  • Update fully tested on staging, including checkout
  • Backup of database, files and configuration taken and restore tested
  • Low-traffic time chosen, no running promotions
  • Abort criterion and responsible people agreed

After the update:

  • Workers and scheduled tasks restarted, cache cleared, theme compiled
  • Test purchase with every active payment method, as guest and with an account, on desktop and mobile
  • Confirmation email and payment status checked
  • Consent banner, tags and purchase event checked
  • Orders, payment method shares, error logs and load times watched for several days

How to keep an eye on the store after an update

If you would rather not compare order numbers and logs by hand every day after an update, Profit Guard can take over that watch: the Shopware 6 plugin learns your store's usual patterns and reports deviations in checkout, payment methods, funnel and frontend errors, each with a likely cause and a recommendation.

Spot problems before they cost revenue

Profit Guard runs as a plugin in your Shopware shop and reports checkout outages, payment problems and drops in the purchase funnel.

Explore Profit Guard