Adobe has adopted Adobe Commerce’s GraphQL APIs as its official commerce API for all commerce related data. Hence, AEM uses GraphQL to exchange commerce data with Adobe Commerce and with any commerce engine via I/O Runtime. This GraphQL API is independent from AEM’s GraphQL API to access Content Fragments.
There is no official AEM Assets – Adobe Commerce integration available. There is a partner connector available on the marketplace.
Or as a workaround, you can store product assets (images) in AEM Assets but you will have to manually store the asset URLs in Adobe Commerce. Dynamic Media is now part of AEM Assets and will work the same way.
No, it does not matter where your commerce solution is deployed. CIF and the AEM storefront will work regardless of the deployment model. However, if the solution is deployed with the recommended E2E reference architecture, E2E tests can run against performance KPIs that represent a typical enterprise customer profile. This will provide additional information that can be used as a benchmark.
Catalog pages and product pages are created and cached dynamically in AEM based on generic catalog and product page templates. No product or catalog data is imported and stored in AEM.
The CIF add-on used with AEM enables data to flow from the commerce solution to AEM on-demand. Hence, this is not a real-time push or a batch process when there is an update in your commerce solution.
This depends on a few additional aspects you have to consider. What is the cache ratio of your catalog data & pages? How many concurrent requests do you expect during peak hours? How scalable are the APIs of your commerce solutions?
PIM data gets exposed to AEM and clients via GraphQL requests. Our recommendation is to integrate PIM with the commerce engine (Adobe Commerce or others) so that PIM data can then be retrieved from the commerce engine.
Dynamic data such as price or inventory is not cached on the Dispatcher. Dynamic data is fetched client-side with web components directly via GraphQL APIs. Only static data (such as product or category data) is cached on the Dispatcher. If product data changes, there will be a need for cache invalidation.
We recommend setting up TTL-based cache invalidation for pages cached on the Dispatcher. For dynamic information such as price or stock, we recommend rendering the date client-side. For more information about TTL-based cache invalidation, please refer to AEM Dispatcher
A product search reference implementation is provided but no unified search with content. This feature is usually very customer specific and better solved on a project-specific level.
CIF provides Search bar and Search Result components. The Search bar component sends a GraphQL request with the search term to the commerce solution which then returns a product list that includes product name, price, SLUG, etc. The Search Result component then displays the search results in a gallery view on a search result page created in AEM. The Search supports basic full-text search. We use the SLUG/url key to build a reference to the PDP.
Product data is usually already translated in PIM or in Adobe Commerce. The AEM – Adobe Commerce Integration supports the connection to multiple Adobe Commerce stores & store views. In an MSM setup typically one AEM site is linked to one Adobe Commerce store view.
We recommend managing marketing related data and content in AEM. Decorate product data from your commerce solution with additional attributes using Content Fragments or create and link Experience Fragments for unstructured content with your products.
We recommend using abstracted payment methods. This puts the browser client in direct communication with the payment gateway provider so that neither Adobe or the commerce solutions hold or pass cardholder data. This approach requires only a level 3 PCI compliance. However, there are additional things to consider to be fully PCI compliant such as how employees interact with the system and data. For more information about Adobe Commerce PCI compliance, please refer to PCI compliance
Yes, Self-Assessment Questionnaire D and Attestation of Compliance are available on-request.
You can request for a trial license to use I/O Runtime here.