{"id":22913,"date":"2024-04-24T11:10:10","date_gmt":"2021-09-17T19:01:00","guid":{"rendered":"https:\/\/www.bloomreach.com\/library\/why-bloomreach-is-the-best-experience-platform-for-composable-commerce"},"modified":"2024-06-11T18:12:55","modified_gmt":"2024-06-11T18:12:55","slug":"why-bloomreach-is-the-best-experience-platform-for-composable-commerce","status":"publish","type":"library","link":"https:\/\/www.bloomreach.com\/en\/blog\/why-bloomreach-is-the-best-experience-platform-for-composable-commerce","title":{"rendered":"Why Bloomreach Is the Best Experience Platform for Composable Commerce"},"content":{"rendered":"<p>The market is buzzing with the concept of <a href=\"https:\/\/www.bloomreach.com\/en\/blog\/why-bloomreach-is-the-best-experience-platform-for-composable-commerce\" rel=\"noopener noreferrer\" target=\"_blank\">\u2018Composable Commerce\u2019<\/a>. Organizations are disassembling old monoliths and replacing them with \u2018Packaged Business Capabilities\u2019, which provide units of functionality that can be easily integrated into a wider stack. In the past, this has been referred to as \u201cmicroservices\u201d, but the change here is the word \u2018composable\u2019.<\/p>\n<p>While some point solutions and integrators may bring some of the ingredients to the table, they do not make it easy for a marketer or a merchandiser to easily build, or compose, an experience.&nbsp; In order for an experience to be truly composable, the practitioner (merchandiser or marketer) must be able to create a campaign or landing page in a drag-and-drop graphical interface, which seamlessly talks to the technology underneath to make that campaign happen. You get to truly \u2018compose\u2019 the experience.<\/p>\n<p>There is a trend right now where some believe that you can simply patch together a group of point solutions, but there are disadvantages associated with that approach. In this post, we are going to examine how the Bloomreach technology stack provides you with more business impact by bringing more of these pieces under one roof.&nbsp; Specifically, it does this by:<\/p>\n<ol>\n<li>\n<p>Providing business teams with the ability to compose experiences in a low-\/no-code way<\/p>\n<\/li>\n<li>\n<p>Sharing data between capabilities (e.g. CDP and Search) to make these experiences more personalized and relevant<\/p>\n<\/li>\n<li>\n<p>Reducing the reliance on IT\/Partners\/Integrators<\/p>\n<\/li>\n<\/ol>\n<h3>Packaged Business Capabilities<\/h3>\n<p>Gartner divides the technology stack in the following way:<\/p>\n<ul>\n<li>Capabilities (e.g. Commerce) are built on stacks. Stacks have 3 layers \u2014&nbsp; Data, Logic, and View\/API<\/li>\n<li>An Experience Layer, which exposes Capabilities to customers<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"\" src=\"https:\/\/www.bloomreach.com\/wp-content\/uploads\/2024\/05\/content-2-at-2x-1.png\" \/><\/p>\n<p>The whole idea behind composable commerce is that you break up your technology into distinct pieces and orchestrate them from an experience perspective. The challenge with that is that there is still a lot of information that needs to flow between the individual pieces of the stack to provide a cohesive experience for the customer.<\/p>\n<p>For example, as a merchandiser or marketer,&nbsp; I want to serve personalized experiences to my customers. In order to do this, I need to segment customers inside a CDP and pass that information in real-time to both the search and website engines. I also need to pass signals back from the search engine and website about each customer\u2019s affinities and preferences.&nbsp;<\/p>\n<p>In order for the CMS platform to show the right <a href=\"https:\/\/www.bloomreach.com\/en\/blog\/why-product-recommendations-are-key-to-winning-with-e-commerce-personalization\">recommended products<\/a> on a personalized campaign landing page, it needs information from both the CDP and the search engine.&nbsp;<\/p>\n<p><img decoding=\"async\" alt=\"\" src=\"https:\/\/www.bloomreach.com\/wp-content\/uploads\/2024\/05\/content-3-at-2x.png\" \/><\/p>\n<p>In other words, the above graphical representation is a bit simplistic. In reality, it looks more like this with lots of information being passed between the different stacks:<\/p>\n<p><img decoding=\"async\" alt=\"\" src=\"https:\/\/www.bloomreach.com\/wp-content\/uploads\/2024\/05\/content-4-at-2x.png\" \/>There is a clear danger here in over-fragmenting our Packaged Business Capability. We can easily turn our entire business into a bunch of point solutions that drive up our reliance on IT\/Integrators. As a consequence, we would reduce the business team\u2019s ability to react to the changing demands of its customers.<\/p>\n<p>What can we do instead? We can still break our stack into pieces while maximizing the value for business users by packaging the component at the point that makes the most sense for the use case. If you just want to address a search use case, take that&nbsp;component \u2014&nbsp; but if you want a fully personalized experience, take the packaging around the DXP + Search and Content.<\/p>\n<p>This is ultimately why Forrester&nbsp;analyst <a href=\"https:\/\/www.forrester.com\/blogs\/buy-an-integrated-platform-not-a-box-of-rocks\/\" rel=\"noopener noreferrer\" target=\"_blank\">Joe Cicman in his post says there is a need for an \u201cintegrated DXP, not just a box of rocks.\u201d<\/a><\/p>\n<p>A box of separate rocks means that you\u2019ll need additional ongoing effort to integrate, design new business workflows (that may or may not exist in a no-code environment), manage third parties, write specifications, QA, triage faults, raise fault tickets, and all the other endless issues which are entailed in orchestrating loosely coupled systems.<\/p>\n<h3>Finding the Sweet Spot<\/h3>\n<p>At Bloomreach, we believe we\u2019ve found the sweet spot \u2014&nbsp; a way for our individual pillars (<a href=\"https:\/\/www.bloomreach.com\/en\/products\/engagement\" rel=\"noopener noreferrer\" target=\"_blank\">Engagement<\/a>, <a href=\"https:\/\/www.bloomreach.com\/en\/products\/discovery\" rel=\"noopener noreferrer\" target=\"_blank\">Discovery<\/a>, and <a href=\"https:\/\/www.bloomreach.com\/en\/products\/content\" rel=\"noopener noreferrer\" target=\"_blank\">Content<\/a>) to act as individual Packaged Business Components, which build together to form a larger Business Component that seamlessly shares signals at the API, logic, and data layers. This saves our customers countless hours and cycles with IT\/Integrators and frees them up to enable the business to meet the demands of its customers.&nbsp;<\/p>\n<p>Customers are free to start with a single \u201cPackaged Business Capability&#8221;. For example, they can start with Search and add others as and when the business need arises, working toward a goal of a fully evolved, <a href=\"https:\/\/www.bloomreach.com\/en\/blog\/composable-commerce\">Composable Commerce<\/a> Architecture.&nbsp;<\/p>\n<h3>Evolved Composable Commerce Architecture<\/h3>\n<p>As you can see from the diagram below, the Bloomreach platform includes a number of Packaged Business Capabilities \u2014&nbsp; namely, <a href=\"https:\/\/www.bloomreach.com\/en\/products\/engagement\" rel=\"noopener noreferrer\" target=\"_blank\">Engagement <\/a>(CDP\/Marketing Automation), <a href=\"https:\/\/www.bloomreach.com\/en\/products\/discovery\" rel=\"noopener noreferrer\" target=\"_blank\">Discovery<\/a> (Search), and <a href=\"https:\/\/www.bloomreach.com\/en\/products\/content\" rel=\"noopener noreferrer\" target=\"_blank\">Content<\/a>. These capabilities stand alone and perform exceptionally on their own. However, when a customer implements multiple, the fact that they can share signals and data in a truly composable fashion brings to life the ultimate promise of composable commerce. It allows the business to define and iterate on customer experiences \u2014&nbsp; across all touchpoints \u2014&nbsp; and on the fly (without having to call IT).&nbsp;<\/p>\n<p><img decoding=\"async\" alt=\"\" src=\"https:\/\/www.bloomreach.com\/wp-content\/uploads\/2024\/05\/content-5-at-2x.png\" \/><\/p>\n<p>In summary, there are some key points worth noting:<\/p>\n<ul>\n<li>Our Individual Packaged Business Components (<a href=\"https:\/\/www.bloomreach.com\/en\/products\/engagement\" rel=\"noopener noreferrer\" target=\"_blank\">Engagement<\/a>, <a href=\"https:\/\/www.bloomreach.com\/en\/products\/discovery\" rel=\"noopener noreferrer\" target=\"_blank\">Discovery<\/a>, and <a href=\"https:\/\/www.bloomreach.com\/en\/products\/content\" rel=\"noopener noreferrer\" target=\"_blank\">Content<\/a>) can stand alone and provide significant benefit on their own.<\/li>\n<li>When implemented together into a larger Packaged Business Component, the unified data layer (shared understanding of people, products, and segmentation) brings a rich set of customer understanding into the platform, which saves the customer integration effort and frees them up to achieve business benefits.<\/li>\n<li>Our Engagement (<a href=\"https:\/\/www.bloomreach.com\/en\/blog\/customer-data-platform\">CDXP<\/a>) Capability, extending over the top of the architectural stack, provides the orchestration of customer experiences, which enables overarching business benefits. For example, composing campaigns on the fly, creating lifetime customer analysis or dynamic segmentations, and utilizing these within landing pages and product grids \u2014&nbsp; all from a low-\/no-code interface. (Gartner identifies this as a characteristic of <a href=\"https:\/\/www.bloomreach.com\/en\/blog\/composable-commerce\">Composable Commerce<\/a>).<\/li>\n<\/ul>\n<p>To cite Joe Cicman, who writes about what an <a href=\"https:\/\/www.forrester.com\/blogs\/buy-an-integrated-platform-not-a-box-of-rocks\/\" rel=\"noopener noreferrer\" target=\"_blank\">\u201cintegrated DXP\u201d <\/a>means: \u201cA DXP that integrates <a href=\"https:\/\/www.bloomreach.com\/en\/blog\/the-ultimate-guide-to-journey-orchestration\">journey orchestration<\/a> into a single pane of glass is good and helpful. A DXP that offers content up to another vendor\u2019s journey orchestration tool is just doing what\u2019s expected of any service that can be orchestrated.\u201d<\/p>\n<p>In other words, with a fully integrated <a href=\"https:\/\/www.bloomreach.com\/en\/blog\/apis-microservices-transforming-shopping-experience\">DXP<\/a>, running your business is less stressful. Your business is more responsive to the needs of your customers as you can write processes, create landing pages, or manage product grids without any coding. You spend less time raising IT tickets, thinking about problems with integrations, or negotiating unexpected limitations of point solutions.&nbsp;&nbsp;<\/p>\n<h3>Evolved Composable Business Capabilities<\/h3>\n<p>Bringing individual functional areas into a Packaged Business Capability not only allows us to share signals easily between functions&nbsp;but it also serves the ultimate goal of Composable Commerce: experience orchestration for the business user.<\/p>\n<p><img decoding=\"async\" alt=\"\" src=\"https:\/\/www.bloomreach.com\/wp-content\/uploads\/2024\/05\/content-1-at-2x-1.png\" \/><em>Experience Orchestration using Bloomreach Scenario Builder<\/em><\/p>\n<p>In the diagram above, a practitioner needed to build a retention campaign to encourage a second purchase. They have built out a scenario using our drag-and-drop UI, which reacts to customers based on recency\/frequency\/monetary analysis of their engagement with the company. The process implements a number of automated strategies (e.g. re-engagement emails or texts) to get customers who are at risk of being lost to re-engage. When customers click on the communications, they land on <a href=\"https:\/\/www.bloomreach.com\/en\/blog\/2019\/07\/digital-commerce-explained\">personalized landing pages<\/a> and become loyal customers, or even champions for the brand.<\/p>\n<h3>Conclusion<\/h3>\n<p>The Bloomreach architecture represents a sweet spot that helps our customers on their journey from monoliths through to Packaged Business Component and then on to achieving the ultimate goal of <a href=\"https:\/\/www.bloomreach.com\/en\/blog\/composable-commerce\">Composable Commerce<\/a>: true composability for the business user.<\/p>\n<p>If you want to learn more about this topic or how Bloomreach can set your business up for ultimate success, <a href=\"https:\/\/www.bloomreach.com\/en\/demo\" rel=\"noopener noreferrer\" target=\"_blank\">schedule a personalized demo with our team<\/a>.&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The market is buzzing with the concept of \u2018Composable Commerce\u2019. Organizations are disassembling old monoliths and replacing them with \u2018Packaged Business Capabilities\u2019, which provide units of functionality that can be easily integrated into a wider stack. In the past, this has been referred to as \u201cmicroservices\u201d, but the change here is the word \u2018composable\u2019. While [&hellip;]<\/p>\n","protected":false},"author":101,"featured_media":22081,"template":"","ew-regions":[],"ew-solutions":[],"library_type":[513],"library_blog_tag":[362,366,370,449,371],"industry":[],"channel":[268],"topic":[],"class_list":["post-22913","library","type-library","status-publish","has-post-thumbnail","hentry","library_type-blog","library_blog_tag-ai-and-innovation","library_blog_tag-ecommerce-search","library_blog_tag-headless-commerce","library_blog_tag-privacy-and-security","library_blog_tag-product-recommendations","channel-email"],"acf":{"library_blog_banner_content":"","library_blog_banner_cta1_text":"","library_blog_banner_cta1_href":"","library_blog_banner_cta1_new_tab":false,"library_blog_banner_cta2_text":"","library_blog_banner_cta2_href":"","library_blog_banner_cta2_new_tab":false,"library_blog_banner_bg_color":"#EAF7FE","library_blog_banner_cta_text_color":"#FFF","library_blog_banner_cta_bg_color":"#019ACE","library_blog_banner_cta2_text_color":"#000","library_blog_banner_cta2_bg_color":"#FFF","library_blog_chatgpt_content":"","library_blog_chatgpt_cta_href":"","library_blog_chatgpt_cta_text":"Ask ChatGPT"},"_links":{"self":[{"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/library\/22913","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/library"}],"about":[{"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/types\/library"}],"author":[{"embeddable":true,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/users\/101"}],"version-history":[{"count":0,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/library\/22913\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/media\/22081"}],"wp:attachment":[{"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/media?parent=22913"}],"wp:term":[{"taxonomy":"ew_regions","embeddable":true,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/ew-regions?post=22913"},{"taxonomy":"ew_solutions","embeddable":true,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/ew-solutions?post=22913"},{"taxonomy":"library_type","embeddable":true,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/library_type?post=22913"},{"taxonomy":"library_blog_tag","embeddable":true,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/library_blog_tag?post=22913"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/industry?post=22913"},{"taxonomy":"channel","embeddable":true,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/channel?post=22913"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/www.bloomreach.com\/en\/wp-json\/wp\/v2\/topic?post=22913"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}