#evolverocks

Introduction to Adobe Experience Manager Based eCommerce

VARUN MITRA | PARTNER TRAINING INSTRUCTOR

August 30th, 2016

2#evolverocks

Introduction to Adobe Experience Manager Based eCommerce

1 | Introducing the eCommerce Framework2 | eCommerce Concepts with Elastic Path3 | Catalog blueprint and section blueprint capabilities4 | Identifying Best Practices for Stores

3#evolverocks

Introducing the eCommerce FrameworkeCommerce Architecture

4#evolverocks

AEM eCommerce ArchitectureThe Adobe Experience Manager eCommerce architecture consists of four layers:1. eCommerce components

Adobe Experience Manager eCommerce components provide the front-end functionality and the shop as viewed by the user. They rely on the eCommerce API to retrieve product data and perform actions related to the commerce eCommerce engine.

2. eCommerce API The central piece of the Adobe Experience Manager eCommerce architecture is the

Adobe Experience Manager eCommerce API. Based on the API, front-end components can be built to implement an eCommerce application.

The Adobe Experience Manager eCommerce API is fixed, and cannot be adapted.

5#evolverocks

AEM eCommerce Architecture

3. eCommerce provider implementation The eCommerce API can be implemented to integrate with a third-party eCommerce

application, or you can create a custom (native) implementation. Out-of-the-box, Adobe Experience Manager provides a native implementation based

on CRX/JCR, as well as an implementation to integrate Elastic Path.

4. eCommerce engine The eCommerce engine is the eCommerce backend integrated in the provider

implementation. In most cases, it is a third-party eCommerce software, such as Elastic Path or an existing or legacy eCommerce solution.

The sample native implementation provided by Adobe Experience Manager for the geometrixx demo site uses the CRX repository itself as the eCommerce engine.

6#evolverocks

eCommerce Concepts with Elastic Path

The integration framework provides the mechanisms and components for:

Connecting to an eCommerce system

Pulling data into Adobe Experience Manager

Displaying data and collecting the shopper's responses

Searching data from both systems Returning transaction details

This means:1. Shoppers can instantaneously

register and shop2. Price changes are immediately

visible to shoppers

3. Products can be added as required

7#evolverocks

Catalog Management

Master and Sales Catalog

Product data cache

Catalog blueprint Product pageTemplates

Experience

Physical touch points

Marketing data

8#evolverocks

C ATA L O G M A N A G E M E N T ( C O N T ’ D )

Catalog Blueprint Provided by Adobe Experience Manager to create a catalog and is in

/content/catalog Catalog

Has a specific LiveSync mechanism tied to catalogs Product importer configuration Full product import Retrieve live price

9#evolverocks

B E S T P R A C T I C E S

For all implementations, keep the following in mind:

As product, stock-keeping units, and categories can be numerous, try to use the fewest nodes possible to model the content.

Avoid duplication. Or, when used, think about how many nodes your duplication will lead to.

Tag your content to prepare the query optimization.

Scaling eCommerce:1. Offload asset post processing to

a dedicated instance.2. Only import product data.3. Import throttling and batch

saves.

#evolverocks

THANK YOU!