DocumentationAEM 6.4Administering Guide

eCommerce ecommerce

Last update: Wed May 03 2023 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Admin
CAUTION
AEM 6.4 has reached the end of extended support and this documentation is no longer updated. For further details, see our technical support periods. Find the supported versions here.

Adobe provides two versions of the Commerce Integration Framework:

CIF on-prem
CIF Cloud
Supported AEM versions
AEM on-prem or AMS 6.x
AEM AMS 6.4 and 6.5
Back-end
- AEM, Java
- Monolithic integration, pre-build mapping (template)
- JCR repository
- Magento
- Java and Javascript
- No Commerce data stored in JCR repository
Front-end
AEM server-side rendered pages
Mixed page application (hybrid rendering)
Product catalog
- Product importer, editor, caching in AEM
- Regular catalogs with AEM or proxy pages
- No product import
- Generic templates
- On-demand data via connector
Scalability
- Can support up to a few million products (depends on the use-case)
- Caching on Dispatcher
- No volume limitation
- Caching on Dispatcher or CDN
Standardized data model
No
Yes, Magento GraphQL schema
Availability
Yes:
- SAP Commerce Cloud (Extension updated to support AEM 6.4 and Hybris 5 (default) and maintains compatibility with Hybris 4
- Salesforce Commerce Cloud (Connector open-sourced to support AEM 6.4)
Yes via open source via GitHub.
Magento Commerce (Supports Magento 2.3.2 (default) and compatible with Magento 2.3.1).
When to use
Limited use-cases: For scenarios where small, static catalogs may need to be imported
Preferred solution in most use-cases

eCommerce, together with Product Information Management (PIM), handles the activities of a website focused on selling products via an online store:

  • Creation, lifetime, and obsolescence of a product
  • Price management
  • Transaction management
  • Management of entire catalogs
  • Live and centralized storage records
  • Web interfaces

AEM eCommerce helps marketers deliver branded, personalized shopping experiences across web, mobile, and social touchpoints. The AEM authoring environment allows you to customize pages and components based on target visitor context and merchandising strategies; for example:

  • Product pages
  • Shopping cart components
  • Checkout components

The implementation allows real-time access to product information. This can be used to enforce:

  • Product information integrity
  • Pricing
  • Stock-keeping inventory
  • Variations in state of a shopping cart
NOTE
To use the integration framework with external eCommerce providers, you first need to install the required packages. For more information, see Deploying eCommerce.
For information about extending eCommerce capabilities, see Developing eCommerce.

Main Features main-features

AEM eCommerce provides:

  • A number of out-of-the-box AEM components to illustrate what can be achieved for your project:

    • Product display
    • Shopping cart
    • Check-out
    • Recently viewed products
    • Vouchers
    • and others

    chlimage_1-150

    note note
    NOTE
    The integration framework provided by AEM also allows you to build additional AEM components for commerce capabilities independent of your specific eCommerce engine.

  • Search - using either:

    • the AEM search
    • the search of the eCommerce system
    • a third party search
    • or a combination thereof.

    chlimage_1-151

  • Uses the AEM ability to present your content on multiple channels, be that full browser window or mobile device. This delivers your content in the format needed by your visitors.

    chlimage_1-152

  • The ability to develop your own integration implementation based on the AEM eCommerce framework.

    The two implementations currently available are both built on the same basis - on top of the general API (the framework). Implementing a new integration only involves implementing the feature(s) that your integration needs. Front end components can be used by any new implementation as they use interfaces (so are independent from the implementation).

  • The possibility to develop experience-driven commerce based on shopper data and activity. This allows you to realize many scenarios:

    • One example might be providing reductions in shipping costs when the total order exceeds a specific amount.
    • Another might allow you to provide seasonal offers that use profile data (e.g. location). These can then be highlighted, again depending on other factors when necessary.

    In the example below one teaser is shown as the contents of the cart are less than $75:

    chlimage_1-153

    This can be changed when the contents of the cart exceed $75:

    chlimage_1-154

  • And other features including:

    • Shopping cart contents retained across sessions
    • Full order history
    • Express catalog update

The Framework the-framework

The Concepts section covers the framework in more detail, but the following provides a high-level, high-speed view of the framework:

What? what

  • The integration framework provides the API, a range of components to illustrate functionality and several extensions to provide examples of connection methods.
  • The framework provides the basic structure needed for a project implementation.
  • The framework is extensible.
  • The framework does not provide an out-of-the-box, ready-to-use site. A certain amount of development work is always needed to adapt the framework to your specifications.

Why? why

  • To provide the basic mechanisms needed to quickly realise a customized eCommerce site.
  • Tp provide the flexibility needed for developing a real-life eCommerce site.
  • Illustrate best practices.
recommendation-more-help
5ce3024a-cbea-458b-8b2f-f9b8dda516e8