When implementing eCommerce solutions, established standard software products (the core of which is standard eCommerce software products such as Intershop, Hybris, or Sitecore Commerce) are usually adapted to the respective customer requirements. In addition to program changes/extensions, you can customize the standard software by setting parameters or configuring the standard software. It describes functional adaptations of standard software products, such as the development of a social media functionality that does not exist in the standard software product (program change/expansion).
eCommerce solutions are used in various industries and customers can have special business models and requirements. This can, for example, be due to the special features of the desired functionality of the solution, the specific properties of its range of goods or the special properties of its business processes. Customer-specific adaptations often extend over several architectural levels. For example, to add a new type of business object, many changes are necessary, such as changes in the business logic (processing the objects), changes in the persistence layer (saving the objects in the database) or changes in the database itself (adjusting the database schema, possibly setting up indexes for searchability).
Customizing for Intershop Commerce Suite includes the following steps: Changes to business logic are made either in business objects, known as BOs, or in business flowcharts, known as pipelines.
The creation of enhancements in business flowcharts, i.e. pipelines, takes place in so-called pipelets, which are Java classes to be created according to a special default pattern. Persistent objects are used to create enhancements and changes to the persistence layer. These can be defined in the modeling language EDL, the Java classes are automatically generated from them. The adjustments of the database schema are defined by so-called DBMigrate steps, Intershop provides many ready-made classes to describe the DBMigrate steps, furthermore, you can also create your own or manipulate database objects directly via SQL.
The customizing of Hybris Commerce Suite includes: The business model is adapted on the basis of an MDA approach (Model Driven Architecture). The Hybris platform automatically generates business objects from the defined or adapted business model and all backend applications such as the Backoffice Administration Cockpit adapt accordingly. The business objects are first specified in XML and then generated automatically during the build process. The changes in the ORM layer for object persistence and database schema adjustments are also generated. The business objects are "completely normal" objects in the Java programming language, so-called POJOs or Plain Old Java Objects. They can easily use the core services of the Hybris platform such as caching, clustering, personalization or internationalization support; and they can be used in all backend applications.
Each open service in the service layer can be adapted or completely replaced. Implementation partners and SAP use the same extension concept. SAP Extensions use the Spring Event System, making it easy for partner extensions to communicate with them. To develop custom extensions, SAP offers its partners tools that generate code modules ("boilerplate code") for new extensions.