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
- 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|
- 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:
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:
The implementation allows real-time access to product information. This can be used to enforce:
AEM eCommerce provides:
A number of out-of-the-box AEM components to illustrate what can be achieved for your project:
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:
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.
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:
In the example below one teaser is shown as the contents of the cart are less than $75:
This can be changed when the contents of the cart exceed $75:
And other features including:
The Concepts section covers the framework in more detail, but the following provides a high-level, high-speed view of the framework: