E-Commerce Platforms & Shop Systems
Intershop Commerce Platform
Provenance unknown 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 Intershop Communications AG · www.intershop.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
Intershop Commerce Platform, sold by Intershop Communications AG, is presented as an agentic B2B commerce platform with practical AI agents. The bench's strongest scores come in operations, where judges credited named modules including Order Management, an aftersales AI assistant said to understand installed base, order history and technical specs and to recommend spare parts, and supplier synchronization for wholesalers. B2B discovery is the best-evidenced selling point — buyers can search by use case fit, compliance, technical specs or image — though catalog and checkout still scores 2-3 because the captured pages show no path to payment: we found no public information on payment methods, variants, bundles or pricing rules. Weakest are tax and legal and data control and exit: we found no public information on VAT handling or German checkout requirements, nor on data export, hosting choice or migration paths. Extensibility scores 1-2 with no public developer surface, and sovereignty rests on the named contracting entity alone, with no public information on hosting location or subprocessors in the checkout path; no prices appear on the captured pages.
Speaks for it
- B2B product discovery is well evidenced, with search by use case fit, compliance, technical specs or image.
- An aftersales AI assistant is described as drawing on installed base, order history and technical specs to recommend spare parts and next-best actions.
- Order Management is one of five named platform modules, alongside Commerce Management, Digital Experiences, Search and Recommendations and the Customer Engagement Center.
- Complex catalog management and supplier synchronization are offered for wholesalers.
- Holding companies can reportedly let subsidiaries launch their own digital sales channels managed from one central platform.
Held against it
- The checkout path is invisible on the captured pages, with no public information on payment methods, variants, bundles, pricing rules or guest checkout.
- Tax and legal scores sit at 0-1, with no public information on VAT determination, reverse charge, OSS or the checkout elements German law requires.
- Data control and exit scores sit at 0-1: we found no public information on export of catalog, customer or order history, or on any migration path.
- Extensibility scores sit at 1-2, with no public information on APIs, themes, app or plugin ecosystems or headless storefronts.
- No prices, tiers or billing terms appear on the captured pages, so an annual cost cannot be computed from public information.
Best for
- You are a wholesaler with complex catalogs and supplier-fed assortments, selling to buyers who find products by technical specification or use case.
- You run an aftersales or spare-parts business where an assistant reading installed base and order history carries real weight.
- You are a manufacturer or holding company wanting regions, subsidiaries and sales channels unified under one central platform.
Avoid if
- You need documented VAT determination, reverse charge and German checkout compliance before signing.
- You need a documented exit path and exportable catalog, customer and order history from day one.
- Your team builds and versions storefronts against a public API, themes or a headless surface.
- You must weigh checkout mechanics — payment methods, variants, customer-group pricing — from documentation alone.
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
The captured pages sell a B2B discovery story — search by use case fit, compliance, technical specs and image, plus complex catalog and supplier synchronization — but the path to payment is invisible. We found no public information on payment methods, guest checkout, vouchers or promotions with rules, per-channel pricing or checkout customisation, and I only score what I can see. 1
The B2B Seller
Discovery is well evidenced — buyers can search by use case fit, compliance, technical specs or even an image, and the platform advertises complex catalogs with supplier synchronisation. But I found no public information on the checkout path, payment methods, variants, bundles, customer-specific price lists or payment on account — exactly the mechanics a trade buyer judges a shop by. 1
The Developer
Complex B2B catalogs and search by use case fit, compliance, technical specs and even image are evidenced, and Commerce Management is a named module, but I found no public information on variants, bundles, tiered or customer-group pricing, or on the checkout flow and its payment methods. The Musgrave testimonial about out-of-the-box B2B features is the only checkout-adjacent statement on the page, and it is a customer quote rather than product documentation. 1
The Operations Lead
The vendor page names complex catalogues for wholesalers and product search by technical specs, compliance or even image, which is more than a flat product list. But we found no public information on variants, bundles, pricing rules, guest checkout, or the checkout path and its payment methods — the conversion machinery a merchant actually sells through. 1
The Data Protection Officer
The captured page shows complex B2B catalogues for wholesalers and product discovery by use case fit, compliance, technical specs and even image search, which is well beyond a flat product list. But that is where it stops: we found no public information on variants, pricing rules, bundles, guest checkout or payment methods of any kind. 1
The Skeptic
The captured page promises complex catalogs and product discovery by use case fit, technical spec or image, but the checkout itself is invisible: we found no public information on variants, bundles, pricing rules, guest checkout or payment methods. Catalog claims at marketing level with no evidenced path to payment sit near the bottom of the scale. 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
The captured material touches nothing on VAT determination by destination or customer type, OSS, reverse charge, VAT-ID validation, invoicing or the checkout legal texts German law demands — we found no public information on any of it. For a German shop this silence is the most expensive kind, so it sits at the floor. 1
The B2B Seller
I found no public information on VAT determination, VAT-ID validation, reverse charge, OSS or the mandatory checkout elements German law imposes. The compliance mention sits in a product-search context rather than tax handling, and only a generic testimonial about out-of-the-box B2B features gestures at B2B trade at all. 1
The Developer
I found no public information on VAT determination by destination or customer type, OSS handling, reverse charge, invoicing per case, XRechnung or ZUGFeRD, nor on the mandatory German checkout elements like order button wording or withdrawal policy. Nothing on the captured page lets me assess legal correctness, so I will not credit competence the vendor has not documented. 1
The Operations Lead
We found no public information on VAT determination, reverse charge, OSS, invoicing or the checkout elements German law demands. The nearest brush with compliance is that buyers can search products by compliance criteria, which says nothing about checkout or invoice correctness. 1
The Data Protection Officer
We found no public information on VAT determination, OSS, reverse charge or VAT-ID validation, gross and net display per customer group, or the mandatory German checkout elements. For a platform aimed squarely at B2B, the complete absence of any tax or legal statement on the vendor's own page is itself information. 1
The Skeptic
We found no public information on VAT determination, OSS, B2B reverse charge or the checkout elements German law requires; compliance appears only as a dimension buyers can search products by. Nothing on the captured pages evidences any tax or legal handling at all. 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
No themes, template language, app ecosystem, API, webhooks or headless storefront appear in the captured material; the only nod is a customer quote about flexibility to scale, which is not a developer surface. We found no public information on how a shop here gets built, changed or version-controlled. 1
The B2B Seller
The page names five platform modules and central management of subsidiaries' sales channels, but I found no public information on APIs, app or plugin ecosystems, theming, headless storefronts or developer documentation. A merchant cannot judge from public pages what shaping this platform to their business would actually cost in effort or lock-in. 1
The Developer
Digital Experiences is named as a module and a customer mentions flexibility to scale, but I found no public information on a template language, an app or plugin marketplace, a REST API, webhooks, a headless storefront API, staging environments or a local development story. I maintain shops for five years, and a developer surface that public pages do not show I read as a future migration, so module naming and a testimonial earn almost nothing here. 1
The Operations Lead
We found no public information on APIs, themes, an app or plugin ecosystem, headless builds, webhooks or local development. All the public page offers is a list of named modules and a customer quote about flexibility, which is not a developer surface. 1
The Data Protection Officer
Five platform modules are named and subsidiaries can reportedly launch sales channels managed from one central platform, which hints at shapeability. But we found no public information on themes, an app or plugin ecosystem, APIs, webhooks, headless storefronts or any developer surface a team could build against. 1
The Skeptic
We found no public information on APIs, themes, an app or plugin ecosystem, or headless storefront options; the only flexibility claim is a customer testimonial about out-of-the-box B2B features and scaling. A developer team cannot evaluate this platform's surface from the public pages. 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
An Order Management module is named, and an aftersales assistant that reads order history and installed base plus supplier synchronization hint at real post-checkout machinery. We found no public information on order workflow, partial shipments, stock, carriers, label printing, returns or named ERP and accounting interfaces. 1
The B2B Seller
Order Management is a named module, the aftersales assistant reads installed base and order history, and supplier synchronisation for wholesalers is offered. Beyond those module names I found no public information on partial shipments, multi-warehouse stock, returns, carrier integrations or interfaces to named ERP and accounting systems. 1
The Developer
An Order Management module is named, supplier synchronization for wholesalers is described, and the aftersales assistant is said to draw on installed base, order history and technical specs — that is genuine post-purchase capability. I found no public information on partial shipments, multi-warehouse stock, named carriers with label printing, a returns and refunds process, or maintained ERP and accounting interfaces, which keeps it short of a full back-office story. 1
The Operations Lead
Order Management is a named module, the aftersales assistant works from order history and installed base, and supplier synchronisation is mentioned for wholesalers. But we found no public information on partial shipments, stock truth across warehouses or channels, carrier integrations with label printing, returns and refunds including partials, or an ERP link the vendor maintains — I cannot run December on a module name. 1
The Data Protection Officer
An Order Management module is named, the aftersales AI is described as working from installed base and order history to recommend spare parts, and supplier synchronisation is mentioned for wholesalers. We found no public information on returns and refunds, carrier integrations, stock across warehouses, or maintained interfaces to named ERP and accounting systems. 1
The Skeptic
Order Management appears as a module name, the aftersales assistant is said to read order history and recommend spare parts, and supplier synchronization is promised for wholesalers. But we found no public information on stock management, shipping integrations, returns, or links to ERP and accounting systems. 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
We found no public information on export of catalogue, customers or order history, on hosting choice or self-hosting, or on a documented migration path in either direction. With nothing published, leaving is a negotiation rather than a right, and I score what is published. 1
The B2B Seller
I found no public information on export of catalogue, customers or order history, on hosting choice or self-hosting, or on any documented migration path or data-return commitment. A buyer has nothing to price an exit against, which for a platform pitched at holding companies running subsidiaries centrally is a real exposure. 1
The Developer
I found no public information on export of catalogue, customers and orders, database-level access, self-hosting, or a documented migration path in either direction. Five years of order history staying mine has to be evidenced in public documentation before I trust it, and the captured page gives me nothing on any of it. 1
The Operations Lead
We found no public information on export of catalogue, customers or order history, on hosting choice, or on a documented migration path in either direction. Nothing published addresses what leaving the platform would cost, so exit is unknowable from public information. 1
The Data Protection Officer
We found no public information on export of catalogue, customers or order history, on how deletion would execute against those order histories, on hosting choice, or on any migration path in either direction. For a platform that markets itself on understanding installed base and buying history, none of the ownership questions I ask first is answered in public. 1
The Skeptic
We found no public information on data export, deletion, hosting choice or a documented migration path; the captured pages say nothing about what a merchant keeps if they leave. As far as public evidence goes, the cost of exit cannot even be framed, let alone computed. 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 only datum on record is the contracting entity Intershop Communications AG, a European corporate form, and no sovereignty attributes are on record beyond that. We found no public information on hosting location or infrastructure, the subprocessor chain in the checkout path, or any certification — half a footprint is not a chain a merchant can audit. 1
The B2B Seller
The only firm fact is the legal entity's name, Intershop Communications AG; I found no public information on its jurisdiction, on hosting location or infrastructure, or on any subprocessor list for the checkout path. The sovereignty record for this product is empty, so no buyer can place where customer and order data sit. 1
The Developer
The contracting entity is named — Intershop Communications AG, a European corporate form — but the captured pages state no hosting location, publish no subprocessor list and show no certification, and the independently sourced sovereignty record is empty. A named European entity with nothing evidenced behind the rest of the chain puts this partway up from the bottom. 1
The Operations Lead
The only fact on record is the contracting entity's name, Intershop Communications AG, a European corporate form, taken from the copyright line. We found no public information on where customer and order data are hosted, on subprocessors in the checkout path, or on certifications, and no sovereignty details were independently on record — hosting is not even offered as a stated option in the public material. 1
The Data Protection Officer
The contracting entity is at least named — Intershop Communications AG — but no sovereignty attributes are on record. We found no public information on where hosting sits, where the CDN and analytics sit, or which subprocessors stand in the checkout path, and no published subprocessor list, which is the first document I request when a checkout is full of third parties. 1
The Skeptic
The only sovereignty-relevant fact is the copyright line naming Intershop Communications AG as the vendor entity, which reads as European. We found no public information on hosting location or on any subprocessor in the checkout path, which leaves an EU-named contracting entity with the rest of the chain unstated. 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
The captured pages show no prices, tiers, billing periods, transaction or revenue-share fees, order limits or VAT treatment; the cost story is left to a sales conversation. We found no public pricing information at all, so an annual cost cannot be computed from these pages — the headline price category's worst case. 1
The B2B Seller
I found no public information on licence prices, tiers, billing periods, transaction fees, hosting or app costs — the page carries module names, value propositions and a testimonial only. Every tier sits behind a sales conversation, so a merchant cannot compute any annual cost from the published pages. 1
The Developer
No price, tier, billing period, transaction fee, revenue share or minimum term appears on the captured page, so a real annual cost is not computable from public information. Every commercial question on this platform starts as a sales conversation, which is exactly the situation a merchant cannot budget from. 1
The Operations Lead
We found no prices of any kind on the public page — no tiers, no transaction fees, no module or hosting costs, and no terms. A merchant cannot compute even a rough annual cost from published information; every commercial question is a sales conversation. 1
The Data Protection Officer
No prices of any kind appear on the captured material: we found no public information on licence tiers, transaction or revenue-share fees, order limits, implementation or hosting costs. An annual cost is not computable from public pages, and this is the category where that gap costs buyers most. 1
The Skeptic
The captured page shows no prices at all: no tiers, no transaction or revenue-share fees, no billing period, no hosting or extension costs. Everything is a sales conversation, so a merchant cannot begin to compute an annual cost from public information. 1
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 | 2 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 29 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.
- We could not confirm any compliance information on the vendor’s own pages as captured, so this page shows none rather than a statement we cannot stand behind. 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
- 7 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
- 6 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 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
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. 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 (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.intershop.com Checked 29 Sep 2026 Details →
- 2 Legal notice — found from the homepage www.intershop.com Checked 30 Sep 2026 Details →
- 3 Privacy policy — found from the homepage www.intershop.com Checked 30 Sep 2026 Details →
- 4 Catalogue & checkout — found from sitemap www.intershop.com Checked 1 Oct 2026 Details →
- 5 Catalogue & checkout — found from sitemap www.intershop.com Checked 1 Oct 2026 Details →
- 6 Tax & German legal correctness — found from sitemap www.intershop.com Checked 1 Oct 2026 Details →
- 7 Tax & German legal correctness — found from sitemap www.intershop.com Checked 1 Oct 2026 Details →
- 8 Extensibility & developer surface — found from sitemap www.intershop.com Checked 1 Oct 2026 Details →
- 9 Extensibility & developer surface — found from sitemap www.intershop.com Checked 1 Oct 2026 Details →
- 10 Order operations & back office — found from sitemap www.intershop.com Checked 1 Oct 2026 Details →
- 11 Order operations & back office — found from sitemap www.intershop.com Checked 1 Oct 2026 Details →
- 12 Data ownership & exit — found from sitemap www.intershop.com Checked 1 Oct 2026 Details →
- 13 Data ownership & exit — found from sitemap www.intershop.com Checked 1 Oct 2026 Details →