Is Shopware Community Edition free above €1 million GMV?
Understand Shopware’s Community Edition policy, Account and Store access, GMV reporting and the costs beyond the core licence.
In this guide
Separate the open-source core from ecosystem access
Shopware’s Fair Usage Policy says Community Edition merchants exceeding €1 million annual GMV through their Shopware store must take a commercial plan to retain access to the Shopware Account and Store. It does not describe every open-source installation as a universal paid licence at that turnover.
Record both parts of the decision: the software being operated and the ecosystem services the business needs. Treating the word free as the whole policy can produce an incomplete budget.
Use the platform’s measurement and time period
Shopware’s GMV reporting explanation also describes the reporting requirement and GMV-based commercial pricing. Confirm what the current policy counts and the period it uses rather than substituting an approximate turnover value.
Imagine a fictional merchant planning a major new sales channel. Ask which orders enter the relevant measurement and who can reconcile it. Keep unresolved scope questions open until the supplier confirms them. A forecast near a boundary deserves an earlier commercial review than a business comfortably below it.
Create a policy-and-budget record
| Question | Input to obtain | Decision owner |
|---|---|---|
| Which sales count? | Current GMV definition and relevant channels | Commercial lead |
| Which ecosystem services are required? | Account, Store and extension dependencies | Technical owner |
| What happens at growth? | Commercial-plan condition and quote | Budget owner |
| What remains operationally necessary? | Hosting, updates and recovery | Store operator |
This record does not establish a real merchant’s GMV or eligibility. Keep the actual figures inside the business’s approved reporting process and retain only the needed commercial conclusion in a shared project brief.
Budget the store even below the threshold
A no-core-licence-fee route can still require infrastructure, implementation, paid extensions, payment services and maintenance. List the required services and the people doing the work. A merchant with no internal platform owner should price that responsibility explicitly.
For a fictional store, define who checks failed jobs, applies updates and restores a usable copy after a problem. A free download does not assign those jobs to the platform supplier. Compare any managed proposal by the responsibilities it actually takes over.
Plan the review before a forced decision
Set a review date based on forecast growth, integration dependencies and the supplier’s current policy. Ask for a proposal before expansion makes the plan decision urgent. Confirm the effective package and costs in writing.
Read the Shopware plan-pricing guide and product profile for the next step. Use the migration checklist if the review also involves a platform move. This article explains the documented commercial boundary; it does not determine an individual contract.
Frequently asked questions
What does Shopware’s €1 million GMV policy concern?
The checked policy ties continued access to the Shopware Account and Store to a commercial plan for Community Edition merchants exceeding the stated annual GMV threshold.
Does being below the threshold mean a Shopware store has no costs?
No. Hosting, extensions, payment services, implementation and maintenance still require separate review.
Put the guide into practice
Explore ecommerce tools, then compare your shortlist.
Explore the category →