JTL-Shop
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by JTL-Software-GmbH · www.jtl-software.de
Compare with Shopware → Compare with Shopify → 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.
JTL-Shop at a glance
- Vendor
- JTL-Software-GmbH
- 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 2 Nov 2026
- Panel verdict
- The AI panel rates JTL-Shop 3.5/5, the mean of 6 judges. JTL-Shop pairs an online shop with the vendor's own ERP, JTL-Wawi, and the bench rewards the pairing: operations scores run 8-9 for automatic order intake from 30+ marketplaces into one system with real-time payment matching and central shipping and returns, while tax and legal holds a steady 8 — the table's most consistent result — for OSS filing with the BZSt, automatic monitoring of the 10,000 € Lieferschwelle, IOSS for imports up to 150 € and GoBD-conform invoicing with DATEV export. 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
JTL-Shop pairs an online shop with the vendor's own ERP, JTL-Wawi, and the bench rewards the pairing: operations scores run 8-9 for automatic order intake from 30+ marketplaces into one system with real-time payment matching and central shipping and returns, while tax and legal holds a steady 8 — the table's most consistent result — for OSS filing with the BZSt, automatic monitoring of the 10,000 € Lieferschwelle, IOSS for imports up to 150 € and GoBD-conform invoicing with DATEV export. Sovereignty is the weakest mark at 3-4: a German contracting entity and a named data protection officer are on record, but the captured pages give no public information on data residency, hosting location, subprocessors or a data processing agreement. Pricing transparency scores 7-8 on published tiers, though Enterprise is auf Anfrage and VAT treatment and minimum term are not stated. The only spread beyond a single point is extensibility at 6-8, where the developer credits the public Git repository and direct database access while lower scores weigh the closed-beta, paid ERP REST API. Persona-weighted totals range from 6.2 to 7.1.
Speaks for it
- Tax and legal holds at 8, the table's steadiest result, on OSS filing for the BZSt, automatic monitoring of the 10,000 € Lieferschwelle and GoBD-conform invoicing with DATEV export
- Operations scores of 8-9 rest on automatic order flow from 30+ marketplaces into one ERP with real-time payment matching and central shipping and returns
- Data ownership is structural, with free local installation on the merchant's own Windows machine and database access through views and stored procedures
- Tiers are publicly priced — Start 0 € / Monat, Advanced ab 99 € / Monat, Pro ab 329 € / Monat — with no transaction fees on shop sales
- The shop source sits in a public Git repository, backed by a plugin system and 700+ extensions
Held against it
- Sovereignty scores of 3-4 are the lowest in the table, with no public information on data residency, hosting location, subprocessors or a data processing agreement
- The documented migration runs into JTL, with no public information on a route out or on data return and deletion at cancellation
- No public information on guest checkout, abandoned-cart recovery or product variants, capping catalog and checkout at 6-7
- Enterprise is priced auf Anfrage and VAT treatment and minimum term are not stated, so a full annual cost is not computable from public pages
- The ERP REST API is a closed beta priced at 199 € / Monat (99 € / Monat also shown), and the vendor states the ERP has no stand-alone plug-in module
Best for
- You are a German mid-market retailer selling cross-border in the EU and want OSS, IOSS and GoBD-conform invoicing handled largely by the vendor's Tax product
- You sell across Amazon, eBay and OTTO alongside your own shop and want orders, payments, shipping and returns run from a single ERP
- You want your ERP and shop data on your own Windows machine or server with direct database access
- You want a largely computable bill, with tier prices and per-order rates for external channels published
Avoid if
- You must confirm data residency, subprocessors or a data processing agreement before signing — the captured pages give no public information on any of them
- You need a documented exit route with full export and contractual data return when the contract ends
- You expect open, unpriced API access to the ERP — the REST API is in closed beta and priced at 199 € / Monat
- You are buying for private use — the offers apply exclusively to commercial customers
The scores
| Criterion | Panel median |
|---|---|
| Catalogue & checkout | 3 of 5 |
| Tax & German legal correctness | 4 of 5 |
| Extensibility & developer surface | 3.5 of 5 |
| Order operations & back office | 4 of 5 |
| Data ownership & exit | 3.5 of 5 |
| European sovereignty | 1.5 of 5 |
| Pricing transparency | 3.5 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
PayPal, Karten und Rechnung direkt im Shop plus 20+ Payment-Anbindungen von Ratenkauf bis Bitcoin give me exactly the German payment mix I sell on, and artikelgenaue Sonderpreise, Rabattstaffeln, Kundengruppen und Gutscheine are the pricing rules I need. The checkout can change without a rebuild — drag-and-drop templates, a Smarty template engine and a plugin system that adds functions without modifying store code. I found no public information on product variants, guest checkout or abandoned-cart recovery, which caps this short of the top. 9 5 11 9 8
The B2B Seller
For a trade seller this matters most: artikelgenaue Sonderpreise, Rabattstaffeln oder Festpreise for selected customers, customer groups for prices and discounts, vouchers and customer credit are all documented, and payments include PayPal, cards and Rechnung via JTL Pay (in beta) plus 20+ connections from Ratenkauf to Bitcoin with Bonitätsprüfung add-ons — payment on account with a credit check, in other words. Multi-language frontends with ECB-synchronised currencies round it out; we found no public information on product variants, guest checkout, abandoned-cart recovery or rule-based promotions. 5 10 9 9 11
The Developer
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. 5 10 9 11
The Operations Lead
Vouchers, customer-specific tiered pricing and a drag-and-drop storefront are documented, and payment is named: PayPal, cards and invoice through the beta JTL Pay plus Amazon Pay, Mollie and twenty-plus connections including instalment purchase in the extension store. Multi-language storefronts on ECB-synced currencies are stated. We found no public information on variants, guest checkout, abandoned-cart recovery or a customisable checkout, so it stops short of the top band. 5 9 10 9
The Data Protection Officer
Payment in the shop is documented through named routes — PayPal, cards and invoice via JTL Pay (beta) plus 20+ payment integrations including instalment purchase — and pricing goes beyond flat rates with article-level special prices, discount tiers and customer-group segmentation; multilingual shops with ECB-synced currencies are also documented. I found no public information on guest checkout, abandoned-cart recovery or rule-driven promotions, which keeps this below the top band. 5 9 10 5 9
The Skeptic
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. 5 9 10 11 9 9
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
GoBD-konforme Rechnungserstellung, E-Rechnungen in XRechnung und ZUGFeRD, DATEV-Export und flexible Steuerschlüssel are documented, and the OSS story runs deeper than data export: complete OSS-Berichte für das BZSt, automatic checking of the 10.000 € Lieferschwelle, IOSS and foreign VAT registration with authority communication handled by the vendor's Tax product, and gross end prices shown in checkout. I found no public information on VIES validation of VAT IDs, B2B reverse charge, or the classic German checkout duties like order-button wording, withdrawal policy and price indications — that last gap matters at my till. 5 6 7 6
The B2B Seller
The Tax service, powered by countX, is documented as producing complete OSS reports for the BZSt, monitoring filing deadlines, automatically detecting the 10.000 € per year delivery limit, and covering IOSS with one registration for 27 EU countries plus monthly filings and VAT registrations in the EU, UK and Switzerland; invoicing is documented as GoBD-conformant with XRechnung and ZUGFeRD and out-of-the-box DATEV export. We found no public information on VIES validation of VAT IDs, B2B reverse charge, or the German checkout requirements such as order-button wording, withdrawal policy and price-indication rules — and for someone selling net across the EU, that is precisely the gap that holds this back. 5 6 7 6 5
The Developer
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. 6 7 5 6
The Operations Lead
The OSS story is unusually complete: the tax module checks the annual distance-selling ceiling automatically, prepares the full BZSt filing file and submits it on time, and IOSS for imports up to 150 € runs on one registration across 27 countries with monthly filing. Invoices are GoBD-conformant, XRechnung and ZUGFeRD are processed, checkout shows end prices including tax, and foreign VAT registrations for the EU, UK and Switzerland are offered. We found no public information on VIES validation, reverse-charge notes or small-business handling, which keeps it below the maintained-in-every-case top level. 5 6 7 5 6
The Data Protection Officer
VAT work is unusually well documented: OSS calculation with complete BZSt filings and automatic monitoring of the 10.000 € Lieferschwelle, IOSS for third-country imports up to 150 €, foreign VAT registrations across the EU, UK and Switzerland, GoBD-conform invoice creation and archiving, XRechnung and ZUGFeRD, and DATEV export out of the box — largely run through the countX-powered Tax product rather than left to the merchant. I found no public information on VIES validation of VAT IDs or on small-business (Kleinunternehmer) handling. 6 7 5 6 5
The Skeptic
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. 5 6 7 5 6 5
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
A Smarty 3 template engine, a plugin system that adds functionality without touching store code, a public Git repository for JTL-Shop, English REST API documentation for Wawi, vouchers and marketplace connectivity, plus 700+ Templates & Plugins let me shape the shop to the business. The ERP REST API is a paid beta at 199 € / Monat and 99 € / Monat, and I found no public information on a storefront API for headless builds, staging environments or documented rate limits. 8 9 2
The B2B Seller
The developer surface is real: Smarty 3 templates, a plugin system that adds functionality without modifying store code, a public Git repository for JTL-Shop, and English-language REST API documentation for the ERP (closed beta), SCX, Vouchers and the fulfilment network, plus 700+ templates and plugins activated by click in the backend. The captured pages also state that the ERP has no stand-alone plug-in module and price the ERP REST API as a beta add-on; we found no public information on webhooks, a headless storefront API or documented rate limits. 8 9 9 2
The Developer
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. 8 12 9
The Operations Lead
Custom themes on the Smarty 3 engine, a plugin system that adds function without modifying store code, 700-plus extensions and several documented REST APIs (fulfillment network, marketplace connector, vouchers, ERP API in closed beta) give a real developer surface, with the shop source in a public Git repository and ERP database access via views and stored procedures. We found no public information on a headless storefront API, webhooks, documented rate limits or local development workflows, and the vendor itself states the merchandise-management system has no stand-alone plug-in module. 8 11 12
The Data Protection Officer
The developer surface is real: Smarty 3 templating, a plugin system that adds functionality without modifying store code, 700+ extensions, English-documented REST APIs for the ERP (closed beta), marketplace connection and fulfilment network, database-level access through views and stored procedures, a public Git repository for the shop and a public issue tracker. I found no public information on a headless storefront API or on documented rate limits. 8 11 12
The Skeptic
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. 8 11 12 2 2
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
Bestellungen laufen automatisch in die Wawi, wo Zahlung, Versand und Retouren zentral gesteuert werden — refunds, status e-mails and return labels included. Marketplace intake from Amazon, eBay and OTTO, warehouse software with mobile devices, a fulfilment network and out-of-the-box DATEV-Export are all documented, with multichannel sync reducing overselling. I found no public information on partial shipments, partial refunds or dropshipping. 9 9 5 1 11
The B2B Seller
Orders from JTL-Shop run automatically into JTL-Wawi where payment, shipping and returns are centrally controlled, with real-time payment matching against bank accounts and payment providers, shipping labels via Shipping 2.0, automated status emails with returns labels, and warehouse management through JTL-WMS. Order intake spans Amazon, eBay, OTTO, Shopify, POS and 30+ marketplaces with synchronisation documented to reduce overselling, and accounting leaves the system out of the box via DATEV export and the JERA interface; we found no public information on partial shipments, partial refunds or dropshipping. 9 5 9 11 1 12
The Developer
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. 5 9 9 1
The Operations Lead
Orders from the shop flow automatically into the ERP where payment, shipping and returns are run centrally, shipping labels come from Shipping 2.0, return labels go out with status emails, refunds are handled, and intake spans 30+ marketplaces including Amazon, eBay and OTTO plus POS tills, with channels synchronised to reduce overselling and DATEV export plus the JERA accounting interface maintained. We found no public information on partial shipments or partial refunds — the parts of December that hurt — nor on dropshipping or fulfilment routing, so I cannot go higher. 5 9 11 2 1
The Data Protection Officer
Orders from the shop flow automatically into the ERP where payment, shipping and returns are managed centrally; intake covers Amazon, eBay and OTTO marketplaces plus POS and connectors for Shopware 6, Shopify, WooCommerce and PrestaShop, with DATEV export out of the box, a named JERA accounting interface, real-time bank matching, multi-level dunning, status e-mails and a BI dashboard. I found no public information on dropshipping or on partial shipments and partial refunds. 5 9 11 9 1 1
The Skeptic
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. 5 9 11 2 9 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
A kostenfreie local installation on my own Windows machine with my own database, backup reimport, database access via prepared views and stored procedures, and a documented CSV migration path in — that is ownership I can feel, with local, hosting and cloud operating modes to choose from. The way out is thinner: I found no public information on a documented export route to another platform or on data return when the contract ends. 12 10 8 10
The B2B Seller
Ownership is close to structural: the ERP installs free on a local Windows machine, runs multi-user in the merchant's own network or on an own server, and the database is directly accessible through prepared views and stored procedures, with backups documented as re-importable; migration in from almost any system via connectors or the CSV-based JTL-DataTransfer tool is well documented. We found no public information on a documented migration path out of JTL or a contractual commitment to return data on cancellation. 12 8 2 10 11
The Developer
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. 8 12 10
The Operations Lead
Ownership is structural: the ERP installs free on your own Windows machine with your own database, backups can be reimported, prepared views and stored procedures give database-level access, and the shop source sits in a public Git repository. Migration in is well documented — connectors transfer automatically, otherwise the import and export tool with CSV, plus a migration team and optimised paths from PlentyONE and Afterbuy. We found no public information on a documented migration path out, on export of media and order documents, or on data return and deletion on cancellation. 8 12 10 10
The Data Protection Officer
A free local installation on the merchant's own Windows machine or server, database backup and re-import, and database-level access via views and stored procedures make ownership structural rather than merely promised, and the shop source sits in a public Git repository. But the migration story runs one way — CSV import via JTL-DataTransfer and a migration team into JTL are documented — and I found no public information on a migration path out or on data return and deletion at cancellation, exactly the terms I would insist on before signing. 2 8 11 12 10
The Skeptic
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. 5 8 11 12 10
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 unambiguously German — JTL-Software-GmbH, Amtsgericht Mönchengladbach HRB 12450, a German VAT number and a named data protection officer — and the privacy policy discloses processing within the JTL-Group for shared customer management. Data residency, hosting location and a data processing agreement are unknown on the captured pages, so only one European element is proven. 3 4
The B2B Seller
The imprint establishes a German contracting entity — JTL-Software-GmbH, Amtsgericht Mönchengladbach HRB 12450, VAT ID DE257864472 — and the privacy policy names that same company as controller, with personal data processed within the JTL-Group for shared customer management. Beyond that, we found no public information on where hosted shop data resides, on a data processing agreement, or on the subprocessor chain in the checkout path, so the German entity is the only European element the captured pages establish. 3 4
The Developer
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. 3 4
The Operations Lead
The contracting entity is German — JTL-Software-GmbH, registered at the Mönchengladbach district court, with a German data protection officer appointed — and a GDPR privacy policy governs group-wide processing with no third-party sharing without consent. Beyond that the chain is unstated: we found no public information on where cloud-hosted shops and data reside, on a published data processing agreement, or on subprocessor locations. 3 4 4
The Data Protection Officer
The contracting entity is proven German — JTL-Software-GmbH, register court Mönchengladbach HRB 12450 — with a named external data protection officer at Proliance GmbH, a privacy policy covering data subject rights and objection, a stated no-disclosure-without-consent rule and a native consent manager for shop and plugins. I found no public information on where the cloud hosting sits, on a subprocessor list with locations, on where analytics or CDN processing happen, or on a data processing agreement — the checkout chain stays dark, which caps this score. 3 4 9 4
The Skeptic
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. 3 11 4
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
0 € / Monat to start, ab 99 € / Monat for Advanced and ab 329 € / Monat for Pro with inclusions per tier, per-order rates for external channels of ab 0,22 €, ab 0,16 € and ab 0,11 €, priced add-ons like Auftragsbezogene Produktion 69 € / Monat, bis zu 17 % annual saving and a stated no-transaction-fee policy for shop sales — I can compute most of my annual bill myself. Enterprise is auf Anfrage, and I found no public information on VAT treatment or minimum term, so the last line of the invoice stays open. 9 2 2 9
The B2B Seller
The main tiers are public with inclusions listed — "JTL Start 0 € / Monat", "JTL Advanced ab 99 € / Monat", "JTL Pro ab 329 € / Monat" — on monthly and annual billing with "bis zu 17 % sparen", per-order rates for external channels from "Ab 0,22 € je weiterem Auftrag", itemised add-on prices such as Dispositionsproduktion 29 € / Monat and Workbench 125 € / Monat per user, no transaction fees on shop sales, and a 30-day hosted trial. JTL Enterprise is "auf Anfrage", and we found no public information on the VAT treatment of the prices or the minimum term, so a full annual cost is not computable from public pages alone. 9 2 2 9 2
The Developer
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. 2 9 2 9
The Operations Lead
Four editions are priced publicly with inclusions and support levels — Start at 0 € / Monat, Advanced ab 99 € / Monat, Pro ab 329 € / Monat, Enterprise auf Anfrage — and the metered part is precise: own-shop and POS orders are free while external channels cost from 0,22 €, 0,16 € or 0,11 € je weiterem Auftrag by plan in bookable packages. Add-ons carry prices (Auftragsbezogene Produktion 69 € / Monat, Workbench 125 € / Monat per user, REST-API ERP Beta 199 € / Monat), monthly and annual billing with up to 17 % saving is shown, and no transaction fees are charged on shop sales. Enterprise pricing on request plus no stated VAT treatment or minimum term keep it just short of full computability. 2 9 2 9
The Data Protection Officer
The main editions are publicly priced with inclusions — Start at 0 € / Monat, Advanced ab 99 € / Monat, Pro ab 329 € / Monat — alongside monthly and annual billing with up to 17 % annual saving, published extra-order rates per tier (Ab 0,22 €, 0,16 € or 0,11 € je weiterem Auftrag), priced add-ons such as Dispositionsproduktion 29 € / Monat and Workbench 125 € per user per month, and a stated absence of transaction fees on shop sales. Enterprise is priced on request, and I found no public information on VAT treatment or minimum term, so a complete annual figure is not fully derivable. 2 9 2 9 2
The Skeptic
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. 2 2 2 9 2 9
European sovereignty — proven facts
1 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 | — | uncited Report an error |
| Hosting options |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about JTL-Shop
Is JTL-Shop European?
Yes. whats-best.ai classifies JTL-Shop as EU-Made. Its vendor, JTL-Software-GmbH, is incorporated in Germany, per the vendor’s page captured 16 Nov 2026.
Where does JTL-Shop store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does JTL-Shop have a free plan?
Yes. JTL-Shop has a free plan, per the vendor’s page captured 2 Nov 2026.
What are the best alternatives to JTL-Shop?
As of 18 Nov 2026, the panel rates Saleor (3/5), Shopware (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 Shopware (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: JTL-Shop 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 — Hosting options. 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.
- 80 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
- 78 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
- 12 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
- 10 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
- 5 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
- 2 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
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was 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 (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.jtl-software.de Checked 16 Nov 2026 +5 earlier captures: 9 Nov 2026, 2 Nov 2026, 15 Sep 2026, 11 Sep 2026, 31 Aug 2026 Details →
- 2 Pricing www.jtl-software.de Checked 16 Nov 2026 +6 earlier captures: 9 Nov 2026, 2 Nov 2026, 26 Oct 2026, 15 Sep 2026, 11 Sep 2026, 31 Aug 2026 Details →
- 3 Imprint www.jtl-software.de Checked 16 Nov 2026 Details →
- 4 Privacy policy www.jtl-software.de Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 19 Oct 2026, 15 Sep 2026 Details →
- 5 Catalogue & checkout — found from sitemap www.jtl-software.com Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 26 Oct 2026 Details →
- 6 Tax & German legal correctness — found from sitemap www.jtl-software.com Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
- 7 Tax & German legal correctness — found from sitemap www.jtl-software.com Checked 16 Nov 2026 Details →
- 8 Extensibility & developer surface — found from sitemap www.jtl-software.com Checked 16 Nov 2026 Details →
- 9 Extensibility & developer surface — found from sitemap www.jtl-software.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 26 Oct 2026 Details →
- 10 Order operations & back office — found from sitemap www.jtl-software.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 26 Oct 2026 Details →
- 11 Order operations & back office — found from sitemap www.jtl-software.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 26 Oct 2026 Details →
- 12 Data ownership & exit — found from sitemap www.jtl-software.com Checked 16 Nov 2026 Details →