Spryker
This page reflects our views and assessments. All information is sourced from publicly available information and does not represent the vendor’s official position.
Evaluation
⭐ Highlights
- Spryker has a very broad and deep feature set, making it ideal for sophisticated projects, such as international B2B marketplaces for spare parts.
- Spryker’s code is fully open and extendable, allowing for extensive customization.
- Spryker ships with fully-working demo shops for all kind of scenarios
- Spryker provides full hosting infrastructure on AWS.
👍 When to use
- For projects with advanced requirements, particularly in B2B and/or marketplaces.
- For companies with mature in-house IT teams that can fully utilize Spryker’s modular architecture.
👎 When to avoid
- For projects with standard requirements and low complexity, such as a basic B2C shop for shoes.
- For companies lacking or not planning to have a senior-level IT team.
Functionality
Development approach
Demo shops
Spryker is a very feature-rich system, that represents totally different use cases. For this reason, there are multiple templates (Demo Shops) available to start with:
Modularity & Flexibility
Spryker is a highly modular system that allows projects to select only the modules they need. The system's architecture can vary depending on the project's requirements (see examples below).
Developers have the option to assemble the modules themselves or start with one of the pre-built templates (as shown in the demo shops above).
Technically, this assembly is done by selecting modules through Composer (PHP’s package manager, similar to NPM for JavaScript) and provisioning applications using Docker Compose.
B2C & B2B setup
Spryker’s default architecture consists of a storefront and a backend (Gateway).
For performance and scalability reasons, the storefront does not directly access the SQL database. Instead, it retrieves all data from a key-value storage system and a search engine.
SPA Setup
Projects that prefer a single-page application (SPA) over Spryker's default PHP-rendered storefront can opt to use Spryker’s framework called Oryx, which leverages web components and the Lit framework.
In this setup, the storefront communicates with a public service called Glue, which exposes a REST API.
Marketplace
When using Spryker to implement a marketplace, you'll also utilize the Merchant Portal application. This is a user interface designed for merchants to manage their products and orders.
Back Office
Spryker includes an admin UI that can be extended at the code level to meet any requirements.
Case Studies
All information is based on public sources and manually curated. Projects that are completely hidden from the public are excluded. Contact us to contribute contact@roq.tech
| Company | Shop URL | Industry | Type |
|---|---|---|---|
| Alles Auto | https://www.alles.auto | Automotive (Used Cars) | B2CMarketplace |
| Daimler Trucks | https://partsportal.au.daimlertruck.com/ | Automotive (Spare Parts) | B2BMarketplace |
| ESA | https://www.esa.ch | Industrial Services | B2B |
| Hardeck | https://www.hardeck.de | Retail (Furniture) | B2CMarketplace |
| Hornbach | https://www.hornbach.de | Retail (DIY and Home Improvement) | B2CMarketplace |
| Jungheinrich | https://www.parts.jungheinrich.de | Industrial Equipment | B2B |
| Kömpf | https://www.koempf24.de | Retail (Building Materials) | B2CB2B |
| Louis | https://www.louis.de | Retail (Motorbike Accessories) | B2C |
| Pferd | https://de.pferd.com/en | Industrial Tools | B2B |
| Scania UK | https://buy.scania.co.uk | Automotive | B2BMarketplace |
| SDVerse | https://www.marketplace.sdverse.auto/ | Technology | B2BMarketplace |
| Siemens Healthineers | https://www.siemens-healthineers.com/de/webshop | Healthcare (Medical Tech) | B2B |
| Stauff | https://stauff.com/en/shop | Industrial (Fluid Technology) | B2B |
| ZF Friedrichshafen | https://aftermarket.zf.com | Automotive | B2B |