Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Modular design for scalable e-commerce needs
What do you like best about the product?
Spryker Commerce OS shows a modular design and has strong API capabilities, catering well to scalable e-commerce needs, especially in terms of complex B2B sales structures.
What do you dislike about the product?
However, initial setup complexity and less user-friendly documentation might create challenges for newcomers. Customisation demands technical expertise which may limit its accessibility for smaller teams. Generally stable, extensive customisation could lead to occasional hiccups.
What problems is the product solving and how is that benefiting you?
Provide a customisable and scalable e-commerce B2B platform to cater to the needs of our customers while improving and extending our business model.
- Leave a Comment |
- Mark review as helpful
A Seamless Journey for New Users - Fast UI, Excellent Support, and a Growing Extension Marketplace.
What do you like best about the product?
Efficient UI, swift performance, excellent support with responsive customer success, and ongoing efforts to enhance the extension marketplace make my experience as a new Spryker user delightful.
What do you dislike about the product?
User-friendly aspects like UI and support are commendable. However, challenges arise for non-developers in executing advanced actions (e.g., imports/exports) and renaming product SKUs, impacting overall user experience.
What problems is the product solving and how is that benefiting you?
Spryker Cloud Commerce OS is helping solve our problem with connecting addtional brands/merchants and their separate ERP systems into one ecommerce platform for seamless operation.
Spryker is a powerful E-Com Toolbox with a very modular setup.
What do you like best about the product?
- Growing fast, future-proof solution
- Modular and very flexible setup
- Existing modules for 3rd parties (payment, tax calculation...)
- Excellent documentation available online
- Nice Look&Feel of the backoffice
- Modular and very flexible setup
- Existing modules for 3rd parties (payment, tax calculation...)
- Excellent documentation available online
- Nice Look&Feel of the backoffice
What do you dislike about the product?
- Default configuration of the system is not always setup in the way most ecom websites would require it, more configuration required compared to some other ecom tools.
- Headless frontend (not Yves) seems to be more complex than expected as GlueAPI does not always provide all required information OOTB
- While the backoffice Look&Feel is very nice, the general UX of it could be improved (less views/less clicks)
- Poor Reporting/Dashboard features makes it almost mandatory to use external BI Tool even for checking basic sales data.
- Headless frontend (not Yves) seems to be more complex than expected as GlueAPI does not always provide all required information OOTB
- While the backoffice Look&Feel is very nice, the general UX of it could be improved (less views/less clicks)
- Poor Reporting/Dashboard features makes it almost mandatory to use external BI Tool even for checking basic sales data.
What problems is the product solving and how is that benefiting you?
Global rollout of B2C webshops in different markets with different volumetry/ERPs/language.
Spryker has been chosen mainly for it's modularity/flexibility (Microservices/APIs) to make it possible for our company to meet diverse specific local requirements in different countries while using a common core Ecom Platform.
Our goal in using Spryker was to find a solution which can offer a good compromise between global standardization and local flexibility - all with minimal complexity and maximum performance.
Spryker has been chosen mainly for it's modularity/flexibility (Microservices/APIs) to make it possible for our company to meet diverse specific local requirements in different countries while using a common core Ecom Platform.
Our goal in using Spryker was to find a solution which can offer a good compromise between global standardization and local flexibility - all with minimal complexity and maximum performance.
Modular and flexible Commerce Framework
What do you like best about the product?
- Flexible, modular and future-proof architecture
- Provides lots of OOTB features
- State machine provides lots of flexibility when it comes to customizing the OMS part
- Motivated and skilled people behind the product
- Smooth GoLive experience
- Provides lots of OOTB features
- State machine provides lots of flexibility when it comes to customizing the OMS part
- Motivated and skilled people behind the product
- Smooth GoLive experience
What do you dislike about the product?
- Steep learning curve, developer experience could be improved (e.g. documentation)
- Access to production system (logs etc.) needs improvement, but already on the roadmap
- Hiring people with relevant experience is quite hard since the product is relatively new
- Access to production system (logs etc.) needs improvement, but already on the roadmap
- Hiring people with relevant experience is quite hard since the product is relatively new
What problems is the product solving and how is that benefiting you?
Spryker helps to build custom, non standard business models on top of a strong framework with lots of commoditized commerce features which can easily be used
Digital Commerce PaaS service, supporting various e-commerce use-cases, in a comprehensive package
What do you like best about the product?
Supports multiple e-commerce use-cases, such as B2C and Marketplace
Enterprise-grade architecture, API-first
Scalable Cloud-based offering
Clear onboarding process
Enterprise-grade architecture, API-first
Scalable Cloud-based offering
Clear onboarding process
What do you dislike about the product?
Steep learning curve for PHP developers who are not exposed to entrprise architecture principles (e.g. like Java EE)
Lacks in certain key funcional areas, especially in Marketplace module
Lacks in certain key funcional areas, especially in Marketplace module
What problems is the product solving and how is that benefiting you?
Provides a solid e-commerce platform, which can be extended to meet our specific functional requirements and can scale according to meet our needs
Spryker support our digitalization journey
What do you like best about the product?
Good set of feature OOTB system feels future ready and supports us in building up what we need.
What do you dislike about the product?
Sometimes more flexibilirty would be good.
What problems is the product solving and how is that benefiting you?
Digital order possibilities for our customers that will make more time for other task in our order management team.
Spryker the ecommerce tool for 2023
What do you like best about the product?
We recently launched a multiregional experience with multiple warehouses and stores in the same instance of Spryker. This was initially a challenge, but with the proper guidance, we could launch on time and provide an excellent experience for our customers.
What do you dislike about the product?
Some issues have come up on the roadmap to maintain Spryker up to date; We need to plan this next year carefully and implement a consistent update approach to our backlog. We will need time from our development team to spend on this regular update.s
What problems is the product solving and how is that benefiting you?
Spryker is providing the backbone of our eCommerce operation. It is crucial on our success in driving revenue with consistent information flow and reliable connections to all other systems involved (Customer Service, Warehouse, Payments, etc)
Top of the line TCO, TTM, scalability, and support
What do you like best about the product?
Spryker's mix of composability and packaged business capabilities enabled us to build and launch an MVP in only six months with a small team. When the time came to quadruple our business in a multi-store structure, the platform's flexibility allowed us to complete the ramp-up in a couple of months. The team at Spryker is invested in our success, supporting us every step of the way.
What do you dislike about the product?
So far, we have not found any relevant roadblocks or flaws worth mentioning.
What problems is the product solving and how is that benefiting you?
We launched B2B digital wholesaling operations in Mexico. Our customers are mom-and-pop grocery shops, typically with pen and paper management and little to nonexistent digitization. Spryker's composability allowed us to build tailored digital experiences with which our customers can feel comfortable.
Developers review
What do you like best about the product?
- layered architecture
- modular
- high traffic optimized
- quick startup
- provided docker sdk
- extensibility
- tech stack somewhat up to date
- modular
- high traffic optimized
- quick startup
- provided docker sdk
- extensibility
- tech stack somewhat up to date
What do you dislike about the product?
- modularity (coz of lots of packages upgrades are very complex and time-consuming)
- poor and not up-to-date documentation
- the steep learning curve for all of the developers, significantly less experienced
- support sometimes is not as responsive as expected
- poor support for monitoring/logging
- no dedicated DevOps support for a Paas solution
- default storefront uses "old" frontend technologies, hard to find frontend devs
- too many layers on top of standard packages/solutions (for example, Symfony libs)
- extensions by extending
- poor and not up-to-date documentation
- the steep learning curve for all of the developers, significantly less experienced
- support sometimes is not as responsive as expected
- poor support for monitoring/logging
- no dedicated DevOps support for a Paas solution
- default storefront uses "old" frontend technologies, hard to find frontend devs
- too many layers on top of standard packages/solutions (for example, Symfony libs)
- extensions by extending
What problems is the product solving and how is that benefiting you?
Replatforming our exisitng e-commerce solutions to standardised platform.
Complex Solution with potential to become the leader in E-Commerce
What do you like best about the product?
- The willingness to support and help their clients is second to none
- Spryker cares for their client's success and invests massive effort into projects
- Platform offers extreme flexibility to build whatever is needed in a relatively short time
- Architecture and modularity are future-proofed when compared with other E-Commerce platforms
- Developers like using concepts and technologies Spryker is based on
- Spryker is regularly evolving, i.e., the academy is regularly adding new courses/trainings, Spryker App Composition Platform, etc.
- If you have an experienced internal dev team composed of med/sen FTEs with detailed project plans in terms of scope/timeline/budget, then Spryker is the way to go
- Spryker cares for their client's success and invests massive effort into projects
- Platform offers extreme flexibility to build whatever is needed in a relatively short time
- Architecture and modularity are future-proofed when compared with other E-Commerce platforms
- Developers like using concepts and technologies Spryker is based on
- Spryker is regularly evolving, i.e., the academy is regularly adding new courses/trainings, Spryker App Composition Platform, etc.
- If you have an experienced internal dev team composed of med/sen FTEs with detailed project plans in terms of scope/timeline/budget, then Spryker is the way to go
What do you dislike about the product?
- Almost non-existing developer community, documentation for developers often not up to date
- Onboarding for developers proved to be extremely long and hard (juniors up to one year, mediors 6 months and more, seniors from 3-6 months)
- Everything can be done; however you must follow the Spryker way (which sometimes is not easy to comprehend) and more than often increasing effort and prolonging the time for delivery
- Best suitable for building MVPs with basic needs in terms of features/functionalities/integrations and then increasing the complexity gradually over the time; in cases when re-platforming is needed, tremendous effort has to be invested in building custom features and functionalities increasing time-to-market
- Not covering complex grocery use cases (catchweight products, timeslots, logistics, integrations), a lot of OOTB features and functionalities provide basics, so they either must be developed from scratch or heavily reworked
- Even though it is PaaS, internal DevOps resources are a must-have, for the majority of AWS settings read-only privileges are granted, increasing the time and effort to make changes (everything has to be done via tickets on Spryker Support Portal)
- Frontend Yves is based on pure js. twig for templates and SCSS making it hard to find/hire frontend devs willing to work with that stack
- Hard to upgrade to newer versions since there is a lot of modules and inter-dependencies to take care of
- Onboarding for developers proved to be extremely long and hard (juniors up to one year, mediors 6 months and more, seniors from 3-6 months)
- Everything can be done; however you must follow the Spryker way (which sometimes is not easy to comprehend) and more than often increasing effort and prolonging the time for delivery
- Best suitable for building MVPs with basic needs in terms of features/functionalities/integrations and then increasing the complexity gradually over the time; in cases when re-platforming is needed, tremendous effort has to be invested in building custom features and functionalities increasing time-to-market
- Not covering complex grocery use cases (catchweight products, timeslots, logistics, integrations), a lot of OOTB features and functionalities provide basics, so they either must be developed from scratch or heavily reworked
- Even though it is PaaS, internal DevOps resources are a must-have, for the majority of AWS settings read-only privileges are granted, increasing the time and effort to make changes (everything has to be done via tickets on Spryker Support Portal)
- Frontend Yves is based on pure js. twig for templates and SCSS making it hard to find/hire frontend devs willing to work with that stack
- Hard to upgrade to newer versions since there is a lot of modules and inter-dependencies to take care of
What problems is the product solving and how is that benefiting you?
Single flexible, future-proofed E-Commerce platform across multiple markets and business models that internal development teams will maintain and further build upon. Spyker Cloud Commerce OS is the foundation for E-Commerce Growth in years to follow.
showing 11 - 20