Paddle vs. Spryker Cloud Commerce OS

I wouldn't recommend them to anybody because their support is getting worse and worse and their business processes require you to contact support whether you want to or not. You will be forced to contact support and then wait for days to get any meaningful response that's not a copy/pasted sentence from FAQ.

Spryker is very well suited (B2C and/or B2B) for big companies with complex and individual business models or also if your company needs a certain level of customization. Very good fit, if you need a scalable system. It is rather not the perfect fit for small companies or companies with very basic E-Commerce needs.

• Super easy to implement SDKs across supported platforms that support modern interface paradigms.
• Real team members that provide backend support for merchant issues. We had issues addressed quickly and taken seriously whenever we needed anything.
• Help with navigating VAT transparently. We never worried that we were messing up in this complicated area of international sales.
• Great first line customer support reduces the need for an extensive customer support organization on our end. They dealt with all purchase related issues as well as lightweight technical issues (e.g pointing users to FAQs, update links, etc.).

Incentivized

• Data Importers - Spryker is able to cope with large chunks of data ingest e.g. from PIM or ERP. Its integrated Middleware of handling this data.
• Scaling - Modern architecture makes it possible to scale flexible.
• Internationalization - Role our your shop with different assortments, pricing and products with out of the box features.
• Pricing - Spryker supports custom pricing out of the box (volume prices, gross/net prices, customer specific pricing).
• Order Management.

Incentivized

• Analytics could support more flexible analysis of reported data and better custom events.
• More customization of the drop in purchase UI on the web without the need for a full custom site integration.
• Sometimes communication from their front line support staff has gone to the wrong address.

Incentivized

• 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.

Incentivized

Spryker's usability depends a lot on custom development. Therefore, I would like not to consider usability as something that comes with Spryker Cloud Commerce OS. Spryker Cloud Commerce OS; however, brings all the tools needed to design a solution with great usability.

Support suffered from Spryker Cloud Commerce OS's rapid growth. Contacts, department heads, and support systems changed frequently. Support processes as well as documentation are rather poor. One notices that they are putting more effort into the customers recently, but in the course of growth, there is still a lack of focus here. As a customer, I would like to see growth at a slower pace and a phase of stabilization.

Incentivized

We tried using Stripe before Paddle, but it was a pain integrating it and it lacked the licensing. Paddle allows us just to add a payment button and don’t ever think about payment methods, we don’t have to make a separate button for card payments and another one for PayPal. Paddle does all this in their checkout process.

Incentivized

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).

• We wanted to grow faster, which was possible once we integrate recurring payment gateway. And we've got Paddle to do that.

Incentivized

• Extending the reach and visibility of the brand through content and commerce.
• Increased customer satisfaction through better accessibility (self-service) and easy access to important product information (CAD data, technical documentation, etc.).
• Rapid deployment thanks to packaged business capabilities and clear development leads to fast ROI and low TCO.

Incentivized