Spryker 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 Spryker Systems GmbH · spryker.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.
Spryker Commerce Platform at a glance
- Vendor
- Spryker Systems GmbH
- Headquarters
- Incorporated in Germany source, captured 30 Sep 2026
- Data hosting
- Not stated on the vendor’s pages as of 1 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 1 Oct 2026
- Panel verdict
- The AI panel rates Spryker Commerce Platform 2.5/5, the mean of 6 judges. Spryker Commerce Platform, from Spryker Systems GmbH of Berlin, scores as a developer's commerce platform, not a turnkey shop. how scores are made
- As of
- Vendor pages captured 22 Sep 2026 to 1 Oct 2026; evaluated by the panel 28 Oct 2026. all sources
Spryker Commerce Platform alternatives, European ones first →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Spryker Commerce Platform, from Spryker Systems GmbH of Berlin, scores as a developer's commerce platform, not a turnkey shop. Extensibility is strongest at 6-8, on Composer modules with version constraints, a documented REST API and plugin interfaces for data events and state-machine commands. The genuine split is catalog and checkout, 2-5: five judges score 4-5 for a documented catalogue with per-store prices in gross and net modes and customer-specific product lists, while the data protection officer scores 2, with payment providers, guest checkout, discounts and abandoned-cart handling undocumented on the captured pages. Tax and legal runs 3-4 — per-country rates and tax sets are documented, but the only automated provider documented, Avalara, is stated to be mostly meant for the USA, with no public information on VAT ID validation, reverse charge, OSS or German checkout requirements. Operations clusters at 5-6 on XML state machines and in-system returns; carrier, label and ERP links such as DATEV are undocumented. Sovereignty splits 3-4: the German entity, register court and external DPO are proven, but not hosting location or checkout-path subprocessors. No prices are published.
Speaks for it
- Extensibility scores 6-8 on Composer modules with version constraints, a REST API documented down to CORS and ETag handling, and plugin interfaces for data events and state-machine commands
- Order flows run as XML-modelled state machines with manual back-office trigger buttons, timeouts, reusable subprocesses and state history, anchoring operations scores of 5-6
- Returns are worked end to end in the system: back-office and storefront returns, printable slips, per-item state changes and displayed refund totals
- Catalogue data moves both ways as CSV — products, prices, images, stock, URLs and localized content — while orders, order items and order expenses export via a console command with date filters and multi-store support
- The vendor chain is documented: Spryker Systems GmbH at Heidestraße 9-10, 10557 Berlin, Hamburg register court HRB 134310, an external data protection officer in Hamburg, and EU Standard Contractual Clauses named for transfers outside the EEA
Held against it
- No captured page names a payment provider, payment method, guest checkout, vouchers or abandoned-cart handling, leaving the path from cart to payment unverifiable
- The only documented tax automation, Avalara, is stated to be mostly meant for the USA with many features not supported yet, and tax and legal scores run 3-4
- We found no public information on VAT ID validation, reverse charge, OSS, invoicing or German checkout requirements such as order-button wording and price indications
- Carrier integrations, shipping-label printing, order-status emails and maintained ERP and accounting interfaces such as DATEV are undocumented
- Customer data export, media and order documents at full fidelity, contractual data return on cancellation and any hosting choice are not documented, so what leaving costs is unknown
Best for
- You have a development team that wants to own the build — Composer modules, a documented REST API and plugin interfaces put extensibility at 6-8, the strongest area of this bench
- Your order flow needs modelled, manually controllable processes — XML state machines with back-office triggers, timeouts and reusable subprocesses anchor operations at 5-6
- You run multi-store catalogues with gross and net price modes and customer-specific product lists — the documentation covers these in depth
- You want a verifiably German contracting party — Berlin address, Hamburg register court, external German DPO and EU Standard Contractual Clauses named for transfers outside the EEA
Avoid if
- You need a documented path from cart to payment — ask the vendor: the public pages we read do not show it
- You sell into Germany and need VAT ID validation, reverse charge, OSS or order-button wording — the captured tax documentation stops at per-country rates, tax sets and a tax display at the final checkout step
- You depend on named carrier, shipping-label or accounting interfaces such as DATEV — the pages document returns handling but we found no public information on those links
- You must budget from published figures — the captured homepage presents portfolio names, analyst placements, customer stories and a solution-partner network rather than licence tiers, transaction fees or billing terms
The scores
| Criterion | Panel median |
|---|---|
| Catalogue & checkout | 2 of 5 |
| Tax & German legal correctness | 1.5 of 5 |
| Extensibility & developer surface | 3.5 of 5 |
| Order operations & back office | 3 of 5 |
| Data ownership & exit | 2 of 5 |
| European sovereignty | 2 of 5 |
Catalogue & checkout
panel disagrees
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
The captured documentation shows a serious catalogue: abstract and concrete products give real variants, prices carry store, currency and gross/net mode, and categories, images and localized URLs all import cleanly. But for a German consumer shop the conversion kit is undocumented — we found no public information on payment providers, invoice, PayPal or direct debit, vouchers, guest checkout or abandoned-cart recovery; the only checkout behaviour the pages describe is that the final tax value appears at the last checkout step. 13 4 5 7
The B2B Seller
The product side is real trade kit: abstract and concrete products, categories, prices held per store, currency and a gross or net mode, and catalogues restricted through product lists assigned to customers — that gross/net split is the first thing I check in a trade shop. The checkout is documented only as far as a final step where tax is calculated and an order-creation request; we found no public information on payment providers, payment methods, guest checkout or customer-specific price lists on the captured pages. 4 5 7 13
The Developer
The catalogue side is strong: abstract and concrete products, prices per store, currency and dimension in gross or net modes, product options, customer-assigned product lists and a marketplace layer with merchant assignments. The checkout evidence stops at tax display timing on the final step — we found no public information on payment providers, discounts or vouchers, or guest checkout on the captured pages, so I score the level the documentation proves. 13 4 5 7 1
The Operations Lead
Abstract and concrete products, categories, prices per store, currency and gross or net mode, product options and localized names and descriptions are all documented, and there is a working cart with images plus a checkout whose final step shows tax; the pages also show customer-specific product lists shaping what each customer sees. We found no public information on payment providers, discounts, vouchers or guest checkout, so the path to payment rests on nothing I can verify. 4 5 6 13
The Data Protection Officer
The captured pages document a real catalogue — abstract and concrete products, categories, prices per store and currency, cart images — and a checkout that shows taxes at its final step, but we found no public information on payment providers, guest checkout, discounts or abandoned-cart handling on these pages. 4 5 6 13
The Skeptic
The catalogue side is documented in depth — abstract and concrete products, categories, images, localized names, and prices per store, currency and gross or net mode — and a cart and checkout exist, with the final tax value displayed only at the last checkout step. But no captured page names a single payment provider, and guest checkout, vouchers, discounts and abandoned-cart recovery went unmentioned everywhere I read. 4 5 7 13
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 rates are definable per country and attach to products, product options and shipments via tax sets managed in the Back Office, and prices support gross and net modes — that is the level the captured pages prove. The automated tax integration on offer, Avalara, is stated to be mostly meant for the USA with many features not supported yet, and we found no public information on VAT ID validation, reverse charge, OSS, invoicing from orders, or the German checkout requirements such as order button wording, withdrawal policy and price indication rules. 6 7 13
The B2B Seller
Tax rates are configurable per country, combined into tax sets applied to abstract products, product options and shipments in the Back Office Taxes section, and prices carry a gross or net mode — sound ground-level handling, and the cart shows a tax section with the final value at checkout. We found no public information on VAT-ID validation, B2B reverse charge, OSS, invoicing or the German checkout requirements, and the one third-party tax engine documented is Avalara, which the documentation itself describes as mostly meant for the USA with many features not yet supported. 6 7 13
The Developer
Tax is a configurable engine: rates defined per country, grouped into tax sets attached to products, options and shipments, with gross/net price modes and tax shown on the cart page and at the final checkout step. We found no public information on VAT-ID reverse charge, OSS, invoicing or e-invoicing, and the only automated provider, Avalara, is documented as mostly meant for the USA with many features not supported yet. 6 7 13
The Operations Lead
VAT rates defined per country, grouped into tax sets applied to products, options and shipments, maintained in the back office or by import, with prices carried in gross and net modes and a tax section on the cart page — that is a real VAT engine. The one named tax automation, Avalara, is stated to be mostly meant for the USA with many features not yet supported. We found no public information on VAT ID validation, reverse charge, OSS, invoicing or the German checkout requirements. 6 7 13
The Data Protection Officer
Tax rates are configurable per country, tax sets attach to products, options and shipments, prices run in gross and net modes, and tax shows on the cart and at the final checkout step. We found no public information on VAT ID validation, reverse charge, OSS, invoicing or the German checkout requirements, and the one named external tax provider is stated to be meant mostly for the USA. 6 7 13
The Skeptic
Tax rates defined per country, tax sets managed in a Taxes section of the back office or by import, and gross and net price modes put this at the basic VAT-configuration level; the only automated tax engine documented is Avalara, which the documentation says "is mostly meant for the USA" and that "many Avalara features are not supported yet". I found no public information on VAT ID validation, B2B reverse charge, OSS, invoicing, or the German checkout requirements such as order-button wording and price indications. 6 7 13
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
This is a developer's platform: modules install via composer with explicit version constraints, custom plugins hook data imports and order state machines, and the Glue REST API is documented down to CORS handling and entity tags, with the marketing pages also positioning the product in headless and composable commerce categories. We found no public information on staging environments, version control for themes or documented rate limits, which is what separates a well-documented platform from one a team can fully own. 9 8 11 1
The B2B Seller
This is a platform a developer team can work with: a documented REST API with the full method set, CORS control and ETag concurrency, a Data Exchange API with custom post-event plugin interfaces, and versioned modules installed by composer alongside public GitHub repositories. We found no public information on themes or a template language, webhooks, documented rate limits or staging environments on the captured pages. 2 4 8 9
The Developer
This is the area I care most about and it holds up: a Composer-based module system with semantic version constraints and update-with-dependencies, a documented Glue REST storefront API with CORS and ETag support, and real plugin interfaces for post-import events and state-machine commands and conditions. I stop short of the top because theme version control, documented rate limits, staging environments and an upgrade path that provably keeps customisations alive are not documented, and the licensing of the core is unclear beyond a link to GitHub repositories. 9 4 5 8 11 2
The Operations Lead
The Glue API is documented down to resources, CORS handling and ETags, modules ship as versioned Composer packages, and plugin interfaces cover data exchange events, post-import hooks and state machine commands — a genuine dependency model, with GitHub repositories linked from the site. We found no public information on documented rate limits, staging environments or theme version control. A development team can build on this; the scaffolding around it is not proven. 2 4 8 9
The Data Protection Officer
There is code-level access throughout — composer packages with version constraints, plugin interfaces that run logic after data changes, and a REST storefront API with CORS and ETag handling — plus documented GitHub repositories. We found no public information on staging environments, documented rate limits or theme versioning on the captured pages. 4 8 9 11
The Skeptic
This is a developer's platform: composer modules with explicit version constraints, plugin interfaces for commands, conditions and post-import events, a documented Glue REST API with CORS and ETag handling, and order processes modeled as editable XML state machines. Webhooks for order events, staging environments, theme version control and documented rate limits went unmentioned in the captured pages, which keeps it short of the full developer-platform level. 4 8 9 11 13
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
After checkout the machine is real: order processes are modelled as state machines with manual and timed events and back-office trigger buttons, and returns are handled in the system with printed slips, per-item state changes and refund totals, with customers able to start returns on the storefront, and stock tracked per warehouse. We found no public information on named carrier integrations, shipping label printing, order status emails or maintained ERP links such as DATEV. 10 11 13
The B2B Seller
After checkout the story holds up: returns are managed in the Back Office with per-item state changes, printable return slips and refund totals shown, stock is held per warehouse, and order flows run on modelled state machines with manual Back Office triggers, timeouts, commands and reusable subprocesses. We found no public information on carrier or label integrations beyond return slips, order-status emails, or maintained interfaces to ERP and accounting systems such as DATEV — the link my German trade customers ask for first. 10 11 13
The Developer
Order operations rest on a proper order-management state machine — XML-modelled processes, manual trigger buttons on the order page, timeouts, flag queries and reusable subprocesses — with returns worked end to end including return slips, per-item state triggers and storefront customer returns, plus stock tracked per warehouse. The links outward are the weak spot: we found no named carrier or label-printing integrations beyond return slips, no named ERP or accounting interface, and no operational reporting on the captured pages. 11 10 13 8 1
The Operations Lead
The order machinery is the strongest part of the documentation: processes modelled as state machines with a manual trigger button on the back-office order page, timeouts, reusable subprocesses including a return process, and state history; returns run in the back office and on the storefront with auto-generated return slips, item-level state changes and refund totals displayed; stock is held per warehouse and order items can carry a warehouse assignment. We found no public information on carrier integrations or shipping labels, on partial shipments or partial refunds, or on maintained ERP and accounting interfaces such as DATEV. A serious order engine, but the last mile to the parcel and the books is undocumented. 6 10 11 13
The Data Protection Officer
Returns are worked inside the system — back office returns, customer self-service returns, printable return slips and per-item state triggers with refund totals — and orders run on configurable state machines with timeouts, reusable subprocesses and manual back office triggers, with stock tracked per warehouse. We found no public information on carrier integrations, status emails or maintained ERP and accounting links. 10 11 13
The Skeptic
After checkout the story is strong: order state machines with manual back-office trigger buttons, automatic on-enter and timeout events, reusable subprocesses and state history, plus Return Management with item-level state changes, printed return slips, storefront returns and refund totals, and stock tracked per warehouse. I found no public information on carrier integrations, status emails, partial shipments, or maintained ERP and accounting interfaces such as DATEV — the link a German merchant actually runs the business on. 7 10 11 13
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
Products, prices, images, stock, categories and localized content move in and out as CSV through the back office, and orders, order items and expenses export via a configurable console command with per-store and date filters — a merchant can clearly take their catalogue and order history with them. We found no public information on customer data export, full-fidelity export of order documents, or what the terms promise about returning data when a contract ends. 12 13
The B2B Seller
Leaving is at least thinkable: the Back Office exports the catalogue side as CSV — products, prices, images, URLs, categories, stock, shipment types — through a guided workflow, and a console command exports orders, order items and order expenses, with import documented for the same entities so the path runs in both directions. We found no public information on customer data export, full order documents, or any statement in the captured terms about data return when a contract ends, and no hosting choice is documented. 12 13
The Developer
The export tooling is genuine: a console-driven, YML-configured export for orders, order items and order expenses with date filters and multi-store support, and a catalogue CSV import and export covering products, prices, images, stock, URLs and localized content — effectively a documented migration in and out for catalogue data. Customer data export, media and order documents at full fidelity, a self-hosting or hosting-choice option and a contractual data-return commitment are not documented on the captured pages, so exit is enabled by tooling rather than guaranteed by structure. 12 13
The Operations Lead
Getting out is documented on the data side: a console export writes orders, order items and order expenses to CSV with date filters and multi-store support, and the back office streams catalogue exports covering products, prices, images, stock and URLs. We found no public information on a customer export, on media or order documents at full fidelity, on a documented migration path, or on data return or deletion on cancellation in the merchant terms. 12 13
The Data Protection Officer
Orders, order items and order expenses export to CSV with date filtering and multi-store support through a documented console command, and the back office exports and re-imports the catalogue. We found no public information on customer data export, contractual data return on cancellation or self-hosting, so what leaving actually costs is not documented. 12 13
The Skeptic
Export is genuinely two-sided: a guided back-office CSV import and export covering products, categories, images, prices, stock and URLs, and a console data export command for orders, order items and order expenses with date filters and multi-store selection. What I could not find is export of customer data, any statement on data return or deletion when a contract ends, or a hosting choice — so what leaving actually costs is undocumented on every page captured. 3 12 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
The captured pages prove a German contracting entity with a Berlin address, a Hamburg register court, a German VAT number and an external German data protection officer, and the privacy policy names EU Standard Contractual Clauses for transfers outside the EEA — more than one European element established. Where shop and checkout data are hosted is not stated, and the published subprocessor information gives categories such as cloud hosting and email rather than named providers with locations, with Google Workspace in use on the vendor's own side. 3 2
The B2B Seller
The contracting party is proven European: Spryker Systems GmbH at Heidestraße 9-10, Berlin, registered at the Hamburg court, with an external data protection officer in Hamburg, references to data processing agreements, and EU Standard Contractual Clauses for transfers outside the EEA; the privacy policy also names subprocessor categories with Google Workspace and LinkedIn Ireland among them. Where the shop and its order data are hosted is unstated on the captured pages, so only part of the chain is lit. 2 3
The Developer
The proven chain is German: Spryker Systems GmbH of Berlin, registered at the Hamburg court with a German VAT ID, acting as controller, an external data protection officer in Hamburg, and EU Standard Contractual Clauses named as the safeguard for transfers out of the EEA. Where the shop itself runs and which subprocessors sit in the checkout path are not established by the captured pages, so I credit one proven European element rather than a full chain. 2 3
The Operations Lead
The corporate chain is verifiably European: Spryker Systems GmbH of Berlin, registered in Hamburg, is named as the controller, with an external German data protection officer and standard contractual clauses named for transfers outside the EEA. Where shops and their customer data are hosted, and which subprocessors sit in the platform itself, are not stated on the captured pages, so only the vendor side of the chain can be scored. 2 3
The Data Protection Officer
The contracting entity is proven European — Spryker Systems GmbH in Berlin, registered in Hamburg — with an external data protection officer in Hamburg, standard contractual clauses for transfers outside the EEA, and a published set of subprocessor categories with a few named providers. Where the merchant's shop is hosted and which processors sit in the checkout path are not established on the captured pages, so the chain is only partly proven. 2 3 7
The Skeptic
The captured pages prove a German contracting entity — Spryker Systems GmbH, register court Hamburg HRB 134310, an address at Heidestraße in Berlin, VAT ID DE298024761 — with an external data protection officer in Hamburg and EU Standard Contractual Clauses named as the safeguard for transfers outside the EEA. Where a merchant's shop customer and order data are hosted, and which subprocessors sit in the checkout path, went unstated in the captured pages. 2 3
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 not rated — no public information
We found no public information on pricing — the captured homepage and imprint list the product portfolio and legal notices, but no licence tiers, revenue share, transaction fees or billing terms a merchant could use to compute an annual cost. 1 2
The B2B Seller not rated — no public information
We found no public information on pricing — no licence tiers, transaction or revenue-share rates appear on the pages I read. The captured homepage presents the platform through portfolio names, analyst placements, customer stories and a solution-partner network, which is an enterprise sales conversation rather than a price a merchant could compute an annual cost from. 1 2 3
The Developer not rated — no public information
We found no public pricing information on any page we read — the homepage, imprint and documentation carry no licence, tier or transaction-fee figures — so a merchant cannot compute an annual cost from the captured pages and I report this criterion as undocumented rather than scored. 1 2
The Operations Lead not rated — no public information
We found no public information on pricing — no tiers, licence figures, transaction fees or billing periods on any page we read, the homepage and imprint included. A merchant cannot compute an annual cost from what is published here, and this criterion is reported without counting toward my verdict. 1 2
The Data Protection Officer not rated — no public information
We found no public information on pricing — no tier prices, licence cost, billing period or transaction fees appear on the captured homepage, imprint or documentation pages. 1 2
The Skeptic not rated — no public information
We found no public information on pricing: no licence tiers, transaction or revenue-share rates, order limits, hosting costs, extension costs, minimum terms or VAT treatment appear on the homepage, imprint or privacy policy captured, and the developer documentation names paid-sounding features without prices. A merchant cannot compute an annual cost from these pages — every number here starts as a sales conversation. 1 2
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 | 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 Spryker Commerce Platform
Is Spryker Commerce Platform European?
Not determined: the vendor’s pages as captured do not say where Spryker Commerce Platform is based. Its vendor, Spryker Systems GmbH, is incorporated in Germany, per the vendor’s page captured 30 Sep 2026.
Where does Spryker Commerce Platform store data?
Not stated on the vendor’s pages as of 1 Oct 2026.
Does Spryker Commerce Platform have a free plan?
Not stated on the vendor’s pages as of 1 Oct 2026.
What are the best alternatives to Spryker 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: Spryker Commerce Platform alternatives.
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
- 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
- 6 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
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 →