# Spryker Commerce Platform — E-Commerce Platforms & Shop Systems

Spryker Commerce Platform by Spryker Systems GmbH holds a panel rating of 2.5/5 from 6 AI judges (category median 2.5/5), as of 2026-10-28. Provenance: provenance unknown; sovereignty: 1 of 6 dimensions proven.

- Vendor: Spryker Systems GmbH (https://spryker.com)
- Category: [E-Commerce Platforms & Shop Systems](https://whats-best.ai/software/e-commerce.md)
- Provenance (editorial classification): provenance unknown
- Canonical page: https://whats-best.ai/software/e-commerce/spryker-commerce-platform
- Alternatives: https://whats-best.ai/software/e-commerce/spryker-commerce-platform/alternatives ([markdown](https://whats-best.ai/software/e-commerce/spryker-commerce-platform/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-10-28 · oldest source captured 2026-09-22

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## At a glance

- Vendor: Spryker Systems GmbH
- Headquarters: Incorporated in Germany [S2]
- 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

## 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

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v2). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The Merchant | The B2B Seller | The Developer | The Operations Lead | The Data Protection Officer | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| Catalogue & checkout | 2/5 | 2/5 | 2.5/5 | 2/5 | 1/5 | 2/5 |
| Tax & German legal correctness | 1.5/5 | 2/5 | 1.5/5 | 1.5/5 | 2/5 | 1.5/5 |
| Extensibility & developer surface | 3.5/5 | 3/5 | 4/5 | 3.5/5 | 3/5 | 3/5 |
| Order operations & back office | 2.5/5 | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 |
| Data ownership & exit | 2/5 | 2/5 | 2.5/5 | 2/5 | 2/5 | 2/5 |
| European sovereignty | 2/5 | 2/5 | 1.5/5 | 2/5 | 2/5 | 1.5/5 |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **2.5/5** | **2.5/5** | **3/5** | **2.5/5** | **2/5** | **2/5** |

### The judges

- **The Merchant** (v1.0): Sells to consumers and lives on conversion. Wants a checkout that can be changed without a rebuild, the payment methods German shoppers expect including invoice, and promotions with rules. Judges price against contribution, not against a competitor's tier.
- **The B2B Seller** (v1.0): Sells to businesses across the EU: net prices, VAT-ID validation, reverse charge, customer-specific price lists and payment on account. Reads a shop that shows gross prices to a trade customer as one that has not met a trade customer.
- **The Developer** (v1.0): Will maintain this for five years. Wants local development, version control for themes, a plugin architecture with a dependency model, and upgrades that do not orphan the customisations. Reads a closed template editor as a future migration.
- **The Operations Lead** (v1.0): Ships the orders and handles the returns. Wants stock that is true across channels, partial shipments, carrier integrations with labels, and an ERP link the vendor maintains. A shop that cannot do a partial refund is a shop that has never had December.
- **The Data Protection Officer** (v1.0): The shop holds customers, addresses and buying histories, and the checkout is full of third parties. Wants the subprocessor list, consent handling that survives a complaint, deletion that executes against order history, and an answer on where the CDN and analytics sit.
- **The Skeptic** (v1.0): Knows the headline price is never the invoice here. Reads for the transaction fee, the apps that turn out to be mandatory, the hosting nobody mentioned, and what the platform charges to let a merchant leave with their own order history.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: 1 of 6 dimensions proven.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Incorporated in DE | 2/2 | [S2] |
| Hosting location | Not determined | — | — |
| Hosting options | Not determined | — | — |
| Open source | Not determined | — | — |
| Data processing agreement | Not determined | — | — |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- Data subject rights: withdraw consent · access · rectification · erasure · restriction · portability · objection [S3]
- DPA: yes [S3]
- International transfers scc: EU Standard Contractual Clauses (Art. 46 GDPR) [S3]
- VAT ID: DE298024761 [S2]

**Data**
- Automated decision making: no [S3]
- Export command: console data:export --config [S12]
- Export configuration: ./data/export/config/ · YML [S12]
- Export CSV format: CSV · orders · order items · order expenses [S12]
- Export data entities: order · order-item · order-expense [S12]
- Export date filter: yes · order_created_at · order_updated_at [S12]
- Export output path: ./data/export/ [S12]
- Export overwrite behavior: yes [S12]
- Export prerequisite: Sales Data Export feature [S12]
- Multi store export: yes [S12]
- Newsletter no third party sharing: no [S3]
- Retention principle: deleted when no longer necessary absent legal retention obligations [S3]
- Special categories: no [S3]
- Website log retention: 1 month [S3]

**Integrations**
- API alternative: Products Backend API available for programmatic product management [S13]
- Avalara checkout timing: final checkout step · checkout [S6]
- Avalara codes hidden: no [S6]
- Avalara requires avatax: AvaTax platform setup · project integration [S6]
- Avalara tax compliance: location · product type · shipping rules · Avalara · yes [S6]
- Avalara usa focus: USA [S6]
- Avalara warehouse requirement: yes [S6]
- Composer package: spryker/product-image-cart-connector · ^1.1.0 [S4]
- Data exchange prerequisites: Prerequisites are installing and configuring the Data Exchange API [S8]
- Data exchange verification flow: GET · POST [S8]
- Data import: product_abstract.csv · product_option.csv · shipment.csv · yes [S7]
- Developer resources: Documentation · GitHub Repos [S2]
- Docs archive: yes [S8]
- Etag support: yes · EntityTagFormatResponseHeadersPlugin adds ETag header; If-Match validated, invalid returns 412 [S9]
- Glue API: Tax · Product Tax Sets [S7]
- Glue API: yes · Spryker provides a Glue API that can be installed as part of Spryker Core [S9]
- Relationships include parameter: GlueApplicationConfig::isEagerRelationshipsLoadingEnabled() · include · yes [S9]
- Required modules: spryker/glue-application · spryker/entity-tags-rest-api · spryker/stores-rest-api · spryker/urls-rest-api · spryker/security-blocker-rest-api [S9]
- Rest API methods: GET · POST · PUT · DELETE · PATCH · HEAD · OPTIONS [S9]
- Rest cors support: disabled · any domain (*) · specific origin · yes · cors-allow-origin [S9]

**Legal**
- Address: Berlin · Heidestraße 9–10 · Germany · 10557 [S2]
- Address: Heidestraße 9-10, 10557 Berlin [S7]
- Content responsible: Sebastiaan Verhaar · § 18 Abs. 2 Medienstaatsvertrag [S2]
- Controller: Controller · Spryker Systems GmbH · Heidestraße 9-10, 10557 Berlin, Germany [S3]
- Copyright entity: Spryker Systems GmbH [S7]
- Copyright holder: 2026 © Spryker Systems GmbH [S2]
- Copyright jurisdiction: German copyright law applies to website contents [S2]
- Entity: Spryker Systems GmbH [S1]
- Entity name: Spryker Systems GmbH [S2]
- Register: Hamburg · HRB 134310 [S2]

**Product**
- Abstract approval statuses: draft · waiting_for_approval · approved · denied [S13]
- AI assisted tools: yes · contractual, technical and organizational safeguards and internal policies [S3]
- Analyst recognition: Gartner Visionary 2025 MQ Digital Commerce; IDC Leader 2026; Forrester Strong Performer 2024 B2B Digital Commerce Wave [S1]
- Approval feature dependency: Product Approval Process feature required by Product Experience Management [S13]
- Async processing: Import job runs processed asynchronously via import:job:run console command [S13]
- Avalara checkout timing: final checkout step [S7]
- Avalara code visibility: no [S7]
- Avalara codes import: Abstract product · Product option · Shipment [S7]
- Avalara integration: location · product type · shipping rules · Avalara [S7]
- Avalara no back office UI: no [S7]
- Avalara primary market: USA [S7]
- Avalara setup requirement: AvaTax platform setup · Avalara integration [S7]
- Avalara warehouse requirement: yes [S7]
- Business models: multiple business models on a single platform: self-service portal, marketplace, beyond-product revenue [S1]
- Cart image expansion: Product + Cart feature integration adds Product Image functionality to cart items [S4]
- Cart verification: Verification: images related to cart items visible on the Yves cart page [S4]
- Categories import: categories · yes [S13]
- Command plugin mapping: Command-to-implementation mapping via StateMachineHandlerInterface::getCommandPlugins() [S11]
- Concrete statuses: active · inactive [S13]
- Condition plugin mapping: Condition-to-implementation mapping via StateMachineHandlerInterface::getConditionPlugins() [S11]
- Constraint avalara partial support: no [S6]
- Constraint no avalara UI: no [S6]
- CSV bulk import export: Back Office users can import and export product data in bulk via guided CSV workflow [S13]
- Customer story optibelt: Optibelt: expansion across 14 markets [S1]
- Customer story swiss krono: SWISS KRONO: 300+ customers onboarded across three markets [S1]
- Data exchange post plugins: Custom post plugins can run events automatically after data is imported or changed through Data Exchange API [S8]
- Error download: yes [S13]
- Error handling: invalid rows skipped; errors recorded with CSV row number and message [S13]
- Event API trigger: Events can be triggered via API call (triggerEvent) [S11]
- Event commands: Events can have attached commands executed when fired [S11]
- Event manual back office button: Manual events render a trigger button in Back Office View Order page [S11]
- Event onenter automatic: Events fire automatically on state entry via onEnter attribute [S11]
- Event timeout trigger: Events can be triggered by timeout [S11]
- Example statemachine module: Example state machine available in Legacy Demoshop (stateMachineExample module) [S11]
- Exclude from customer flag: exclude-from-customer flag hides orders from customer Yves order details and list pages [S11]
- Export download: Exports streamed to user for download [S13]
- Feature integration: Integrates CMS, Product Lists, and Catalog features [S5]
- Final tax at checkout: checkout [S6]
- Final tax on checkout: upon checkout [S7]
- Google adwords: yes · interest-based advertising, conversion tracking [S3]
- Hype cycle: sample vendor in four categories of Gartner 2026 Hype Cycle for Digital Commerce [S1]
- Images import: product images · yes [S13]
- Import jobs: Reusable import jobs with product type and column schema [S13]
- Import steps domains: abstract product · concrete product · prices · images [S13]
- Linkedin insight tag: yes · LinkedIn Ireland Unlimited Company · yes [S3]
- Localized attributes: localized attributes · yes [S13]
- Localized content: localized names and descriptions · yes [S13]
- Manual or automated events: yes [S11]
- Merchant assignments: merchant assignments · yes [S13]
- Module installed: ProductImageCartConnector · vendor/spryker/product-image-cart-connector [S4]
- Partner network: Solution Partners and Technology Partners network [S1]
- Performance recommendation: Performance: use timeout=1 second instead of onEnter=true to move heavy work off the order-creation HTTP request [S11]
- Portfolio: B2B Commerce · AI Commerce · Enterprise Marketplace · B2C Commerce · Business Intelligence · Composable Value Services [S1]
- Portfolio modules: B2B Commerce · AI Commerce · Enterprise Marketplace · B2C Commerce · Business Intelligence · Composable Value Services [S2]
- Positioning: B2B commerce platform with built-in AI efficiencies [S1]
- Post create plugin interface: Events after data import use DynamicEntityPostCreatePluginInterface [S8]
- Post update plugin interface: Events after data updates use DynamicEntityPostUpdatePluginInterface [S8]
- Prices import: prices · yes [S13]
- Required features: Cms · 202608.0 · Product lists · 202608.0 · Catalog · 202608.0 · Customer · 202608.0 [S5]
- Required module: spryker/customer-catalog · ^1.0.0 [S5]
- Required modules: 202608.0 [S4]
- Return customer information fields: Customer reference · Name · Email [S10]
- Return general information fields: Order Reference · Return Reference · Return Date · State [S10]
- Return item state trigger: yes [S10]
- Return slip printing: yes [S10]
- Return storefront customer returns: yes [S10]
- Return total refund display: yes [S10]
- Returns back office navigation: Back Office returns managed under Sales > Returns [S10]
- Returns viewing: yes [S10]
- Reusable subprocesses: Reusable sub-processes, programmable commands and conditions [S11]
- Row type model: each CSV row is either an abstract or concrete product, never both [S13]
- Run summary: run detail page shows processed, successful and failed row counts [S13]
- Schema driven mapping: schema-driven column mapping · batch processing · per-row error reporting [S13]
- Security blocker login protection: blocks customer and agent accounts after failed login attempts, returns 429 · yes [S9]
- Shipment types import: shipment types · yes [S13]
- Sm storage location: State machine configs stored under config/Zed/StateMachine/{StateMachineName}/ [S11]
- State flags: States defined by name in XML with optional display glossary key [S11]
- State flags query: Items queryable by state flags via StateMachineFacade methods [S11]
- State machine definition: State machines define, execute and visualize predefined and automated processes, e.g. in the order process [S11]
- Statemachine module capabilities: StateMachine module provides SM graph drawing, event triggering, initialization, and state history [S11]
- Status required: yes [S13]
- Stock import: stock · yes [S13]
- Store assignments: store assignments · yes [S13]
- Storefront cart tax display: yes [S6]
- Storefront cart tax display: yes [S7]
- Stores resource: stores · yes [S9]
- Subprocess prefix: Subprocess prefixes can be defined for state/event definitions [S11]
- Subprocess reuse: Common process parts can be extracted into reusable subprocesses [S11]
- Supported data scope: abstract and concrete products · yes [S13]

**Subprocessors**
- Categories: email services · messaging and collaboration platforms · document management systems · CRM systems · cloud hosting services · video conferencing services [S3]
- Google workspace: Google Workspace · email security and phishing protection [S3]

**Support**
- Portals: Customer Success Hub · Support Portal · Partner Portal [S2]
- Support portal: Support Portal and Partner Portal offered in footer [S1]

23 more facts on the canonical page: https://whats-best.ai/software/e-commerce/spryker-commerce-platform

## Questions

### 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](https://whats-best.ai/evidence/2076).

### 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)](https://whats-best.ai/software/e-commerce/jtl-shop), [Saleor (3/5)](https://whats-best.ai/software/e-commerce/saleor) and [Shopware (3/5)](https://whats-best.ai/software/e-commerce/shopware) 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](https://whats-best.ai/software/e-commerce/jtl-shop) (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [Spryker Commerce Platform alternatives](https://whats-best.ai/software/e-commerce/spryker-commerce-platform/alternatives).

## What this page leaves out

- 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.
- 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.
- 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.
- 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.
- 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.

## Sources

- [S1] Vendor page: https://spryker.com (checked 2026-09-22)
- [S2] Imprint — found from the homepage: https://spryker.com/imprint (checked 2026-09-30)
- [S3] Privacy policy — found from the homepage: https://spryker.com/privacy-policy (checked 2026-09-30)
- [S4] Catalogue & checkout — found from sitemap: https://docs.spryker.com/docs/product-cart-feature-integration (checked 2026-10-01)
- [S5] Catalogue & checkout — found from sitemap: https://docs.spryker.com/docs/cms-page-search-product-lists-catalog-feature-integration (checked 2026-10-01)
- [S6] Tax & German legal correctness — found from sitemap: https://docs.spryker.com/docs/tax-feature-overview (checked 2026-10-01)
- [S7] Tax & German legal correctness — found from sitemap: https://docs.spryker.com/docs/international-tax-rates-sets-1 (checked 2026-10-01)
- [S8] Extensibility & developer surface — found from sitemap: https://docs.spryker.com/docs/integrations/custom-building-integrations/data-exchange/create-post-plugins-for-data-exchange-api.html (checked 2026-10-01)
- [S9] Extensibility & developer surface — found from sitemap: https://docs.spryker.com/docs/glue-api-spryker-core-feature-integration (checked 2026-10-01)
- [S10] Order operations & back office — found from sitemap: https://docs.spryker.com/docs/managing-returns (checked 2026-10-01)
- [S11] Order operations & back office — found from sitemap: https://docs.spryker.com/docs/order-process-modelling-state-machines (checked 2026-10-01)
- [S12] Data ownership & exit — found from sitemap: https://docs.spryker.com/docs/scos/dev/data-import/202212.0/data-export.html (checked 2026-10-01)
- [S13] Data ownership & exit — found from sitemap: https://docs.spryker.com/docs/pbc/all/product-experience-management/latest/back-office-product-csv-import-and-export-feature-overview.html (checked 2026-10-01)

---

Cite as: whats-best.ai, "Spryker Commerce Platform — E-Commerce Platforms & Shop Systems", AI panel analysis, as of 2026-11-21. https://whats-best.ai/software/e-commerce/spryker-commerce-platform

Corrections: https://whats-best.ai/correct/299?target=page
