E-Commerce Platforms & Shop Systems
Spryker 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 Spryker Systems GmbH · spryker.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.
No written verdict for this product
The panel scored Spryker 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
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 page markets B2B, B2C and marketplace business models on one platform, but we found no public information on variants, bundles, guest checkout, promotions with rules, or the payment methods a German shop needs — invoice and direct debit included. That is the whole conversion story for me, and none of it is on the page. 1
The B2B Seller
The captured page shows a portfolio spanning B2B commerce, B2C commerce and an enterprise marketplace, with self-service portals and multiple business models on a single platform. Beyond that positioning, we found no public information on variants, bundles, tiered or customer-specific price lists, guest checkout, or the payment methods a trade customer needs — the path to payment is never shown. 1
The Developer
The portfolio positions marketplace, B2B and B2C commerce with customer stories spanning fourteen markets, but that is positioning; I found no public information on variants, pricing rules, bundles, the checkout flow or the payment methods behind it. 1
The Operations Lead
The captured page names B2B Commerce, B2C Commerce and Enterprise Marketplace as offerings, but we found no public information on variants, pricing rules, payment methods or the checkout path itself. A catalogue I cannot see and a checkout I cannot walk is a conversion story told in logos. 1
The Data Protection Officer
The captured pages market B2B, B2C and enterprise marketplace business models on a single platform, but we found no public information on product variants, pricing rules, the checkout path or any payment method, let alone invoice or direct debit for a German shop. 1
The Skeptic
The homepage sells B2B, B2C and Enterprise Marketplace editions alongside customer stories about fourteen-market expansion, but we found no public information on variants, bundles, pricing rules, guest checkout or payment methods — the conversion machinery itself stays undocumented on the captured page. 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
We found no public information on VAT determination by destination or customer type, OSS handling, reverse charge, XRechnung or ZUGFeRD, or the checkout texts German law imposes. For a German-form merchant platform to publish nothing on legal conformity is itself information. 1
The B2B Seller
The vendor positions itself squarely at B2B, yet on the tax and legal questions that decide a trade relationship we found no public information on VAT determination by destination, VAT-ID validation with reverse charge, net price display for business customers, OSS, or the mandatory German checkout texts. A shop that shows a trade customer nothing about net-price handling has, on this evidence, never met one. 1
The Developer
The German contracting entity and multi-market B2B stories hint at German-market intent, but I found no public information on VAT determination, OSS, reverse charge, net display for B2B, or e-invoicing — and legal correctness is not something I will assume from a vendor's flag. 1
The Operations Lead
We found no public information on VAT determination, OSS, reverse charge, VAT-ID validation or the German checkout requirements on the captured page. For a vendor whose showcase customer operates across 14 markets, that silence on country-by-country tax handling is the finding. 1
The Data Protection Officer
We found no public information on VAT determination, OSS, reverse charge, VAT-ID validation or the mandatory legal texts and order-button wording a German checkout must carry; the captured material contains nothing on tax or legal correctness. 1
The Skeptic
We found no public information on VAT determination, OSS, reverse-charge handling or the checkout legal texts German law demands; the German GmbH on the copyright line is the only Germany signal on the page, and an address is not a tax feature. 1
Extensibility & developer surface
panel disagrees
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
Analyst recognition as a sample vendor in headless, composable and modular commerce, plus a composable services line in the portfolio, tells me the storefront can be shaped to the business rather than rebuilt; that matters to me because I need a checkout I can change at will. We found no public information on the app ecosystem, staging environments, or documented API rate limits. 1
The B2B Seller
Being named a sample vendor for API-based (headless), composable and modular commerce, together with a network of solution and technology partners, is a genuine signal of a buildable platform. We found no public information on API documentation, an app or plugin ecosystem, webhooks, staging environments or a local development story, so the developer surface remains assertion rather than evidence. 1
The Developer
Analyst placement in the headless, composable and modular commerce categories plus a technology partner network gives me some architectural confidence, but the captured pages document no API reference, no plugin or dependency model, no theme versioning and no local development story — the surface I would live in for five years is asserted rather than shown. 1
The Operations Lead
The headless direction is evidenced only indirectly: the vendor is named a sample vendor in Gartner categories for API-Based Digital Commerce (headless), Composable Commerce and Modular Commerce, next to a Solution and Technology Partner network. We found no public information on APIs, themes, webhooks or a local development story in this capture, so I stop at the low-middle mark. 1
The Data Protection Officer
Analyst recognition places the vendor in API-based, headless, composable and modular commerce categories, and a partner network is offered, but the captured pages show no documented API, no app or plugin ecosystem and no extension lifecycle a development team could plan around. 1
The Skeptic
The vendor points to analyst recognition in the API-based headless, composable and modular commerce categories and sells a 'Composable Value Services' line, which speaks to modular ambitions, but we found no public information on documented APIs, webhooks, themes, an app ecosystem or a local development story. 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
Customer stories evidence serious multi-market B2B operations — Optibelt across 14 markets, SWISS KRONO onboarding 300+ customers with orders every five minutes on average — but we found no public information on returns, stock across warehouses, carrier label printing, or maintained interfaces to ERP and accounting systems. 1
The B2B Seller
Business intelligence sits in the portfolio and the customer stories speak of B2B workflows, self-service portals and orders arriving every few minutes, so orders clearly flow somewhere. We found no public information on order workflow, multi-warehouse stock, carrier integrations and label printing, returns, or maintained interfaces to ERP and accounting — the back office stays unshown on the captured pages. 1
The Developer
A Business Intelligence line in the portfolio and B2B workflow references in the customer stories gesture at back-office depth, but I found no public information on order workflow, stock, returns, shipping integrations or ERP and accounting interfaces. 1
The Operations Lead
The customer stories show real throughput — SWISS KRONO's customer portal takes an order every five minutes on average in one market, and Optibelt runs B2B workflows across 14 markets — but we found no public information on stock accuracy across channels, partial shipments and refunds, carrier integrations with label printing, returns or ERP interfaces. As the one who ships December, I will not credit a back office I cannot see beyond the order volume it demonstrably handles. 1
The Data Protection Officer
Customer stories describe B2B workflows across fourteen markets and a portal taking orders every five minutes on average, but we found no public information on order management, stock, returns, shipping integrations or interfaces to named ERP or accounting systems. 1
The Skeptic
Customer stories mention B2B workflows and one portal taking orders every five minutes, yet we found no public information on order management, stock accuracy, returns, carrier integrations or maintained ERP interfaces. 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 completeness for catalogue, customers and order history, on hosting choice or self-hosting, or on any documented migration path. Nothing captured lets me price what leaving would actually cost. 1
The B2B Seller
We found no public information on export of catalogue, customers or order history, on hosting choice, on documented deletion, or on any migration path. On this evidence, leaving the platform is an unpriced and undocumented conversation. 1
The Developer
I found no public information on export completeness, hosting choice, self-hosting, source availability or any documented migration path in either direction; for a platform I intend to maintain for five years, an unevidenced exit story is itself the risk. 1
The Operations Lead
We found no public information on export of catalogue, customers or order history, on hosting choice or self-hosting, or on any documented migration path in either direction. On public evidence, leaving this platform is an undescribed event, and that is worth the bottom mark. 1
The Data Protection Officer
My first questions drew blanks: we found no public information on export completeness for catalogue, customers and order history, no documented deletion commitment, no hosting choice and no migration path in either direction. 1
The Skeptic
We found no public information on export completeness, hosting choice, self-hosting or any migration or exit commitment, so a merchant cannot begin to price what leaving with their own order history would cost. 1
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where customer and order data live, who the contracting entity is, and which subprocessors sit in the checkout path. Independently sourced by the sovereignty pipeline.
0 — Non-EU vendor and contracting entity, hosting unstated or non-EU, subprocessors unnamed.
3 — EU hosting offered as an option while the contracting entity is non-EU, or the subprocessor list is absent.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — CDN, analytics, payment routing, support tooling — are non-EU without an explained safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, complete subprocessor list published, any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor European, certification published, and a self-hosted option that puts the shop entirely under the merchant's control.
The Merchant
The contracting party is Spryker Systems GmbH, a German-formed company, which is the one European signal on the page. We found no public information on where customer and order data are hosted, on any certification, or on a subprocessor list, so I cannot say who sits in the checkout path. 1
The B2B Seller
The contracting entity is Spryker Systems GmbH, a German company, which is where a European buyer wants the contract to sit. Beyond that, no sovereignty attributes are on record: we found no public information on hosting locations, the infrastructure behind the shop, or the subprocessors sitting in the checkout path. 1
The Developer
The contracting entity is German and therefore European, which is the one confirmed fact in this area, but I found no public information on where customer and order data are hosted or which subprocessors sit in the checkout path — no sovereignty attributes are on record at all. 1
The Operations Lead
The copyright line names Spryker Systems GmbH as the contracting entity, which reads European, but no sovereignty attributes are on record and we found no public information on where customer and order data are hosted or which subprocessors sit in the checkout path. A German legal form is a start, not a chain. 1
The Data Protection Officer
The contracting entity is a German GmbH, which is a start, but nothing else follows: we found no public information on where hosting and the CDN sit, no subprocessor list, and no word on where analytics or payment routing land in the checkout path. 1
The Skeptic
The copyright line names a German GmbH as the contracting entity, but we found no public information on where customer and order data are hosted or which subprocessors sit in the checkout chain, and no independently sourced sovereignty attributes are on record. 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
We found no public information on pricing at all — no tier price, no billing period, no transaction or revenue-share rate, no order limits, no minimum term, no VAT treatment. I judge price against contribution, and this page gives me no price to judge; that is the worst case for a merchant like me. 1
The B2B Seller
The captured pages show no prices at all; we found no public information on licence tiers, transaction or revenue-share fees, order limits, minimum term or VAT treatment. A merchant cannot compute even a first estimate of annual cost from what is published, and the sales-and-partner motion points every figure towards a conversation. 1
The Developer
No price, tier, billing period, transaction fee or order limit appears anywhere in the captured pages, so an annual cost cannot be computed from public information; with a partner-led enterprise motion, every tier is a sales conversation. 1
The Operations Lead
No figure appears anywhere on the captured page — no tier price, no billing period, no transaction fee, no order or revenue limits. A sales-led motion may be normal for enterprise platforms, but from public pages alone the annual cost is unknowable, which is the lowest mark on this scale. 1
The Data Protection Officer
We found no public prices on the captured pages — no tiers, no billing period, no transaction or licence figures — so a merchant cannot compute even a rough annual cost from public information. 1
The Skeptic
The captured page shows no prices at all — no tiers, no transaction fees, no implementation, app or hosting figures — while marketing 'Lower Your IT Costs with Built-in AI Efficiencies'; the real invoice remains a sales conversation. 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 | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We found no public information on pricing on the pages we read (spryker.com, spryker.com/imprint, spryker.com/privacy-policy, docs.spryker.com/docs/product-cart-feature-integration, docs.spryker.com/docs/cms-page-search-product-lists-catalog-feature-integration, docs.spryker.com/docs/tax-feature-overview and 7 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 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 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
- 7 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
- 2 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 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 spryker.com Checked 22 Sep 2026 Details →
- 2 Imprint — found from the homepage spryker.com Checked 30 Sep 2026 Details →
- 3 Privacy policy — found from the homepage spryker.com Checked 30 Sep 2026 Details →
- 4 Catalogue & checkout — found from sitemap docs.spryker.com Checked 1 Oct 2026 Details →
- 5 Catalogue & checkout — found from sitemap docs.spryker.com Checked 1 Oct 2026 Details →
- 6 Tax & German legal correctness — found from sitemap docs.spryker.com Checked 1 Oct 2026 Details →
- 7 Tax & German legal correctness — found from sitemap docs.spryker.com Checked 1 Oct 2026 Details →
- 8 Extensibility & developer surface — found from sitemap docs.spryker.com Checked 1 Oct 2026 Details →
- 9 Extensibility & developer surface — found from sitemap docs.spryker.com Checked 1 Oct 2026 Details →
- 10 Order operations & back office — found from sitemap docs.spryker.com Checked 1 Oct 2026 Details →
- 11 Order operations & back office — found from sitemap docs.spryker.com Checked 1 Oct 2026 Details →
- 12 Data ownership & exit — found from sitemap docs.spryker.com Checked 1 Oct 2026 Details →
- 13 Data ownership & exit — found from sitemap docs.spryker.com Checked 1 Oct 2026 Details →