Item: Spryker Cloud Commerce OS
Rating: 10
Author: Verified User

Use Cases and Deployment Scope

We are a reseller and implement Spryker [Cloud Commerce OS]! Our experience is that with the Commerce OS, Spryker has created a unique operating system for the development of digital business models in all industries, both B2B and B2C. It enables the implementation of all conceivable customer interfaces in order to map the increasing diversity of devices within the framework of an increasingly complex customer journey and to position companies for the future. Today, the end customer decides which channels he uses to contact the company and its product range, how he prepares his purchase, and how he ultimately buys. Be it via the desktop store, blockchain and bot technology, or voice assistants such as Alexa. The modular architecture of Spryker [Cloud] Commerce OS delivers a highly productive platform with high flexibility and allows working in a try & error mode, whereby promising models can be developed and expanded based on data and customer preferences.

Pros and Cons

Modular architecture with numerous extensions
Open, scalable technical basis
Clear separation of backend, frontend and APIs
Very fast TTM
No high investments over a longer period of time, thus ROI is achieved faster

That there is also a license model for smaller companies

Return on Investment

Faster TTM, New sales channels opened up more quickly and sales increased as a result
More flexible response options to the market and end customers
New detailed KPIs can be obtained and thus more precise recommendations for action can be made

Alternatives Considered

HCL Commerce, Intershop Commerce Suite, Magento Commerce and part of Adobe Commerce Cloud

If you compare Spryker with commerce solutions on the market, you will notice that the focus is not on the front end. Spryker assumes that the store is only one of many possible channels through which customers order today and in the future. To understand the differences, one must therefore take a look at Spryker's architecture. This is divided into the Spryker [Cloud] Commerce OS (the backend with all process-related components), the front-end modules for B2C and B2B, as well as the integration modules (middleware) and interfaces (Glue API).

Support Rating

Because this reflects our years of collaboration with Spryker.

Usability

PHP-based commerce framework, thereby high availability of resources.
Independently functional components.
Modular architecture with numerous extensions.

Key Insights

Do you think Spryker Cloud Commerce OS delivers good value for the price?

Yes

Are you happy with Spryker Cloud Commerce OS's feature set?

Yes

Did Spryker Cloud Commerce OS live up to sales and marketing promises?

Yes

Did implementation of Spryker Cloud Commerce OS go as expected?

Yes

Would you buy Spryker Cloud Commerce OS again?

Yes

Likelihood to Recommend

[Spryker Cloud Commerce OS is] well suited when:
Faster TTM: I want to quickly map, test and optimize individual functions and business processes online.

Customer centric development: I know my customers' requirements and they form the basis for my online activities.

Individual business processes: My business processes are not standard, I must be able to map them digitally in order to realize my business model.

Target of at least 10 million euros in e-commerce sales: E-commerce is not a token project for me; we have a clear strategy and the goal of achieving or increasing annual sales of at least 10 million euros online.

Replacement of monolithic legacy solutions: I already use a monolithic e-commerce system that prevents us from growing due to high maintenance and slow development.

Less appropriate when: the points listed above do not apply to the company/project and the IT is seen as a loss center

Spryker from a digital partner's perspective

Software Version

Overall Satisfaction with Spryker Cloud Commerce OS