---
title: Shopware Update | Shopware Community Hub
description: This section describes types and ways to update Shopware effectively.
canonical_url: 'https://hub.shopware.com/learn/unit/shopware-update'
---

# Shopware Update

<LearningObjectives>

- Explain the critical importance of **Shopware updates** for security, performance, and feature enhancements
- Differentiate between **major, minor, and patch releases** and their respective update frequencies
- Implement **best practices** for planning and executing Shopware updates safely and efficiently

</LearningObjectives>

# Shopware Update

Shopware is a powerful, flexible ecommerce platform, but like any software, it requires regular updates to stay secure, compatible, and efficient. For agencies managing Shopware sites for clients, updates are key to maintaining a robust, reliable ecommerce environment.

## Why Shopware Updates Are Essential

Shopware updates are crucial for several reasons:

- Security: Updates address vulnerabilities and prevent potential data breaches that could lead to revenue loss and damage to brand reputation.
- Performance: Many updates include optimizations that improve load speeds and site performance, directly impacting customer satisfaction and sales.
- New Features: Shopware frequently releases new features and tools that improve site functionality and offer clients a competitive edge.
Long-Term Stability: Regular updates prevent technical debt, reduce compatibility issues, and ensure that the site remains resilient and compliant with the latest technologies and standards. They also keep the platform compliant with data protection and industry standards, helping clients avoid legal issues and maintain customer trust.

Different types of releases can contain different kinds of changes. The release process also varies depending on the distribution type of Shopware. For the SaaS version of Shopware, a continuous delivery process is in place where forward-compatible changes are deployed once a week. For the self-hosted version of Shopware, a typical semantic versioning system is in place, which includes the following releases.

## What are the types of releases and frequency?

| Release type | Details | Frequency |
|--------------|---------|-----------|
| Major | It's the' biggest form of a release. It focuses primarily on technical improvements, and it's the only type of release that allows for breaking changes. In this, all the deprecated code parts of the previous major cycle are removed, 3rd party frameworks are updated, minimum system requirements are raised, and those features flagged as `@experimental` are moved to stable. | Once a year |
| Minor | It's the most common release type and delivers recent bug fixes and new forward-compatible features to our customers. | Every first Monday of the month |
| Patch | It's performed on demand, and its scope is limited to the necessary fix - critical issues or security vulnerabilities | On demand |

To perform these updates, follow the [guidelines](https://docs.shopware.com/en/shopware-6-en/update-guides/updating-shopware)

## The Right Approach to Shopware Updates

Not every update needs to be applied immediately. A strategic approach to updates helps ensure that the client receives maximum value with minimal risks or costs. Here's how to decide when and what to update.

### Prioritize Beneficial Updates

- Value-Driven Updates: Focus on updates that bring direct benefits, such as security patches, performance improvements, or valuable new features that enhance the customer experience.
- Urgent vs. Routine: Security patches or critical bug fixes should be addressed immediately, while minor updates and feature releases can be planned around client needs.

### Avoid Updating Just to Update

Applying every update as soon as it's released can disrupt site stability and create unnecessary work. Only apply essential updates or add meaningful value, reducing the risk of downtime or compatibility issues.

## Planning and Preparing for Shopware Updates

A clear, well-organized update plan helps agencies manage updates effectively while minimizing client impact.

### Establish a Maintenance Schedule

- Regular Maintenance Calendar: Set a schedule for routine updates, like quarterly or biannual reviews, to keep the platform secure without frequent interruptions.
- Flexibility for Urgent Updates: Use flexibility to apply critical patches or bug fixes as needed.

### Plan Major Updates in Advance

Major updates often involve significant changes, including potentially breaking changes that can affect plugins and themes. To handle these effectively:

- Resource and Time Allocation: Major updates require thorough testing and staging, so set aside adequate resources.
- Client Communication: Coordinate with clients on timing and expected benefits well in advance, particularly if downtime is anticipated.
- Plugin and Theme Compatibility: Before any major update, inventory plugins and themes should be checked for compatibility with the new version and prepared for adjustments if needed.

### Implement a Reliable Backup and Rollback Plan

Having a solid backup and rollback plan is essential for minimizing risk:

- Automate Backups: Regular, automated backups of the codebase and database ensure a safety net before any update.
- Practice Rollbacks: Practice rolling back updates in a staging environment to ensure smooth execution if needed.

### Use a Staging Environment for Testing

Testing in a staging environment reduces the risk of issues on the live site:

- Mirror Production Setup: Set up a staging environment that mirrors the production setup to catch potential issues early.
- Automated and Manual Tests: Automated tests are used to verify critical functions, and follow up with manual testing on essential areas like checkout and payment gateways.

## What is the most recommended way?

While Shopware doesn't have plugins specifically for automating updates, some tools can streamline parts of the process:

### CI/CD Tools for Update Management

- Use Tools like Jenkins, GitLab CI/CD, or GitHub Actions: These tools automate tasks like running composer update, deploying updates to staging, and testing for potential issues.
- Monitor for Available Updates: Set up monitoring to be notified of new updates for Shopware core and plugins.

### SaaS Version Auto-Updates

If using Shopware's SaaS (cloud) version, many updates are deployed automatically by Shopware, minimizing the need for hands-on updates. Agencies can focus on testing and compatibility adjustments, rather than manual updates.

However, before you perform a successful update, you must take a backup of your existing data. The next section discusses this.
