Alderich Web Solutions worked great for us however when it came to diagnosing and fixing issues with the website we had to rely on the support with little ability for us to "get under the hood" and look at the issue for ourselves. After switching to Optimizely, having this …
Stibo STEP MDM was a powerhouse. It seems we could do anything we could dream up, but we also had an in-house IT dev team to support it. The cost was the reason we went with Optimizely Commerce Cloud. We did not explore HubSpot for this project.
Optimizely Commerce Cloud offers a very wide range of features for admin users. There is less a need for an IT specialist or programmer to be involved when changes need to be made.
Optimizely is more flexible and more customizable, but also more efficient from a development standpoint. Salesforce Commerce Cloud has more capabilities but is more prone to become complex, and also generally more expensive. Magento is a comparable alternative but with less …
During the evaluation, Episerver was by far the most flexible as far as features and implementation go. Some of the more SaaS-based products don't allow for the level of customization needed for our clients, clientele. While the other platform boasted similar features, they …
Just depends on the use case. Some clients are more heavily weighted towards a marketing CMS and don't need a ton of complex technical functions of their eCommerce platform. For these we recommend Episerver.
Episerver did not have a headless CMS offering when we implemented. They may offer one now, but they are very late to the game in offering an API-based CMS experience. If you use an Angular or React front end, and you want to communicate with this incredibly expensive product …
Overall, Episerver seemed easier to use from a user perspective and easier setup. There was also preexisting resources with Episerver experience. Factoring in costs it became an easy solution.
Episerver's plug and play architecture is the winning factor comparing to AspDotNetStorefront. We did not choose Magento because it was not built on .Net.
Coming from a Software Engineering background, Episerver was the preferred system as it was an attractive platform from a developer's point of view. Today, I consult solely on Episerver solutions and still prefer the platform for multiple reasons (some already covered earlier …
Episerver was by far the most user friendly content platform allowing our business to easily manage the content with ease resulting in an overall productivity increase and time for the team to spend less time doing content management and more time managing the personalization …
I did evaluate other products in addition to Episerver. The other finalist was Magento, which has a very robust cart and a large market share. I have used that platform in the past and overall had been happy with it's performance. I ultimately selected Episerver because it was …
Our experience may be unique because we opted for an Epi core team to implement our website/console set-up and connection to our PIM and ERP. The experience may have been different with a 3rd party or it may not have. That said, we have been live with our primary website for almost 2 years and I still do not consider it was ever "done". We have been going back and forth on functionality issues and bugs since launch. I have low confidence that changes made the previous day will 100% be online the next - so my team rechecks the work they did the previous day to ensure everything is online. The addition of a second channel and enhancement requests have compounded the issues. I feel this product would work fine with singular or less complex market SKU offerings.
Episerver has a robust discount engine. This engine, combined with "visitor groups" allow our marketing department to categorize customers and offer a variety of discounts to targeted customers at specific times.
Episerver has a full-featured, storefront experience that can handle everything you might want for an e-commerce website.
Episerver offers A/B testing that can be helpful for trying out new content ideas and tracking the results.
Support. Episerver used to have direct support and access to the tech team to discuss and resolve issues. The new support portal is not enough for developer needs.
Quality Assurance. We find issues in the Episerver code that should have been resolved in QA before release.
Sales. Episervers sells the framework as a solution while showing Alloy. While it helps Episerver sell more, it puts the implementation partner into trouble as the client thinks they bought the solution. Episerver does not provide a solution. It provides a framework that you can build a solution on.
Really want to be able to spend more time and resources on rolling out new things with Episerver but at the moment we seem to be fixing alot of issues and pain points with the way our system was setup.
The administrative interface is largely intuitive and relatively easy to use. The complexity of business needs and ability to customize can affect this (i.e. you have to set up and develop with the user in mind), but the basic structure is largely solid. There are some areas of redundancy (such as Commerce Manager overlapping with other administrative areas) that can sometimes cause confusion or offer some functions in one place, whereas other related functions are managed on a completely different page.
We had an incredible team at Episerver Supporting us with the go live, reviewing our integration, and pushing our integration partner to deliver a quality product
Fully understand what is OOTB feature of the platform before proceeding to develop. Then implement a customization of key features once you can prove they are working as OOTB to make them more user friendly and productive for the business. Eg pre order and e gift card
Optimizely Commerce Cloud offers a very wide range of features for admin users. There is less a need for an IT specialist or programmer to be involved when changes need to be made.