E-Commerce Platforms & Shop Systems
JTL-Shop
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 4 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? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
JTL-Shop is a German shop-plus-ERP platform, and its strength is operations, where scores run 7-8: synchronised selling on 30+ marketplaces without extra licences, WMS with mobile warehouse devices, shipment tracking, bank reconciliation from Advanced and the JTL2DATEV bridge, docked because JTL-Shipping labels are only 'coming soon' and partial refunds and dropshipping are unevidenced. Weakest is tax & German legal correctness at 2-3: judges found GoBD-conformant finance processes and a 'Tax powered by' module name but no destination-based VAT, OSS, reverse charge or VAT-ID validation on the evidence. Scores spread on data ownership & exit, where judges weighed the 'Lokal – Auf eigenem Server' hosting option against silence on export, deletion and any exit path, and on pricing transparency, where public per-order metering (ab 0,22 € Start, 0,16 € Advanced, 0,11 € Pro) sits beside an Enterprise tier that is 'Auf Anfrage'. Catalogue & checkout is thin beyond payment integrations and unlimited articles; sovereignty holds at 3-4 on a German imprint with a named DPO but no subprocessor list.
Speaks for it
- Sells on 30+ marketplaces without extra licences, with multichannel sync that reduces overselling.
- Provides a WMS with mobile warehouse devices and shipment tracking in the ERP.
- Publishes per-order overage pricing by tier — ab 0,22 € (Start), ab 0,16 € (Advanced), ab 0,11 € (Pro) — with orders from your own JTL-Shop or POS free.
- Offers a 'Lokal – Auf eigenem Server' hosting option as structural data control.
- Contracts through a German GmbH (Amtsgericht Mönchengladbach HRB 12450, VAT ID DE257864472) with a named external DPO at Proliance GmbH.
Held against it
- Evidences no VAT determination — nothing on destination-based VAT, OSS, reverse charge or VAT-ID validation; GoBD conformity covers bookkeeping only.
- Exposes its only API as a Beta add-on priced 99-199 €/month, with no webhooks, themes, staging or headless storefront in evidence.
- Lists JTL-Shipping labels as 'coming soon', with partial shipments, partial refunds and dropshipping flows unevidenced.
- Publishes no subprocessor list, leaves data residency unstated, and discloses group-wide data sharing across JTL-Group companies.
- Holds Enterprise at 'Auf Anfrage' with Start and Pro headline prices absent from the evidence, and payment-gateway rates, VAT treatment and minimum term unstated.
Best for
- You run multichannel retail across marketplaces and want shop, ERP and warehouse in one system — operations is where the bench scores highest.
- You want to host the platform on your own server via 'Lokal – Auf eigenem Server'.
- You are a German mid-market business that lives on DATEV export and bank reconciliation, available from the Advanced tier (ab 99 €/month).
- You need order-metered pricing you can compute, with unlimited JTL-Wawi users and free orders from your own JTL-Shop or POS.
Avoid if
- You need a platform-maintained VAT engine for cross-border sales — ask the vendor: the public pages we read do not show it
- Your team plans to build extensively on the API — the only one in evidence is the JTL-Wawi REST API, a Beta add-on at 99-199 €/month.
- You must audit the full processing chain before signing — ask the vendor: the public pages we read do not show it
- You need a documented exit path — ask the vendor: the public pages we read do not show it
The scores
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 — Flat product list with one price and no variants; checkout is a form and one payment method.
3 — Variants and categories with a standard checkout and two or three payment methods, but no bundles, no tiered pricing and no guest checkout worth the name.
5 — Full variant matrix, product bundles, tiered and customer-group pricing, guest checkout, and the payment methods a German shop needs including invoice and direct debit.
8 — Configurable products, per-channel pricing, promotions and vouchers with rules, a checkout that can be customised without a rebuild, and payment via the major providers plus 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
Payment integrations 'zu allen beliebigen Payment-Anbietern' plus unlimited articles, multiple Profi-Shops and rule-based repricing get it past a flat form, but the evidence is silent on variants, bundles, customer-group pricing, guest checkout, vouchers-with-rules and the German must-haves — invoice and direct debit are never named. Nothing says I could change the checkout without a rebuild, and that silence caps it. 1 2
The B2B Seller
Unlimited articles and integrations to all popular payment providers are the only merchandising facts on the evidence; the checkout itself is never evidenced. Nothing on variants, bundles, tiered or customer-group pricing — as a trade seller I see no net-price or customer-specific price list story at all, which tells me this page has not met a trade customer. 1 2
The Developer
The evidence gives me 'unlimited articles' and 'Integrationen zu allen beliebigen Payment-Anbietern', and that is the entire catalogue-and-checkout story — not one word on variants, bundles, tiered pricing, guest checkout, promotions or vouchers. Payment integrations exist, so it is above the flat-list floor, but silence on everything else caps it well below the standard-checkout anchor. 1 2
The Operations Lead
Payments via "allen beliebigen Payment-Anbietern" and 24/7 rule-based repricing are evidenced, plus unlimited articles per shop — but variants, bundles, tiered or customer-group pricing, guest checkout and per-channel pricing are all silent, and silence is not a variant matrix. Payment breadth puts it a notch above barebones, nothing else does. 1 2
The Data Protection Officer
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. 1 2
The Skeptic
Everything the evidence offers on the selling side is 'unbegrenzte Artikel' and 'Integrationen zu allen beliebigen Payment-Anbietern' — not one word on variants, bundles, tiered pricing, guest checkout, vouchers or German payment habits like invoice and direct debit. For a shop product, checkout evidence this absent is information: I cannot credit conversion features nobody documented. 1 2
Tax & German legal correctness
Show reasoningHide reasoning
How this is scored
VAT determination, OSS, B2B reverse charge, and the checkout requirements German law actually imposes — judged on what the platform does, not on a plugin someone could buy.
0 — A single VAT rate applied everywhere; no B2B handling, no country logic, no legal-text handling in checkout.
3 — Per-country VAT rates configurable by hand, net prices for B2B possible with effort, and legal texts as free-form pages.
5 — Automatic VAT by destination and customer type, VAT-ID validation with reverse charge, gross and net display per customer group, and the mandatory checkout elements (order button wording, withdrawal policy, price indications) handled.
8 — OSS thresholds tracked and reported, correct invoicing 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- and DSGVO-conformant finance processes, a 'Tax' module and the JTL2DATEV bridge evidence German accounting correctness, but there is not one fact about VAT by destination, OSS, reverse charge, VAT-ID validation or the mandatory checkout elements German law imposes. From a German vendor selling to German merchants, that silence in the evidence is loud — a lawyer could review nothing here. 1 2
The B2B Seller
The tax evidence is accounting adjacency — GoBD-conform processes, a DATEV booking service and a 'Tax powered by' module name. No VAT-ID validation, no reverse charge, no OSS, no gross/net display per customer group: the checkout tax engine this criterion needs is simply absent from the evidence, and I cannot put a B2B shop on that silence. 1 2
The Developer
All I have is a 'Tax powered by' module name and a DSGVO/GoBD compliance claim for finance processes — no VAT-by-destination, no OSS, no reverse charge, no VAT-ID validation, no XRechnung/ZUGFeRD, nothing on mandatory checkout elements. For a German mid-market vendor this should be the strongest section, and the evidence evidences almost none of it; a compliance slogan is not tax correctness. 1 2
The Operations Lead
A "Tax powered by" module exists and the vendor claims GoBD-conformant finance processes with DATEV export, but GoBD is bookkeeping, not VAT determination — nothing on destination-based VAT, OSS, reverse charge, VAT-ID validation or checkout legal texts. That is below even hand-configured per-country rates. 1 2
The Data Protection Officer
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. 1
The Skeptic
A 'Tax powered by' module name and DSGVO-/GoBD-konforme Abläufe is bookkeeping hygiene, not tax determination; the evidence contains nothing on VAT by destination, OSS, B2B reverse charge, VAT-ID validation or the checkout texts German law demands. Being a German vendor with a DATEV booking service earns nothing on this criterion until the pages say what the shop itself computes. 1 2
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 — Fixed templates, no app ecosystem, no API.
3 — Theme editing within limits and a small app store; a read-mostly API and no local development story.
5 — Custom themes with a template language, an app or plugin ecosystem, a documented REST API, and webhooks for the core order events.
8 — Full storefront API for headless builds, an extension framework with its own lifecycle, staging 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
Partner apps, extensions, interfaces and stepwise migration exist, and there is a REST API — but it is a Beta sold as a paid add-on at 199/99 EUR a month, which tells me how they feel about me building on the platform. No themes, no webhooks, no headless storefront API, no local development story in evidence. 1 2
The B2B Seller
Schnittstellen, partner apps and extensions are confirmed, but the REST API ships as a paid beta add-on at 99–199 €/month — an API you rent, still in beta. No webhooks, no headless storefront API, no theme language or staging story appears anywhere in the evidence. 1 2
The Developer
The only API in evidence is the JTL-Wawi REST API, marked Beta and priced at 199/99 € per month as an add-on — an API behind a paywall is a revenue line, not a developer surface I can build a five-year maintenance commitment on. Partner apps, extensions and interfaces are claimed, but there is no mention of themes, template editing, webhooks, staging, local development or version control anywhere; a closed template story is a future migration, and here I cannot even confirm templates exist. 1 2
The Operations Lead
Modular build with interfaces, partner apps and extensions plus 500+ partners is a real ecosystem, but the REST API is in Beta and costs 99–199 €/month as an add-on — an API you rent in beta is not a developer surface. No evidence on themes, webhooks, staging or headless keeps it under the middle anchor. 1 2
The Data Protection Officer
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. 1 2
The Skeptic
Schnittstellen, Partner-Apps und Extensions exist, but the REST API is Beta and rented as an add-on at 99–199 €/month — a monthly fee to talk to your own shop is lock-in dressed up as a surface. No evidence of themes, webhooks, headless, staging or a local development story anywhere in the evidence. 1 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 — An order list and an email; stock is a number nobody trusts, returns are manual.
3 — Order statuses and basic stock, one shipping integration, and returns handled by hand.
5 — Order workflow with partial shipments, multi-warehouse stock, named carrier integrations with label printing, and a returns process in the system.
8 — Multi-channel order intake, automated fulfilment routing, supplier and dropshipping flows, and maintained interfaces to named ERP and accounting systems.
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
JTL is the ERP and WMS itself: mobile warehouse devices, sendungsverfolgung im ERP, 30+ marketplaces without extra licences, multi-channel sync that reduces overselling, a Returns module, bank reconciliation from Advanced and DATEV export. Shipping labels are only 'coming soon' and dropshipping/supplier flows are unevidenced, so it sits at 8, not higher — but this is the strongest part of the evidence. 1 2
The B2B Seller
Clearly the strongest area: 30+ marketplaces with oversell protection, WMS with mobile devices and shipment tracking, a returns module and the JTL2DATEV accounting interface, plus an AI BI dashboard driving reorder and discount decisions. Held below 8 because shipping labels are only 'coming soon' and no named carriers, partial shipments or supplier/dropshipping flows are evidenced. 1 2
The Developer
This is the one criterion where the evidence is dense: multichannel sync that 'reduziert Überverkäufe', 30+ marketplaces without extra licences, WMS with mobile warehouse devices, bank reconciliation, and a named accounting bridge via JTL2DATEV powered by JERA. It falls short of the top anchors because shipping labels are literally 'Coming soon', and dropshipping, supplier flows and partial returns/refunds are silent despite a Returns module name appearing. 1 2
The Operations Lead
This is the heart of the product: synced shops and 30+ marketplaces with overselling reduced, ERP-native operations with mobile warehouse devices, shipment tracking in the Wawi, DATEV bank reconciliation and BI reporting a merchant can steer by. But shipping labels via JTL-Shipping are explicitly "coming soon", no carrier is named, and partial shipments and partial refunds appear nowhere — a shop that cannot do a partial refund has never had December, so it stops short of the top anchors. 1 2
The Data Protection Officer
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". 1 2
The Skeptic
This is where the money actually went: WMS with mobile warehouse devices and shipment tracking, 30+ marketplaces synchronised without extra licences to stop overselling, POS connections, production modules, and a named DATEV bank-reconciliation service. It stays off the 8 because shipping labels via JTL-Shipping are only 'coming soon' and supplier, dropshipping and partial-returns flows are entirely unevidenced. 1 2
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 — Export is a partial CSV; order history and customer records cannot leave intact, and hosting is the vendor's alone.
3 — CSV export of products and customers, order history partial, no self-hosting, no documented migration path.
5 — Complete export of catalogue, customers and orders via API or dump, documented deletion, and a stated data-return commitment.
8 — Full-fidelity export including media and order documents, 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
'Lokal – Auf eigenem Server' is real ownership — running the stack on my own server beats any export promise. But the evidence says nothing about export completeness, documented deletion or a migration path out; 'schrittweise Migration möglich' reads as getting data IN. Self-hosting evidenced, exit unevidenced. 1 2
The B2B Seller
A genuine 'Lokal – auf eigenem Server' option plus stepwise migration give structural rather than promised control. But the evidence is silent on export completeness, documented deletion and any data-return commitment — local hosting only counts as ownership if the catalogue, customers and order history can leave intact. 1 2
The Developer
'Lokal – Auf eigenem Server' is the one structural ownership fact, and it matters — self-hosting beats a promised export. But the evidence says nothing about export completeness, database access, or a documented path out; the only 'Migration' mention is about migrating INTO the platform, not leaving it, and the beta paid REST API is a poor extraction route. 1 2
The Operations Lead
"Lokal – Auf eigenem Server" is genuine structural control and better than any export promise, but that is the only ownership fact on the evidence — no export completeness, no documented deletion, no exit path (the only migration fact points inbound). Self-hosting earns it above the bottom anchors; silence on everything else holds it under the middle. 1 2
The Data Protection Officer
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. 1 2
The Skeptic
'Lokal – Auf eigenem Server' is genuine hosting choice and the only exit-relevant fact in the evidence; export of catalogue, customers or order history, deletion and any data-return commitment are documented nowhere, and 'schrittweise Migration möglich' reads as a path in, never a path out. Ownership is hinted at, not evidenced. 1 2
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.
0 — Non-EU vendor and contracting entity, hosting unstated or non-EU, subprocessors unnamed.
3 — EU hosting offered as an option while the contracting entity is non-EU, or the subprocessor list is absent.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — CDN, analytics, payment routing, support tooling — are non-EU without an explained safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, complete subprocessor list published, 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 imprint shows a German GmbH, Amtsgericht Mönchengladbach, a German VAT ID and a named DPO via Proliance GmbH — vendor and contracting entity are clearly European. But the sovereignty pipeline could not confirm data residency or ownership, no subprocessor list appears anywhere, and the privacy policy discloses group-wide data sharing across the JTL-Group; the chain is German at the front and undocumented behind it. 3 4
The B2B Seller
The imprint is unambiguous — JTL-Software-GmbH, Hückelhoven, Amtsgericht Mönchengladbach, DE VAT ID — so despite the pipeline marking jurisdiction unknown, the contracting entity is plainly German. But data residency is unstated and no subprocessor list exists anywhere in the evidence, so I cannot verify who sits in the checkout path even though a local hosting option exists. 3 4 2
The Developer
The pipeline scored this 0 on unknowns, but the imprint is unambiguous: JTL-Software-GmbH, Amtsgericht Mönchengladbach HRB 12450, German VAT ID, German address, external DPO appointed — a German contracting entity, not a non-EU vendor. It stalls at 4 because data residency and the subprocessor list are absent even though named partners (Dealavo, JERA, GREYHOUND) sit inside the product chain; the local hosting option is a partial mitigation but not evidence of a named, European chain. 3 4 2
The Operations Lead
The imprint shows a German GmbH with a German register court and VAT ID, and a local self-hosted option exists — so this is not a non-EU vendor despite the pipeline's unknowns. But the subprocessor list is absent, hosting infrastructure is unnamed, data residency is unstated and no certification is published, which lands it on the anchor where the missing subprocessor list sits. 3 2
The Data Protection Officer
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. 3 1
The Skeptic
The imprint pins a German GmbH to Amtsgericht Mönchengladbach with a German VAT-ID, but data residency is unstated, no subprocessor list exists in the evidence, and third parties like Dealavo, JERA and GREYHOUND are wired into pricing, finance and service functions with no word on where they process. Group-wide data sharing across the JTL-Group companies adds another unexamined hop — EU vendor, unknown chain. 3 4 2
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 monthly headline exists, but transaction fees, mandatory apps or hosting costs are unstated — the invoice is unknowable from the page.
5 — Tier prices public with billing period stated and transaction fees given, but at least one commonly needed piece (a required app, hosting, payment gateway rate) is unpriced.
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
Real, computable numbers: Advanced at 99 EUR/month, orders from your own shop and POS free, extra-order packages at 0.11–0.22 EUR, and the API, Workbench, production modules and Wawi Cloud all priced. But Enterprise is 'Auf Anfrage', the Start and Pro headline prices are absent from the evidence, payment gateway rates are unstated and neither VAT treatment nor minimum term is stated — most of the invoice is computable, with a sales conversation hiding at the top. 2
The B2B Seller
The metering is unusually public: per-order prices tiered at 0.22/0.16/0.11 €, order packages, and priced add-ons like the REST API, Workbench and production modules. But the Start and Pro tier prices are missing from the captured evidence, Enterprise is 'Auf Anfrage', payment-gateway rates are unpriced, and neither VAT treatment nor minimum term is stated — the invoice is close to computable, not computable. 2
The Developer
Genuinely better than the category norm: order-limit overages are priced per tier (0,22/0,16/0,11 € per extra order), order packages, module add-ons like the REST API and production modules, the annual discount and Wawi Cloud pricing are all public. It cannot reach 8 because Enterprise is 'Auf Anfrage' — a sales conversation — payment transaction rates, VAT treatment and minimum terms are not stated, and only the Advanced tier's headline price appears in the captured evidence. 2
The Operations Lead
Order metering is unusually computable: per-order packages priced per tier (0,22 €/0,16 €/0,11 €), orders from your own shop and POS free, modules like Workbench and the REST API openly priced. But Enterprise is "Auf Anfrage", payment transaction rates are nowhere, and VAT treatment and minimum term are unstated — the top tier and the payment fee are both sales conversations. 2
The Data Protection Officer
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. 2
The Skeptic
Credit where due: the order metering is published (ab 0,11–0,22 € je Auftrag in packages of 100 to 10,000), add-ons are priced (Wawi Cloud ab 49,99 €, Workbench 125 €/user, REST-API ab 99 €) and up to 17 % annual discount is stated. But the Start and Pro tier prices never appear, Enterprise is 'Auf Anfrage', and VAT treatment, minimum term and payment-gateway rates are silent — the invoice is half-computable, and the half missing is the expensive half. 2
European sovereignty — proven facts
1 of 4 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 | 3/3 pts | 3 Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
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.
- 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.
- 47 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
- 47 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
- 8 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
- 6 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
- 4 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
- 3 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
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. 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 15 Sep 2026 +2 earlier captures: 11 Sep 2026, 31 Aug 2026 Details →
- 2 Pricing www.jtl-software.de Checked 15 Sep 2026 +2 earlier captures: 11 Sep 2026, 31 Aug 2026 Details →
- 3 Imprint www.jtl-software.de Checked 15 Sep 2026 Details →
- 4 Privacy policy www.jtl-software.de Checked 15 Sep 2026 Details →
- 5 Catalogue & checkout — found from sitemap www.jtl-software.com Checked 1 Oct 2026 Details →
- 6 Tax & German legal correctness — found from sitemap www.jtl-software.com Checked 1 Oct 2026 Details →
- 7 Tax & German legal correctness — found from sitemap www.jtl-software.com Checked 1 Oct 2026 Details →
- 8 Extensibility & developer surface — found from sitemap www.jtl-software.com Checked 1 Oct 2026 Details →
- 9 Extensibility & developer surface — found from sitemap www.jtl-software.com Checked 1 Oct 2026 Details →
- 10 Order operations & back office — found from sitemap www.jtl-software.com Checked 1 Oct 2026 Details →
- 11 Order operations & back office — found from sitemap www.jtl-software.com Checked 1 Oct 2026 Details →
- 12 Data ownership & exit — found from sitemap www.jtl-software.com Checked 1 Oct 2026 Details →