Adobe Commerce vs. Magnolia

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.

Incentivized

If you need a business CMS that brings along a good amount of features and also give you the chance to develop features on your own, Magnolia would be a good choice. Even if you have not the fitting infrastructure around, Magnolia provides you different ways like SAAS oder PAAS. If you have to review your code our have any problems the team behind will helps in a short time. Without using the connectors it is not so easy to connect special functionalities like Marketing tools or optimization tools. The DAM is very slow if you have an huge amount of documents and pictures to store for your website - you have to add an external DAM.

Incentivized

• 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.

Incentivized

• Use of YAML to define content models with code.
• Versatility of defining actions for custom handlers.
• Reloading classes when code is modified in a local dev environment is nice. While it doesn't seem to work when changes extend beyond the method body (i.e., adding methods), it remediates the pain of long startup times.

Incentivized

• 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.

Incentivized

• As a developer the learning curve is long, you can start developing relatively quickly but getting to know the platform in depth takes time.
• Having a history of modifications not only at the page level but also at the Content Apps level would be very useful.

Incentivized

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

Magnolia is an innovative CMS, for example it is possible to use the ipad to manage the contents. Magnolia’s team works hard to improve the product; the community is small but active and the support for the enterprise version is good. Magnolia’s team asks the users what they think and what they need, and the new functionalities planned for Magnolia 5.3 are very exciting for example the content personalization.

As an experienced user of Adobe Commerce platform, i found the platform complex for beginners yet very flexible to customize as per the client requirements be it a integration with third party system, implementing any payment gateway, managing multiple stores or customising the Adobe Commerce default functionalities, we did not experience issue with it.

Incentivized

There are a ton of small things that could make this CMS great Off the top of my head... 1) Better navigation between a component and its corresponding node in the jcr ( devs often have to flip between a page and a spot in the jcr even though there could be a button to take you from a page/component in the pages app to its location in the JCR) 2) Why does a content editor need to open the page to edit the page properties? They could just as easily edit the dialog from the tree view if they have many pages to touch, and it would save them time by not having to render the page.

Incentivized

It's a lean and performant platform. You don't need to put reverse proxy servers in front of it to speed it up (although that does make it go even quicker) as there are various layers of caching built in to the application. While it's a little cryptic, the internal caching system is actually quite configurable and can be tuned to the right sort of content.

Often what tends to surprise many an IT manager is that you can run it on relatively modest hardware. We've often been met with "are you sure ?" but the reality is that it doesn't need a whole lot of horsepower.

Incentivized

The technical service was impeccable. They were on point and were very knowledgeable.

You always get an answer based on your SLA. But you always get a solution. That's the successfactor in this case. To often i was frustrated about people in a company without even a clue what there product is about or how to solve a problem. Magnolia's Support Team does a very good job and try to help you in most of the cases

Great value for an flexible, open source platform.

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.

Incentivized

Magnolia DXP offers similar or more capability compared to the other platform, while much easier to implement. For example, Adobe Experience Manager tend to be more monolithic in nature, heavier footprint compared to Magnolia. Hence when implementing a DXP, it is much faster to build using Magnolia, at a much lower TCO. The other platform like Kontent.ai and Strapi are pure headless platform and offer lesser features. What really make Magnolia different is the APAC team, who are all out to support their client in the implementation, ensuring their client maximize their platform and the project implementation is successful. This is some thing that is not experienced when using other platform(s)

• 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!

Incentivized

• We have placed web content management in the hands of the organisation than retained it within the technology team.
• We were able to quickly move to MVP and release and we are now focussed on moving the platform forward at some pace whilst not being burdened with BAU work inside the technology team as so much as self-service to trained organisational users
• The use of the SAAS/PASS has inbuilt business resiliency as specialist work and aspects such as underlying security is done by Magnolia and we are able to focus internal effort on building out the platform.