E-Commerce Platforms & Shop Systems

plentysystems

EU-Made Report an error

Panel 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 plentysystems AG · www.plentymarkets.com

An AI-assisted analysis of public evidence — not a hands-on test.

Every score, rationale and verdict on this page is AI-generated. Every claim cites the source it was read from. Nothing here is a human star review — and no score can be bought. How scores are made →

Method and versions

The Merchant v1.0 · The B2B Seller v1.0 · The Developer v1.0 · The Operations Lead v1.0 · The Data Protection Officer v1.0 · The Skeptic v1.0 · rubric v1 · evaluated 5 Oct 2026

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 Merchant

Weighted verdict

Sells to consumers and lives on conversion. Wants a checkout that can be changed without a rebuild, the payment methods German shoppers expect including invoice, and promotions with rules. Judges price against contribution, not against a competitor's tier.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Merchant

Catalogue & checkout

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.

Report an error

The Merchant

Invoice, direct debit, prepayment and cash on delivery are documented payment methods, and I can set a default payment method per client, sort methods by priority, allow or exclude them per customer class and give discounts on them — the German payment breadth I sell on is genuinely there. But I found no public information on promotions or vouchers with rules, bundles, tiered pricing or guest checkout, which is what separates a shop that converts from one that is merely configurable. 5 6 10 2

Report an error

Tax & German legal correctness

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.

Report an error

The Merchant

GOBD-compliant invoicing, a documented VAT calculation per order item with credit notes and returns deducted, and a legal-requirements section covering procedural documentation show German tax machinery exists. But I found no public information on automatic destination-based VAT, VAT-ID validation with reverse charge, OSS reporting, e-invoicing formats, or the mandatory checkout legal texts German law demands. 1 7 8

Report an error

Extensibility & developer surface

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.

Report an error

The Merchant

A documented REST API with rights granted separately per module, real tutorials, a plugin marketplace where I can upload my own plugins free of charge, and plugin sets that let me stage new versions before going live — that is a shop I can change without a rebuild. I found no public information on a headless storefront API, webhooks, documented rate limits or local development support. 9 10

Report an error

Order operations & back office

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.

Report an error

The Merchant

This is an operation, not just a shop: multi-channel order intake across 150+ marketplaces, warehouse counts that scale by tier with a mobile app, no-code workflows counted per tier, POS, order group functions, and returns tracked with return reasons and VAT deduction. I found no public information on partial shipments, supplier or dropshipping flows, or maintained interfaces to named ERP and accounting systems — the payment pages cover bank setup, not accounting exports. 1 2 8 11 6

Report an error

Data ownership & exit

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.

Report an error

The Merchant

Export tooling is documented — CSV export of product, warehouse and order data that can be revised and re-imported, REST retrieval of all contacts at once, and guidance on cleansing or backing up data. I found no public information on self-hosting, a documented migration path out, or a contractual data-return commitment, so what leaving actually costs stays an open question. 13 14 9

Report an error

European sovereignty

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.

Report an error

The Merchant

A German contracting entity in Kassel with a German VAT number and a German-language privacy contact is the right starting point for a German shop. But the captured pages leave hosting location and the subprocessor list unstated — cloud-native tells me nothing about where my customers' data sits or who sits in the checkout chain. 3 4 1

Report an error

Pricing transparency

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.

Report an error

The Merchant

Tier prices, monthly billing period, net-of-VAT treatment and unusually concrete limits — SKUs, users, warehouses, data syncs per day and a revenue cap per tier — are public, and the trial needs no credit card, no subscription, no fees. But prices scale with average monthly GMV beyond an included amount, the top tier is only on request, and I found no public information on transaction or payment fees, the GMV pricing detail, minimum term or plugin costs, so the annual invoice is not computable from the page alone. 2 1 14

Report an error

European sovereignty — proven facts

1 of 4 dimensions proven

Built 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 ⚠ unverified	—	uncited Report an error

Where this could be wrong

Evidence ages. The oldest capture behind this page is from 16 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
Weak sourcing — Subprocessors. 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.

20 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
18 subprocessors 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
13 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
9 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
7 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
5 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 data 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 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
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

Do you know more about plentysystems? Tell us Report an error on this page

Sources (14)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

1 Vendor homepage www.plentymarkets.com Checked 16 Sep 2026 Details →
2 Pricing www.plentymarkets.com Checked 16 Sep 2026 Details →
3 Imprint www.plentymarkets.com Checked 16 Sep 2026 Details →
4 Privacy policy www.plentymarkets.com Checked 16 Sep 2026 Details →
5 Catalogue & checkout — found from sitemap knowledge.plentyone.com Checked 1 Oct 2026 Details →
6 Catalogue & checkout — found from sitemap knowledge.plentyone.com Checked 1 Oct 2026 Details →
7 Tax & German legal correctness — found from sitemap knowledge.plentyone.com Checked 1 Oct 2026 Details →
8 Tax & German legal correctness — found from sitemap knowledge.plentyone.com Checked 1 Oct 2026 Details →
9 Extensibility & developer surface — found from sitemap knowledge.plentyone.com Checked 1 Oct 2026 Details →
10 Extensibility & developer surface — found from sitemap knowledge.plentyone.com Checked 1 Oct 2026 Details →
11 Order operations & back office — found from sitemap knowledge.plentyone.com Checked 1 Oct 2026 Details →
12 Order operations & back office — found from sitemap knowledge.plentyone.com Checked 1 Oct 2026 Details →
13 Data ownership & exit — found from sitemap knowledge.plentyone.com Checked 1 Oct 2026 Details →
14 Data ownership & exit — found from sitemap knowledge.plentyone.com Checked 1 Oct 2026 Details →