Adobe Experience Manager vs SAP Commerce Cloud (formerly SAP Hybris)

• Adobe Experience Manager keeps your content separate from your layout which allows for a lot of flexibility in how you display your content.
• Adobe Experience Manager integrates really well with other Adobe products like Adobe Analytics.
• Adobe Experience Manager 's drag and drop interface makes it fairly easy to utilize with minimal familiarity.

Read full review

• Large scale product and user data management.
• Out of the box support for common eCommerce functionality.
• Robust platform that is supported well and consistently by the Hybris team who are available for direct support if needed.
• Integrates well with other services if Hybris does not meet all business needs.
• Localization for multi-national support was easy to implement.

Read full review

• Upgrading and applying patches can be hit or miss - I recommend backups because of the potential to damage the existing infrastructure
• Space management is an issue - every change or request takes up space that can be reclaimed, but only through a complicated procedure done through command prompts. There was no documentation for this on their site and we had to use a third party to create the procedure. It has to be run manually.
• There isn't a good backup system, particularly one that can be scheduled to run reliably.

Read full review

• CMS Cockpit is slow and inefficient for performing certain kinds of content management and template manipulation tasks. I often defer to the HMC, but this is not a feasible option for our client's content management team.
• The OOTB UI code that ships with v5.0.1 is several years behind industry standard front end technology. v5.1 shows no promise of significant improvements in this arena. Some things I'd like to see: Dropping the Blueprint framework in favor of something Like Bootstrap, Less Framework or AngularJS. Jquery and key dependent plug-ins need to be upgraded and large, over-featured plugins like JQuery UI abandoned. SASS + Compass should replace static CSS. Granule should be dropped in favor of better tools for JS dependency management, code minification, and file concatenation.
• Maintaining independent codebases for Desktop and Mobile views increases UI development hours by a margin of 30-50%. Natively supporting the option to configure a responsive design with a framework such as AngularJS would offer flexibility to serve up content and site chrome targeted at a wider range of device classes than just desktop machines and mobile phones.

Read full review

• Our brand requires a high level of polish and crisp functionality. AEM provides that for us. We do look as good as possible and it reflects well on our brand.
• We can product new pages rapidly with our modules and so we can keep our content fresh and relevant.
• Our brand value has risen considerably since we polished our web properties with AEM.

Read full review

• Our business went through 3 major initiatives to migrate our legacy platform and data to Hybris over the course of several years with multiple tech leadership and dev teams. All 3 of these initiatives failed to launch, largely due to the complexity of the platforms and massively associated tech burdon. A 4th re-platforming succeeded in launching an MVP version with support from expensive consulting firms and to the tune of millions of dollars.
• Due to the inflexibility of the content management features, marketing teams are severely limited and have had to seek 3rd-party software to layer on top of Hybris to deliver modern customer experiences.

Read full review