Commerce Project

Consulting Services

Achieve the amazing usability for your B2B Customers which only a customised SAP Commerce Cloud solution can provide.

Commerce Cloud implementations prove challenging due to 2 major developments in the consulting industry:

• The SAP Commerce Cloud as shipped by SAP including its accelerators and pre-built solutions doesn´t fulfil the individual process needs and logic which exists within a company and subsidiaries of companies.

• Many integrators promise to solve this solution gap with a pre-built additional accelerator stack which is sold at a premium.

This common project setup leads to several shortcomings. Once installed both standard SAP Commerce and integrator accelerators solve one particular scenario, but:

• • Many enhancements are still necessary since the pre-built stack doesn´t fulfil the requirements to 100%.

  • Dependencies on many Hybris extensions are introduced which are not needed for the solution to work.

  • The combination of adding unused application code and adding customisation on top results into unnecessary complexity due to overwritten objects (in particular facades, populators and services)

  • The result: Regression risk with every customisation and an increase of estimates for every further enhancement.

  • Once the final customisation is done the many components of the standard and pre-shipped accelerators become redundant and need to be removed at a large expense to make the solution extensible again.

  • Integrators often miss to provide an upgrade path for their pre-built additional accelerator stack to new storefront features introduced with new Hybris releases. If upgrade paths are provided additional effort is offered to merge, test and release the customisations done in the project with the upgrade.

YUNIT´s Commerce Project Methodology is different from this approach:

• In requirements gathering and blueprint sessions the business processes are modelled, the main order management scenario (synchronous or asynchronous) is determined, and custom integration requirements are clarified.

• The implementation starts with extending the shipped B2B accelerators which require customisation into the customer namespace

• To make the storefront easily upgradable to new Hybris releases all changes are made in Addon Extensions (Addons leave the original storefront accelerator intact and overwrite objects during build time).

• The custom integrations, business logic, UI implementation and System tests are implemented specifically for the customer. In case integration templates are available in the YUNIT integration repository the core aspects are applied to the customer codebase, leaving all unused complexity out (= main difference in contrast to rolling out an integrator accelerator stack).

• Once the solution is released the result is a clean codebase which is free from clutter and easily extensible.