
After working on multiple B2B and B2C implementations, the biggest strength I’ve seen is how extensible the platform is. The accelerator-based architecture, layered extensions, and strong service layer make it possible to customize almost anything without breaking the core. For complex business requirements — especially in B2B (custom pricing, approval workflows, contract-based catalogs) — it handles them really well out of the box.
Another big advantage is its integration capability within the SAP ecosystem. When integrated with SAP S/4HANA, SAP Customer Experience, or other SAP products, the data flow becomes very structured and reliable. For clients already invested in SAP, this reduces a lot of integration overhead.
I also appreciate the cloud-native direction (especially with CCv2). CI/CD pipelines, managed infrastructure, and environment consistency have improved deployment stability compared to older on-prem setups.
From a developer perspective, the strong type system, flexible data modeling (items.xml), and powerful search with Solr make it a very capable platform for building scalable commerce solutions.
Overall, it’s a solid enterprise-grade platform that can support very complex commerce scenarios if architected correctly. Review collected by and hosted on G2.com.
First, the learning curve is steep. For new developers, the platform can feel overwhelming. The extension structure, Spring configuration layers, items.xml modeling, impex, cronjobs — there are many moving parts. If the project isn’t architected properly from the beginning, technical debt builds up quickly.
Second, performance tuning can be challenging. Out of the box, it’s powerful, but not always lightweight. You really need experienced architects to design caching, indexing (Solr), and database queries correctly. Otherwise, scaling becomes expensive.
Deployment and environment management — even though CCv2 improved things — can still feel restrictive. Debugging production issues is not as straightforward as traditional self-managed environments. You depend heavily on logs and cloud pipelines.
Another area is upgrade effort. Major version upgrades are rarely “plug and play.” Customizations, deprecated APIs, and accelerator changes can require significant rework, especially in long-running projects.
Lastly, licensing and infrastructure cost can be high compared to some modern headless or SaaS-native commerce platforms. For mid-sized businesses, it can sometimes feel like overkill. Review collected by and hosted on G2.com.