Intershop Commerce Platform
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 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? →
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.
Intershop Commerce Platform at a glance
- Vendor
- Intershop Communications AG
- Headquarters
- Incorporated in Germany source, captured 2 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 2 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 2 Nov 2026
- Panel verdict
- The AI panel rates Intershop Commerce Platform 2.5/5, the mean of 6 judges. how scores are made
- As of
- Vendor pages captured 29 Sep 2026 to 2 Nov 2026; evaluated by the panel 2 Nov 2026. all sources
Intershop Commerce Platform alternatives, European ones first →
Read this page as one judge. Each weighs the same scores by what they care about.
No written verdict for this product
The panel scored Intershop Commerce Platform, but the summary our synthesizer wrote did not survive our own contradiction check — twice. Rather than print a paragraph we cannot stand behind, we print none. Every score, rationale and source below is unaffected; read them and draw the conclusion yourself.
The scores
| Criterion | Panel median |
|---|---|
| Catalogue & checkout | 3.5 of 5 |
| Tax & German legal correctness | 2 of 5 |
| Extensibility & developer surface | 2 of 5 |
| Order operations & back office | 3.5 of 5 |
| Data ownership & exit | 1.5 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 — Not a shop: no product catalogue and no checkout of its own.
3 — A product catalogue with categories and a checkout that takes payment through at least one provider.
5 — Products with variants, discounts or vouchers, guest checkout, and several payment methods including those German buyers expect (PayPal, invoice or direct debit) through named providers.
8 — Tiered and customer-group pricing, bundles or configurable products, rule-based promotions, per-channel or per-market pricing, abandoned-cart recovery, a checkout customisable without a rebuild, and 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
Customer- and country-specific price lists, taxes, time-limited offers, currency conversion and cross-sell or alternative product links are all documented in the product information pages, and the discovery pages cover configurable or bundled products and image search — serious merchandising muscle. Payment is documented as integration with various providers, with named extensions for KEKS Pay, Revolut Pay and a B2B buy-now-pay-later, but I found no public information on the methods German shoppers expect such as PayPal, invoice or direct debit, nor on guest checkout, abandoned-cart recovery or a checkout I could change without a rebuild. 4 5 10 9
The B2B Seller
Customer- and country-specific price lists, taxes, time-limited offers and currency conversions are documented, alongside AI-guided ordering for configurable, bundled or built-to-order products, payment and billing management with approval and credit workflows, and B2B buy-now-pay-later through a named provider — the trade pricing I look for first. I found no public information on guest checkout, abandoned-cart recovery, or the methods German buyers expect such as PayPal, invoice or direct debit, which keeps the documented evidence at strong B2B merchandising without the consumer-side checkout features. 4 5 10 8
The Developer
The product information management page documents customer- or country-specific price lists, taxes, time-limited offers and currency conversion, and ordering for configurable, bundled or built-to-order products is described, with payments through named providers including a B2B buy-now-pay-later. We found no public information on abandoned-cart recovery, guest checkout, or a checkout customisable without a rebuild. 4 5 10 9
The Operations Lead
The catalogue pages show customer- and country-specific price lists, taxes, time-limited offers and currency conversion, plus configurable, bundled and built-to-order products through AI-guided ordering, image search, and a B2B buy-now-pay-later partner — customer-group and per-market pricing with payment provider integrations is most of the way to the top. We found no public information on abandoned-cart recovery, vouchers or how customisable the checkout itself is, so I stop short of the top rung. 4 5 10 1 9
The Data Protection Officer
The catalogue side is well documented: customer- or country-specific price lists, taxes, time-limited offers and currency conversion, plus configurable, bundled and built-to-order products with AI-guided ordering. Payment and billing management is described with integration to various providers, and the extension pages name KEKS Pay, Revolut Pay and B2B buy-now-pay-later from UnLock. We found no mention of PayPal, invoice or direct debit routes for German buyers, nor of guest checkout or abandoned-cart recovery. 4 5 10 9
The Skeptic
The catalogue side is deep and documented: unlimited assortment with localization, syndication to marketplaces and customer groups, pricing that is customer-specific and country-specific with currency conversion, plus AI-guided ordering for configurable and bundled products and a B2B buy-now-pay-later extension. The checkout itself is where the pages go quiet — I found no public information on variants, guest checkout, abandoned-cart recovery, or German payment methods such as PayPal, invoice or direct debit; payment providers appear as named integrations (KEKS Pay, Revolut Pay) rather than a documented checkout path. Strong catalogue and pricing rules, thin checkout evidence. 4 5 9 10 1 8
Tax & German legal correctness
Show reasoningHide reasoning
How this is scored
VAT determination, OSS, B2B reverse charge, invoicing, and the checkout requirements German law imposes (Button-Lösung, Widerrufsrecht, Preisangabenverordnung) — judged on what the platform documents it does or ships as a maintained extension.
0 — No tax handling at all; prices carry no VAT logic and the merchant calculates tax outside the platform.
3 — VAT rates configurable per country or product, with prices shown gross or net and legal texts placed as pages in the checkout.
5 — VAT by destination country with gross and net display per customer group, B2B with VAT ID and reverse charge, and the German checkout requirements (order button wording, withdrawal policy, price indications) handled by the platform or a named official extension.
8 — VIES validation of VAT IDs, OSS thresholds tracked or OSS reporting data provided, invoices issued from orders with correct content 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
Tax runs through a named partner: Vertex tax solutions are offered as an Intershop extension covering VAT among other tax lines and the compliance phase of the tax lifecycle, and the pricing pages mention taxes within price lists. I found no public information on the German checkout requirements — order button wording, withdrawal policy, price indications — or on OSS, VAT ID validation, invoice content and e-invoicing formats, so a German merchant would be buying on trust there. 4 6 7
The B2B Seller
Taxes sit in the pricing options and a named Vertex extension is offered for the shop, covering value-added tax across planning, accounting, compliance and audit — more than bare rate configuration. But nothing on the captured pages shows VAT-ID validation, reverse charge, OSS, e-invoicing or the German checkout requirements, so the documented tax correctness leans on a partner's engine rather than on platform features shown to me. 4 6 7
The Developer
Tax handling is documented through a named partner, Vertex, described as available as an extension integrated into the online shop and covering value added tax among other tax lines in cloud and on-premise form, with taxes also configurable in the price lists. We found no public information on the German checkout requirements, VAT ID validation, reverse charge, OSS reporting or e-invoicing. 4 6 7
The Operations Lead
Tax determination is delegated to Vertex, a named partner available as an Intershop extension with VAT among its tax lines and compliance in its lifecycle, and the pricing configuration mentions taxes — that clears configurable rates. But we found no public information on German checkout law (order-button wording, withdrawal policy, price indications), VIES validation, OSS or e-invoicing, so the part a German lawyer would check is unproven on the captured pages. 4 6 7
The Data Protection Officer
Tax is carried by Vertex, offered as an extension on the vendor's own pages and covering VAT among income, sales and payroll taxes across the whole lifecycle including compliance and audit; product pricing settings also carry taxes. Beyond that, we found no public information on the German checkout duties — order button wording, withdrawal policy, price indications — or on VAT ID validation, reverse charge, invoicing content or e-invoicing formats. 4 6 7
The Skeptic
Tax is delegated to a named third party: Vertex Tax Solutions is offered as an Intershop extension covering VAT among other tax lines and the full tax lifecycle through compliance and audit, and the pricing page mentions taxes in price configuration. I found no public information on destination-VAT mechanics, VAT-ID validation, OSS reporting, e-invoicing (XRechnung/ZUGFeRD) or the German checkout requirements — order button wording, withdrawal policy, price indications — so the merchant buys an engine and a partner, not documented German legal correctness from the vendor. 4 6 7
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 — A closed shop builder: no themes to edit, no apps or plugins and no API.
3 — Themes adjustable in an editor and a set of apps or plugins to add features.
5 — Custom themes with a template language or code access, an app or plugin ecosystem, and a documented API with webhooks for order events.
8 — A storefront API for headless builds, an extension framework with its own lifecycle, staging or development 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 genuine extension catalogue with category filters listing named third-party applications from content management to observability, and the pages state standard APIs and a composable architecture for adding specialised apps. I found no public information on themes or template code, webhooks, a headless storefront API, staging environments or rate limits, so the developer surface beyond standard APIs is not shown. 9 8 9
The B2B Seller
A catalogue of third-party extensions filterable by category is documented, with standard APIs and a composable architecture named as the way to add specialised applications. The documentation shown to me is marketing-level: I found no public information on a storefront or headless API, webhooks, staging environments, version control for themes or rate limits. 9 8 9
The Developer
There is a real extension marketplace listing third-party applications with category filters, and the vendor points to standard APIs and a composable architecture for adding specialised applications. We found no public information on a template language or code access for custom themes, webhooks for order events, a headless storefront API, local development, or version control for themes, which is the surface I would need before committing five years of customisations. 8 9 8 9
The Operations Lead
There is a genuine extension catalogue with named third parties (dotCMS, Storyblok, New Relic, payment and BNPL providers) plus standard APIs on a composable architecture, which is more than a plain app store. We found no public information on themes or template code, webhooks for order events, a storefront API for headless builds, staging environments or rate limits, so the developer surface is asserted more than documented. 9 8 9
The Data Protection Officer
There is a real extension marketplace with category filters listing third-party applications for content management, 3D visualisation, payments and observability, and the vendor states standard APIs and a composable architecture for adding specialised applications. We found no public information on a theme or template language, a storefront API for headless builds, webhooks for order events, or documented rate limits, so the developer surface reads as a catalogue rather than a documented surface. 8 9 8 9
The Skeptic
There is a genuine extensions marketplace with named vendors — Azure, Storyblok, dotCMS, New Relic, Vertex, payment and BNPL providers — plus repeated one-line claims of standard APIs and composable architecture. Beyond that assertion, I found no public information on a storefront API for headless builds, webhooks, theme or template code access, extension lifecycle, staging environments or rate limits; the developer surface is asserted in a marketing sentence rather than documented. 8 9 8 9
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 — No order handling in the product; orders leave as emails or exports to be processed elsewhere.
3 — An order list with statuses, stock counts per product, and shipping rates set up in the shop.
5 — Order management with status emails, stock tracking, named carrier integrations or label printing, and refunds or returns handled in the system.
8 — Partial shipments and partial refunds, multi-warehouse or multi-location stock, multi-channel or marketplace order intake, fulfilment routing, dropshipping, and maintained interfaces to named ERP and accounting systems (DATEV among them for German merchants).
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
Order management is this platform's home turf: central orchestration collects orders from online shops, EDI, marketplaces and sales teams, real-time inventory spans all locations, orders are automatically split and routed by inventory, cost, delivery time or sustainability, returns are automated, and payment and billing workflows are managed in the system. A customer case cites ERP integration on a 1.3 million-product range; I found no public information on partial refunds, dropshipping or maintained interfaces to named accounting systems such as DATEV. 5 10 11
The B2B Seller
Order management is documented as a central orchestration layer capturing orders from online shops, EDI, marketplaces and sales teams, with real-time inventory across locations, automatic order splitting and routing by inventory, cost, delivery time or sustainability goals, automated returns, and payment approval and credit workflows; a customer story documents ERP synchronisation with real-time data. I found no public information on dropshipping or maintained interfaces to named ERP and accounting systems such as DATEV, so the top of the back-office scale stays out of reach on this evidence. 5 10 11
The Developer
Order management is a documented product of its own: central orchestration unifying orders from online shops, EDI, marketplaces and sales, real-time inventory across all locations, fulfilment routing by inventory, cost, delivery time or sustainability with automatic order splitting, automated returns, and ERP synchronisation shown in the customer stories. We found no public information on partial shipments and partial refunds, dropshipping, or maintained interfaces to named ERP and accounting systems such as DATEV. 5 10 11
The Operations Lead
This is where the platform earns its keep: orders arrive from shops, EDI, marketplaces and sales teams in one orchestration layer, inventory is real-time across all locations, orders are automatically split and routed by stock, cost, delivery time or sustainability, returns are automated end to end, and customer stories show ERP sync and real-time backend data. What keeps it off the top rung: we found no public information on partial refunds, on a vendor-maintained interface to a named ERP or accounting system such as DATEV, or on operational reporting — and a shop that cannot show me a partial refund is a shop that has never had December. 5 10 11
The Data Protection Officer
Order management is the centre of the product: orders arrive from online shops, EDI, marketplaces and sales teams into one orchestration layer, with real-time inventory across all locations, automatic splitting and routing by inventory, cost, delivery time or sustainability, automated returns across systems and partners, and payment and billing workflows with approvals. Customer stories back ERP-connected real-time inventory over a 1.3 million-product range; we found no mention of dropshipping, partial refunds or DATEV. 5 10 11
The Skeptic
Order management is the best-evidenced part of the platform: orders unified from shops, EDI, marketplaces and sales teams, real-time inventory across locations, automatic order splitting and routing by inventory, cost, delivery time or sustainability, automated returns across systems and partners, and payment, approval and billing workflows. The gaps matter to the invoice and the back office alike: I found no public information on partial refunds, dropshipping, or maintained interfaces to named ERP and accounting systems — ERP integration appears only inside a customer story, with no mention of DATEV. 5 10 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 — The terms state that the merchant's data cannot be exported or is not returned on cancellation.
3 — CSV export of products and customers, or of orders, from the admin.
5 — Export of catalogue, customers and orders documented (CSV, API or dump), with data deletion or return on cancellation stated in the terms or help centre.
8 — Full-fidelity export including media and order documents, a documented migration path in and out, 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 only export evidence is batch processing of product data through standard import and export formats in the product information module, and a press release describes a customer moving from an on-premises solution onto the cloud platform. I found no public information on exporting customers or order history, on what happens to data when a contract ends, or on a self-hosted option for the current platform. 4 13
The B2B Seller
Product data can be maintained in bulk through standard import and export formats, and one customer is documented moving from an on-premises Intershop solution to the cloud platform, which at least shows the platform has run on-premises. I found no public information on exporting customers or order history, or on data return and deletion when a contract ends — the exit cost stays a conversation. 4 13
The Developer
Product data moves through standard import and export formats, and a customer case documents a migration from an on-premises deployment into the cloud-based platform, which is a path in rather than out. We found no public information on export of customers and order history, data return or deletion on cancellation, or a currently offered self-hosting option. 4 13
The Operations Lead
Product data moves through batch processing in standard import and export formats, and a long-standing customer moved from an on-premises install to the cloud platform with a partner, which shows migration happens in practice. We found no public information on exporting customers and order history, on data deletion or return when the contract ends, or on self-hosting options, so what leaving actually costs is not stated anywhere I read. 4 13
The Data Protection Officer
Product data moves through standard import and export formats, ERP systems sync in real time, and one customer's move from an on-premises deployment to the cloud platform is documented — but that is a migration in, not a path out. We found no public information on export of customer records and order history, on data return or deletion when a contract ends, or on a self-hosted option offered today. 4 5 13
The Skeptic
The only export evidence is product-data batch processing supported by standard import and export formats; I found no public information on export of customers or order history, on data return or deletion on cancellation, or on a self-hosting option for the current cloud-based platform. The one migration actually documented runs in the wrong direction for an exit — a long-standing customer moving from its own on-premises installation into Intershop's Azure-based cloud. 4 13
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. Dimensions the evidence does not establish are unknown, not non-EU.
0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.
3 — One European element proven — an EU hosting option, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.
5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain (CDN, analytics, payment routing, support tooling) is unstated or partly non-EU.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessor list published with locations, 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
One European element is firmly proven: the contracting entity is a German stock corporation on Steinweg in Jena, registered at the district court in Jena with a German VAT ID, and founded in Germany in 1992. Beyond that the chain stays unstated — the platform is offered as a scalable solution on Microsoft's Azure with no region named, and I found no public information on data residency, a DPA or hosting choice for the shop itself; the published subprocessors concern the vendor's own website. 2 8 12
The B2B Seller
The contracting entity is proven European — Intershop Communications AG of Jena, registered at the district court Jena with a German VAT ID — and the platform is documented to run on Microsoft Azure, while the subprocessors named in the privacy policy cover the vendor's own website rather than the shop's checkout path. I found no public information on platform data residency, a DPA, or where the Azure processing lands; one proven European element with the rest of the chain unstated is what the evidence supports. 2 3 8
The Developer
The contracting entity is proven European: Intershop Communications AG with its seat in Jena, Germany, registered at the district court there. Hosting is documented on Microsoft's Azure cloud with no region stated, and we found no public information on platform data residency or on the locations of the payment providers that sit in the checkout path, so only one European element is established. 2 8 9
The Operations Lead
The contracting entity is provably German — an AG at Steinweg 10, Jena, registered at Jena district court with a German VAT ID — which is one solid European element. Hosting runs on Microsoft Azure with no region stated, and the subprocessors named in the privacy policy (HubSpot, Kiflo, Teams and the like) serve the vendor's own website rather than a shop's checkout path, so the rest of the chain is unstated. 2 8 12
The Data Protection Officer
The contracting entity is proven European: Intershop Communications AG, registered at the district court in Jena with a German VAT ID, founded in Germany in 1992. The privacy policy publishes named processors with locations and, for HubSpot, the EU-U.S. Data Privacy Framework as the transfer basis — though those processors serve the vendor's own website and marketing, and hosting is on Microsoft Azure with no region stated. We found no published data processing agreement for the platform, and the location of the infrastructure behind shops stays open. 2 3 8 12
The Skeptic
The contracting entity is proven European — a German AG at Steinweg 10, Jena, registered at the Jena district court with a German VAT ID — and that is where the proof stops. Hosting is described only as Microsoft's Azure cloud with no region stated, we found no public information on a platform data-processing agreement or on where shop and order data reside, and the published subprocessor list covers the vendor's own website (HubSpot, Kiflo, Personio, TalentLMS and others) rather than a merchant's checkout chain. 2 8 9 12
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 public "from" price or one priced tier.
5 — Prices for the main tiers public with the billing period stated and the main inclusions per tier listed.
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 on any page I was shown: the public path is a free online demo via a contact form, a personalized order-management demo request, a factsheet download, and named specialists to consult about extensions — every tier is a sales conversation. As a merchant I cannot compute licence, transaction fees or the cost of the extensions a shop would actually need from public pages. 5 11 1 8
The B2B Seller
The only commercial step on any captured page is a free demo or an expert consultation arranged through a contact form. I found no public information on licence tiers, prices, billing periods, transaction or revenue-share rates — a merchant cannot begin to compute an annual cost from these pages. 5 1 8
The Developer
No price appears on the captured pages; the public path to cost is a free online demo, a factsheet download and named contact persons. A merchant therefore cannot compute an annual licence, transaction or extension cost from public pages alone. 5 11 1
The Operations Lead
Across the product, order-management, extension and partner pages we read, the only pricing-related information is a free online demo arranged through a contact form. We found no public information on licence, subscription, transaction or revenue-share costs, so a merchant cannot compute the real annual cost from what is published — for a platform of this class that is a sales conversation, not a price list. 5 1
The Data Protection Officer
We found no public prices on the captured pages. What the pages offer instead is a free online demo via a contact form, a personalized order-management demo on request, and consultation with named specialists — so the real annual cost becomes visible only in a sales conversation. 5 1
The Skeptic
No price appears on any captured page: the only pricing-adjacent items are a free demo arranged through a contact form and repeated invitations to consult a specialist — even on the extensions marketplace, where the cost of a Vertex tax or CMS integration would live, the answer is "contact our specialist to discuss your wishes". We found no public information on licence tiers, transaction or revenue-share fees, term lengths or hosting costs; the real annual cost is entirely a sales conversation, which is exactly what this criterion exists to catch. 5 1 9
European sovereignty — proven facts
1 of 6 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
unverified
Why unverified?The imprint mentions a similarly named Intershop Holding AG (Switzerland) but states the company is legally independent from it, so the Swiss holding does not weaken the German registration. |
2/2 pts | 2 Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Intershop Commerce Platform
Is Intershop Commerce Platform European?
Not determined: the vendor’s pages as captured do not say where Intershop Commerce Platform is based. Its vendor, Intershop Communications AG, is incorporated in Germany, per the vendor’s page captured 2 Nov 2026.
Where does Intershop Commerce Platform store data?
Not stated on the vendor’s pages as of 2 Nov 2026.
Does Intershop Commerce Platform have a free plan?
Not stated on the vendor’s pages as of 2 Nov 2026.
What are the best alternatives to Intershop Commerce Platform?
As of 18 Nov 2026, the panel rates JTL-Shop (3.5/5), Saleor (3/5) and Shopware (3/5) highest among the other 28 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, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Intershop Commerce Platform alternatives.
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 — Legal entity. The imprint mentions a similarly named Intershop Holding AG (Switzerland) but states the company is legally independent from it, so the Swiss holding does not weaken the German registration.
- 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.
- 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
- 5 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 legal 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
- 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
- The panel’s written verdict is withheld: our own re-read found claims in it that the evidence does not carry, and a second synthesis did not fix them. The scores and the material below are unaffected. 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 2 Nov 2026 +1 earlier capture: 29 Sep 2026 Details →
- 2 Legal notice — found from the homepage www.intershop.com Checked 2 Nov 2026 Details →
- 3 Privacy policy — found from the homepage www.intershop.com Checked 2 Nov 2026 Details →
- 4 Catalogue & checkout — found from sitemap www.intershop.com Checked 2 Nov 2026 Details →
- 5 Catalogue & checkout — found from sitemap www.intershop.com Checked 2 Nov 2026 Details →
- 6 Tax & German legal correctness — found from sitemap www.intershop.com Checked 2 Nov 2026 Details →
- 7 Tax & German legal correctness — found from sitemap www.intershop.com Checked 2 Nov 2026 Details →
- 8 Extensibility & developer surface — found from sitemap www.intershop.com Checked 2 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 9 Extensibility & developer surface — found from sitemap www.intershop.com Checked 2 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 10 Order operations & back office — found from sitemap www.intershop.com Checked 2 Nov 2026 Details →
- 11 Order operations & back office — found from sitemap www.intershop.com Checked 2 Nov 2026 Details →
- 12 Data ownership & exit — found from sitemap www.intershop.com Checked 2 Nov 2026 Details →
- 13 Data ownership & exit — found from sitemap www.intershop.com Checked 2 Nov 2026 Details →