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

Use Cases and Deployment Scope

It's used to cover business ecommerce requirements of our customers. An additional use case is to add new custom customer features that might be missing in Spryker OS or adjust existing features to customer needs i.e. write an importer module to import them frequently to Spryker product-reviews feature. The main use case currently is to connect external systems with Spryker and provide them in a functional way to a user interface.

Pros and Cons

Very good code quality
Heavily usage of PHP feature scope
Always looking for new initiatives and to support latest platform versions
Good Support Desk - Very experienced contacts and professional tech experts
Good focus on technical solvings compared to provide marketing focused solutions

Part Confusion in Layer structure i.e. GLUE has less features than YVES and ZED is also a frontend but as well a backend API. Frontends could be leaved as frontends and backend frontends are seperate frontends
Lack of back-office / admin API i.e. to import customers, products via API
The company going in the direction to bind customers more and more with SaaS, PaaS, FaaS solutions - but leave no option for on-premise
No example integrations that clarify third partner modules provided in Spryker eco-namespace. This leaves a lot of space for issues and unexpected behaviors (additional work that needs to be done). Would be much better if a third-party integration is covered with a demo integration that can be booted to have more comprehensible estimations for the customer. Currently only ~3 demo applications with mock data. It's not a real-world scenario.

Return on Investment

Currently, we are selling our worktime to adjust Spryker to customer needs.

Alternatives Considered

We integrating different ecommerce systems for our customers, but as I hear - Spryker has the most flexibility and most professional tech stack. They have a good focus on performance.

Support Rating

The Spryker support is very good!!

Usability

Documentation and code is very good maintained - keep doing it!

Key Insights

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

Not sure

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

It forces you to build code in a maintainable and structured way. One of the key features is that it has less magic and easy-to-follow code. They started to provide a docker setup that works on all OS by abstracting their platform issues. When you start a project, there is always the possibility the customer informs itself about a specific feature i.e. Akeneo integration support or factfinder integration out of the box - but the real world always shows it's not working that way in Spryker. The integrations always have to be adjusted on the project level and are not matching all of the Spryker features they provide - this is a big issue at the moment. The good part is, the existing boilerplate applications with mocked data are very good covered with solved development issues i.e. test execution (e2e, integration, unit), development toolsets, and good example workflow pipeline (phpstan, phpcs, phpmd...), working project level and well-tested feature integrations, automated dependency updates and support for different version combinations like php7.4 + MySQL, php8+psql, etc.

Spryker OS - System Review (technical perspective)

Software Version

Overall Satisfaction with Spryker Cloud Commerce OS