Modulare Architekturen und der Aufstieg des Composable Commerce

How companies benefit from innovative approaches

Enabling composable commerce

Composable CX

In recent years, several innovative approaches have revolutionised how companies operate and act across industries.

One of the most exciting developments is the concept of Composable Customer Experience. This approach allows companies to flexibly and individually design their business model and IT landscapes with a holistic view of customer interaction.

The most important idea here for companies is that companies can react quickly to changes, regardless of the nature of these changes.

The constant growth in communication channels, the changes brought about by new information structures, the emergence of new market opportunities, and trading on marketplaces make it hard for companies to keep up. The need for a new lightness in the face of all changes is excellent; this is precisely where the Composable concept comes in. Through a modular design, the aim is to re-orchestrate as needed and optimise again and again.

The mindset of modular architecture refers to composable business and composable commerce: the independence of individual components that communicate with each other is the crucial point here. The new approach makes it possible to take risks, as modular IT projects are no longer interdependent. At the same time, generally applicable designs and paradigms can be found in orchestration, which can simplify and control complex structures.

The new way of thinking is implemented by solution providers with suitable technology, for example, through the API-first principle or headless commerce: practical tools for composable trade.

How does Composable Commerce define itself?

Composable Commerce aims to make eCommerce flexible and customisable according to the concept of a Composable CX. Instead of using a large and rigid system monolith, Composable Commerce relies on a compilation of different, independent building blocks. This allows the best available tools and services to be selected to create a customised solution for specific requirements. It is important to strategically think through and plan the necessity of the individual components and their coordination. A consulting effort pays off quickly at this point.

The basic approach in Composable Commerce is to divide the software into two parts: what the customers see (frontend) and the technology in the background (backend). This creates the freedom to select and combine specific technologies according to a 'best-of-breed' approach. The goal is a flexible and responsive structure for online commerce that can cope with all changes.

"Composable Commerce" was first coined in the early 2010s when companies began to recognise the need for more flexible and customisable eCommerce solutions.

Knowledge

"Composable Commerce" was first coined in the early 2010s when companies began to recognise the need for more flexible and customisable eCommerce solutions. During this time, it became clear that traditional monolithic eCommerce platforms needed to meet the needs of the rapidly changing digital marketplace. Companies sought new approaches to make their eCommerce systems more modular and agile.

The UK has a thriving eCommerce landscape with compelling customer experience solutions and is known for its innovation in the digital economy. British companies have realised that a flexible approach to building their eCommerce systems is crucial to keep up with ever-changing customer demands. Many companies have jumped on the Composable Commerce bandwagon thanks to this realisation.

Within the framework of this trend movement, those above technological focal points developed:

  • Headless Commerce is to be seen as an essential building block in Composable Commerce: Front-end and back-end components of the eCommerce system are decoupled from each other. Companies switched to headless commerce for more flexibility and freedom in designing customer experiences.
  • Composable Commerce now goes one step further by decoupling the front-end and back-end and every system element. Only in this way can a completely customised IT landscape be created.
MACH architectures can provide an ideal foundation through microservices, APIs, cloud, and headless.
  • APIs (Application Programming Interfaces) enable integration and communication between different systems. Many companies relied on API-based solutions to make their eCommerce platforms modular and scalable.
  • MACH architectures can provide an ideal foundation through microservices, APIs, cloud, and headless. They ensure that the architecture is current and that individual components are easier to adapt. The frontend and backend communicate via interfaces (APIs), and each component can be replaced without affecting other parts.
Spryker

Wissen

Composable Commerce Trends

The eCommerce landscape is striving to take advantage of the modular approach across Europe, but especially in Germany, the Netherlands, and Sweden. Composable commerce initiatives and platforms, such as those from Spryker, commercetools, or SAP, are emerging to help companies implement them.

Large retailers and international brands such as Nike, L'Oréal, and Coca-Cola are turning to Composable Commerce to make their eCommerce systems more effective and responsive to the needs of local markets. The modular eCommerce architecture enables faster scaling and high-quality personalised customer experiences.

With the growing demand for customised customer experiences and agile business models, Composable CX is expected to grow in importance and permanently change how companies do business online.

commercetools

MACH Alliance

MACH Alliance: The MACH Alliance is a cross-industry initiative that promotes open and composable technology standards in eCommerce. It consists of leading companies such as commercetools, Contentstack, and EPAM Systems. MACH Alliance members work together to demonstrate the benefits of composable commerce and develop best practices. The initiative provides training, case studies, and a knowledge-sharing platform to promote the development and implementation of composable commerce solutions.

Composable CDXP Hub: The Composable Commerce Hub is a platform launched by the CMS platform Magnolia.  This initiative brings together companies, technology experts, and trade associations to provide best practices and resources around Composable Commerce. The Hub provides insights, case studies, guides, and events to help advance the understanding and implementation of Composable Commerce. The Composable Commerce Hub helps strengthen the composable commerce community by sharing knowledge and best practices.

Further development through projects and studies: Experts and companies work together to further develop technology solutions. These initiatives promote frameworks for new technologies, the development of best practices, and the creation of an academic framework.

Countless solutions available for us to explore and utilise

Various platform and solution providers are helping to realise the vision of Composable Commerce. For the best choice, companies face difficult decisions: For example, while one solution provider focuses on content delivery and flexibility, another focuses on user-friendly management tools. 

The choice between different solutions and components depends on a company's specific needs and goals. Consultancy is an excellent support from the beginning of the planning process. One needs to know the advantages and disadvantages of each solution component well to make the right decision. With the selection of the best partner solutions, a holistic strategy for building the modular architecture must be designed.

Integration of components and systems

Integration of components and systems

One of eCommerce companies' primary tasks is seamlessly integrating different components and systems. The challenge is that companies often work with heterogeneous IT landscapes where legacy systems and various applications coexist. A robust integration strategy is needed to effectively connect these systems. Solution strategies such as using APIs, integration-as-a-service platforms, or middleware tools can help facilitate integration and make the ecosystem more effective.

Data exchange and data consistency

In composable commerce, data plays a crucial role as it needs to be shared between different components and systems. The challenge is to ensure that data is transferred in real-time and consistently to provide a seamless customer experience. By implementing event-based architectures, using ETL (Extract, Transform, Load) processes, and setting up data warehouses or data lakes, data exchange can be optimised and data consistency improved.

Scalability and performance

Another aspect to consider is the scalability and performance of the systems. With an increasing number of users and transactions, eCommerce solutions must be able to cope with the demands. Solution strategies such as the use of cloud infrastructures, the implementation of microservices, and the use of caching technologies are essential here. These approaches can improve scalability and performance to ensure a smooth and fast shopping experience.

Solution strategies include utilizing cloud infrastructures, implementing microservices, and utilizing caching technologies.

Ensuring Security and Privacy

In the digital age, security and privacy are of paramount importance. Composable commerce brings new security risks as multiple components and systems interact, sharing sensitive customer data. Here, solution strategies such as implementing security standards and protocols, conducting regular security audits, and training employees on handling sensitive data are essential.

Solution

6. Sustainable strategy through composability

Let's summarise: The concept of a Composable Customer Experience offers the possibility to build the IT landscape modularly, adapt it flexibly, and tailor it to the individual requirements of the user groups. It enables the seamless integration of different components and systems so that companies can select and combine their technology stacks as needed.

The Composable approach also allows your eCommerce business to quickly adapt to implement new functionality as needed and be fully resilient to changing market conditions.

Achieving Resilience in eCommerce: The modular building blocks are independently scalable.

Achieving Resilience in eCommerce

The modular building blocks are independently scalable. This means businesses can scale individual components of their eCommerce infrastructure as needed without impacting the overall system. This modular architecture allows companies to use resources more efficiently and prepare for peak times without bottlenecks or performance loss.

Customer expectations are high when it comes to personalised customer experiences.

Composable CX solutions provide companies with the tools and capabilities to deliver personalised content, product recommendations, loyalty programms, and other tailored offers. By integrating Customer Data Platforms (CDPs) and marketing automation tools, companies can get a comprehensive picture of their customers and create targeted marketing campaigns.

"In a rapidly increasingly connected world, the customer journeys of user groups are becoming almost limitless. This makes it all the more important for companies to be able to offer their products and services consistently across different interaction channels. The Composable CX concept enables seamless integration of online shops, mobile apps, marketplaces, social media channels, and other sales channels - always tailored to the corresponding needs of the users. This gives companies a clear competitive edge, enables them to reach new target groups and markets, and creates a perfect shopping experience across all touchpoints," confirms Michaela Mürmann, Associate Partner, focus Customer Experience, at KPS.

More Insights

These topics may be of interest to you

Marketplace Insights

Marketplace Insights

How can retail benefit?

Is an online marketplace right for your brand? Most candidates need to learn what a successful entry can look like and what promising concepts there are for retailers. In addition, it often needs to be clarified which typical pitfalls can lurk and which technical challenges have to be overcome.
KPS ist Premium Partner von commercetools

News

Did you know that KPS is a Premium Partner of Commercetools?

As the leading composable software – and a founding member of the MACH® Alliance – commercetools is a strong partner for KPS to cover the topics of eCommerce, Customer Interaction, and Software-as-a-Service and to equip all digital touchpoints with a unique user experience.
Gamification: Level up your Loyalty-Program

Gamification

Level up your Loyalty-Program

Contests, badges and tier levels - companies rely on gamification elements to incentivise customers to interact with their brand and motivate them to buy and spend.

Privacy settings

We use cookies on our website. Some of them are essential, while others help us to improve this website and your experience. With your consent, we use cookies to analyse the usage of our website.

We also use cookies for marketing to help us measure the success of our marketing efforts. In the settings you will find detailed information about the individual cookies, and you can refuse the use of cookies.

You can change or revoke your selection at any time on any KPS.com page in the footer under Privacy Settings.

Essential Cookies

Essential cookies enable basic functions and are necessary for the proper functioning of the website.

Cookie Banner

  • Cookie Name: kps-privacy-settings
    Value: PrivacyLevel_0#a
    Storage Duration: 4 weeks
    Description: This cookie is required to save cookie settings. It is a purely technical cookie.

HubSpot:

  • Cookie Name: __hs_opt_out
    Storage Duration: 6 months
    Description: This cookie is used by the opt-in privacy policy to prompt the visitor to accept cookies again. It is set when you allow visitors to disable cookies. It contains the string "Yes" or "No."

  • Cookie Name: __hs_d_not_tracking
    Storage Duration: 6 months
    Description: This cookie can be set to prevent the tracking code from sending information to HubSpot. It contains the string "Yes."

  • Cookie Name: _hs_initial_opt
    Storage Duration: 7 days
    Description: This cookie is used to prevent banners from being displayed every time visitors access your website in strict mode. It contains the string "Yes" or "No."

  • Cookie Name: __hs_cookie_cat_pref
    Storage Duration: 6 months
    Description: This cookie is used to capture the categories a visitor has consented to. It contains data about those categories.

  • Cookie Name: __hs_gpc_banner_dismiss
    Storage Duration: 3 months
    Description: This cookie is used when the Global Privacy Control banner is dismissed.

  • Cookie Name: hs_ab_test
    Storage Duration: Until the end of the session
    Description: This cookie is used to ensure that visitors see the same version of an A/B test page they were shown previously. It contains the ID of the A/B test page and the ID of the variant selected for the visitor.

  • Cookie Name: __cfruid
    Storage Duration: Until the end of the session
    Description: This cookie is set by HubSpot's CDN provider in accordance with its rate-limiting policies.

  • Cookie Name: ___cfuvid
    Storage Duration: Until the end of the session
    Description: This cookie is set by HubSpot's CDN provider in accordance with its rate-limiting policies.

  • Cookie Name: ___cf_bm
    Storage Duration: Until the end of the session
    Description: This cookie is set by HubSpot's CDN provider in accordance with its rate-limiting policies.

Functional cookies

Functional cookies are used by third parties or publishers to display personalised advertisements. They do this by tracking visitors across websites.

Google Analytics

Cookie Name: _ga
Storage Duration: 2 years
Description: Used to distinguish between users.

Cookie Name: _gid
Storage Duration: 24 months
Description: Used to distinguish between users.

Cookie Name: _gat
Storage Duration: 1 minute
Description: Used to throttle the request rate. If Google Analytics is provided via Google Tag Manager, this cookie is named dc_gtm<property-ID>.

Cookie Name: hide-cookieinfo
Storage Duration: 30 days
Description: Cookie set for querying the cookies.

HubSpot

Cookie Name: __hstc
Storage Duration: 6 months
Description: The main cookie for visitor tracking. It contains the domain, the user token (hubspotutk), the first timestamp (of the first visit), the last timestamp (of the last visit), the current timestamp (for this visit), and the session count (increases with each subsequent session).

Cookie Name: hubspotutk
Storage Duration: 6 months
Description: This cookie tracks the identity of a visitor. This cookie is passed to the HubSpot software when submitting a form and is used for deduplicating contacts. It contains an opaque GUID to represent the current visitor.

Cookie Name: __hssc
Storage Duration: 30 minutes
Description: This cookie tracks sessions. It is used to determine whether the HubSpot software needs to increment the session count and timestamps in the __hstc cookie. It contains the domain, the number of page views (viewCount, increases with each page view in a session), and the session start timestamp.

Cookie Name: __hssrc
Storage Duration: End of session
Description: Whenever the HubSpot software changes the session cookie, this cookie is also set. It determines whether the visitor has restarted the browser. If this cookie is not present when HubSpot manages cookies, it is considered a new session. It contains the value "1" if present.

External media

Content from video platforms and social media platforms is blocked by default. If cookies from external media are accepted, access to this content no longer requires manual consent.

LinkedIn Tag

Cookie Name: bcookie
Storage Duration: 365 days
Description: Browser Identifier cookie to uniquely identify devices accessing LinkedIn to detect abuse on the platform and for diagnostic purposes.

Cookie Name: bscookie
Storage Duration: 365 days
Description: Used for remembering that a logged-in user is verified by two-factor authentication and has previously logged in.

Cookie Name: JSESSIONID
Storage Duration: Session
Description: Used for Cross-Site Request Forgery (CSRF) protection and URL signature validation.

Cookie Name: lang
Storage Duration: Session
Description: Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings.

Cookie Name: lidc
Storage Duration: 1 day
Description: To facilitate data center selection.

Cookie Name: sdsc
Storage Duration: Session
Description: Signed data service context cookie used for database routing to ensure consistency across all databases when a change is made. Used to ensure that user-inputted content is immediately available to the submitting user upon submission.

Cookie Name: li_gc
Storage Duration: 180 days
Description: Used to store consent of guests regarding the use of cookies for non-essential purposes.

Cookie Name: li_mc
Storage Duration: 180 days
Description: Used as a temporary cache to avoid database lookups for a member's consent for use of non-essential cookies and used for having consent information on the client side to enforce consent on the client side.

Cookie Name: UID
Storage Duration: 720 days
Description: Cookie used for market and user research.

Cookie Name: UserMatchHistory
Storage Duration: 30 days
Description: LinkedIn Ads ID syncing.

Cookie Name: AnalyticsSyncHistory
Storage Duration: 30 days
Description: Used to store information about the time a sync took place with the lms_analytics cookie.

Cookie Name: lms_ads
Storage Duration: 30 days
Description: Used to identify LinkedIn Members off LinkedIn for advertising.

Cookie Name: lms_analytics
Storage Duration: 30 days
Description: Used to identify LinkedIn Members off LinkedIn for analytics.

Cookie Name: li_fat_id
Storage Duration: 30 days
Description: Member indirect identifier for Members for conversion tracking, retargeting, and analytics.

Cookie Name: li_sugr
Storage Duration: 90 days
Description: Used to make a probabilistic match of a user's identity.

Cookie Name: _guid
Storage Duration: 90 days
Description: Used to identify a LinkedIn Member for advertising through Google Ads.

Cookie Name: BizographicsOptOut
Storage Duration: 10 years
Description: Used to determine opt-out status for non-members.

Cookie Name: li_giant
Storage Duration: 7 days
Description: Indirect identifier for groups of LinkedIn Members used for conversion tracking.

Cookie Name: oribi_cookie_test
Storage Duration: Session
Description: To determine if tracking can be enabled on the current domain.

Cookie Name: oribili_user_guid
Storage Duration: 365 days
Description: Used to count unique visitors to a website.

Cookie Name: ln_or
Storage Duration: 1 day
Description: Used to determine if Oribi analytics can be carried out on a specific domain.

Cookie Name: ar_debug
Storage Duration: Session
Description: Supports Google attribution reporting API integration to mitigate signal loss.

Lead Forensics

Cookie Name: __lfluuid
Storage Duration: 10 years
Description: The _lfuuid cookie allows a website to track visitor behavior on the sites on which the cookie is installed. Tracking is performed anonymously until a user identifies himself by submitting a form.

Changing privacy settings

Imprint

Data protection statement