Skip to content

Vendor-neutral, engineer-written explanations. Clear definitions first, then practical steps with real examples — no fluff.

.How do I test updates on staging and then deploy to production (best practice)?

SB
Written by StageBit Engineering Team
Updated May 2026 0 min readVerified by engineers

Quick Answer

The safest way to update Shopware is to test every update on a staging environment first, validate storefront and checkout behaviour, then deploy the exact same code and database changes to production during a controlled release window. Your staging store should closely match production in PHP version, extensions, caching, search, and server setup. The process below covers a reliable deployment workflow most agencies use for real production stores.

Before You Start

  • Separate staging environment — it should mirror production as closely as possible.
  • Version control with Git — deploying directly from FTP usually creates rollback problems later.
  • Recent database and media backups — you need a clean rollback point before every release.
1

Clone production into staging

Start by copying the live database, media files, installed plugins, and environment configuration into staging. Your staging store should behave almost exactly like production. That includes PHP version, Redis setup, Elasticsearch or OpenSearch, cron jobs, and payment integrations. Most update problems only appear when environments differ slightly.

  • Copy the latest production database
  • Sync uploaded media and theme assets
  • Disable real payment and email sending
IMPORTANT Never test updates on an outdated staging database—plugin migrations can behave differently from live.
2

Apply updates in staging

Update Shopware core, plugins, themes, and Composer dependencies inside staging first. Run migrations, clear caches, rebuild the administration, and compile storefront assets. Keep a deployment log so you know exactly which commands and versions were used during testing.

  • Run Composer updates carefully
  • Execute database migrations
  • Rebuild storefront and administration assets
PRO TIP Tag the tested release in Git before production deployment so rollback is faster later.
3

Run functional testing

Test the areas that generate revenue first. Checkout, login, shipping, payment methods, ERP integrations, promotions, customer groups, and search should all be checked manually. Stores with many plugins usually break in edge cases rather than obvious pages.

  • Create test orders with multiple payment methods
  • Validate plugin workflows and automations
  • Check logs for hidden PHP or plugin errors
COMMON MISTAKE Teams often test only the homepage and PDPs while skipping checkout edge cases and B2B pricing logic.
4

Prepare production deployment

Schedule deployment during lower traffic hours and put the store into maintenance mode if needed. Create fresh backups immediately before deployment. The safest production releases are predictable and repeatable—not rushed changes directly on the server.

  • Create final database and media backups
  • Freeze content edits during deployment
  • Confirm rollback steps before starting
IMPORTANT A backup is useless if nobody has tested the restore process before release day.
5

Deploy and validate production

Deploy the same tested release from staging into production. Then validate the storefront immediately after launch. Most serious issues appear within the first 15 minutes after cache warm-up and traffic resumes.

  • Run migrations and cache clears
  • Place a real production test order
  • Monitor logs, queues, and server resources
PRO TIP Keep the previous release ready for rollback for at least 24 hours after deployment.

Shopware Deployment Checklist

0 of 8 complete

Mistakes Most Developers Make

! Testing with old staging data

What happens: Plugin migrations and customer data issues appear only after production deployment.

Fix: Refresh staging from production before every major release cycle.

! Updating plugins blindly

What happens: One incompatible plugin can break checkout or administration access.

Fix: Check plugin compatibility against your Shopware target version before deployment.

! No rollback plan prepared

What happens: Small deployment failures turn into hours of downtime while teams improvise fixes.

Fix: Keep the previous release, backups, and rollback commands ready before deployment starts.

Key Takeaway

The short version: safe Shopware deployments come from testing updates on staging first, validating business-critical flows, and deploying the exact tested release into production. Most failures happen because staging does not match production or because rollback planning was skipped. Your biggest priorities should be checkout testing, plugin compatibility, and reliable backups. Stores with heavy customisation should also monitor logs closely after launch. Start with Step 1—that one alone handles most of it.

Was this answer helpful?

Your feedback helps us improve our answers.

Still need help?

Talk to our Shopware experts

We've handled GDPR/CCPA compliance for dozens of EU & US Shopware stores.

Talk to Shopware Experts

Tell us more about your brand!

Rohit Kundale, Our VP of Sales and Marketing is ready to meet with your team.