E-Commerce Platforms & Shop Systems
plentysystems
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 plentysystems AG · www.plentymarkets.com
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
PlentyONE is the cloud commerce platform of PlentyONE GmbH in Kassel, stated at more than 55,000 users. The bench scored it highest on operations, 6 to 7 — multi-warehouse stock, automated order processing, POS and order intake from 150+ marketplaces — and on extensibility, 5 to 6, for a documented REST API with per-module rights and plugin sets testable before going live. Tax and legal is the weakest area at 2 to 3: GOBD-compliant invoicing is documented, but no public information exists on VAT-ID validation, reverse charge or OSS. Sovereignty scored 3 to 4 — a German entity, VAT ID and privacy contact are shown; hosting location, ownership and subprocessors are not. Pricing transparency is the genuine split, 4 to 6, the widest spread on the bench, turning on whether four public tiers (Ab 59€ / Monat to Ab 229€ / Monat, net plus VAT, per-tier limits, a trial with no credit card) offset a bill that cannot be computed: the GMV rate above the included 10.000 Euro sits behind an uncaptured details page and Ultimate is Auf Anfrage.
Speaks for it
- Operations scored 6 to 7, backed by multi-warehouse stock, automated workflows, POS and intake from 150+ marketplaces.
- Extensibility scored 5 to 6 for a documented REST API with per-module rights, tutorials, free marketplace uploads and testable plugin sets.
- Four tiers are priced publicly from Ab 59€ / Monat to Ab 229€ / Monat, with SKU, user, warehouse and monthly-revenue limits stated.
- GOBD-compliant invoices and shipping labels, plus a manual section on procedural documentation and GDPR, evidence German compliance scaffolding.
- A free CSV export plugin and REST bulk retrieval cover product, warehouse, order and contact data.
Held against it
- Tax and legal scored 2 to 3, with no public information on VAT-ID validation, reverse charge, OSS or destination-based VAT determination.
- Hosting location, vendor ownership and the subprocessor chain are unstated, while payment methods arrive as plugins from the marketplace.
- No public information on guest checkout, bundles, tiered pricing or voucher and promotion rules, leaving catalog and checkout at 4.
- Exit rests on export alone, with no self-hosting, migration path, documented deletion or data-return commitment shown.
- The annual invoice is not computable from public pages: the GMV rate above the included 10.000 Euro is uncaptured and Ultimate is Auf Anfrage.
Best for
- You run multichannel commerce across marketplaces and warehouses and want order, stock and customer management in one system.
- You have developers who will extend the platform through the REST API, custom plugins and the marketplace.
- You sell mainly to German customers and need GOBD-compliant invoicing with invoice, direct debit, prepayment and cash on delivery.
Avoid if
- You sell cross-border and need documented VAT-ID validation, reverse charge and OSS reporting before committing.
- You want a self-hosted option or a vendor-committed migration and data-return path.
- You must compute your annual invoice from public pricing before signing.
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
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
The B2B Seller
Variants and a serious payment surface are documented — invoice and direct debit included, default payment method set per client, payment methods sortable by priority and allowed or excluded per customer class. But I sell to trade customers, and I found no public information on customer-specific price lists, tiered pricing, bundles or voucher rules, so checkout reads as configurable-yet-generic rather than trade-ready. 1 2 5 10
The Developer
Variant management is real and priced by SKU count, and the payment surface is broad — invoice, direct debit, SEPA mandate setup and a dozen marketplace payment types, configurable per client, per customer class and by checkout priority, with currencies manageable in the payment module. The captured pages show no bundles, tiered or customer-group product pricing, guest checkout or promotion and voucher rules, which caps this short of the fuller merchandising level despite the payment breadth. 2 5 6
The Operations Lead
Variants are first-class — plans are sold by product-variant count up to 25,000 — and payment is configurable in depth: invoice, direct debit and cash on delivery are documented, with payment methods allowed or excluded per customer class, discounts on payment methods via customer classes, and a default method set per webshop client. We found no public information on bundles, tiered product pricing, guest checkout or promotion and voucher rules, and those are exactly the pieces a converting German shop needs, so this sits mid-table. 2 5 6
The Data Protection Officer
Payment is the strong part: invoice, direct debit and prepayment are documented, methods arrive as plugins from the marketplace, can be permitted or discounted per customer class, and plugin sets let each webshop run its own payment line-up. We found no public information on guest checkout, bundles, tiered product pricing or promotion rules, so it sits below the fully featured level. 5 6 10 2
The Skeptic
Variant counts are priced into the plans and the payment breadth is real — invoice, direct debit, cash on delivery and prepayment alongside a dozen marketplace payment types — but every provider is installed as a plugin from the marketplace, and we found no public information on what those plugins cost or on guest checkout, bundles, tiered pricing or voucher rules. 2 5 6
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-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
The B2B Seller
GOBD-compliant invoicing, a legal-requirements section covering procedural documentation and GDPR, and VAT sliced by invoice and delivery country in analytics are the whole of what is evidenced. I found no public information on VAT-ID validation, reverse charge for B2B buyers, OSS reporting or XRechnung/ZUGFeRD e-invoicing — a trade customer cannot tell from these pages whether they would ever see net prices. 1 7 8
The Developer
Invoices and shipping labels are documented as GOBD-compliant, there is a legal-requirements section covering procedural documentation and GDPR, and the VAT reporting nets credit notes and returns and breaks down by delivery and invoice country. Beyond that I found no public information on automatic VAT determination by destination and customer type, VAT-ID validation with reverse charge, OSS reporting, e-invoicing formats, or the checkout elements German law actually imposes. 1 7 8
The Operations Lead
Invoices and shipping labels are marketed as GOBD-compliant, VAT is computed per order item, credit notes and returns deduct their VAT, and the manual carries a legal-requirements section covering procedural documentation and GDPR. We found no public information on destination-based VAT determination, VAT-ID validation with reverse charge, OSS reporting or e-invoicing, so the German tax depth rests on one compliance claim rather than documented machinery. 1 7 8
The Data Protection Officer
What is documented is GOBD-compliant invoicing, a legal-requirements section covering procedural documentation and GDPR, and a VAT analytics figure that nets credit notes and returns out of the total — reporting arithmetic, not VAT determination at the till. We found no public information on per-country VAT rates, VAT-ID validation or reverse charge, OSS thresholds, or the German checkout elements such as order-button wording and withdrawal policy. 7 8 1
The Skeptic
The German accounting scaffolding is evidenced — GOBD-compliant invoices, a procedural-documentation and GDPR section, SEPA mandate and EBICS setup — but the only VAT mechanics shown are an analytics figure computed as gross minus net per order line. We found no public information on VAT-ID validation, reverse charge, OSS tracking or the mandatory checkout elements German law imposes. 1 6 7 8
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
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
The B2B Seller
A documented REST API with rights granted separately per module, a plugin marketplace with free distribution, custom plugin development docs and plugin sets that let new versions be tested before going live add up to a real developer surface. I found no public information on a headless storefront API, theme version control or documented rate limits, which is what would carry it higher. 1 9 10
The Developer
The plugin architecture is the strongest part of this platform: plugin sets let me group extensions, run different layouts and payment types per shop, and test new plugin versions before going live even with a single sales channel, and custom plugin development, a documented REST API with rights granted per module and sub-module, tutorials and free marketplace upload are all public. I found no public information on local development, version control for themes, a storefront API for headless builds, a dependency model between plugins, or documented rate limits — exactly what I would need to own the platform rather than rent it, and a closed template editor would read to me as a future migration. 9 10
The Operations Lead
The developer surface is real: a documented REST API with tutorials, bulk routes and rights granted per module, plugin sets that can be staged before going live, free uploads to plentyMarketplace, and custom plugin development on a dedicated developers site. We found no public information on webhooks for order events, a headless storefront API, local development or documented rate limits, which keeps this in the middle band. 9 10
The Data Protection Officer
The developer surface is real: a documented REST API with rights granted separately per module, bulk routes and tutorials, free plugin uploads to the marketplace, and plugin sets that can be tested before going live even on a single channel. We found no public information on a headless storefront API, webhooks for order events or documented rate limits, which keeps it out of the upper group. 9 10
The Skeptic
A documented REST API with rights granted per module and sub-module, tutorials and bulk routes, plus a plugin marketplace open to third-party uploads free of charge and plugin sets that can be tested before going live — that is a working developer surface. We found no public information on a headless storefront API, webhooks or documented rate limits. 9 10
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
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
The B2B Seller
Back office is the strongest story here: OMS, WMS and CRM as core modules, automated order processing, multi-warehouse limits per plan with a mobile app, shipping label creation, POS, and return reasons and credit notes flowing into VAT reporting, all over an order screen with search, group functions and custom views. I found no public information on partial shipments, dropshipping or maintained interfaces to named ERP and accounting systems. 1 2 6 8 11
The Developer
Order operations look genuinely deep: multi-warehouse stock with a mobile app, automated order processing with workflow counts scaling by plan, order search with column configuration and group functions, a POS system, and plentyBI reporting that tracks return reasons, warehouses and payment types. The pages show shipping label creation but name no carriers, and I found no public information on supplier or dropshipping flows or maintained interfaces to named ERP and accounting systems. 1 2 8 11
The Operations Lead
This is the platform's spine: OMS, WMS and CRM in every core plan, one to ten warehouses with a mobile app, automated order processing with per-plan workflow counts, GOBD-compliant shipping labels and invoices, return reasons and outgoing-goods bookings as analytics dimensions, and order intake from 150+ marketplaces with POS on top. We found no public information on partial shipments, partial refunds — and December always brings partial refunds — or dropshipping flows. "External systems, seamlessly connected" is a slogan, not a named ERP interface, so the maintained accounting link I want is only hinted at. 1 2 8 11
The Data Protection Officer
Order handling shows search, configurable columns, group functions and an unpaid-amount total, backed by multi-warehouse stock up to ten warehouses with a mobile app, automated workflows, a returns-reason dimension in reporting and a POS offering. We found no public information on named carrier integrations, partial shipments, dropshipping or maintained ERP interfaces, which is where the bar sits higher. 11 1 2 8 6
The Skeptic
The back office is broad: order search, group functions and custom views, stock across up to ten warehouses with a mobile app, POS, automated order processing and 150+ marketplace channels, with returns visible as return-reason analytics and credit notes deducted from VAT totals. We found no public information on partial shipments, dropshipping or maintained interfaces to named ERP and accounting systems. 1 2 8 11
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
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
The B2B Seller
Export tooling is documented across product, warehouse and order data as CSV, with contacts and orders retrievable through the REST API and backup guidance in the manual, which covers the catalogue-customer-order spread. The platform is presented as cloud-native only, and I found no public information on documented deletion, a stated data-return commitment or a migration path out. 1 9 13 14
The Developer
Export is documented through a free elastic-export plugin writing CSV of product, warehouse and order data that can be revised and re-imported, plus REST access to pull all contact data at once, and the data documentation covers importing, exporting, backing up and monitoring events. I found no public information on full-fidelity export of media and order documents, documented deletion, a data-return commitment or a migration path — and no self-hosting option, so on a cloud-native platform leaving means a rebuild. 9 13 14
The Operations Lead
Export goes both ways and is documented: CSV export of product, warehouse and order data that can be revised and re-imported, custom data formats via FormatDesigner, and REST retrieval of all contacts at once. We found no public information on documented deletion, a stated data-return commitment or any hosting choice beyond the vendor's cloud, so leaving means CSVs and API calls rather than a migration path. 1 9 13 14
The Data Protection Officer
Export is genuinely documented: CSV of product, warehouse and order data that can be revised and re-imported, custom data formats via a designer plugin, and REST access to all contacts and orders in bulk, with documentation on cleansing and backups. But we found no public information on a documented deletion procedure, a stated data-return commitment or self-hosting, and the platform is cloud-native on the vendor's own stack, so an exit rests on export alone. 13 14 9
The Skeptic
Export comes in two shapes — a free CSV plugin covering product, warehouse and order data, and REST retrieval of contacts and orders — but hosting is the vendor's cloud and we found no public information on self-hosting, a documented migration path, deletion or a data-return commitment. Data syncs are metered per plan at 5,000 to 50,000 per day, the same quota a full migration export would draw on. 1 2 9 13 14
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
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
The B2B Seller
The contracting entity is clearly European — PlentyONE GmbH in Kassel with a German VAT number, and a published data protection contact. Beyond that the evidence ends: I found no public information on where customer and order data are hosted, and no published subprocessor list, so who sits in the checkout chain cannot be assessed. 1 3 4
The Developer
The contracting entity is clearly European — PlentyONE GmbH in Kassel with a German VAT number and named officers — and the privacy statement is downloadable with a German data-protection contact. But I found no public information on where the cloud hosting actually runs, on data residency, or on which subprocessors sit in the checkout path, which for a shop whose payment flow runs through third-party plugins is the unanswered question. 3 4
The Operations Lead
The contracting side is clean: PlentyONE GmbH with a Kassel address, German VAT ID, named officers, a German privacy contact, and an audit-ready EU-compliant pitch. We found no public information on where customer and order data are hosted, on the ownership behind the entity or on the subprocessor chain in the checkout path, so the sovereignty question is only half answered. 1 3 4
The Data Protection Officer
The contracting entity is plainly European — a German company in Kassel with a German-language privacy contact and a downloadable data protection statement — and the pages claim audit-ready and EU-compliant without a published certificate behind it. We found no public information on where the shops are hosted, and no subprocessor list at all, which matters when payments, shipping and customer communication all arrive as third-party plugins into the checkout. 3 4 5 1
The Skeptic
The imprint pins the contracting entity in Kassel, Germany, but the platform is sold as cloud-native and we found no public information on where that cloud runs, who owns the vendor, or which subprocessors sit in a checkout whose payment methods route through marketplace plugins. A downloadable privacy statement and a data-protection contact address are the extent of what the captured pages show. 1 3 5
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
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
The B2B Seller
Four tiers are priced publicly with the billing period stated, unusually explicit per-plan limits on SKUs, users, warehouses and monthly revenue, and a plain statement that prices are net plus VAT — which, as a B2B seller, I respect. But the price rides on average monthly GMV above an included 10.000 Euro, and I found no public information on the GMV rate, transaction fees, payment plugin costs or minimum term, so the annual invoice for a given volume is not computable from the public pages alone. 1 2 14
The Developer
Four tiers are priced publicly with monthly billing stated — Lite at Ab 59€ / Monat up to Scale at Ab 229€ / Monat — net pricing plus statutory VAT is declared, and an unusual amount of limit detail is published: SKU counts, users, workflows, warehouses, marketplaces, data syncs per day and monthly revenue caps per plan. What I cannot compute from the captured pages is the cost above the included 10.000 Euro monthly revenue, since the price-calculation detail was not captured, nor typical plugin and payment-provider costs from the marketplace, and no minimum term is stated while Ultimate is on request only. 2
The Operations Lead
Four plans are publicly priced with billing period, SKU, user, warehouse and monthly revenue limits, VAT treatment stated as net plus statutory VAT, and a trial with no credit card, no subscription and no fees — more than a headline. But pricing runs on plan plus average monthly GMV with 10.000 Euro monthly revenue included at the start price, the top plan is "Auf Anfrage", and we found no public information on the price-calculation details, payment-plugin costs or minimum term, so the annual invoice for a given volume is not computable from the pages. 1 2
The Data Protection Officer
Four tiers are priced publicly with monthly billing, net-of-VAT treatment stated, per-tier caps on SKUs, users, warehouses, syncs and monthly revenue, and the model disclosed as plan plus average monthly GMV with 10,000 Euro per month included at the start. For full computability the gap is that the pricing beyond the included GMV sits behind a details page we could not see, the top tier is on request, and we found no public information on transaction fees or the cost of the payment and export plugins. 2 1
The Skeptic
Unusual openness on limits: four monthly tiers from 'Ab 59€ / Monat' to 'Ab 229€ / Monat', stated net plus VAT, with SKU, user, warehouse and monthly revenue caps all public and a trial requiring no credit card. But the invoice is still not computable — the model bills on average monthly GMV with only 10.000 Euro included and the pricing page references calculation details without giving the rate, Ultimate is 'Auf Anfrage', and we found no public information on transaction fees, payment-plugin prices or the cost of the plentyBI editions. 2 5 8
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 ⚠ 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
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 →