Integrating Content and Commerce

EXPERIENCE-
DRIVEN
COMMERCE
Technology Patterns for
eCommerce Web Deployments

EXPERIENCE-DRIVEN COMMERCE COREMEDIA.COM
Martin Tavener joined IBM in March 2000, having
previously worked in the travel and transport
industryin both technical and management roles.
Since joining IBM, Martin has spent most of his
time working as a software architect with many
of IBM’s UK Retail clients and advising them on
both technical and business strategy.
As the UKI CTO for Customer Engagement
Solutions,Martin works closely with some of IBM
Commerce’s flagship accounts, for whom he
coordinates sales, technical sales and product
management.
Jochen Toppe joined CoreMedia in 2013 as Vice
President of Product Management and UX, having
previously worked in various roles on the client,
product and agency side.
Jochen has a long history of shaping strategic
brand and eCommerce experiences, having led
key customer initiatives in Europe and the US.
He is now responsible for the strategic develop-
ment of the company’s key offerings, including
CoreMedia’s digital experience platform for IBM
WebSphere Commerce.
Offering your customers a great digital experience across all touchpoints is, according to Forrester, “no longer a nice-to-have,
it’s a make-or-break point for your business as we more fully enter the digital age.”1
However, successfully delivering an
engaging and informative digital customer experience – particularly when this experience combines both branded content
and product data – can be extremely difficult.
This white paper examines the integration patterns that have emerged and compares and contrasts their respective merits.
This is not just a topic for solution architects or those with a technical focus but a topic for eCommerce directors too, as the
choices made have a significant impact on business issues, i.e.:
›› Operational efficiency
›› Speed in delivering new functionality to your customers
›› Initial project duration
›› Investment required
It is worth noting that some organizations have already built integrations between their commerce systems and their content
systems. The focus on this topic in the eCommerce and vendor communities has grown markedly in the past 2 years, so more
options are available, and they display a higher level of maturity. However, these options still have their own strengths and
weaknesses, and these require careful consideration.
EXECUTIVE SUMMARY
ABOUT THE AUTHORS
1
Forbes.com – Forrester: Top Technology Trends for 2014 and Beyond – http://www.forbes.com/…

EXPERIENCE-DRIVEN COMMERCE –
BRINGING CONTENT AND COMMERCE TOGETHER
Shoppers today want to do more than simply transact. They
want to interact with the brand, explore different product
categories, converse with their peers, obtain product tips and
see products in a real-world context. The actual purchase
and fulfillment process is really just one part of a much
broader customer journey that many people are beginning to
call “experience-driven commerce.”
According to the 2016 IBM Guide to Retail Technology,
“Consumers now expect retailers to provide an online expe-
rience that is optimized for their mobile devices. They want
shopping to be smooth, uncomplicated and personalized,
regardless of where they are or what device they may be
using. They also expect speed and responsiveness when they
do research, buy an item or change an order.” Additionally,
customers expect retailers “to enrich the in-person experi-
ence with relevant digital content and drive more personal-
ized one-on-one engagement than ever before.”2
Until now, however, it’s been extremely difficult for retailers
to deliver the kind of content-based emotional shopping
experiences that help organizations to succeed across
multiple channels. Part of the problem is cultural. Digital
marketing and eCommerce teams have traditionally worked in
separate worlds with different content, processes and goals.
Marketers are focused on creating deeper customer engage-
ment with the brand, while eCommerce teams have laser
vision on product sell-through and revenues. This problem is
compounded by a similar disconnect at the technology level.
Marketing teams typically rely on web content management
and marketing automation tools to reach customers, while
commerce teams depend upon their eCommerce platform.
The variation in experience can be so abrupt that customers
end up confused and not at all pleased with their experience.
Forrester identified the reason why as early as 2013, in their
“Commerce and Content” report, where they comment that
the end result is often “a fragmented and poorly integrated
digital presence that confuses the customer, is difficult to
manage and – ultimately – leaves revenue on the table.”3
What’s surprising is that this is still the case today, with most
companies unaware and in the dark about the severity of this
disconnect. A recent study by IBM and eConsultancy4
found
that 81 % of companies believe they have – or are close to
having – a holistic view of their customers, yet only 37 % of
consumers feel that their favorite brands understand them.
Clearly, something has to change.
Unifying the customers’ shopping and brand experiences re-
quires a concerted effort of marketing and eCommerce teams.
Siloed teams and missions must be aligned, along
with the disconnected technologies that often compound the
problem. Technology should enable customers to shift seam-
lessly across multiple channels and eliminate unnecessary
confusion and friction. Collaboration and workflow tools that
expand visibility – along with the teams that use them – need
to work effectively together rather than in silos. A range of key
technologies must be effectively combined to deliver inspi-
rational customer journeys in an eCommerce environment,
including Commerce Servers, Content Management Systems
(CMS), Digital Asset Management (DAM) and more. The integra-
tion of these technologies has traditionally been a challenge,
and a number of integration patterns have emerged as
potential best practices. Whether the Commerce Server or the
Content Management System own the customer experience,
or potentially both at the same time, has a crucial influence
on the customer experience, the ease of management of the
experience and the overall cost of ownership and speed-to-
market. Utilizing a CMS that includes DAM capabilities helps to
simplify the integration.
However, selecting the right integration model for your com-
pany is not a simple decision. This paper will introduce you to
the four leading approaches – commerce-led, content-led,
hybrid and headless integration – and will offer practical
guidelines on how to select the best model for your organiz-
tion and your customers. Implementing a seamless, real-time
integration of content and commerce is not something that
can be accomplished overnight, but it doesn’t need to be a
show-stopper either. By selecting the right model and adopt-
ing an iterative approach that allows you to leverage your ex-
isting investments while laying the groundwork for long-term
competitive advantage, you can deliver seamless multi-chan-
nel customer experiences that win new customers, encourage
repeat purchases, attract brand advocates and grow revenue.
2
2016 IBM Guide to Retail Technology Trends – http://www-01.ibm.com/…
3
“Content And Commerce: The Odd Couple Or The Power Couple?”, by Stephen Powers, Peter Sheldon, Forrester Research, November 19, 2013
4
“The Consumer Conversation”, by Stefan Tornquist, eConsultancy, April, 2015

PATTERNS FOR INTEGRATING ECOMMERCE AND CONTENT
eCommerce systems have traditionally focused on facilitating transactions and managing product content. Although most
eCommerce systems include the ability to create and manage the front-end store experience, their built-in editorial functional-
ity is not comparable to what is typically found in an enterprise Content Management System (CMS). The opposite is true of most
CMS platforms. They are excellent tools for building content-based experiences, but they typically lack a rich integration into
the eCommerce systems.
Traditionally, CMS and eCommerce systems have been deployed as entirely separate technologies. In some cases, they are
even positioned competitively, with each technology striving to own the direct interaction with the consumer. In order to provide
eCommerce customers with the right content at the right time in the right place, however, the worlds of transactions and con-
tent need to come together as part of a single experience. Bringing these worlds together requires the underlying technologies
to come together too. The four major integration patterns are: commerce-led, content-led, hybrid and headless integration.
We’ll examine each approach separately and consider the potential impact from an organizational, technological and consum-
er perspective. Following this analysis, we’ll summarize the key benefits and drawbacks of each approach and provide some
guidelines for selecting the best approach for your company.
OPTION #1:
COMMERCE-LED INTEGRATION
In this approach, the eCommerce system is responsible for delivering the primary front-end experience, thus owning the direct
interaction with the consumer. The CMS delivers content fragments to the eCommerce system, which incorporates it into
the existing store template and delivers the assembled page to the consumer. This pattern is often used when the consumer
view requires more catalogue views than content.
This has been the traditional way to integrate these systems as it requires the least effort to accomplish. To add a layer of
complexity, a number of eCommerce systems provide basic content management functionality, which lessens the need for
an additional, integrated CMS. However, the need for combined content and commerce experiences extends beyond the
online store. There is also a need to bring eCommerce functionality into existing brand sites. This requires more mature content
management capabilities that exceed the limits of the built-in CMS functionality of most eCommerce systems. Other use cases
that require more advanced CMS functionality include: the need to manage large amounts of content, the integration
of rich media assets, such as images and videos, dynamic text and image, translation and localisation of content for multi-na-
tional brands, quick publication to cater for fast-moving social channels and personalizing content to the individual user.
CMS
DAM
Commerce Server
Consumer

Organizational Impact
Unless the content management system features a deep level
of integration with the eCommerce system, this integration
approach may force marketers to manage content assets and
content placement in both systems simultaneously – result-
ing in a tedious and error-prone process, particularly when
you are managing large amounts of content. However, for
sites with many products and limited content requirements, it
strikes a solid balance between content creation and cata-
logue management.
From an organizational perspective, keeping the eCommerce
system and the CMS separate can be an advantage. While it
should be the goal of any customer focused organization to
break down internal silos, many companies still have separate
units for creating different customer experiences. Merging
these units is not something that can happen overnight.
Giving the marketing team access to parts of the commerce
experience and expanding their reach slowly may provide a
more graceful transition to an experience-driven joint eCom-
merce organization.
Consumer Impact
Compared to a standalone eCommerce system, commerce-
led integration provides consumers with more helpful content
within the eCommerce environment to drive increased brand
engagement – from individual page elements to entire pages.
However, the web store, is still predominantly a transaction-
based experience.
Companies wishing to gain a greater level of engagement
and competitive differentiation must ensure that the solution
chosen can evolve to support more advanced use cases such
as personalization of both products and brand experiences.
Not only should product selection be personalized for a
certain audience-content selections need to meet the same
criteria too.
Technology Impact
When the key elements of the consumer experience are split
between the CMS and the eCommerce system, development
(of templates for example) and management must take place
in both systems. If the two systems are clearly separated,
this might not result in redundant development, but it needs
to be considered. Without a deeply integrated CMS, many
advanced use cases such as user unified search, banner
personalization, campaign scheduling and the blending of
content with real-time pricing will require significant custom
development efforts.
If the commerce system is not deeply integrated into the
CMS preview, it might be necessary to unify the authorization
of the management user interfaces (UIs) across both systems
via a Single-Sign-On system.
In addition, an increasing number of consumers browse the
content in web stores as a way of researching products for
future purchase, a practice known as “webrooming”. In a
commerce-led environment, where all content is ultimately
published by the eCommerce system, this can place an unex-
pectedly heavy load on the Commerce Servers, which may not
be designed for this kind of traffic.

OPTION #2:
CONTENT-LED INTEGRATION
In this model, the CMS system fronts the consumer experience completely, integrating the eCommerce system via an applica-
tion programming interface (API), typically Representational State Transfer-based (REST-based). From a customer engagement
perspective, this may seem like the perfect approach. It makes it much easier to deliver content-rich consumer experiences
that go beyond the purely transactional and can be tailored to provide personalized experiences and a consistent look and feel
across multiple eCommerce sites, brand sites and other touchpoints. This approach unlocks the full potential of a sophisticated
CMS solution and allows both marketers and merchants to work in their preferred tools with less jumping between UIs. Advanced
CMS-centric capabilities such as personalization are easily leveraged everywhere.
This approach is typically chosen by companies with extensive technology development capability and an appetite for large,
innovative projects. These companies tend to be committed to providing the best possible customer experience across all digi-
tal touchpoints – and less inclined to perform a cost/benefit analysis around business change.
The content-led approach requires organizations to adopt
a marketing-centric approach to the creation and manage-
ment of eCommerce experiences. As such, it will have the
most dramatic impact on organizations where consumer
experiences are still managed in silos – for example, with
different units managing mobile and web interactions with
entirely separate brand and eCommerce sites. This approach
may force teams to work in a much more coordinated fashion
than they are used to doing, which may require you to spend
more time on training and change management processes.
It is important to note that the CMS is in charge of fronting
the check-out process in this model, and consequently handles
all financial payments and associated Personally Identifiable
Information (PII). This means that the solution may need to be
Payment Card Industry (PCI) certified. The Payment Card Indus-
try Data Security Standard (PCI DSS) is an information security
standard that governs how companies handle data from the
major card corporations including Visa, MasterCard, American
Express, Discover and JCB. All businesses that process, store
or transmit payment card data are required to implement
the standard to prevent cardholder data theft. Any company
planning to build a solution based on this integration approach
will need to factor PCI certification into their project.
Consumer Impact
From a consumer perspective, this approach can provide
an excellent experience for the broadest possible range of
shopper types. Shoppers have always had different personal-
ities. They are motivated to buy for all kinds of reasons, and
their shopping strategies can be radically divergent. Some
shoppers know exactly what they want; others are looking
for inspiration. Some are extremely price-conscious; others
are looking for a specific brand experience. The traditional
product- and catalog-driven eCommerce site with its focus on
transactions and fulfillment doesn’t allow for brand and prod-
uct stories that are personalized and based on the context of
the customer. Although a well-implemented commerce-led
solution can address some of these challenges, it can be
extremely difficult, expensive and time-consuming to extend
these benefits across multiple sites and regions. Also, the
experience will always be constrained by the limitations of
the front-end Commerce Server, which was not designed to
deliver content-based experiences.
This is particularly true for companies looking to deliver
content to multiple touch points, including mobile, tablet,
desktop, Smart TV and in-store experiences. It provides the
shopper with consistent brand interaction in today’s diverse
digital world.
Commerce Server
DAM
CMS
Consumer

Technological Impact
One of the most obvious advantages of this approach is that
the coding of front-end templates is managed in a single sys-
tem. However, this approach also presents some significant
challenges that may increase the amount of effort required to
implement an experiential commerce solution.
Experience has shown that the level of jumping between
UIs that a marketer has to do to accomplish everyday tasks
depends on how much has been invested in rebuilding the
commerce system management tools in the CMS editing
environment. If there hasn’t been substantial investment in
this area, a commerce-led and content-led approach will feel
fairly similar to the marketing and eCommerce teams.
Most eCommerce systems provide in-depth marketing and
personalization tools that allow you to deliver targeted prod-
ucts and promotions based on a consumer’s shopping history,
behaviour and general profile data. Many CMS systems offer
their own personalization tools for content delivery. In order to
take full advantage of the data stored in the Commerce Server
and deliver experiences that combine personalized content
and product data, the CMS personalization engine must be
deeply integrated with the eCommerce personalization tools.
Product information – including pricing and inventory – must
be published on the site in real time. The final price that each
shopper sees depends on a range of factors including profile
data, coupons, geography and many more factors. Inventory
levels determined in real-time have a significant impact on
the experience too. Depending on business rules, products
and related content may or may not be featured if they are out
of stock, and the site experience needs to adapt according-
ly. Special care has to also be applied to shop performance
for these real-time actions. Requests from the browser hit
the CMS first and may then be delegated to the eCommerce
system via the CMS’s eCommerce APIs, adding an additional
REST-based call and additional overhead. The amount of
REST calls and their impact on performance should not be
underestimated.
Search capability needs to effectively work across both the
content and product worlds, honoring personalization and
“searchandising” rules set up in the eCommerce system.
Unless the CMS is already pre-integrated, the amount of
effort and risk involved in implementing a solution based on
this model in a customized fashion is significant and would
require very careful consideration of time, costs and degree
of disruption to existing operations. Also, many eCommerce
systems are not fully API-enabled, which creates an
additional challenge to integration.

OPTION #3:
HYBRID INTEGRATION
The hybrid integration model attempts to bring the best of the content-led and commerce-led approaches together. A typical
approach involves giving the CMS responsibility for delivering the experience up to the checkout process, at which point the
eCommerce system takes over, hence eliminating the need for PCI compliance within the CMS. Other scenarios are also possi-
ble – hybrid integration is the most flexible approach, and it even allows for evolution over time. For example, you could elect to
serve all campaign pages and commerce-enabled brand sites directly from the CMS while providing product detail pages from
the eCommerce system. You could also choose to serve up “long-tail” product data from the Commerce Server and experi-
ence-driven “short-tail” products from the CMS.
From an organizational perspective, this approach allows you
to more precisely tailor the management of the experience
to the needs of the organization. Any component, page or site
section can be managed either by the CMS or by the eCom-
merce system, making it the “Swiss army knife” of eCom-
merce integrations. The functional separation of teams can
be maintained without sacrificing the unity of the customer
experience. The commerce team administers the buying
experience, the content team administers the content ex-
perience and the creative team puts the digital assets into a
digital asset management repository for all to use. In order
for this approach to work, however, someone must take re-
sponsibility for ensuring that all of the separate parts cohere
into a single seamless experience for consumers.
Consumer Impact
The impact from a consumer perspective depends on how
closely this integration is tailored either towards the content-
led or the commerce-first integration approach. In the scenario
in which only checkout is handled by the eCommerce system,
the experience will feel virtually identical to the content-led
approach.
Technology Impact
Like the commerce-led approach, this approach may require
front-end templating to be managed in two systems. The
difference with this model is that the CMS can easily manage
the majority of design elements for both content-driven and
commerce-driven pages, including headers, footers and
navigation. By allowing both the commerce and content
systems to deliver pages, the potential performance problem
associated with “webrooming” (non-commerce related traffic
generating load on the commerce servers) is easily alleviated.
The biggest challenge of this approach is to ensure that the
CMS and eCommerce systems appear as one cohesive expe-
rience to the consumer. To facilitate a seamless hand-off be-
tween the browsing experience and the checkout process, the
user’s session needs to be shared between the two systems.
Losing your shopping basket and login information at the time
of handover is simply not an option. A solution with a pre-in-
tegrated content management system should support this
out of the box, but custom solutions tend to be complex, and
due consideration needs to be given to the non-functional
requirements, especially in the area of security in which cus-
tomers’ personal and payment details are being processed.
Another challenge, which is present to some degree in the
other two approaches as well, is synchronizing the published
assets across systems. Most effective CMS systems are
designed to publish content in near real time, while product
catalogue information tends to be staged nightly. As content
management and commerce systems become more inter-
twined, however, content publication processes will become
increasingly dependent on product data availability and vice
versa. As such, the synchronization of the assets managed
in each system becomes a concern. A deeply integrated CMS
can leverage catalogue information dynamically and automat-
ically hide any content items (e.g. promotional banners) linked
to products that have not been staged yet.
DAM
Consumer
CMS
Commerce Server

The headless integration approach is, strictly speaking, a variation of the hybrid integration approach. However, rather than the
CMS or the eCommerce system rendering pages or parts of pages, both only provide a set of web services APIs (REST-based).
The eCommerce engine exposes all commerce functionality, from the product information to user profile information and trans-
actional behavior such as basket and checkout. The CMS exposes the ability to deliver individual content, assets or even entire
pages – especially for marketing or content-heavy pages. Typically, the CMS will also create static shells of the pages with
content purely for search engine optimization. The end user experience is then created dynamically using front-end technolo-
gies, for example client-side templating or frameworks such as Angular, Handlebar, or ReactJS. Additionally, this code can run
either directly in the browser, on the server side or in both places at once – a pattern called isomorphic Javascript. This allows
the developer to carefully balance the need between search engine optimization, page load times and responsiveness of the
user interface.
OPTION #4:
HEADLESS INTEGRATION
In a similar way to the hybrid integration approach, the
management of the experience can be tailored to match the
organizational readiness and needs – no matter whether it is
to be more content-centric or product-centric.
Deep integration between the CMS and the eCommerce server
is still required in order to manage this blended experience.
The ability to preview pages can be challenging, as they
are dynamically assembled outside both the CMS and the
eCommerce system. For this reason, choosing an integrated
solution stack with the flexibility to handle this architecture
in order to provide a seamless management experience with-
out IT involvement is an imperative.
Consumer Impact
For the consumer, this architecture will result in a completely
blended experience, with no divide between transactional
eCommerce and branded content. Also, as APIs can be called
from any rendering technology – be it a native app or a smart
TV - a true omni-channel experience can be created.
In fact, new business models can thrive in this approach, giv-
ing more flexibility to the consumer. Exposing the eCommerce
and experience management functionality as REST-based
services leads to an API-first approach. Opening these APIs up
to third-party developers can foster an ecosystem of inno-
vation outside of the shop. Companies such as Best Buy are
a prime example of retailers that have opened up their APIs
from product selection to checkout to third party developers,
who in return have created numerous applications that prop-
agate their brand and often offer direct in-app purchase. In
this scenario, it is advisable to leverage an API management
technology to handle versioning, authentication and usage
enforcement.
Technology Impact
The greatest advantage of this approach is the ability to
create the end user experience directly from re-usable web
services. As such, the final experience doesn’t need to be a
web page, but the REST services could also be called from a
native application on a phone, tablet or third party applica-
tion. This makes this approach the ultimate omni-channel
architecture. Templating can also be managed in a central
place instead of in two or more applications.
Also, aggregate website performance may be higher. In con-
tent-led integration, most web service requests hit the CMS
first and are then potentially delegated to the eCommerce
system from the CMS’s eCommerce APIs. This additional step
can optionally be removed in headless integration, and the
front end can call the individual back-end system directly.
On the flip side, this architecture hasn’t been widely adopted
by players except for larger, technology-focused organiza-
tions. One reason might be the higher development cost,
which is a result of the need to re-architect the technology
landscape - and the need ton be on a very recent version of
the eCommerce system in which fully REST-based APIs are
available.
REST
DAM
Consumer
CMS
Commerce Server
Front-End
Technology
REST

CONCLUSION
A winning customer experience is one that delights customers across all channels, combining rich visuals, product information,
branded content and transactional commerce functionality in one single seamless package. All four scenarios outlined can play
an important role in bringing together content and eCommerce and, in more sophisticated setups, multiple scenarios may come
into play at once. There is no simple way of deciding which scenario is right for a company, and there is no one-sizefits-
all solution. Selecting the technology that provides for the freedom to choose the approach that is most well-suited is key.
Choosing the Right Model for Your Business
All four models outlined are able to bring content and com-
merce together. Each approach has both unique benefits and
disadvantages, and in many sophisticated setups, more
than one integration scenario will come into play at once.
The content-led, hybrid and headless integration scenarios
achieve seamless integration across content, commerce and
delivery channels – be they web, mobile web, app, tablet
or kiosk applications. Be careful when choosing a content
management system, though. The most important consid-
eration is to choose a Content Management System that can
address all the common pitfalls outlined above and bring
the content and commerce system together to create a
seamless experience for consumers, as well as the mer-
chants and content marketers behind the scenes.
Many companies may not be mature enough from a tech-
nological or organizational perspective to successfully
implement a customer-experience-centric strategy. This
includes the ability to overcome organizational silos in order
to centrally manage content and activities across teams. The
same holds true for marketing and eCommerce technolo-
gies, which should allow for a single view of the customer on
a seamless platform. Using the commerce-first integration
scenario is a good way to get started, and it will allow you to
improve the customer experience very quickly. Testing the
content-led approach in isolated sites or markets before
gradually moving towards a more experience-driven approach
is a great way to move at your own pace and mitigate the risk
and disruption caused by an expensive and time-consuming
“rip and replace” approach.

Copyright 2017. CoreMedia Corporation. All rights reserved. IBM and IBM WebSphere Commerce
Cloud are registered trademarks of IBM.com, Inc. in the United States and in several other coun-
tries. All other trademarks are the property of their respective owners.
IBM & COREMEDIA: A POWERFUL COMBINATION
CoreMedia’s solution is based on a deep integration between
two exceptional enterprise technology providers: CoreMedia
and IBM. CoreMedia’s fully productized and IBM-validated
offering ensures that you can innovate quickly, reduce
implementation costs, and protect existing investments while
maximizing both platforms. Each system is utilized for its
strengths. IBM WebSphere Commerce provides a powerful
customer interaction platform for cross-channel commerce.
CoreMedia is an expert at managing content and delivering
engaging, contextual customer experiences across all touch-
points. CoreMedia and IBM are working together to help you
reduce production costs, accelerate time-to-web, and increase
the quality of your customers’ shopping experiences — leading
to higher average revenue per visitor, more repeat customers,
and enhanced organic web traffic. The CoreMedia Content
Experience Platform is available as a subscription-based
service in CoreMedia on Cloud or can be installed on-premises
or in a private cloud environment.
For more information, please visit our website: www.coremedia.com

Integrating Content and Commerce

More Related Content

What's hot (20)

Similar to Integrating Content and Commerce (20)

Recently uploaded (20)

Integrating Content and Commerce