1. Record the starting point
Write down the current Shopware release, target release, installed extensions, theme customisations and hosting requirements. Read the release-specific update instructions and confirm extension compatibility. Do not assume that instructions for a different version or hosting model apply unchanged.
Keep this list with the release notes. It makes failures easier to investigate and gives another developer enough context to help.
2. Make recovery a real option
Prepare a consistent backup of files and database, and verify that your team can restore it. A backup job reporting success is not the same as a successful restore test. Define who can trigger recovery and what happens to orders received after the backup.
Use a separate staging environment for the rehearsal. Prevent it from sending real customer emails, charging live payment methods or pushing test orders into production systems.
3. Test the customer journey
- Open a category and a product with variants.
- Search for an item, apply filters and check stock display.
- Add, change and remove cart items; test a promotion.
- Check guest and account checkout, shipping and tax scenarios.
- Use payment-provider test modes and verify order confirmation.
- Inspect connected ERP, fulfilment and notification workflows.
Record the expected and actual result for each test. Use representative products and supported delivery destinations rather than testing only the homepage.
4. Launch and observe
Agree a release window, responsible person and rollback decision point. After launch, inspect application errors, scheduled tasks and queue processing as well as the storefront. Confirm that new orders reach the systems that depend on them.
If checkout or data integrity is uncertain, pause further changes and investigate. A successful installation message alone is not a completed release. For an ongoing process, review our Shopware maintenance packages; for extension work, see Shopware development.