Adobe Commerce delivers personalized shopping at scale. Delivered as Adobe Commerce as a Cloud Service (ACCS), it boosts conversion with an AI-powered storefront, built-in merchandising, and GenAI-driven content. ACCS supports rapid expansion through multi-site, multi-language, and multi-brand capabilities, handling millions of SKUs, complex catalogs, and custom pricing. Always-on SaaS innovation lowers total cost of ownership by removing upgrade overhead and minimizing…
N/A
Adobe Experience Manager
Score 8.6 out of 10
N/A
Adobe Experience Manager is a combined web content management system and digital asset management system. The combined applications of Adobe Experience Manager Sites and Adobe Experience Manager Assets is offered by the vendor as an end-to-end solution for managing and delivering marketing content.
WooCommerce is unreliable and often has a lot of downtime and issues. Shopify is a lot more reliable, scalable and offers a lot of features out of the box or with easy and well-vetting apps and plugins. I would suggest that unless there is a very clear limitation of Shopify or …
Adobe Commerce is in the lead, more scalable and flexible than Shopify, more robust than Kibo and Big Commerce and more open and easier to implement than Spryker and SalesForce. It is a strong contender for organization with development capabilities, needing a multisite, …
Bigcommerce offers strong saas simplicity and lower maintenance, but it lacks the customisation and multi store flexibility., woocommerce is cost effective and easy to use and come with a huge extension directory most of them freely available, but it is suited for smaller …
Shopify is also a great solution for the customers that comes with different set of benefits and limits when comparing with Adobe Commerce. Shopify provided very limited b2b support, limits in the integration with third party, checkout and theme custimization is limited, …
Open source nature of Magento was a key consideration, particularly when launching in new markets. Cost is another key factor here and the GMV model is an important enabler for us as we continue to grow.
Adobe Commerce is highly extensible and advanced customization and …
Shopify is just better. In my opinion, it can save quotes, have different pricing for resellers, have multiple catalogues, do blogs, change the website, etc. It feels like Shopify is designed to do everything and does it all quite well overall, whilst Magento is for one thing …
Shopify has the bad habit of charging transaction fees unless you use Shopify Payments, and this aspect only is usually a no-go if you have a big eCommerce to handle. Salesforce has very similar capabilities and probably has a better ecosystem, but it's customization capability …
Shopify and BigCommerce are great if you are a small business that is creating your first business and don't have many Skus or complex pricing. For us, having over 2 million Skus and a very complex inventory management of those Skus, Adobe Commerce (Magento Commerce) being …
Magento Commerce was previously put into place and used right when I came onboard. We used it for quite some time, but ultimately the need for our company's specific customizations became too difficult to manage during core updates. We specifically needed a more specialized way …
Magento Commerce Cloud is much more robust then Magento Open Source for e-commerce online stores who have a lot of orders and need a lot of security and speed. Using one of the common smaller web hosts, or even your own web servers, might not be up to par when your company has …
Adobe Experience Manager, built on Java, means that the pool of developers available to work on the platform is large. Adobe Experience Manager's front-ends and client library management tooling mean that front-end developers can feel at home despite a lack of Java knowledge.
We wanted a CMS which is known in market, which have a good ecosystem. With Adobe Experience Manager, we get integration with Target, Tag management, and other Adobe products.
Adobe Experience Manager provides way more. It is a much more holistic tool to help us manage the entire customer Journey. I, however, do not have enough power to make those decisions. I did not in fact choose Adobe Experience Manager, but I do like it better.
Adobe's integration with all of its other products requires digital marketing, making its system stand out from the rest. AI integration takes it to the next level.
I selected Adobe Experience Manager because it was the easiest to connect to our platforms, the best cost for the size of our company, and I was using Adobe for almost everything else at the time. I think this was the best solution for our smaller company at the time.
We need to do a lot of quotes, and sometimes customers call and want to pay. Adobe Commerce (Magento) did not let you keep saved quotes, so you had to put people on hold whilst you started making the order from scratch rather than just taking payment, which was very annoying.
I'll answer the second one because I mean, the first one I don't have an issue with. The second scenario is we oftentimes have the need to spin off very small campaign style sites or sites that generate leads but are unbranded and that sort of thing. So that's hard to do in AEM because you have to then create another organization within AEM to do that. And we're talking about sites that are maybe five to 10 pages in size. So we've been investigating Edge, but then that's a different workflow, so we'd have to train people on that. So it would be nice if there was something within the AEM structure that could allow you to do something very similar to Edge, where you make some small micro sites that are not necessarily branded, that you could still host within the platform and not have to retrain everybody on a completely different platform.
Magento Commerce Cloud allows us to develop our own custom solutions for problems that we need solved.
Magento Commerce Cloud can also be integrated with many of the third part vendors that we use. This has made many implementations go very smoothly and tends to be much quicker than developing our own custom solution.
There are many features available right out of the box. Many of them we have not implemented yet, but it is great to have them available to us when we are ready.
It allows us to scale so that we can make a change on a global footer. And it applies to all of the different property websites. It allows us to set up components and compartmentalize things in a way. The big thing is that it's scalable. And then it also ties into Adobe Analytics and other Adobe products. So we are a complete Adobe shop. Every Adobe product that we can use, we use. I don't think we do it for marketing so much, but for doing target testing and analytics, data scientists are using the same product and so it all speaks.
The Magento admin is not as user-friendly has other e-commerce platforms, and this is why I never recommend it for smaller ecommerce stores.
You absolutely need a skilled developer to customize and extend Magento. A skilled developer can make Magento amazing, but if you're looking for a DIY website option, Magento will frustrate you.
Magento takes a lot of server resources, so you will not be able to run on it a shared hosting account. You will need a dedicated server for it.
There are some glitches in permissions inheritance that require us to toggle a save on permissions in groups that inherit from a group that was recently updated.
Large packages require stopping the workflow launcher OSGi components or many workflows will slow down the server.
Locked pages are hard to find unless I use /siteadmin... I often hear that the CQ tools will go away, but if we lose that, some small things might be harder to do, like finding locked pages.
Magento is well-supported by a big development team at eBay, which not only addresses bug reports very quickly, but also is constantly working on improvements to the platform. The wealth of Magento third party modules ensures that the platform will be up to date with future changes to Payment or ERP systems. Security is always a concern and with the Zend framework as a foundation, Magento has had very few security-related patches since I have started to work with it
We had and still have a fantastic experience using Adobe CQ. Lots of flexibility, great integration with other Adobe products we already use and a powerful technology make it a great fit for our corporate environment. Also as the community grows, it makes it easier to network with other developers and users to get new ideas on how to continue to get the best out of the software.
It is a simple platfrom for users and an open code platfrom for developers making it one of the easiest ecosystem in ecommerce. It is flexible and controlable. It enables speed and scale. Documentation is readily available and there is a large pool of experience developers and expert as it is a leading platfrom for some time
Considering I'm completely self-taught on Adobe Experience Manager, I have to rate usability quite high since plenty of aspects were easy to figure out on my own. With its cloud-based platform, access from anywhere it super great for overall usability. Edits can also be made pretty quick and easy, which is another great feature.
Being part of Adobe Suite means you are already notified when the tool has any outages. However, I have never faced unplanned outages. Whenever you face any issue with the site, it is clearly stated if there were any planned outages and how quickly you will be back to normal. So, I will say that even the outages are planned and managed in a great way like their other services.
With respect to performance, Adobe experience manager is one of the best in the CMS space. We didn't observe frequent slowness on platform, however the systems which are accessing experience manager should be of good specifications without which slowness would be observed. Adobe experience manager works well in integration with other solutions, unless the destination application is designed to trigger frequent calls to AEM.
Adobe Experience Manager, in all its capacity, is a great alternative to any other CMS you are using. It helps in rapid development and makes life easier for maintaining the website for multi-language sites. Technical know-how is eliminated at content authoring. Better documentation in terms of live examples with videos would be appreciated.
Depending on your individual needs, It is really quite simple to create an authoring experience for a website that looks really good. I have been part of many implementations and many teams and have seen many projects that were super successful and others that were not implemented well. AEM has room for a lot of flexibility in the implementation process compared to other CMS like SharePoint
Open source nature of Magento was a key consideration, particularly when launching in new markets. Cost is another key factor here and the GMV model is an important enabler for us as we continue to grow. Adobe Commerce is highly extensible and advanced customization and flexibility built in meaning that we can shape the product into exactly what we require.
SSO is one fits all, so we don't have to have a separate SSO for each application of Adobe The integration with Analytics works perfectly and bring directly value really quickly Target remains more complicated to set up, but can also bring a lot of value once integrated with the rest of the Adobe platform The fact that the solution is Cloud services is also a big advantage for maintenance
When we first went LIVE with Adobe Commerce our SEO / Organic traffic plummeted and so did our conversion so our initial take of Adobe Commerce wasn't great. This was partly to do with business decisions but also to do with out of box functionality not being as expected.
Fast forward and we basically did a redesign on the platform and partnered with a fantastic SEO partner and improved results and now are doing extremely well on the Magento platform. Much improved!
