When the Shopware Community Edition is enough and when a paid plan is needed
A self-hosted shop can stay on the free, MIT-licensed Shopware Community Edition while its gross merchandise value over the preceding 365 days stays at or below 1 million euros and the team can support the platform without vendor response commitments. Shopware's pricing page says that shops linked to an account above that figure need a paid plan, so the threshold is the first test. Calculate your rolling 365-day GMV from your own order data, then confirm with Shopware exactly which accounts count as linked to your shop. Because the figure rolls forward daily, a shop just under the line can cross it during a peak season, so the check belongs in monthly reporting, not in an annual review.
The Community Edition is a working shop, not a trial. It includes a visual page builder, product management and Shopware Payments, but support for these comes from the community only. Paid plans are priced on gross merchandise value and other individual factors, so the threshold alone does not tell you the fee. Request a written quote that explains how GMV, hosting and plan features were weighed, and compare it with the internal cost of your own hosting, upgrades and developer time. The free edition fits when your team can run upgrades and resolve incidents, when community answers meet your risk tolerance and when your required features are already in the Community Edition. It is a weaker fit when you need contracted response times or B2B quotes and approvals, which the pricing page ties to the paid plans.
Plan the transition before you need it. Shopware lists SaaS, PaaS and self-hosted as ways to run the platform, so moving to a paid plan may also change who operates the stack, not only who bills for it. Ask Shopware how an account moves between plans, whether the move requires a change of hosting model and how a cutover is scheduled. Also confirm which maintained line you will run. Shopware 6.7.15.1 and 6.6.10.29 were both released on October 7, 2026, and the Shopware GitHub releases page shows both lines. Keep a tested staging environment on the line you intend to run, so a plan change does not coincide with an unplanned upgrade.
Which Shopware capabilities are free and which sit in paid plans
This table sets the published Community Edition feature split against Rise, Evolve and Beyond, so you can see which capabilities are free and which depend on a plan. Where the vendor's pricing page gives no detail, the table tells you what to confirm before you commit. The main takeaway is that the free edition covers the core storefront tooling, while B2B approvals, AI-assisted content and 24/7 support sit behind paid tiers.
| Capability | Community Edition (free) | Rise, Evolve and Beyond |
|---|---|---|
| Visual page builder | Included | Included on paid plans. Confirm whether any builder features differ by tier. |
| Product management | Included | Included on paid plans. Confirm any tier limits on catalog size or variants. |
| Shopware Payments | Included, community support only | Included on paid plans. Confirm which support channel applies to payment issues. |
| AI-assisted content | Not listed on the pricing page | Listed for Rise. Confirm scope, usage limits and whether it applies to Evolve and Beyond. |
| B2B quotes and approvals | Not listed on the pricing page | Listed for Evolve. Confirm whether Rise excludes it and how approval workflows are configured. |
| Support response time | Community support only, no published response time | Rise: 8-hour response. Evolve: 4-hour response. Beyond: 1-hour response, 24/7 support. |
| Pricing basis | Free, but a shop over 1 million euros in annual GMV must move to a paid plan | Rise at 600 euros per month, Evolve at 2,400 euros per month (vendor pricing page), Beyond custom. Ask for a written quote including GMV basis. |
| Hosting options | Self-hosted deployment | SaaS, PaaS on managed infrastructure or self-hosted, per the vendor pricing page. Confirm which options each plan allows. |
How licensing, support and updates differ between editions
The code licence is the same starting point for everyone, so the real differences sit in hosting options, support response times and update coverage. Each card below names one of those differences and the check to run before you commit to a tier.
MIT licence covers the code
The Shopware code is published under the MIT License, as stated in the LICENSE file of the shopware/shopware repository. That licence governs what you may copy, modify and redistribute. It does not decide who answers your support tickets or who operates your servers. Read the licence file yourself and have legal confirm it fits your internal use before you build on the Community Edition.
Community support only
The Community Edition includes the visual page builder, product management and Shopware Payments, but support for it is community-supported only. Nobody is contractually obligated to answer a production incident on a free shop. If an outage would cost you revenue, budget for an internal team or a partner who can respond on your behalf.
Rise response within 8 hours
Rise is listed at 600 euros per month with AI-assisted content and an 8-hour support response, per Shopware's pricing page. That window suits merchants whose outages can wait part of a business day. Confirm whether the 8 hours applies to every severity level and whether it counts business hours or calendar hours.
Evolve response within 4 hours
Evolve is listed at 2,400 euros per month with B2B quotes and approvals and a 4-hour response. The shorter window and the B2B features are bundled together, so you pay for both when you need only one. Ask whether the B2B quote and approval workflow is configured for you or delivered as a feature you set up yourself.
Beyond offers 1-hour 24/7 cover
Beyond is priced on custom terms and includes 1-hour, 24/7 support. This tier fits operations where a checkout outage is a material incident at any hour. Because pricing is custom, request the written support definition, the severity scale and the escalation path before you compare it with the fixed-price tiers.
Two maintained minor lines
Shopware 6.7.15.1 and 6.6.10.29 were both released on October 7, 2026, and both lines are maintained. Your shop should sit on a line that is still receiving fixes, and you should plan your upgrade path before a line stops. Confirm with Shopware which line each plan covers and how long each receives security fixes.
How the hosting model changes the edition decision
Shopware can be self-hosted on servers your team controls. In this model, the platform team owns the PHP runtime, database, cache, search, queues, file storage, backups and the upgrade path between minor lines. The Community Edition is free to license, but the infrastructure and operating effort are not. If you run a self-hosted shop, the edition question is less about the software and more about whether your team can absorb the operating work that a paid plan might otherwise shift onto the vendor.
- Patching and upgrades: Your team schedules and tests each update against your extensions and theme, and it must keep pace with the maintained minor lines.
- Backups and recovery: Database, media and configuration backups, along with restore testing, remain your responsibility.
- Scaling: Capacity planning for traffic peaks, search and background workers sits with your engineers.
- Support path: Community Edition support is community-based, so incident response depends on your own staff and partners.
- Customization freedom: You control plugins, hosting topology and data residency without asking a vendor for permission.
Check with Shopware which plan features, if any, can be deployed in your self-hosted setup before you assume they are available.
Shopware's pricing page describes PaaS on managed infrastructure as one of three ways to run the platform. In a PaaS model, the vendor or its hosting partner typically operates the underlying infrastructure, while your team keeps more control over the storefront and integrations than it would in a fully managed SaaS. The division of duties is the key question, because it determines how much of the edition decision is really a decision about operations.
- Shared responsibility: Confirm in writing which layers the provider patches, which backups it runs and how restores are tested.
- Scaling limits: Ask how capacity is added during peak trading periods and who pays for it.
- Customization boundaries: Verify which server-side extensions, custom services and network integrations the managed environment permits.
- Plan alignment: Check whether the plan you need is offered on the PaaS option, since plan pricing is tied to gross merchandise value and individual factors.
- Exit path: Ask how data, configuration and custom code can be moved if you later self-host.
Request the exact responsibility matrix and the plan tier that includes your required support response times before signing.
Shopware also offers SaaS. A SaaS model suits teams that want the vendor to run the platform and keep it current, with the engineering team focused on storefront, content and integrations. The trade-off is that your control over infrastructure, hosting location and some custom server-side code is narrower, and the operating decisions are made within the vendor's service model. Do not assume SaaS and self-hosted offer the same extensibility or support terms.
- Operations handled by the vendor: Patching, infrastructure monitoring and routine maintenance are generally part of the service, but confirm the specifics.
- Less infrastructure control: Custom hosting, network placement and some back-end changes may be limited.
- Data location: Confirm where data is stored and processed, and under which terms, especially for regulated sales data.
- Support tiers: Compare the response times on each plan, since they differ across Rise, Evolve and Beyond.
- Exit and portability: Ask how you would export shop data, customizations and media if you move to another model.
What to check: the written service description for SaaS, including what the vendor operates, what you operate, and how the plan you choose affects both.
What each edition costs to run and what a quote covers
This table separates published Shopware plan fees from the one-time and recurring work that sits around them, so you can see who gets paid for what. Read the published prices as the starting point only, since Shopware states that plan pricing depends on gross merchandise value and other individual factors. The main takeaway is that the licence fee is often the smaller line item once migration, extensions, integration and operations are priced.
| Cost component | Who is paid | One-time or recurring | What drives it |
|---|---|---|---|
| Community Edition licence | No licence fee to Shopware under the MIT License (shopware/shopware LICENSE file) | No plan fee, but hosting and labor still apply | Shop must stay under 1 million euros annual GMV or move to a paid plan |
| Rise plan | Shopware, at 600 euros per month (Shopware pricing page) | Recurring monthly | GMV and other individual factors; includes AI-assisted content and 8-hour support response |
| Evolve plan | Shopware, at 2,400 euros per month (Shopware pricing page) | Recurring monthly | GMV and other individual factors; adds B2B quotes and approvals and 4-hour response |
| Beyond plan | Shopware, at custom pricing with 1-hour 24/7 support (Shopware pricing page) | Recurring, amount set by quote | Scope, GMV and support level; ask Shopware for the written figure |
| Migration, theme, extensions and integration | Internal team or an implementation partner such as DeployOpen, under a written scope | One-time, sometimes followed by maintenance | Catalog size, custom checkout logic, ERP or PIM links, number of extensions |
| Hosting and operations | Your cloud provider or data center, plus whoever patches and backs up the stack | Recurring | SaaS, PaaS or self-hosted choice, staging needs, uptime targets and on-call coverage |
| Community support | Free community channels only, per Shopware's pricing page for the Community Edition | No contract cost, but no guaranteed response | Your internal capacity to diagnose issues without a vendor SLA |
| What a quote should cover | Ask Shopware and any partner for written line items | Both one-time and recurring | Request GMV assumptions, support tier, hosting model, upgrade effort and exclusions in writing |
Moving a live shop from Community Edition to a paid plan
This sequence moves a shop from the free Community Edition to a paid Shopware plan without losing orders, payment settings or B2B approval rules. Each step closes with a check the team can verify before the next one starts.
Confirm GMV against the 365-day rule
Finance and the shop owner pull gross merchandise value for every shop linked to the account over the preceding 365 days. Shopware's pricing page says a shop above 1 million euros in that period must move to a paid plan under its Fair Usage Policy, so compare the total against that figure, not a single month. Count all linked shops, not only the storefront you plan to migrate. Done when the team has a signed-off GMV figure and a written decision on whether the threshold or a paid feature triggers the move.
Select the plan and confirm terms
The shop owner compares Rise, Evolve and Beyond against the features the business needs, such as B2B quotes and approvals, the support response time and AI-assisted content. Shopware states that plan pricing depends on gross merchandise value and other individual factors, so ask Shopware for a written quote that names the plan, the billing terms and what happens at renewal. Beyond is priced individually. Done when a signed order form or written quote matches the feature list the team requires.
Review hosting model and extensions
The platform lead decides whether the shop will run as SaaS, as PaaS on managed infrastructure or self-hosted, since Shopware supports all three. Then the team inventories every installed extension and custom plugin, checks which ones depend on Community Edition behavior, and asks each vendor or internal developer for compatibility with the chosen plan. Done when the team has a written inventory with a compatible or replace decision for each item and a hosting model confirmed with Shopware.
Rebuild the shop in staging
The implementation team creates a staging environment that mirrors production, including the database, media, payment configuration and the extensions from the inventory. They apply the plan-specific features and run the upgrade path there first, so any configuration gap appears before customers see it. Done when staging passes a full order test and the team has logged every change that differs from production.
Verify payments and B2B approval workflows
QA and finance run test transactions through each payment method, including Shopware Payments, and check refunds, settlement reports and tax output. If the paid plan includes B2B quotes and approvals, the sales lead tests the full path: quote request, internal approval, customer acceptance and order creation under each approval role. Done when every test order reaches the correct ledger entry and every approval role completes its step without manual workarounds.
Cut over and monitor the first orders
The team schedules the change in a low-traffic window, freezes content and catalog edits, moves data and DNS or routing to the production environment, and confirms the plan is active on the account. Operations watches order placement, payment callbacks and error logs for the first business cycle, with a named person responsible for rollback decisions. Done when a set of live orders completes end to end and the team signs off the cutover record.
Confirm the reverse path before committing
Before the team treats the move as permanent, the shop owner asks Shopware in writing whether a return to the free Community Edition is available if the business later drops paid features and falls below the GMV threshold. This path is only available when the business no longer needs the paid features, and the terms are Shopware's to define. Done when the answer is recorded in the decision file with the date and the Shopware contact who gave it.
When the paid plan pays for itself
The paid plan pays for itself when a specific business condition makes the free Community Edition more expensive to run than a subscription, not when a shop simply grows. The clearest trigger is B2B selling. The Rise plan is listed at 600 euros per month with 8-hour support response, while Evolve, listed at 2,400 euros per month, adds B2B quotes and approvals and 4-hour response. If your sales process needs negotiated price lists, quote documents and multi-step buyer approval chains, building and maintaining that logic yourself or through a partner is a recurring engineering cost. Compare that cost against the Evolve price, and ask Shopware and your partner to confirm exactly which B2B functions are included at each tier before you assume a feature exists.
The second condition is support urgency. Community Edition support comes from the community, and the pricing page ties paid response times to each tier. For a shop where a broken checkout costs revenue every hour, a paid response window may be worth more than the subscription itself. Pair that with the Fair Usage Policy: a shop linked to an account that generates more than 1 million euros in gross merchandise value over the preceding 365 days must move to a paid plan. Track your trailing GMV now, because the obligation applies to the rolling window, not to a planned launch date. Also confirm how Shopware calculates GMV for your account, since plan pricing also depends on other individual factors.
The third condition is capacity. Running the Community Edition means your team, or a hosting partner, owns the server stack, patching and upgrades between the maintained 6.7 and 6.6 minor lines. If nobody on staff can absorb that work, a SaaS or managed PaaS plan can shift operations to the vendor, which is a cost you should compare against a partner retainer and your internal salary costs. The Community Edition remains the better choice when you have strong in-house platform skills, low B2B complexity, GMV well under the threshold, and a partner willing to deliver a fixed-scope roadmap of extensions and upgrades. In that case, a one-time implementation plus a predictable retainer can cost less than a subscription that duplicates features you never use. Ask for both quotes in writing before deciding.
Questions buyers ask before choosing a Shopware edition
Is the 1 million euro limit measured per shop or per account?
The limit is tied to the account, not to a single storefront. Shopware's pricing page says shops linked to an account that generate more than 1 million euros in gross merchandise value over the preceding 365 days need a paid plan instead of the free Community Edition. If one account runs several shops, add their GMV together before you assume the free edition still applies. Confirm the exact counting rules, including how marketplace or multi-channel sales are attributed, with Shopware before you commit to a build. Ask for the rule in writing, since it determines when a migration becomes mandatory.
What does a paid Shopware plan cost beyond the published monthly fee?
The published fees are only one part of the bill. Shopware states that plan pricing is based on gross merchandise value and further individual factors, so the quote can differ from the list figure. The published monthly fees on the pricing page are 600 euros for Rise and 2,400 euros for Evolve, with Beyond priced on request. Beyond the subscription, you also pay for your own hosting if you self-host, for implementation and integration work, for the agency or partner who builds your theme and plugins, and for the internal staff who run upgrades. Ask the vendor which factors drive the quote and what the recurring and one-time parts are.
How much work does moving from Community Edition to a paid plan involve?
The effort depends on how much your shop has customized and how it is hosted. A shop that uses only standard features and the included visual page builder has less to move than one with custom plugins, custom checkout logic, or integrations with an ERP or warehouse system. Typical drivers are the number of extensions, the test coverage you already have, the data volume to migrate, and whether the paid plan changes your hosting model (SaaS, PaaS, or self-hosted). Ask the implementation partner for a written scope that lists each integration, each custom extension, and the test plan, since that scope is what decides the timeline.
Can a team run the Shopware Community Edition on its own servers?
Yes, the Community Edition is MIT-licensed, so you can self-host it and modify it within the license terms. Shopware's pricing page says Shopware can run as SaaS, as PaaS on managed infrastructure, or self-hosted, so the self-hosted route is one of several options. Self-hosting shifts the operating work to you: you own the PHP and database stack, security patching, backups, monitoring and upgrades between the maintained minor lines. Confirm which PHP, database and search versions the release you target requires, and assign someone to own the upgrade calendar before go-live.
What support does the free Shopware Community Edition include?
The Community Edition includes community support only. Shopware's pricing page lists the visual page builder, product management and Shopware Payments as included features with community support only. Paid plans add defined response times: Rise lists an 8-hour response, Evolve a 4-hour response, and Beyond a 1-hour response with 24/7 support. Community forums and public documentation can help with common questions, but they carry no response commitment. If a checkout outage would cost you revenue, weigh that against the plan's response times and ask Shopware what happens outside those windows.
What does running Shopware need from our own team?
Your team needs enough skill to own the platform after go-live, even if a partner builds it. Expect responsibilities in four areas: hosting and infrastructure, application upgrades, customizations and integrations, and security and incident response. Upgrades matter most, because Shopware maintains two minor lines at once, with 6.7.15.1 and 6.6.10.29 both released on October 7, 2026, and your extensions must work with the line you choose. If you lack in-house PHP or ecommerce operations skills, plan for a retainer or managed plan, and define in the scope who handles each upgrade and rollback.
Can DeployOpen help plan the edition choice and the implementation?
DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own infrastructure. For a Shopware decision, that can include scoping the migration, building integrations, hardening a self-hosted shop, and documenting the upgrade process. Most engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts. DeployOpen does not publish a price list, so a quote follows from the written scope. Ongoing support, upgrades and continuous testing are available as retainers.
Does the Community Edition meet our compliance evidence needs?
A free edition does not replace the evidence your compliance program requires. Your auditor will look at access control, change management, backups, logging and vendor support, and the Community Edition's community-only support affects how you document vendor responsibility. DeployOpen prepares systems, controls and evidence for compliance assessments, but it does not issue audit reports, attestations or certifications, and independent auditors and certification bodies do. Ask your assessor which controls they expect to see before you choose an edition.
How DeployOpen scopes and supports either Shopware edition
DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own infrastructure. For Shopware, that means working out in writing whether the free Community Edition fits your shop, or whether a paid plan and its support terms are the right path before any build starts.
How we scope
- Engagements are fixed-scope, with deliverables and timelines agreed in writing before work starts.
- Scope starts from your current GMV, sales channels, B2B needs and the features you expect from a paid plan.
- Written scope names which Shopware features are used and which support tier your team will rely on.
How we build
- Work runs inside your own cloud accounts, data centers or air-gapped networks, whichever Shopware hosting model you choose.
- Customizations, payment and integration work are built and tested against the edition and minor line you are running.
- Hardening, backup and upgrade procedures are designed around your team's operating capacity and change process.
How we hand over
- Deliverables include architecture notes, configuration records, runbooks and documentation your team can keep using.
- Handover covers which parts stay community-supported and which depend on a paid plan's support commitments.
- Upgrade steps between maintained Shopware lines are documented so your team can repeat them without us.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers, scoped separately from the build.
- Retainer terms should state response expectations in writing, since plan support windows differ by edition.
- DeployOpen does not issue audit reports or certifications, so any compliance evidence you need comes from independent assessors.
