Adobe Experience Manager is a strong contender in the digital market for managing content for companies on a large scale. Magento is a widely used eCommerce platform. Adobe Experience Manager (AEM) was not built for commerce, and Magento was not built for content (although some basic functionality has been added).
Allowing each of these systems to operate independently while relying on each other creates a synergistic relationship that translates to a better user experience, both for the business and the customer.
Based on our experience, we’ve rounded up our top key learnings, best practices, and recommendations for integrating AEM and Magento.
What could drive the need to use both AEM and Magento together? Is a headless integration ideal? What if a separate integration is needed during the checkout or login process? Can a mostly-headless integration be done? Let’s dig in!
The main tool we used for integration between these two systems is a tool developed by Adobe, called the CIF (Commerce Integration Framework) connector. One of the best parts about this tool is that it allows you to easily tie together AEM and Magento, and start seeing products or product categories in a short amount of time.
The first part of the integration is adding your Magento store view, and root category ID. Once these are set up (and connected to the instance through the OSGi configuration), you can start adding commerce components to your page!
What If I Don’t Want Headless?
Not headless you say? Well, there are times you just have to do things differently! Since multiple CRMs support having a login API, and your cart may need more complicated logic, AEM can be the “marketing” side of the house, and you can configure Magento to be the “sales” side of the house—passing API information for logging in, taking credit card and user information, and ultimately completing the sale process.