Shopware
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 4 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by shopware AG · www.shopware.com
Compare with JTL-Shop → Compare with Gambio → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Shopware at a glance
- Vendor
- shopware AG
- Headquarters
- Incorporated in Germany source, captured 16 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 16 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 5 Oct 2026
- Panel verdict
- The AI panel rates Shopware 3/5, the mean of 6 judges. Shopware, from shopware AG of Schöppingen, is an e-commerce platform with an MIT-licensed core, self-hosting alongside SaaS and PaaS, and tiers from a free Community Edition through Rise from €600 per month and Evolve from €2,400 per month, both net of VAT, to custom-priced Beyond. how scores are made
- As of
- Vendor pages captured 31 Aug 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Shopware, from shopware AG of Schöppingen, is an e-commerce platform with an MIT-licensed core, self-hosting alongside SaaS and PaaS, and tiers from a free Community Edition through Rise from €600 per month and Evolve from €2,400 per month, both net of VAT, to custom-priced Beyond. Extensibility is the strongest category at 8-9: a documented Store API for headless builds, plugins as Composer packages, open development on GitHub. Weakest is tax and legal at 3-4, where a tax-provider framework is documented but we found no public information on destination-country VAT, VIES validation, OSS or German checkout requirements. Catalog and checkout sits at 5-6 with no public information on vouchers, guest checkout or abandoned-cart recovery; operations at 6-7; pricing transparency at 6 — Shopware Payments fees unnamed, Beyond custom-priced. Data control and exit spans 6-8, the widest spread — the Data Protection Officer at 6 over no public information on export or data return at cancellation. Sovereignty holds at 4-5: a German contracting entity and a published data processing agreement, but hosted shop data's location is not confirmed on the vendor's own pages.
Speaks for it
- Extensibility scores 8-9, on an MIT-licensed core developed on GitHub through pull requests, RFC discussions and a public roadmap
- Plugins are Composer packages that can declare dependencies, and the Store API supports headless builds with custom endpoints, decorators and extension events
- Order handling is documented in depth, with three configurable state machines covering partial shipment, partial refund, chargeback and partial returns
- Self-hosting on infrastructure of the merchant's choice is offered alongside SaaS and PaaS, with a hosting-partner locator
- Tier prices are public with per-tier inclusions — Community Edition at €0, Rise from €600 per month and Evolve from €2,400 per month, each stated net of VAT, with 30 days free on Rise
Held against it
- Tax and legal scores 3-4, with VAT determination delegated to tax provider apps that the platform calls during checkout
- We found no public information on vouchers, guest checkout or abandoned-cart recovery on the captured pages
- Shopware Payments states that transaction fees apply without naming the rates, and Beyond is priced only as Individuell, so full costs are not computable from public pages
- We found no public information on export of catalogue, customers and orders out of the platform, or on data return and deletion on cancellation
- European data centres are named for the AI assistant only; we found no public information on where hosted shop data resides or on a subprocessor list with locations
Best for
- You have a development team that wants to own the code — an MIT-licensed, forkable core with a documented Store API for headless builds.
- You want to run the shop on your own infrastructure or through a hosting partner, keeping the data path under your control.
- Your fulfilment runs on fine-grained order states — partial shipment, partial refund, chargeback and partial returns are first-class in three documented state machines.
- You are migrating an existing shop in — the Migration Assistant documents profiles, checksum-based delta runs and media handling for the inbound path.
Avoid if
- You need the platform itself to determine destination-country VAT and cover German checkout requirements such as order button wording — the documented tax system delegates determination to provider apps.
- You must know total payment costs before signing — Shopware Payments states transaction fees apply without publishing rates, and Beyond is priced only as Individuell.
- Your back office depends on maintained interfaces to named ERP or accounting systems such as DATEV, or on named carrier integrations — the captured integration surface names CRM, payments and shipping only in general terms.
- Your data-protection review requires a stated location for hosted shop data and a subprocessor list — the vendor's pages name European data centres for the AI assistant only.
The scores
| Criterion | Panel median |
|---|---|
| Catalogue & checkout | 3 of 5 |
| Tax & German legal correctness | 2 of 5 |
| Extensibility & developer surface | 4 of 5 |
| Order operations & back office | 3.5 of 5 |
| Data ownership & exit | 4 of 5 |
| European sovereignty | 2.5 of 5 |
| Pricing transparency | 3 of 5 |
Catalogue & checkout
Show reasoningHide reasoning
How this is scored
Products, variants, pricing rules and the path to payment — the part that either converts or does not.
0 — Not a shop: no product catalogue and no checkout of its own.
3 — A product catalogue with categories and a checkout that takes payment through at least one provider.
5 — Products with variants, discounts or vouchers, guest checkout, and several payment methods including those German buyers expect (PayPal, invoice or direct debit) through named providers.
8 — Tiered and customer-group pricing, bundles or configurable products, rule-based promotions, per-channel or per-market pricing, abandoned-cart recovery, a checkout customisable without a rebuild, and buy-now-pay-later where offered.
10 — Merchandising and checkout are the product: rule-driven pricing and promotions, A/B-testable checkout, multi-currency and multi-language as standard, and conversion features (abandoned cart, one-page checkout) shipped rather than bolted on.
The Merchant
The developer documentation gives me a real catalogue — hierarchical categories, variant products assembled through a configurator, properties with filtering — and a documented two-step checkout with PayPal and Shopware Payments named. Customer-specific pricing and customer-group content arrive only in the Evolve and Beyond plans; we found no public information on vouchers, guest checkout, abandoned-cart recovery or rule-based promotions, the levers I actually pull to lift conversion. 1 2 5 6 2
The B2B Seller
Variants, a configurator and hierarchical categories are documented, alongside a payment architecture with synchronous and asynchronous handlers and PayPal named, and customer-specific prices with customer-group content targeting are listed — though only in the custom-priced upper tiers. I found no public information on invoice or direct-debit payment methods, payment on account for trade customers, guest checkout or abandoned-cart recovery, all of which I would need before recommending this to a B2B buyer. 5 6 1 2
The Developer
Variants are modelled properly — a parent-child product with a configurator object assembled for Store API requests, hierarchical categories and property groups for filtering — and payments run through documented synchronous and asynchronous handlers with PayPal named and Shopware Payments in the paid plans. Customer-specific prices sit on the top Beyond plan. We found no public information on discounts or vouchers, guest checkout, abandoned-cart recovery or rule-based promotions, so this sits at the variants-plus-named-payment level. 5 6 1 2
The Operations Lead
The developer documentation shows a real catalogue — hierarchical categories, variant products with parent-child inheritance and a storefront configurator — plus a checkout with synchronous and asynchronous payment handlers, PayPal named, and Shopware Payments built in. Customer-specific prices exist but sit in the top Beyond tier, and we found no public information on vouchers, guest checkout, abandoned-cart recovery or rule-based promotions on the captured pages. 5 6 1 2
The Data Protection Officer
The developer documentation covers products with variants, a configurator, hierarchical categories and packaging units, and a payment system of pluggable handlers with PayPal named and Shopware Payments included from the free Community Edition upward; customer-specific prices and customer-group targeting arrive in the paid plans. We found no public information on vouchers, guest checkout, buy-now-pay-later or abandoned-cart recovery in the captured pages. 5 6 1 2
The Skeptic
Variants with parent-child inheritance, a configurator assembled per storefront request, and a payment system with synchronous and asynchronous handlers, PayPal named and Shopware Payments built in, are documented on the developer pages. Customer-specific prices and B2B quote flows are listed only from the paid tiers upward, and we found no public information on guest checkout, discounts, vouchers or abandoned-cart recovery on the captured pages. 5 6 1 2 2
Tax & German legal correctness
Show reasoningHide reasoning
How this is scored
VAT determination, OSS, B2B reverse charge, invoicing, and the checkout requirements German law imposes (Button-Lösung, Widerrufsrecht, Preisangabenverordnung) — judged on what the platform documents it does or ships as a maintained extension.
0 — No tax handling at all; prices carry no VAT logic and the merchant calculates tax outside the platform.
3 — VAT rates configurable per country or product, with prices shown gross or net and legal texts placed as pages in the checkout.
5 — VAT by destination country with gross and net display per customer group, B2B with VAT ID and reverse charge, and the German checkout requirements (order button wording, withdrawal policy, price indications) handled by the platform or a named official extension.
8 — VIES validation of VAT IDs, OSS thresholds tracked or OSS reporting data provided, invoices issued from orders with correct content per case including reverse-charge notes, small-business and third-country handling, and e-invoicing (XRechnung/ZUGFeRD) for B2B orders.
10 — Tax and legal correctness are maintained by the vendor rather than the merchant: rates and thresholds updated as the law moves, OSS reporting produced, every invoice case correct out of the box, and documented conformity a lawyer could review.
The Merchant
What the pages document is tax plumbing: apps can act as tax providers, called during checkout by priority, with Shopware trusting the provider's sums, and tax settings visible in the administration. We found no public information on VAT rates per country or customer group, reverse charge with VAT ID validation, OSS, invoice contents, or the German checkout requirements such as order button wording, withdrawal policy and price indication rules — the compliance I would be personally liable for. 7 8
The B2B Seller
There is a genuine tax subsystem — tax settings in the administration and an app framework whose tax providers are called during checkout by priority, with signed requests and responses covering line items, delivery and cart price — but the rates come from third-party provider apps rather than the vendor. I found no public information on VAT-ID validation, reverse charge, OSS, gross and net display per customer group, or the German checkout requirements such as order button wording and price indications. 7 8
The Developer
There is a genuine tax subsystem: tax settings in the administration, and since version 6.5 apps can register custom tax providers that Shopware calls in priority order during checkout, with signed requests and line-item, delivery and cart-level tax sums the platform trusts as authoritative. That is a serious framework for destination-based VAT determination, but the determining is done by the merchant's or a partner's app, not the platform. We found no public information on VAT-by-country behaviour out of the box, reverse charge, invoicing content, or the German checkout requirements such as order button wording and price indications. 7 8
The Operations Lead
Tax runs through an extension point: apps register tax providers that are called during checkout by priority, with signed requests and sums Shopware trusts as given, configurable under Settings > Tax in the administration. That is a socket for plugging in a tax engine rather than documented German correctness — we found no public information on VAT by destination country, OSS, VIES validation, invoice content or the German checkout requirements on the captured pages. 7 8
The Data Protection Officer
The pages document a tax provider framework — tax settings in the administration and app providers called during checkout by priority, with signed requests and a five-second timeout — so VAT logic sits in the platform rather than outside it. We found no public information on destination-country VAT, VIES validation, OSS, invoice contents, or the German checkout requirements such as order button wording, withdrawal policy and price indication rules. 7 8 12
The Skeptic
The documented tax surface is a hook rather than a shipped determination: apps register as tax providers, are called by priority during checkout with a five-second timeout, and the platform trusts the tax sums the provider returns. We found no public information on VAT by destination country, reverse charge, VIES or OSS handling, invoice content, or the German checkout requirements on the captured pages. 7 8
Extensibility & developer surface
Show reasoningHide reasoning
How this is scored
Themes, apps, APIs and headless — whether the shop can be shaped to the business, and at what cost in lock-in.
0 — A closed shop builder: no themes to edit, no apps or plugins and no API.
3 — Themes adjustable in an editor and a set of apps or plugins to add features.
5 — Custom themes with a template language or code access, an app or plugin ecosystem, and a documented API with webhooks for order events.
8 — A storefront API for headless builds, an extension framework with its own lifecycle, staging or development environments, version control for themes, and documented rate limits.
10 — A platform a team can own: headless-first APIs, open-source or source-available core, plugin architecture with a real dependency model, local development and CI supported, and upgrade paths that do not orphan customisations.
The Merchant
This is the platform's strongest suit: an MIT-licensed core on GitHub that I can fork, plugins built as Composer packages able to declare dependencies, an API-first Store API for headless builds, and apps for cloud stores — a checkout I can reshape without a rebuild. Local development is described with a tunneling service for app endpoints, though we found no public information on staging environments, theme version control or documented rate limits. 8 9 10 16
The B2B Seller
The core is open source under MIT with fork-and-contribute development, plugins are Symfony bundles declared as Composer packages that can define dependencies, and the Store API is documented for headless builds with custom endpoints, response decorators and deprecation guidance. I found no public information on staging environments, version control for themes or documented rate limits, which keeps this short of the top level. 9 10 16 6
The Developer
This is a core a team can own: MIT licence, a GitHub repository you can fork and pull-request against with RFC discussions and a public roadmap, plugins that are Symfony bundles where every plugin is a Composer package that may define dependencies — a real dependency model, not a store listing — plus a documented Store API for headless builds with decoratable routes and extension events. Local development is implied by the app guidance suggesting tunnelling with ngrok, and the deprecation of the Sales Channel API is written down rather than silent, which is how you survive five years. I hold back the last step because we found no public information on version control for themes, CI guidance, or a stated promise that upgrades do not orphan plugins. 9 10 16 6 8
The Operations Lead
This is a developer platform: an MIT-licensed open-source core on Symfony with an API-first Store API for headless builds, plugins shipped as Composer packages that can declare dependencies, a separate app system with a manifest-based lifecycle for cloud stores, and open development through pull requests and RFC discussions. We found no public information on staging environments or documented API rate limits, which keeps it off the top step. 9 10 16 16
The Data Protection Officer
This is a developer-grade surface: a Store API for headless builds with custom endpoints, decorators and extension events, payments that return redirect URLs in the API response, and plugins built as Composer packages that can declare their own dependencies. The MIT-licensed open-source core is developed on GitHub through pull requests, RFCs and a public roadmap. We found no public information on documented API rate limits or staging environments. 9 10 10 16 6
The Skeptic
An MIT-licensed core on GitHub with pull requests accepted, plugins built as Composer packages that can declare dependencies, and a storefront API designed for headless builds (redirect URL returned in the API response, session explicitly not used) make this a platform a development team can own. We found no public information on documented API rate limits or version control for themes. 9 10 6 16 16
Order operations & back office
Show reasoningHide reasoning
How this is scored
What happens after checkout: order management, stock, returns, shipping, and the link to ERP or accounting.
0 — No order handling in the product; orders leave as emails or exports to be processed elsewhere.
3 — An order list with statuses, stock counts per product, and shipping rates set up in the shop.
5 — Order management with status emails, stock tracking, named carrier integrations or label printing, and refunds or returns handled in the system.
8 — Partial shipments and partial refunds, multi-warehouse or multi-location stock, multi-channel or marketplace order intake, fulfilment routing, dropshipping, and maintained interfaces to named ERP and accounting systems (DATEV among them for German merchants).
10 — The shop is the front of an operation: real-time stock across channels and warehouses, returns and refunds fully worked including partials, ERP integration the vendor maintains, and operational reporting a merchant runs the business from.
The Merchant
Orders are documented in depth: three state machines covering partial shipment, partial refund and partial returns, plus order notifications, customisation and order history, with returns management from Rise and multi-location inventory only from Beyond. The integration surface names CRM, payments and shipping in general terms, but we found no public information on named carriers, label printing, or maintained interfaces to ERP and accounting systems such as DATEV, which I would need at year end. 1 11 12 2
The B2B Seller
Order handling is first-class: three configurable state machines model order, delivery and transaction with documented partial shipment, partial payment, partial refund and chargeback states, returns management ships from the Rise tier, and multi-location inventory plus B2B quotes and purchase approvals come in the upper tiers. I found no public information on named carrier integrations, label printing, or maintained interfaces to named ERP and accounting systems such as DATEV. 11 2 2
The Developer
Orders are a first-class concept with three documented state machines, delivery states covering shipped-partially, returned and returned-partially, transaction states covering refunded-partially and chargebacks, order notifications, and plugin extension points; the paid plans add returns management on Rise and multi-location inventory on Beyond, with unlimited sales channels from Rise. Integration to CRM, payments and shipping is named generically. We found no public information on maintained interfaces to named ERP or accounting systems such as DATEV, on fulfilment routing, dropshipping or operational reporting, which is what the top of this scale turns on. 11 12 2 2 1
The Operations Lead
The order machinery is what I want to see: state machines carrying Shipped partially, Returned partially and Refunded partially as first-class final states, order notifications, denormalised line items persisted independently of the catalogue, returns management from the Rise tier, multi-location inventory at Beyond, and unlimited sales channels. Shipping shows up only as a generic integration surface — we found no public information on named carrier integrations, label printing, or maintained interfaces to ERP and accounting systems such as DATEV. 11 12 2 1 5 2
The Data Protection Officer
Order handling is documented in real depth: orders are persisted denormalised with all line items and calculated prices, three configurable state machines cover partial shipment, partial refund, chargeback and both return states, and order notifications ship with it; returns management comes with Rise and multi-location inventory with Beyond. We found no public information on named carriers or label printing, dropshipping, or maintained ERP and accounting interfaces such as DATEV — only a general line that CRM, payment and shipping tools connect. 11 12 2 1
The Skeptic
The order model is genuinely worked: denormalised line items with persisted prices, three state machines whose delivery states include partial shipment and partial return and whose transaction states include refunded and chargeback, plus order notifications and history. Returns management is listed from the Rise tier and multi-location inventory only with the custom-priced Beyond tier, and we found no public information on named carrier integrations, label printing or maintained ERP and accounting links such as DATEV. 11 12 2 1
Data ownership & exit
Show reasoningHide reasoning
How this is scored
Whether the catalogue, customers and order history remain the merchant's: export completeness, hosting choice, and what leaving actually costs.
0 — The terms state that the merchant's data cannot be exported or is not returned on cancellation.
3 — CSV export of products and customers, or of orders, from the admin.
5 — Export of catalogue, customers and orders documented (CSV, API or dump), with data deletion or return on cancellation stated in the terms or help centre.
8 — Full-fidelity export including media and order documents, a documented migration path in and out, self-hosting or a choice of hosting partner, and no metering that prices a migration out of reach.
10 — Ownership is structural rather than promised: open-source or source-available platform the merchant can run anywhere, database-level access, documented migration in both directions, and contractual data return.
The Merchant
Ownership here is structural rather than promised: a permissive MIT licence with full code access, self-hosting on infrastructure of my choice with a hosting partner programme, and a documented migration assistant that brings data in — media included — with checksum-based delta migrations. We found no public information on exporting catalogue, customers and orders out of the platform, on a documented migration path away from it, or on data return or deletion at cancellation. 14 15 16
The B2B Seller
Ownership is structural: self-hosting on infrastructure of the merchant's choice, a hosting-partner programme, and an MIT-licensed core with full code access, plus a Migration Assistant documenting the path in with media processing, delta runs via checksums, logging and error resolution. The documented migration path runs into Shopware; I found no public information on a documented export or migration out, or on contractual data return on cancellation. 15 16 13 14
The Developer
Ownership is structural rather than promised: the code is MIT-licensed with full access claimed, self-hosting is the default posture alongside SaaS and PaaS, and a hosting-partner locator exists, so the shop runs on infrastructure of my choosing. The Migration Assistant is documented in real depth — profiles, connections, media processing, premapping, logging and error resolution — but everything captured describes the path into Shopware. We found no public information on documented export of catalogue, customers and orders out of the platform, or on contractual data return on cancellation. 16 15 14 15 13
The Operations Lead
Ownership is structural: an MIT-licensed core with full code access that you can run on infrastructure of your choice, plus a documented Migration Assistant that brings data in — media included — with delta runs via checksums, premapping and error resolution. What leaving actually costs is only half answered, because we found no public information on export out of the platform or on data return stated in the terms on the captured pages. 14 15 16
The Data Protection Officer
The Migration Assistant is documented in depth for bringing data in — profiles, persistent mappings, checksum-based delta runs, dedicated media handling, logging and error resolution — and with self-hosting on infrastructure of the merchant's choice plus an MIT-licensed core, the data model sits in a database the merchant can reach. We found no public information on export of catalogue, customers and orders out of the platform, or on data return and deletion on cancellation in the terms; deletion that executes against order history is exactly what I would want in writing before signing. 13 14 15 16
The Skeptic
Ownership is structural: an MIT-licensed core that is self-hosted by default with SaaS and PaaS as options, full code access, and a documented Migration Assistant that persists mappings, skips unchanged data by checksum and processes media via HTTP or the local filesystem. The migration path documented runs into Shopware; we found no public information on export of catalogue, customers and orders out of the hosted plans or on data return at cancellation. 15 14 16 1 15
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where customer and order data live, who the contracting entity is, and which subprocessors sit in the checkout path. Independently sourced by the sovereignty pipeline. Dimensions the evidence does not establish are unknown, not non-EU.
0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.
3 — One European element proven — an EU hosting option, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.
5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain (CDN, analytics, payment routing, support tooling) is unstated or partly non-EU.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessor list published with locations, any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor European, certification published, and a self-hosted option that puts the shop entirely under the merchant's control.
The Merchant
The contracting entity is German — shopware AG in Schöppingen, registered at Amtsgericht Coesfeld — with a published data processing agreement based on EU Implementing Decision (EU) 2021/915, ISO 27001 certification, and a self-hosting option that keeps the shop entirely under my roof. Where hosted customer data resides in the SaaS and PaaS offers is not confirmed on the vendor's own captured pages — European data centers are named only for the AI assistant — and we found no public information on a subprocessor list with locations. 1 2 3 4 15
The B2B Seller
The contracting entity is shopware AG in Schöppingen, registered at Amtsgericht Coesfeld with a German VAT ID, a data processing agreement on the basis of EU Commission Implementing Decision (EU) 2021/915 is published, and the platform is self-hostable; European data centers are stated only for the AI component. Where customer and order data live in the hosted offerings, and which subprocessors sit in the checkout path, are not established by the captured pages. 3 4 15 1
The Developer
The contracting entity is shopware AG of Schöppingen, registered at Amtsgericht Coesfeld, and a data processing agreement on the basis of EU Commission Implementing Decision (EU) 2021/915 is published for customers and technology partners; ISO 27001 and SOC 2 Type II are claimed for the hosting environments, and European data centers are named for the AI component. Where shop, customer and order data reside under the SaaS and PaaS offerings is not confirmed on the vendor's own captured pages, and we found no public information on a subprocessor list with locations. Self-hosting is the lever that puts the whole data path under the merchant's own control. 3 4 1 15
The Operations Lead
The vendor is shopware AG in Schöppingen with a German register court, a published data processing agreement based on the EU Commission's standard clauses, and a self-hosting option that puts the shop entirely under the merchant's control. The captured pages state European data centres only for the AI copilot; the location of the vendor's managed hosting and the subprocessor chain are unstated. 3 4 15 1
The Data Protection Officer
The contracting entity is shopware AG of Schöppingen, registered at Amtsgericht Coesfeld, and a data processing agreement on the basis of the EU Commission's Implementing Decision (EU) 2021/915 is published for customers and technology partners; European data centres are named for the AI assistant, and ISO 27001 certification with SOC 2 Type II hosting environments is claimed. We found no public information on a subprocessor list with locations — where the CDN, analytics or payment routing sit — and the captured pages do not confirm where shop data resides by default. Self-hosting on infrastructure of one's choice is what keeps this partly under merchant control. 3 4 4 1 15
The Skeptic
The contracting entity is proven European — shopware AG, registered at Amtsgericht Coesfeld with a German VAT ID — and a data processing agreement on the basis of EU Commission Implementing Decision (EU) 2021/915 is published, with self-hosting available and European data centers claimed for the AI Copilot. The captured pages give no location for hosted shop data itself, and we found no public information on a subprocessor list with locations in the checkout path. 3 4 4 1 15
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a merchant can compute the real annual cost — licence, transaction fees, apps, hosting — from public pages alone. The category where the headline price is least often the invoice.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or one priced tier.
5 — Prices for the main tiers public with the billing period stated and the main inclusions per tier listed.
8 — Every tier priced publicly including transaction or revenue-share rates, order or GMV limits, and the cost of the extensions most shops need; VAT treatment and minimum term stated.
10 — Complete price computability: annual cost derivable for a given order volume and GMV including licence, transaction fees, hosting and typical extensions — and for open-source platforms, an honest statement that the licence is free and where the money actually goes.
The Merchant
The main tiers are public with inclusions listed and net pricing stated — Community Edition "Kostenlos € 0", Rise "Ab € 600 /Monat exkl. MwSt.", Evolve "Ab € 2.400 /Monat exkl. MwSt." — and add-ons carry figures: Intelligence+ at "€ 29 /Monat" or "€ 19 /Monat" exkl. MwSt. and Nexus extra executions at "10 € pro Block von 1.000", with 30 days free on Rise. Beyond is priced only as "Individuell", the payments note says transaction fees apply without naming them, and we found no public information on order or revenue limits, minimum terms or the cost of the Nosto search add-on — so my true annual bill stays an estimate. 2 2 2 2
The B2B Seller
Three of four tiers carry public monthly prices quoted net of statutory VAT — Community Edition "Kostenlos € 0", Rise "Ab € 600 /Monat exkl. MwSt.", Evolve "Ab € 2.400 /Monat exkl. MwSt." — with per-tier inclusions, a 30-day trial and priced add-ons (Shopware Intelligence+ at "€ 29 /Monat exkl. MwSt." or "€ 19 /Monat exkl. MwSt.", Nexus extra executions at 10 € per block of 1,000). Beyond is individually priced, Shopware Payments states transaction fees apply without naming the rates, and I found no public information on minimum terms or order and revenue limits, so the real annual cost is not computable from the public pages. 2 2 2
The Developer
The tiers are public with billing period and inclusions listed — Community Edition at € 0, Rise from € 600 /Monat exkl. MwSt., Evolve from € 2.400 /Monat exkl. MwSt., Beyond at Individuell — and add-ons carry real prices (Shopware Intelligence+ at € 29 /Monat exkl. MwSt. for the Community Edition and € 19 /Monat exkl. MwSt. for the paid plans, Nexus executions at 10 € per block of 1.000), with the net-of-VAT treatment stated. What stops a merchant computing the real invoice: Shopware Payments states transaction fees apply without naming a rate, the top tier is a sales conversation, and we found no public information on order or revenue limits or minimum terms. 2 2 2 15
The Operations Lead
Three tiers carry public monthly prices — Community Edition at € 0, Rise from € 600/Month and Evolve from € 2.400/Month, each stated exclusive of VAT — with per-tier inclusions, support response times and priced add-ons (Intelligence+ at € 29 or € 19 per month, Nexus overage at 10 € per block of 1.000 executions). Beyond is priced only as Individuell, Shopware Payments acknowledges transaction fees without publishing rates, and we found no public information on order or revenue limits or minimum terms. 2 2 15 2
The Data Protection Officer
Rise from €600 per month and Evolve from €2,400 per month, both quoted net of VAT with the monthly billing period and per-tier inclusions listed, plus a free Community Edition at €0; add-ons carry figures too — Intelligence+ at €29 or €19 per month and Nexus executions at €10 per block of 1,000. Beyond is priced individually and Shopware Payments states that transaction fees apply without naming the rates, so payment costs are not computable from public pages. We found no public information on minimum contract terms. 2 2 2 2
The Skeptic
Tier prices are public with inclusions listed per tier — Community Edition at € 0, Rise from "Ab € 600 /Monat exkl. MwSt.", Evolve from "Ab € 2.400 /Monat exkl. MwSt." — add-ons are priced (Intelligence+ at € 29 or € 19 per month excl. VAT, extra Nexus executions at 10 € per block of 1.000), and the net-of-VAT treatment is stated. Beyond is priced only as "Individuell", Shopware Payments states that transaction fees apply without publishing their rates, and we found no public information on minimum terms or order and revenue limits — so the real annual invoice is not computable from these pages alone. 2 2 2 2 2 15
European sovereignty — proven facts
4 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Incorporated in DE | 2/2 pts | 3 Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Hosting options | Self-hostable | 1/1 pts | 15 Report an error |
| Open source |
Open source (permissive)
unverified
Why unverified?The licence statement concerns Shopware's open-source core, and the excerpts do not name the licence of the commercial plans or paid extensions. |
1/1 pts | 16 Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?The excerpt shows only the linked entry on the privacy page, not the agreement text itself or an online conclusion flow. |
1/1 pts | 4 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Shopware
Is Shopware European?
Yes. whats-best.ai classifies Shopware as EU-Made. Its vendor, shopware AG, is incorporated in Germany, per the vendor’s page captured 16 Nov 2026.
Where does Shopware store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does Shopware have a free plan?
Yes. Shopware has a free plan, per the vendor’s page captured 5 Oct 2026.
What are the best alternatives to Shopware?
As of 18 Nov 2026, the panel rates JTL-Shop (3.5/5), Saleor (3/5) and Medusa (3/5) highest among the other 28 E-Commerce Platforms & Shop Systems products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is JTL-Shop (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Shopware alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 31 Aug 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. The excerpt shows only the linked entry on the privacy page, not the agreement text itself or an online conclusion flow.
- Weak sourcing — Open source. The licence statement concerns Shopware's open-source core, and the excerpts do not name the licence of the commercial plans or paid extensions.
- Weak sourcing — Hosting location. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 172 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 35 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 27 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 20 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 11 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 11 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 9 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (17)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.shopware.com Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 19 Oct 2026 Details →
- 2 Pricing www.shopware.com Checked 16 Nov 2026 +5 earlier captures: 9 Nov 2026, 2 Nov 2026, 5 Oct 2026, 15 Sep 2026, 31 Aug 2026 Details →
- 3 Imprint www.shopware.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
- 4 Privacy policy www.shopware.com Checked 16 Nov 2026 +5 earlier captures: 9 Nov 2026, 2 Nov 2026, 19 Oct 2026, 15 Sep 2026, 11 Sep 2026 Details →
- 5 Catalogue & checkout — found from sitemap developer.shopware.com Checked 16 Nov 2026 Details →
- 6 Catalogue & checkout — found from sitemap developer.shopware.com Checked 16 Nov 2026 Details →
- 7 Tax & German legal correctness — found from sitemap developer.shopware.com Checked 16 Nov 2026 Details →
- 8 Tax & German legal correctness — found from sitemap developer.shopware.com Checked 16 Nov 2026 Details →
- 9 Extensibility & developer surface — found from sitemap developer.shopware.com Checked 16 Nov 2026 Details →
- 10 Extensibility & developer surface — found from sitemap developer.shopware.com Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
- 11 Order operations & back office — found from sitemap developer.shopware.com Checked 16 Nov 2026 Details →
- 12 Order operations & back office — found from sitemap developer.shopware.com Checked 16 Nov 2026 Details →
- 13 Data ownership & exit — found from sitemap developer.shopware.com Checked 16 Nov 2026 Details →
- 14 Data ownership & exit — found from sitemap developer.shopware.com Checked 16 Nov 2026 Details →
- 15 Self-hosting / on-premises installation docs — found from the homepage www.shopware.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
- 16 Open-source licence page — found from the homepage www.shopware.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
- 17 Structured-data backfill: markup only, no text or screenshot www.shopware.com Checked 8 Nov 2026 Details →