E-Commerce Platforms & Shop Systems
xt:Commerce
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by xt:Commerce GmbH · www.xt-commerce.com
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.
xt:Commerce at a glance
- Vendor
- xt:Commerce GmbH
- Headquarters
- Not stated on the vendor’s pages as of 13 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 13 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 13 Oct 2026
- Panel verdict
- The AI panel rates xt:Commerce 1/5, the mean of 6 judges. xt:Commerce, from xt:Commerce GmbH, was judged from a thin capture — a blog post on automatic plugin updates and a version announcement. how scores are made
- As of
- Vendor pages captured 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
xt:Commerce, from xt:Commerce GmbH, was judged from a thin capture — a blog post on automatic plugin updates and a version announcement. The strongest scores land on data control and exit (2 to 4) and extensibility (3 to 4): a vendor plugin marketplace updates plugins automatically from the vendor's plugin server from version 6.2.00, and the FTP-based install routine points to merchant-hosted deployment — ownership is structural, not promised, though the low mark there holds the exit path unevidenced. It is weakest at operations and catalog and checkout (both 0 to 1): we found no public information on order management, stock, returns, variants, payment methods or the checkout path. Pricing transparency also sits at 0 to 1; the captured pages carry no prices. Sovereignty scores 3 to 4 on a German GmbH and merchant-hosted deployment, while we found no public information on hosting, subprocessors or certification. Tax and legal runs 2 to 4: the lone 4 credits the vendor for shipping the statutory withdrawal button with 6.7.1; lower scores weigh VAT determination, OSS and reverse charge as unevidenced.
Speaks for it
- Vendor plugin marketplace with automatic updates from the vendor's plugin server from version 6.2.00, replacing manual FTP copies
- Statutory German checkout changes ship as vendor releases, as with the withdrawal button in xt:Commerce 6.7.1
- Deployment on the merchant's own server via the plugin workflow makes data ownership structural rather than promised
- German-language online manual, blog and forum sit behind the plugin ecosystem
- The contracting entity is a German GmbH
Held against it
- We found no public information on order management, stock, returns, shipping or ERP and accounting interfaces
- We found no public information on product variants, pricing rules, payment methods or the checkout path
- We found no public information on VAT determination, OSS, reverse charge or e-invoicing
- We found no public information on themes, storefront APIs, webhooks or a local development story beyond plugins
- We found no public information on hosting commitments, subprocessors or certification
Best for
- You want shop, customer and order data on infrastructure you control — the plugin workflow runs on the merchant's own server
- You run a German-market shop and want statutory checkout changes, like the new withdrawal button, delivered as vendor updates
- You value a maintained extension ecosystem — a vendor plugin marketplace whose plugins update automatically from version 6.2.00 onward
Avoid if
- You want the vendor to host and run the shop — the captured plugin workflow deploys to your own server via FTP
- Your team does not work in German — ask the vendor: the public pages we read do not show it
- You need published licence or transaction figures before engaging sales — the captured pages carry no prices
The scores
| Criterion | Panel median |
|---|---|
| Catalogue & checkout | 0.5 of 5 |
| Tax & German legal correctness | 1 of 5 |
| Extensibility & developer surface | 1.5 of 5 |
| Order operations & back office | 0 of 5 |
| Data ownership & exit | 2 of 5 |
| European sovereignty | 1.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 — 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
This is where I earn my money and I found no public information on the product catalogue, variants, pricing rules, or the checkout path — let alone the invoice and direct debit methods a German shopper expects or a checkout I could change without a rebuild. Nothing captured shows me a conversion machine. 1
The B2B Seller
The only checkout-relevant item in the captured material is the withdrawal button introduced with xt:Commerce 6.7.1, which tells me a checkout exists and is maintained for German law. Beyond that we found no public information on variants, tiered or customer-group pricing, bundles, payment methods or guest checkout — and nothing that shows a trade customer would ever see net prices. 1
The Developer
The captured pages say nothing about product catalogues, variants, pricing rules, checkout flows or payment methods — I found no public information on any of it, so products and the path to payment count as not evidenced for me. 1
The Operations Lead
We found no public information on variants, bundles, tiered pricing, or the checkout path and its payment methods; the only adjacent signal is a vendor plugin marketplace that could in principle carry payment plugins. From the captured pages a buyer cannot judge whether this checkout converts at all. 1
The Data Protection Officer
We found no public information on products, variants, pricing rules, payment methods or the checkout path — the captured announcement is about plugin updates and a withdrawal-button change only. With nothing evidencing any commerce capability, this sits at the bottom of the scale. 1
The Skeptic
The captured pages are a blog post about plugin updates and a version announcement; we found no public information on product variants, pricing rules, payment methods or the checkout path itself. Nothing captured lets me judge whether this storefront converts or not. 1
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
One legal fact is real: version 6.7.1 ships the new statutory withdrawal button (Widerrufsbutton), which shows the vendor moves with German law on mandatory checkout elements. Beyond that I found no public information on VAT determination by destination or customer type, OSS, reverse charge, VAT-ID validation or invoicing — the tax machinery behind my invoices is unevidenced. 1
The B2B Seller
The vendor demonstrably tracks German law — the 6.7.1 release ships the newly required withdrawal button — but that is the entire legal evidence on record. We found no public information on VAT determination by destination and customer type, VAT-ID validation with reverse charge, OSS or e-invoicing, which for my B2B buyers is the difference between a shop and a liability. 1
The Developer
The release note announcing version 6.7.1 to implement the new statutory withdrawal button is real evidence the vendor pushes updates for German checkout law, which is the direction I want to see; on VAT determination, OSS, B2B reverse charge and e-invoicing I found no public information, so this stays near the bottom. 1
The Operations Lead
One concrete, positive signal: the vendor ships a release specifically to implement the withdrawal button required by new German law, which shows checkout legal correctness being maintained in the product rather than left to the merchant. Beyond that we found no public information on VAT determination, OSS, reverse charge, or e-invoicing. 1
The Data Protection Officer
The one positive signal is vendor-maintained legal compliance: the announcement ships a statutory withdrawal button in version 6.7.1 as German law moves. We found no public information on VAT determination, OSS, B2B reverse charge, VAT-ID validation or e-invoicing, so most of what a German shop needs is unevidenced. 1
The Skeptic
One real signal: the vendor shipped a release for a statutory change to the withdrawal button in checkout, which suggests German legal changes reach merchants as updates rather than do-it-yourself fixes. Beyond that we found no public information on VAT determination, OSS, reverse charge or e-invoicing. 1
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
There is a vendor plugin marketplace, and from version 6.2.00 plugins update themselves — automatic download from the vendor's plugin server and automatic installation, replacing the old manual FTP copy to your own server. That is an app-store-grade update flow, but I found no public information on themes, a storefront or REST API, webhooks or staging environments, so I cannot call it more than a plugin system within limits. 1
The B2B Seller
There is a genuine vendor plugin marketplace with automatic updates pulled from the vendor's own plugin server from version 6.2.00 onward, replacing manual FTP copies — a real, maintained extension ecosystem. We found no public information on themes, APIs, webhooks or a headless storefront, so the developer surface rests on the marketplace alone. 1
The Developer
A vendor plugin marketplace plus automatic updates pulled from a plugin server gives a genuine ecosystem with a managed upgrade path for plugins, and an update path that keeps customisations alive is exactly what I look for; but I found no public information on themes, a template language, version control for themes, APIs, webhooks or a plugin dependency model, and the workflow these updates replace was manual FTP copying to a server, which tells me development happens on the box rather than locally. 1
The Operations Lead
A vendor plugin marketplace is evidenced, and from version 6.2.00 plugins update automatically by download from the vendor's plugin server with automatic installation, replacing manual FTP copies; an online handbook and forum sit behind it. We found no public information on themes, APIs, webhooks, or a local development story. 1
The Data Protection Officer
A vendor plugin marketplace is confirmed, with automatic plugin updates downloaded from the vendor's plugin server, plus an online manual and forum — a real but narrow ecosystem. We found no public information on themes, APIs, webhooks or headless builds. 1
The Skeptic
There is a genuine vendor plugin marketplace with automatic updates pulled from the vendor's plugin server, replacing the old copy-by-FTP ritual — real extension plumbing. We found no public information on themes, storefront APIs, webhooks or a local development story, so the developer surface beyond plugins is unshown. 1
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
I found no public information on order management, stock, returns, shipping integrations or any ERP and accounting link. For a merchant, everything after the buy button is a black box in what was captured. 1
The B2B Seller
The captured pages say nothing about what happens after checkout. We found no public information on order management, stock, returns, shipping integrations or ERP interfaces, so I have nothing concrete to point an operations buyer at. 1
The Developer
The captured pages give me nothing on order management, stock, returns, shipping or links to ERP and accounting — I found no public information on any of it and score it as not evidenced. 1
The Operations Lead
Nothing after checkout is in evidence: no order workflow, no stock a merchant could trust across channels, no partial shipments, no named carriers with label printing, no returns or partial refunds in the system, and no ERP or accounting link — we found no public information on any of it. A generic plugin marketplace is not an operations capability. 1
The Data Protection Officer
The captured pages say nothing about order management, stock, shipping, returns or ERP interfaces; we found no public information on any back-office capability. An operations story this unevidenced takes the lowest score. 1
The Skeptic
The captures stop at the checkout door: we found no public information on order management, stock, returns, shipping or ERP and accounting interfaces. The support channels listed are a manual, blog and forum, none of which evidence back-office capability. 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 — 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
The old plugin workflow — copying files via FTP onto your own server — tells me the shop runs on the merchant's infrastructure, which is the right starting point for ownership. But I found no public information on export completeness for catalogue, customers and order history, on deletion, or on a documented migration path. 1
The B2B Seller
The plugin workflow described — unpacking and copying plugins to your server via FTP — shows the shop runs on the merchant's own server, which structurally keeps catalogue, customers and order history in the merchant's hands. We found no public information on export completeness, database-level access or a documented migration path, so the exit story is implied by the hosting model rather than evidenced. 1
The Developer
The plugin instructions describe copying plugins onto the merchant's own server via FTP, which points to merchant-hosted software and ownership that is structural rather than promised; on export completeness, documented deletion or a migration path I found no public information. 1
The Operations Lead
The old plugin routine of unpacking files and copying them to the merchant's own server via FTP implies deployment on infrastructure the merchant controls, which is a structural point in the platform's favour. We found no public information on export completeness, database-level access, or a documented migration path in either direction. 1
The Data Protection Officer
The vendor's own description of the old workflow — copying plugins to your own server via FTP — indicates shops run on merchant-controlled infrastructure, which is the structural kind of ownership that matters most here. We found no public information on export completeness, on deletion executing against customer and order records, or on a documented migration path. 1
The Skeptic
The old install ritual — copying plugins onto your own server via FTP — says the shop runs on the merchant's infrastructure, which makes ownership structural rather than merely promised. But we found no public information on export completeness, documented deletion or a migration path in either direction. 1
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 contracting entity is a German GmbH, but I found no public information on where the shop and its data are hosted or which subprocessors sit in the chain, and plugin updates are pulled from the vendor's own plugin server with no stated location. An EU entity on paper with the rest of the chain unaccounted for is not a sovereign answer. 1
The B2B Seller
The vendor is a German GmbH and deployment happens on the merchant's own server, which by default puts customer and order data under the merchant's roof. But we found no public information on subprocessors in the checkout path, on certification, or on any named infrastructure behind the plugin server. 1
The Developer
The German-language announcements, manual and forum point to a German-speaking vendor, but the captured pages give no hosting location, no contracting entity and no subprocessor information — I found no public information on any of it, so I can only credit the absence of a published subprocessor list at the low end. 1
The Operations Lead
The contracting entity carries the German GmbH form and the shop appears to run on the merchant's own server, which helps, but we found no public information on hosting location, named infrastructure, any subprocessor list, or certification. 1
The Data Protection Officer
The vendor presents itself as a German company and the plugin workflow points to merchants' own servers, but we found no public information on hosting commitments, on the subprocessor list, or on where CDN, analytics and payment routing sit. For a checkout full of third parties, that silence is the deciding fact. 1
The Skeptic
The contracting entity is a German GmbH and the deployment model implied by the captured workflow is merchant-hosted, which is a decent start. The sovereignty record is otherwise empty: we found no public information on hosting, subprocessors or certification. 1
Pricing transparency
not rated — the vendor publishes no price
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
No price appears anywhere in what was captured — I found no public information on licence cost, tiers, transaction fees, hosting, term or VAT treatment. I judge spend against contribution and here I cannot even begin the arithmetic. 1
The B2B Seller
The captured material contains no prices whatsoever — no licence tiers, no plugin costs, no transaction or hosting figures. A merchant cannot compute any part of the annual cost from what is published here, so every budget is a sales conversation. 1
The Developer
The captured pages contain no figures at all — no licence tiers, no transaction fees, no plugin prices from the marketplace — so a real annual cost is not computable from what I can see, and I found no public information on pricing. 1
The Operations Lead
The only captured page is a blog announcement about plugin updates and carries no prices, fees, billing periods, or tier limits; we found no public information from which a merchant could compute a real annual cost. 1
The Data Protection Officer
We found no public information on licence, transaction, plugin or hosting costs; the captured announcement prices nothing. A merchant cannot derive any annual cost from this material. 1
The Skeptic
No headline price, no licence term, no transaction fee, no hosting line item — the captures contain nothing a merchant could build an annual invoice from. We found no public information on pricing at all, so the real cost is unknowable from what was captured. 1
Questions about xt:Commerce
Is xt:Commerce European?
Not determined: the vendor’s pages as captured do not say where xt:Commerce is based.
Where does xt:Commerce store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does xt:Commerce have a free plan?
Not stated on the vendor’s pages as of 13 Oct 2026.
What are the best alternatives to xt:Commerce?
As of 21 Oct 2026, the panel rates JTL-Shop (3/5), Medusa (3/5) and Shopify (3/5) highest among the other 25 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 JTL-Shop (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: xt:Commerce alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 13 Oct 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.
- We found no public information on compliance on the pages we read (xt-commerce.com/automatische-plugin-updates-ab-6-2-00). If the vendor publishes it somewhere else, send us the page. 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 (1)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Extensibility & developer surface — found from sitemap www.xt-commerce.com Checked 13 Oct 2026 Details →