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

Use Cases and Deployment Scope

I work in an agency and we support Spryker projects for our customers. We are several interdisciplinary teams working with Spryker. It is possible to split into frontend / backend or developers from the customer and developer of the agency.

Pros and Cons

Good modularity, solid, clean code principles
Catalog and detail page are quick as no DB queries are necessary in the standard
Expansion is easily possible with a good plugin concept

Local development environment is sometimes difficult to understand
High entry barrier for Publish & Sync, OMS, Yves <-> Client <-> Zed
A lot of boilerplate when creating new modules

Return on Investment

Increase the shopping experience
Expand into new markets
Increase sales

Support Rating

Good community, good email contact

Usability

It's a fast shop system, but some troubleshooting is difficult.

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?

I wasn't involved with the selection/purchase process

Did implementation of Spryker Cloud Commerce OS go as expected?

Yes

Would you buy Spryker Cloud Commerce OS again?

Yes

Likelihood to Recommend

I think it is not well suited for a project with a low budget because a lot of technological knowledge is required to put the shop into production.

This is certainly well suited to implement specific features. In addition, Spryker has an API to build apps or for IOT topics.

Large, extensive shop system with many options

Software Version

Overall Satisfaction with Spryker Cloud Commerce OS