JTL-Shop vs Shopware

JTL-Shop

EU-Made

Sovereignty: 1 of 6 dimensions proven

Full evaluation →

Shopware

EU-Made

Sovereignty: 4 of 6 dimensions proven

Full evaluation →

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 Developer

Will maintain this for five years. Wants local development, version control for themes, a plugin architecture with a dependency model, and upgrades that do not orphan the customisations. Reads a closed template editor as a future migration.

JTL-Shop

This judge's pick

Shopware

Criterion by criterion

Catalogue & checkout

JTL-Shop

The captured pages show a real shop with a checkout that takes payment: PayPal, cards and invoice "direkt in deinem Shop" via the new Pay solution, more than twenty payment connections from Ratenkauf to Bitcoin in the Extension Store, vouchers, and customer-group segmentation driving prices, discounts and article-level special prices with Rabattstaffeln. We found no public information on product variants, guest checkout, abandoned-cart recovery or a checkout customisable without a rebuild, so it sits above the mid anchor but not near the top.

Shopware

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.

Tax & German legal correctness

JTL-Shop

Tax is handled largely by the vendor's Tax module rather than the merchant: OSS calculation, the complete filing file for the BZSt via the BOP portal with timely submission, deadline monitoring, authority communication taken over, automatic recognition of the Lieferschwelle of 10.000 € per year, IOSS registration covering 27 EU countries, plus GoBD-conformant invoicing and archiving and XRechnung/ZUGFeRD e-invoices. We found no public information on VIES validation of VAT IDs, reverse-charge handling, or the German checkout formalities such as order-button wording and withdrawal policy, which is what holds this below the top level.

Shopware

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.

Extensibility & developer surface

JTL-Shop

This is the surface I would bet five years on: a public Git repository for JTL-Shop, Smarty 3 templates over an HTML5 front end, a plugin system that adds functionality "without modifying the store code", documented REST APIs for SCX, Vouchers and the fulfillment network, and genuine database access through prepared views and stored procedures, with 700+ templates and plugins behind it. The ERP REST API is in closed beta and even priced, the merchandise management "does not have a stand-alone plug-in module", a test system requires sales activation, and we found no public information on a headless storefront API, documented rate limits, theme versioning or continuous integration support.

Shopware

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.

Order operations & back office

JTL-Shop

Operations are the product's centre of gravity: orders from JTL-Shop flow automatically into JTL-Wawi where payment, shipping and returns are controlled, intake spans Amazon, eBay, OTTO, Shopify and 30+ marketplaces with synchronisation that reduces overselling, payments are matched in real time from banks and providers, DATEV export works out of the box, shipping labels come via Shipping 2.0, and a BI dashboard covers sales and stock. We found no public information on partial shipments, partial refunds or dropshipping.

Shopware

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.

Data ownership & exit

JTL-Shop

The merchant can physically hold the data: local installation on a Windows machine or the company's own server, staff working on a shared database in the local network, database-level access via views and stored procedures, and a JTL-Wawi database backup that can be re-imported — that is structural ownership, not a promise. Migration into JTL is documented in steps with CSV via JTL-DataTransfer or automatic transfer via Connector, but we found no public information on a documented migration path out, full-fidelity export including media and documents, or contractual data return on cancellation.

Shopware

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.

European sovereignty

JTL-Shop

One European element is proven emphatically: the contracting entity is JTL-Software-GmbH at Amtsgericht Mönchengladbach under HRB 12450, with a named data protection officer and a privacy policy naming the company as controller while describing processing across the JTL-Group. We found no public information on where the offered cloud and SQL hosting physically resides, on a published data processing agreement, or on subprocessor locations in the checkout path.

Shopware

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.

Pricing transparency

JTL-Shop

Nearly the whole annual cost is computable from public pages: JTL Start at 0 € / Monat, JTL Advanced ab 99 € / Monat, JTL Pro ab 329 € / Monat with support levels named per tier, order packages from 0,22 € per additional order, priced add-ons such as Dispositionsproduktion at 29 € / Monat and Workbench at 125 € / Monat per user, up to 17 % savings on annual billing, and the statement that shop sales carry no transaction fees. Enterprise is priced only on request, and we found no public information on the VAT treatment of the listed prices or minimum contract terms.

Shopware

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.

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.

Fact JTL-Shop Shopware
Legal · Entity JTL-Software-GmbH1

captured 16 Nov 2026 · Report an error

shopware AG2

captured 16 Nov 2026 · Report an error

Legal · Register court 12450 · Amtsgericht Mönchengladbach3

captured 16 Nov 2026 · Report an error

HRB 11471 · Amtsgericht Coesfeld4

captured 2 Nov 2026 · Report an error

Legal · VAT ID DE2578644723

captured 16 Nov 2026 · Report an error

DE2616794935

captured 16 Nov 2026 · Report an error

Questions about JTL-Shop and Shopware

Which is better, JTL-Shop or Shopware?

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.