---
title: "Shopware GMV: Calculation, €1 million threshold and consequences"
description: "How does Shopware calculate GMV? What happens above €1 million, and what are the consequences of using Community Edition without a commercial plan?"
canonical_url: "https://nuonic.de/en/insights/shopware-gmv-calculation-one-million-threshold"
---

The short answer first: **Shopware Community Edition remains open source and
can still be operated above the €1 million threshold.** However, merchants
whose stores assigned to one Shopware Account generate more than €1 million
in GMV during the previous 365 days need a commercial Shopware plan if they
want to continue using the Shopware Account and Extension Store. GMV is
calculated net: merchandise value after discounts plus shipping, excluding
taxes — and returns do not reduce it.

GMV, revenue, sales, or order value? Since Shopware introduced its Fair Usage
Policy and automated GMV reporting, few metrics have caused as many questions.
Does a merchant have to buy a license once the threshold is exceeded? Will
Shopware disable the Community Edition? And what value does a commercial plan
provide in return?

Shopware does not automatically shut down the store if no plan is purchased.
It may, however, restrict access to the Account and Store and terminate
existing extension subscriptions. For a production store that depends on
rented Store extensions, this is not merely a formal limitation. It is an
important operational and business-continuity issue.

This article reflects Shopware's official information as of August 17, 2026.
It is not legal or tax advice. The current Shopware Terms and Conditions and
the individual commercial offer remain decisive for contractual matters.

## Start with the terminology: what is GMV?

GMV stands for **Gross Merchandise Value**. Shopware defines it as the total
value of transactions processed through a Shopware system. Although the word
"gross" appears in the name, taxes are excluded, so Shopware calculates the
metric on a net basis.

GMV is therefore not automatically the same as:

- revenue reported in the financial accounts,
- payments received in the bank account,
- gross profit or contribution margin,
- sales after returns and refunds,
- net merchandise value without shipping.

Merchants with high return rates or low margins can consequently reach the GMV
threshold even though the revenue or profit they ultimately retain is much
lower. Shopware presents the threshold as part of a fair and scalable platform
model and recommends an individual discussion for unusual business models.
This is especially relevant for low-margin industries such as
[electronics and IT retail](/en/shopware-agency/electronics-retail), where the
platform math shapes the business model itself.

## How Shopware GMV is calculated

Shopware GMV is the net merchandise value after discounts plus net shipping
costs: taxes are excluded, and returns do not retrospectively reduce GMV
already recorded. Shopware's official
[Fair Usage Policy](https://www.shopware.com/en/news/fair-usage-policy-community-edition/)
sets out four central rules for this:

1. **Returns remain included.** A return does not reduce GMV already recorded.
2. **Discounts reduce GMV.** The value after discounts is relevant.
3. **Taxes are excluded.** Shopware calculates using net values.
4. **Shipping costs are included.** Net shipping contributes to the metric.

The simplified formula is therefore:

> GMV = net merchandise value after discounts + net shipping costs

> Returns do not reduce this value retrospectively.

### A calculation example

<table>
<thead>
  <tr>
    <th>
      Component
    </th>
    
    <th align="right">
      Value
    </th>
    
    <th align="right">
      Effect on GMV
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Net merchandise value before discount
    </td>
    
    <td align="right">
      €1,000
    </td>
    
    <td align="right">
      + €1,000
    </td>
  </tr>
  
  <tr>
    <td>
      Discount
    </td>
    
    <td align="right">
      €100
    </td>
    
    <td align="right">
      − €100
    </td>
  </tr>
  
  <tr>
    <td>
      Net shipping
    </td>
    
    <td align="right">
      €20
    </td>
    
    <td align="right">
      + €20
    </td>
  </tr>
  
  <tr>
    <td>
      VAT
    </td>
    
    <td align="right">
      €174.80
    </td>
    
    <td align="right">
      €0
    </td>
  </tr>
  
  <tr>
    <td>
      Subsequent return with a net value of €300
    </td>
    
    <td align="right">
      €300
    </td>
    
    <td align="right">
      €0
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Shopware GMV
      </strong>
    </td>
    
    <td align="right">
      
    </td>
    
    <td align="right">
      <strong>
        €920
      </strong>
    </td>
  </tr>
</tbody>
</table>

Even though part of the order is returned, the GMV in this example remains
€920. This is precisely why merchants should not derive the metric from their
annual accounts. The value shown by Shopware's GMV reporting is the more useful
starting point for monitoring the threshold.

## Which period applies to the €1 million threshold?

Shopware often describes the metric as annual GMV. The Terms and Conditions
are more precise: the relevant period is **the previous 365 days**. This is a
rolling window rather than necessarily a calendar or financial year.

For example, if the relevant GMV crosses the threshold on October 15, the fact
that the merchant's financial year ends on December 31 does not postpone the
assessment. The 365 days preceding each point in time are considered.

The Terms and Conditions also refer to the GMV of the **stores belonging to a
Shopware Account**. Multiple registered stores should therefore not simply be
viewed in isolation. Merchants should understand which production, test, and
staging systems are assigned to which Account and license host.

Special situations involving multiple companies, currencies, or tenant
structures should be clarified with Shopware in writing before the threshold
is reached.

## How does automated GMV reporting work in 2026?

On [April 14, 2026](https://www.shopware.com/en/news/automated-gmv-reporting/),
Shopware introduced integrated GMV reporting starting with
Shopware 6.7.8. Merchants running these versions no longer need to install the
previous GMV Reporting app or submit the metric manually on a regular basis.

According to Shopware, the system transmits the following once per day:

- cumulative GMV,
- cumulative order count.

Shopware states that customer names, contact information, and individual order
details are not transmitted. The data is aggregated and encrypted. Merchants
can view the reporting status, daily values, synchronization status, and
license host in the Administration under **Settings → System → GMV Reporting**.
The technical setup is explained in the official
[Shopware GMV Reporting documentation](https://docs.shopware.com/en/shopware-gmv-reporting).

Starting with Shopware 6.7.13, the Reporting Service can no longer be disabled
or uninstalled manually when the technical and contractual prerequisites are
met. This also applies to deactivation via the command line.

### Who is covered by automatic reporting?

Integrated reporting applies to:

- Rise, Evolve, and Beyond customers because GMV influences their pricing and
contractual classification,
- Community Edition stores connected to a Shopware Account that use the
Account or Extension Store.

According to Shopware, Community Edition merchants who do not use the Account
or Store are excluded from automatic tracking. For registered test and staging
systems, Shopware recommends placing test orders with only minimal values or
not registering those systems in the Account in the first place.

## Do merchants below €1 million still have to report GMV?

Yes, when Community Edition is connected to the Shopware Account or Store. The
reporting requirement does not begin only when the threshold is exceeded.
Shopware needs the metric to apply the Fair Usage Policy.

This distinction is important:

- **Below €1 million GMV:** Community Edition may use the Account and Store
without a commercial plan, but GMV reporting is still required.
- **Above €1 million GMV:** A Rise, Evolve, or Beyond plan is required to retain
access to the Account and Store.
- **Community Edition without Account and Store:** The open-source core may be
operated independently above the threshold as well.

Merchants that continuously fail to fulfil the reporting requirement despite
repeated reminders risk restrictions to their Account and Store access and the
termination of existing extension subscriptions, irrespective of their actual
GMV.

## What happens when GMV exceeds €1 million?

Crossing the threshold causes **neither an automatic plan change nor an
automatic charge** — it starts a staged clarification process. Shopware
explicitly states that it will first contact the affected Community Edition
merchant and discuss an appropriate solution; only if no solution is reached
does the choice between a commercial plan and operation without Account and
Store arise.

The expected process is therefore:

1. GMV reporting shows that the threshold has been exceeded.
2. The merchant may book a plan directly or contact Shopware.
3. If no plan is booked, Shopware contacts the merchant.
4. The plan, GMV classification, requirements, and commercial terms are
discussed individually.
5. If no mutual solution is reached, the merchant has to choose between a
commercial plan and Community Edition without Shopware Account and Store.

Shopware promises an individual discussion and sufficient time for a smooth
transition. Merchants should not interpret this as a universally guaranteed
transition period for every future case. Businesses approaching the threshold
should act before the first notice arrives.

## What if I do not subscribe to a Shopware plan?

The store keeps running — but Shopware may restrict the Account, cut off
Extension Store access, and terminate rented extension subscriptions. The
open-source core remains usable and keeps its
[MIT license](https://github.com/shopware/shopware/blob/trunk/LICENSE); the
real risk lies in rented Store extensions and Account-based processes. The
clear distinction in detail:

### What does not happen automatically

- Shopware does not technically disable the open-source core.
- Community Edition does not lose its MIT license.
- The production store is not shut down solely because of its GMV.
- There is no automatic migration to Rise, Evolve, or Beyond.

Shopware confirms that Community Edition may continue to be used above the
threshold without the Shopware Account and Store.

### Consequences Shopware may impose

If a merchant declines a plan after the individual discussion, Shopware may:

- restrict access to the Shopware Account,
- restrict access to the Shopware Extension Store,
- terminate existing extension subscriptions.

The Account is the central interface for managing extensions, purchases,
addresses, payment methods, invoices, and Shopware support. Losing access
therefore affects considerably more than simply browsing the Store.

Shopware's Fair Usage FAQ adds an important practical detail: one-time
purchased extensions remain active and usable, while rented extensions keep
working only until the end of their current contract period. Without Account
access, merchants can no longer buy new Store extensions or retrieve Store
updates for existing plugins.

### Operational risks of staying without a plan

Rented Store extensions are the most immediate risk. If their subscriptions
end, every affected function must be replaced, developed in-house, or removed
from the business process. The normal route for purchasing and managing future
Store extensions is no longer available either.

Before intentionally continuing without a commercial plan, merchants need at
least:

- a complete inventory of apps, plugins, themes, and subscription models,
- a dependency analysis for checkout, payment, ERP, and shipping,
- a plan for software updates and security fixes,
- alternative supply and support routes for critical extensions,
- an experienced technical operator or agency partner under contract,
- a cost estimate for replacement development and long-term maintenance.

"Community Edition remains usable" does not mean that the existing setup can
continue unchanged and without risk.

## What are the benefits of a commercial Shopware plan?

The most obvious benefit is **continued use of the Shopware Account and
Extension Store**. From a business perspective, a plan should not be viewed
only as a fee for this access. Rise, Evolve, and Beyond combine additional
commerce features with manufacturer support.

### 1. Reliable access to the ecosystem

Store extensions, subscriptions, invoices, and store registrations can
continue to be managed centrally. For stores whose processes rely on
commercial extensions, this reduces an immediate operational risk.

### 2. Support directly from Shopware

Community Edition comes with community support but no contractual manufacturer
support. In its
[feature documentation](https://docs.shopware.com/en/shopware-6-en/features),
Shopware currently lists an eight-hour service response time for Rise,
four hours plus phone support for Evolve, and one hour plus 24/7 availability
for Beyond. A response time is not a guaranteed resolution time, but it adds an
escalation path alongside the implementation partner.

### 3. Commercial features

Depending on the plan, merchants gain functionality that would otherwise need
plugins or custom development:

- **Rise:** Shopware Intelligence, unlimited sales channels, 3D capabilities,
and basic support, among other features,
- **Evolve:** B2B Components, Advanced Search, Dynamic Access, and phone
support, among other features,
- **Beyond:** Multi-Inventory, customer-specific pricing, Subscriptions,
Digital Sales Rooms, and enhanced 24/7 support, among other features.

Our detailed guide to
[Shopware 6 plans and pricing](/en/insights/shopware-6-plans-pricing-2026)
compares the complete options and current starting prices.

### 4. Fewer custom substitutes

A commercial plan may replace several plugin subscriptions or custom
developments. The benefit does not result from the length of the feature list.
It arises when included functionality is genuinely used and reduces
development, update, or support effort.

### 5. A more predictable manufacturer relationship

A commercial contract defines the plan, support level, and GMV classification.
For business-critical stores, a direct manufacturer relationship can matter in
escalations, complex releases, and strategic platform decisions.

## How much does a commercial plan cost?

Rise starts at €600 per month, Evolve at €2,400 per month, and Beyond is
quoted individually — each excluding VAT and, according to the official
[pricing page](https://www.shopware.com/en/pricing/), dependent on GMV and
other individual factors. These prices are explicitly not an automatic
invoice triggered by crossing the threshold. The starting prices at a glance:

<table>
<thead>
  <tr>
    <th>
      Plan
    </th>
    
    <th align="right">
      Starting price
    </th>
    
    <th>
      Typical focus
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Rise
    </td>
    
    <td align="right">
      from €600 per month
    </td>
    
    <td>
      Growth and core commercial features
    </td>
  </tr>
  
  <tr>
    <td>
      Evolve
    </td>
    
    <td align="right">
      from €2,400 per month
    </td>
    
    <td>
      Complex B2C and B2B commerce
    </td>
  </tr>
  
  <tr>
    <td>
      Beyond
    </td>
    
    <td align="right">
      Individual
    </td>
    
    <td>
      Enterprise functionality and 24/7 support
    </td>
  </tr>
</tbody>
</table>

The business case should consider the plan fee, extensions that can be retired,
manufacturer support, an agency SLA, and avoided replacement development
together. Rise can be expensive if none of its additional capabilities are
used. It can be cost-effective when it closes several critical dependency and
support gaps.

## When is a commercial plan worthwhile?

A plan should not be selected solely because GMV has reached a specific number.
It becomes particularly compelling when several of the following statements
apply:

- The store depends on rented extensions from the Shopware Store.
- Manufacturer support is part of the incident and escalation process.
- B2B Components, Advanced Search, Multi-Inventory, or other commercial
features replace planned custom development.
- Multiple sales channels or complex international operations are involved.
- Downtime costs more than the annual plan fee.
- The business wants clear contractual responsibility in addition to agency
support.

Conversely, a highly customized setup can technically operate on Community
Edition without Account and Store if the merchant owns all critical components
and has sufficient development, maintenance, and security capabilities. That
is a strategic operating model, not a way to run the same Store-dependent
setup for free.

## What merchants should do before reaching the threshold

Do not wait for €999,999. A useful process can begin at roughly €750,000 to
€850,000 rolling GMV:

1. **Verify the metric.** Compare the Administration values with an independent
calculation and understand discounts, shipping, taxes, and returns.
2. **Check assignments.** Review all stores, companies, domains, and license
hosts connected to the Account.
3. **Inventory extensions.** Separate purchased, rented, custom-built, and
open-source components.
4. **Model growth.** Forecast when the rolling 365-day value will cross the
threshold.
5. **Compare plans.** Match Rise, Evolve, and Beyond against actual requirements
rather than feature count alone.
6. **Calculate alternatives.** Include replacement development, maintenance,
security, and downtime risk in the no-plan scenario.
7. **Contact Shopware early.** Clarify the relevant GMV, offer, transition, and
any unusual business structure in writing.

This turns the threshold from a surprise into a budgeted platform decision.

## Frequently asked questions

The most common questions revolve around the same misconceptions: the
threshold is not a revenue cap for Community Edition, GMV is calculated net,
returns do not reduce it, and the relevant period is the previous 365 days —
not the calendar year. The answers in detail:

### Is GMV the same as revenue?

No. Shopware includes net shipping and does not deduct returns retrospectively.
Taxes are excluded and discounts reduce GMV. The accounting revenue figure may
therefore differ significantly.

### Is the €1 million threshold calculated net or gross?

Net of taxes. Despite the term Gross Merchandise Value, Shopware explicitly
excludes taxes.

### Do returns reduce Shopware GMV?

No. According to Shopware's definition, returns remain included. Discounts do
reduce GMV.

### Does Shopware automatically charge for Rise above €1 million?

No. Integrated reporting does not automatically switch the plan. Shopware says
it will contact affected Community Edition merchants and discuss a solution.

### Will the store be switched off if I do not buy a plan?

Not automatically. Community Edition and its MIT-licensed source code remain
usable. However, Shopware may restrict the Account and Store and terminate
extension subscriptions following an individual discussion and deadline.

### Can I continue to use extensions I purchased outright?

According to Shopware's Fair Usage FAQ, purchased extensions remain active and
usable. Without Account access, however, Store updates and new purchases are no
longer available. Rented extensions work only until the end of their current
contract period.

### Does every Community Edition store have to report GMV?

The Fair Usage reporting rules apply to Community Edition merchants using the
Shopware Account and Store. Shopware states that CE installations not using
these services are excluded from automated tracking.

## Conclusion: plan the threshold instead of fearing it

The €1 million GMV threshold does not mark the end of Shopware Community
Edition. It marks the point at which continued use of the Shopware Account and
Extension Store requires a commercial plan under Shopware's Fair Usage Policy.
The open-source core remains available.

For most merchants, the real decision is therefore not "license or shutdown."
It is a comparison between a commercial plan with ecosystem access, additional
features, and manufacturer support, and an independent operating model that
must replace Store subscriptions, updates, and support with its own resources.

Merchants that understand the rolling GMV early, audit their extension
dependencies, and calculate both scenarios can negotiate and decide from a
position of control.

## Official sources

- [Shopware Fair Usage Policy for Community Edition](https://www.shopware.com/en/news/fair-usage-policy-community-edition/)
- [Automated GMV reporting](https://www.shopware.com/en/news/automated-gmv-reporting/)
- [Shopware GMV Reporting documentation](https://docs.shopware.com/en/shopware-gmv-reporting)
- [Shopware plans and pricing](https://www.shopware.com/en/pricing/)
