
Modularity, flexibility and robustness of the software is very good. The software architecture is build on top of design patterns and follows principles (e.g. SOLID) and standards, which is simple awesome from developer perspective and really helps during the implementation phase of a project. Review collected by and hosted on G2.com.
There are a lot of modules and a very fast developing from spryker side, which makes it not that easy to keep a project always up-to-date with the latest spryker modules - here the (mostly) independence of the modules helps you out in the end and also does not make it necessary to updated each single module all the time. Review collected by and hosted on G2.com.
I like Spryker's out-of-the-box orientation to quality and scalability. It is easy to switch from one project to another using Spryker because the code structure is the same and the concepts are well enforced. Spryker has a large number of available modules to choose from which helps in implementing features faster. Spryker's Glue layer is a feature that may help to implement more exotic ecommerce solutions. Spryker's code quality tools enable teams to have unified quality standards. Review collected by and hosted on G2.com.
Developing Spryker can sometimes be a bit tedious, quite a lot of boiler plate code is required. The learning curve is steep. The core code sometimes might be of higher quality. Review collected by and hosted on G2.com.
Spryker provides solutions to problems that are often encountered in e-commerce. It is scalable and provides standard e-commerce feature set out of the box. Spryker's code quality is great and it can be used as a reference as well as documentation helping out developers working on the product. Modular architecture allows for great team changeability (developers can switch teams without wasting time with on-boarding, as Spryker has unified structure) and with experienced developers quick time to market. Overall Spryker solves a lot of frequently encountered problems (asynchronous updates, cart, checkout, product storing/updating/viewing/administrating) and it implements a lot of design patterns, that enforces scalable, changeable and readable code avoiding long lasting project's issues related to legacy and outdated code. Due to modular architecture, it is possible for a larger team to work on Spryker without interfering with one another. Review collected by and hosted on G2.com.
At first Spryker has a steep learning curve and a lot to take in, which might be discouraging. There is also a lot of boilerplate code, but keeping the benefits in mind it actually helps in the long term. In order to use Spryker effectively and efficiently experienced developers are required. For small projects, without big plans for the future, there is no sense to use Spryker as it would be a big overhead. Review collected by and hosted on G2.com.
The Seperation between Backend and Frontend (Yves and Zed), which bringswith High Flexibility and modularity
When ever a customer has special needs for a sophisticated digital Business-modell combined with transactions and high flexibility for different Frontends, the Spryker Commerce OS is suited very well. Review collected by and hosted on G2.com.
The Integration in Third-Party Systems can be improved and extended Review collected by and hosted on G2.com.
Whenever a client wants to build a sophisticated digital business model that fits into existing infrastructures and requires high flexibility in the front-end, Spryker is a good choice. We see many use cases in the B2B and unified commerce sector. Especially the packaged business capabilities brings a high modularity and flexibility and this is what our customers need to be competitive and spryker delivers. Review collected by and hosted on G2.com.
Integration in Third party-systems have to be improved Review collected by and hosted on G2.com.
(+) The modular and extendable nature of Spryker
(+) Well documented interfaces
(+) A lot of interesting features, most of which are features requested by customers
(+) Focus on scalable, cloud native architectures
(+) Free software based and open source development model Review collected by and hosted on G2.com.
(-) While the core of Spryker is very stable, all frontend-facing features are less developed and refined
(-) A couple of must have features like Guest Checkout for B2B cases aren't easily installable, they must be deeply integrated into the code
(-) Versioning is a mess, upgrading is always a pain - even for Patch releases
(-) While using static typing in PHP can enhance legibility and stability of code, Spryker often over does this which makes it needlessly complex to work with Spryker Review collected by and hosted on G2.com.
Due to the modular architecture, Spryker allows a fast start in dismantling legacy ecommerce solution and integration in existing IT landscapes. The clean headless approach and the modular backend is key for a fast, smooth and inexpensive for integration in existing IT landscapes, since adapting to business needs is key for success. Review collected by and hosted on G2.com.
The fresh approach Spryker takes needs a culture change in your development teams, if you have decade old legacy eCommerce system. Review collected by and hosted on G2.com.
The software architecture of Spryker enables good performance that comes along with good scalability and customization.
Speaking as a developer, it's fun to work with! Review collected by and hosted on G2.com.
While the code architecture is one of Spryker's pros, it's also hard to start as a beginner. It takes some time to understand all of the concepts.
Documentation also sometimes lacks information. Review collected by and hosted on G2.com.
Spryker doesn't start with the pure product offer, but first wants to understand our business, needs and expectations. This enabled us to form a good set up for the creation and realisation of the offer even bofire the start.
Very fast realisation of the project after the start of first quote.
Platform was launched within 3 weeks developement.
Spyker's agile corporate culture fits well woth our way of working and company DNA. Review collected by and hosted on G2.com.
Even more proactive approach in terms of process optimization. Review collected by and hosted on G2.com.
Best B2B eCom Functionality OOTB you can get on the market. Spryker is highly customizable according to your business needs and helps to scale your ecommerce business model. Review collected by and hosted on G2.com.
Relatively high efforts to maintain and update Spryker OS. To implement Spryker a really good and experienced development team is required. Review collected by and hosted on G2.com.
Spryker is a large modular construction kit with a very tidy code base.
It uses the advantages of recognized technologies (e.g. RabbitMQ, Jenkins, Elasticsearch, etc.) and combines them into a suite that makes the creation of an online store very fast. The closeness of the developers to the community is very visible and suggestions from the community are taken into account, which I consider a big advantage over the competition. Review collected by and hosted on G2.com.
You can see that the majority of Spryker developers use MacOS/Ubuntu based systems for development.
Here it would be nice if the focus would be set on Windows and WSL2 so that developers using this environment can use the framework more easily.
Also, unfortunately only very outdated software versions are used (e.g. Elasticsearch 5.6 vs 7.9.1, PostgreSQL 10.6 vs 13, etc.). Here you should pay a bit more attention to the newer versions.
The documentation could also be made easier and more detailed for new developers. Review collected by and hosted on G2.com.
- modular architecture
- highly scalable
- packaged business capabilities for best of breed approach Review collected by and hosted on G2.com.
- not so big community around it
- developer enablement takes some time
- documentation needs improvement Review collected by and hosted on G2.com.
Active community, many developers available, fast growing feature set, direct contact to Spryker personel (even at higher levels) Review collected by and hosted on G2.com.
Not mature yet, Spryker decisions sometimes not understandable (DB switch), no communication about it, rather junior in some fields (PaaS), documentation in some areas outdated, third party modules not timed in roadmap (FirstSpirit connector, PSP modules, Marketplace module ... ), no real issue tracking, communication delays. UX in Yves B2B rather junior Review collected by and hosted on G2.com.
Code quality, infrastructure, modularity, splitting of frontend and backend components, managing of complex business logic for after sales processes Review collected by and hosted on G2.com.
complexity, high learning curve, missing standards for after sales processes Review collected by and hosted on G2.com.
Due to the modular structure it is very easy to extend and change the existing code. In addition, the GLUE API ensures that a completely different front end can be connected. Review collected by and hosted on G2.com.
Due to some legacy code that is not yet adapted to today's Spryker state, it is sometimes more time-consuming to extend and modify old code at project level. Review collected by and hosted on G2.com.
Spryker HandsOn onboarding material (Bootcamp) + training/certification offering. Direct contact to people/departments in Spryker (e.g. documentation, technology, partner management / customer care). Review collected by and hosted on G2.com.
Status/Maturity level of third party modules (e.g. payment, connectors to other systems) and status of default features. Often not completely implemented/fully fleshed functionality in comparisson to other e-Commerce systems. Issue tracking only via webform + mail. Review collected by and hosted on G2.com.
Modularity
Scalability
Great Community
The Development of the Documentary
BootCamp
Workshop Review collected by and hosted on G2.com.
In the communication concerning misfunctionality needs improving!!!
Features that are sold to customers, but are not well tested and do not work as "promised" - untested features (Adyen, Akeneo Connector)
Therefore I'd say Spryker is still in its child shoes
Differences between principles and actual coding
Same thing is done in three ways, e.g defining forms, declaring constants CLIENT_XY vs XY_CLIENT
Things are annotated as deprecated but the actual replacement is not provided (Route Provider which constants are protected and not accessible anymore) Review collected by and hosted on G2.com.
- Flexibility
- Customizability
- Scalability Review collected by and hosted on G2.com.
- Complex Architecture and hosting
- Sometimes much code for little functionality
- Needs stabilization concerning used technologies, base-code, .. Review collected by and hosted on G2.com.
The speed to spin up the platform and the right combination of predefined functionalities with the flexibility for taylored solutions. Review collected by and hosted on G2.com.
Limited scalability of individual functions within the Spryker OS. Review collected by and hosted on G2.com.