JTL-Shop vs Shopware

JTL-Shop

The only evidenced commerce surface is payment breadth ("Integrationen zu allen beliebigen Payment-Anbietern") plus a 30-marketplace and 24/7 repricing engine; variants, bundles, tiered pricing, guest checkout, promotions rules and checkout customisation appear nowhere on this sheet, so the catalogue itself is essentially unevidenced.

Shopware

Variants are properly modelled — parent-child inheritance, a configurator assembled for each variant product, hierarchical categories — and payments sit on a documented handler architecture with synchronous and asynchronous flows, PayPal the one provider named. We found no public information on bundles, tiered pricing, guest checkout, or German-standard payment methods such as invoice and direct debit; customer-specific prices appear only in the Beyond tier. The checkout is clearly extendable, but the conversion machinery itself is not evidenced.

JTL-Shop

A GoBD-conformity claim and an unnamed "Tax powered by" module are all the evidence there is; destination-based VAT, OSS, reverse charge, VAT-ID validation, e-invoicing and the checkout legal texts German law actually imposes (order-button wording, withdrawal policy) are absent, which lands this at hand-configurable-and-hoped-for rather than platform-maintained.

Shopware

What the platform itself does is expose tax settings in the administration and orchestrate external tax providers — since version 6.5 an app can be called during checkout with signed requests, priority ordering and a five-second timeout, its sums used as-is. The German-law work — destination VAT, OSS, reverse charge with VAT-ID validation, checkout legal texts, e-invoicing — rests on whichever tax app the merchant connects, and we found no public information on any of it being handled by the platform. That is configuration plus an extension point, not maintained correctness.

JTL-Shop

Partner-apps, extensions and a stepwise-migration story plus a REST API give a real ecosystem, but the API is Beta and paywalled up to 199 €/month, and themes, webhooks, staging environments and any headless storefront API are unevidenced.

Shopware

The developer surface is real: plugins are Symfony bundles and Composer packages with a dependency model, the Store API is a documented service-based route system with decorators, and the payment flow is explicitly designed for headless use. The Community Edition is open source and self-hosted, so a team can run the whole thing. We found no public information on staging environments, theme version control or documented rate limits, and the documentation states plugins are not compatible with the cloud stores, where apps are required instead.

JTL-Shop

This is where the platform shows itself: ERP/WMS with mobile warehouse devices and shipment tracking, 30+ marketplaces synchronised against overselling, a returns module, JTL2DATEV bank reconciliation and a BI dashboard recommending markdowns and restocks; only shipping labels via JTL-Shipping are still "coming soon".

Shopware

The order model is workflow-built: three state machines for order, transaction and delivery with configurable, otherwise blocked transitions, and partial states throughout — shipped partially, returned partially, refunded partially — so partial shipments, returns and refunds are worked into the core. Multi-inventory arrives only with the Beyond tier, and shipping appears as an integration category without named carriers, label printing, or any named ERP or accounting system. We found no public information on fulfilment routing, dropshipping or operational reporting.

JTL-Shop

A genuine local-hosting option ("Lokal – Auf eigenem Server") and "schrittweise Migration möglich" beat most SaaS, but nothing evidences complete export of customer records and order history, deletion that actually executes, or a data-return commitment — exactly what I would demand before a merchant signs.

Shopware

Ownership is partly structural: the Community Edition is open source and self-hosted, orders are denormalised and persisted independently of the catalogue, and numerous data-portability and management tools are claimed. The Migration Assistant is documented in depth — connections, profiles, gateways, dedicated media handling, checksum-based deltas — but the captured pages describe migrating into Shopware; we found no public information on a documented export or exit path out, on deletion executing against order history, or on a data-return commitment.

JTL-Shop

The imprint puts the contracting entity squarely in Germany (HRB 12450, Amtsgericht Mönchengladbach, DE VAT ID) with a named external DPO, but hosting as standard is unstated and no subprocessor list is published — the chain runs on "powered by Dealavo / JERA / GREYHOUND" modules whose data locations and legal bases are unexplained.

Shopware

The contracting entity is solidly European — shopware AG, registered at the Amtsgericht Coesfeld, seat in Schöppingen, German VAT ID — and European data centres are claimed alongside self-hosting, PaaS and SaaS, with a data processing agreement on the EU Commission's standard contractual clauses plus ISO 27001 and SOC 2 Type II stated. We found no public information on a subprocessor list, on where the CDN, analytics or payment routing sit, or on confirmed data residence for the hosted offerings beyond a data-centre claim made in the context of the Copilot. A German entity with an unnamed processing chain — and a compliance statement that privacy standards in the USA and further markets are also met — leaves the checkout path unaccounted for.

JTL-Shop

Per-order overage rates (from 0.11–0.22 €), order packages, add-on prices and an annual discount up to 17 % are public, making most of the bill computable; but Enterprise is "Auf Anfrage", the Start tier price is not captured, and VAT treatment and minimum term are nowhere on the page.

Shopware

Tier prices are public with VAT treatment stated — Community Edition at € 0, Rise "Ab € 600 /Monat exkl. MwSt.", Evolve "Ab € 2.400 /Monat exkl. MwSt." — and the Intelligence+ add-on is priced per tier, with Nexus in a free introductory phase carrying a non-binding review limit of 10,000 requests per customer and calendar month. From-pricing and an individually quoted Beyond tier mean the annual invoice is not computable from the page, and we found no public information on transaction or revenue-share fees, order or revenue limits, minimum terms, or the cost of the extensions most shops need beyond that one add-on.