Item: Spryker Cloud Commerce OS
Rating: 8
Author: Moritz Jung

Use Cases and Deployment Scope

We are an integrator for Spryker Cloud Commerce OS, and work with the system for more than 2 years now, to provide our clients a solid, stable and extendable platform for their E-Business. My personal involvement is focused on transforming complex B2B-sales models into an online platform, to connect our clients with their clients.

Pros and Cons

Extendable - you can extend the core functionalities to every business need.
Scalable - the technical implementation supports a highly scalable system approach.
Adjustable - besides implementing new functionalities the core functionalities can be adjusted to the business needs.
Up-to-date - compared to other E-Business solutions, the technological foundation of Spryker is growing, with the technological development and implementations [which] are kept up-to-date with quarterly releases.

Content - content administration is not a strong part of Spryker, although it improved over the years. I still see room for improvement in the world of bigger CMS systems being able to also do "commerce".
Backoffice-usability - for non-technical users the first few days, weeks and month[s] can be full of surprises. An extended documentation, or more intuitive handling on the backoffice could serve every party on Spryker.
Off-the-shelf internationalization - Spryker right now comes with an initial data set in English and German, which is for a German based company already a pretty stable starting point. Extension on the base data for Europe-wide used countries would be very helpful - French, Italian, Polish, Russian, etc.

Return on Investment

Connecting new business together with Spryker as a foundation (e.g. FAAS with Spryker baseline).

Alternatives Considered

Magento Commerce, part of Adobe Commerce Cloud and SAP Commerce Cloud (formerly SAP Hybris)

The complexity of development and stability of Spryker weigh in against most of the smaller e-commerce frameworks, like Magento or Shopware. In comparison to SAP Hybris, the licensing costs and complexity of development does not give a better experience than Spryker.

Support Rating

Support on client projects is always great, especially when the support is backed by Spryker internal developers. The community, which is the "first point of contact" for every Spryker developer, is also very helpful and always supports a newcomer in questions or problems. Just a few points to improve from my side are:

better technical support, if the request comes from a partner vs. a partner in the name of a client
extended documentation on also older parts which are still relevant in modern Spryker projects

Usability

As mentioned before Spryker offers a lot for users and developers, but the steep learning phase can be sometimes a bit rough.

In the correct setup of developers and business, I would always vote Spryker over other e-commerce frameworks like OXID, Magento, or Shopware. Due to its stability and extendibility on the technical side.

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?

I wasn't involved with the implementation phase

Would you buy Spryker Cloud Commerce OS again?

Yes

Likelihood to Recommend

From my experience, I categorise client businesses right now in two groups, Spryker-ready and "just not suitable". These two categories are based on the technical background which come with the clients business. If the business seems to be very simple on the outside, but has a lot of technical dependencies, connections and input resources, I would instantly go for Spryker as the architecture and way to implement "data driven" projects - is just supporting the way of consuming "endless endpoints," and present them in a simple way for the clients' customer to pursue the E-business.

On the other hand, projects which have no big technical background but a more complex, or "fancier" presentation, I would recommend a simpler and easier to adjust framework as the overhead are not worth it and the capabilities of Spryker won't be used fully.

Complex businesses require a solid baseline

Software Version

Overall Satisfaction with Spryker Cloud Commerce OS