As of 18 Nov 2026, the panel rates JTL-Shop 3.5/5 and Shopware 3/5 in E-Commerce Platforms & Shop Systems. Weighted by what each judge cares about, 6 of the 6 judges pick JTL-Shop and 0 pick Shopware. JTL-Shop scores higher on 4 of 7 criteria (Tax & German legal correctness, Order operations & back office, Pricing transparency, plus 1 more). Shopware scores higher on 3 of 7 criteria (Extensibility & developer surface, European sovereignty and Data ownership & exit). Provenance — JTL-Shop: EU-Made, Germany; Shopware: EU-Made, Germany. Ratings are the AI panel’s opinion, formed from public evidence: how scores are made.
The short answer
The per-criterion leans split — that split is the answer. JTL-Shop takes tax and legal 6 judges to 0 (means 8.0 to 3.5, on OSS filing with the BZSt, the 10,000 € Lieferschwelle and GoBD-conform DATEV export), operations 6 to 0 (8.2 to 6.8, on order intake from 30+ marketplaces into JTL-Wawi), pricing transparency 6 to 0 (7.2 to 6.0) and catalog and checkout 4 to 0 with two ties. Shopware takes extensibility 6 to 0 (8.3 to 6.7, on the Store API, Composer plugins and open development) and sovereignty 6 to 0 (4.7 to 3.2, on self-hosting, a permissive open-source core and a self-serve data processing agreement). Data control and exit splits: 3 judges to 1 for Shopware, two ties. Both contract under a German entity; both list data residency as unknown. Weighted totals lean JTL-Shop across the six personas — merchant 7 to 6.2, developer 7.1 to 7.
Choose JTL-Shop if
You sell cross-border in the EU and need OSS filing with the BZSt, automatic monitoring of the 10,000 € Lieferschwelle and IOSS for imports up to 150 € — tax and legal leans JTL-Shop 6 judges to 0 (means 8.0 to 3.5).
Your team takes orders from 30+ marketplaces and wants automatic intake into one system with real-time payment matching and central shipping and returns — operations leans JTL-Shop 6 judges to 0 (means 8.2 to 6.8).
You invoice under German rules and need GoBD-conform invoicing with DATEV export — part of JTL-Shop's tax and legal result, while we found no public information on Shopware destination-country VAT, VIES validation or OSS.
You want published pricing tiers before committing — pricing transparency leans JTL-Shop 6 judges to 0 (means 7.2 to 6.0), with tiers published though Enterprise is auf Anfrage.
You weigh catalog and checkout heavily — the leans run 4 judges to 0 for JTL-Shop with two ties (means 6.3 to 5.7), and we found no public information on Shopware vouchers, guest checkout or abandoned-cart recovery.
Choose Shopware if
You build headless storefronts and need a documented Store API, plugins as Composer packages and open development on GitHub — extensibility leans Shopware 6 judges to 0 (means 8.3 to 6.7).
Your team must run the shop on its own infrastructure — Shopware lists hosting options as self-hostable alongside SaaS and PaaS, while JTL-Shop's hosting options show unknown (sovereignty leans Shopware 6 judges to 0).
You must sign a data processing agreement before go-live — Shopware lists a self-serve data processing agreement, while JTL-Shop's data processing agreement status shows unknown.
Your developers need to audit or fork the core — Shopware lists its open-source license as permissive (an MIT-licensed core), while JTL-Shop's open-source status shows unknown.
Data control and exit is your deciding criterion — the leans there run 3 judges for Shopware to 1 for JTL-Shop with two ties (means 7.3 to 6.8).
Read this comparison as one judge. Each weighs the same scores by what they care about.
The Skeptic
Knows the headline price is never the invoice here. Reads for the transaction fee, the apps that turn out to be mandatory, the hosting nobody mentioned, and what the platform charges to let a merchant leave with their own order history.
JTL-Shop
This judge's pick
Shopware
Criterion by criterion
Catalogue & checkout
JTL-Shop
Customer-group pricing, article-exact special prices with discount tiers, and vouchers are documented, and payment breadth is real: 20-plus connections in the extension store plus PayPal, card and invoice through JTL Pay in beta. I found no public information on product variants, guest checkout or abandoned-cart recovery, and the free entry ends at one shop with a 500-article cap.
Shopware
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.
Tax & German legal correctness
JTL-Shop
Genuinely deep: OSS calculation with automatic checking of the 10.000 € yearly cross-border sales limit, the complete filing file prepared for the BZSt via the BOP portal, IOSS for imports, foreign VAT registrations in the EU, UK and Switzerland, XRechnung and ZUGFeRD processing, and GoBD-conformant invoicing with DATEV export. What the pages do not evidence is VAT-ID validation, reverse-charge handling or the German checkout requirements such as order-button wording, so it stops short of the top.
Shopware
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.
Extensibility & developer surface
JTL-Shop
Smarty 3 templates, a plugin system that adds features without touching store code, 700-plus extensions and a public Git repository for JTL-Shop are on the table, alongside documented REST APIs for the marketplace connector, the fulfilment network and vouchers. But the developer surface has an invoice attached: the ERP REST API is a closed beta priced at 199 € / Monat (99 € / Monat also shown), a test system means contacting sales, and the vendor states the ERP has no stand-alone plug-in module. Nothing captured on headless storefront APIs, webhooks or rate limits.
Shopware
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.
Order operations & back office
JTL-Shop
Order handling is the product: shop orders flow automatically into the vendor's own ERP where real-time payment matching, shipping labels, returns and out-of-the-box DATEV export live, with Amazon, eBay, OTTO, Shopify and POS intake on 30-plus marketplaces. The detail I watch for is that every order from an external channel is metered through order packages — operations scale, but at a per-order price. Partial shipments, dropshipping and true multi-warehouse routing are not documented in the captured pages.
Shopware
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.
Data ownership & exit
JTL-Shop
Free local installation on your own Windows machine plus documented database access through views and stored procedures make ERP data ownership structural rather than promised, and a database backup and re-import path exists. But the migration story captured runs one way — a JTL team moving your data in via connector or CSV — and I found no public information on exporting the full catalogue, customers and order history out, or on data return when a contract ends.
Shopware
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.
European sovereignty
JTL-Shop
A German contracting entity with a German register court and VAT ID is proven, and processing across JTL-Group companies for shared customer management is disclosed. Everything else in the chain — where the offered cloud hosting actually sits, a published data-processing agreement, subprocessor locations — is unstated on the captured pages, so one proven European element is all I can credit.
Shopware
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.
Pricing transparency
JTL-Shop
Unusually computable: JTL Start at 0 € / Monat, Advanced ab 99 € / Monat, Pro ab 329 € / Monat, order packages for external channels at 0,22 €, 0,16 € and 0,11 € per further order, named add-on prices from 29 € / Monat to 125 € / Monat per user, a stated no-transaction-fee policy on shop sales, and bis zu 17 % savings on annual billing. What keeps it from the top: Enterprise is only on request, VAT treatment and minimum term are not stated, and no hosting price for the shop itself appears anywhere captured.
Shopware
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.
Sovereignty, side by side
Dimension
JTL-Shop
Shopware
Legal entity
Incorporated in DE
Incorporated in DE
Hosting location
Not determined
Not determined
Hosting options
Not determined
Self-hostable
Open source
Not determined
Open source (permissive)
Data processing agreement
Not determined
Published, self-serve
Transfer impact assessment
Not determined
Not determined
Facts, side by side
Only facts both products carry under the same definition — anything else would not be a fair row.
As of 18 Nov 2026, the panel rates JTL-Shop higher: 3.5/5 against 3/5. Weighted by what each judge cares about, 6 of the 6 judges pick JTL-Shop and 0 pick Shopware. Which one fits depends on the criteria that matter to you; the table on this page shows both side by side, and each judge’s reading has its own page. Both were scored by the same AI bench under the same rubric, from public evidence only, as the methodology describes.
Is JTL-Shop or Shopware European?
JTL-Shop is European (EU-Made, Germany). Shopware is European (EU-Made, Germany). Provenance is read from each company’s own legal pages: who builds it and who owns it.
Do JTL-Shop and Shopware have a free plan?
As of 18 Nov 2026, both vendors’ own pages state a free plan. Each product page links the pricing page it was read from.