A note from 2026: This article was published in 2016. The “hybris” brand has since been phased out in favor of SAP Commerce Cloud, and older PCM/Product Cockpit-era tooling has been deprecated in favor of Backoffice-based product content management.

Situation

One of the grocery stores has the following business requirements:

A general approach to implementing these requirements is the following:

Complexity

There are a lot of existing news items and recipes that are supposed to be migrated from the existing website. The client may also need to add search capabilities in the future, as well as filtering and tagging.

Challenge

How can we speed up development without losing flexibility? How can we leverage existing hybris functionality?

Solution

The solution is to use the product data model to store non-product items such as news and recipes. An additional product type should be added. Product categories will serve as news categories. Product detail pages might be used for news details and recipe details. News and recipes could be stored in the SOLR index to reuse product list and search results capabilities and templates.

However, this solution has its pros and cons. Using unsuitable objects for news and recipes could make the solution less clear. Some side effects could occur as well, especially if hybris content development has not been harmonized with hybris commerce development.

© Rauf Aliev, June 2016