Optimizely Commerce Connect is a PaaS e-commerce backend solution coupled with Optimizely's PaaS CMS to help e-commerce organizations, of any type, create highly customized websites and buying experiences with a two-in-one content and commerce solution.
N/A
Optimizely Configured Commerce
Score 7.0 out of 10
N/A
Optimizely Configured Commerce is a SaaS, headless, and composable e-commerce platform that helps manufacturers and distributors scale e-commerce growth using as much or as little out-of-the-box functionality as they prefer; saving organizations time to deploy meaningful buying experiences.
N/A
Pricing
Optimizely Commerce Connect
Optimizely Configured Commerce
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Optimizely Commerce Connect
Optimizely Configured Commerce
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Required
Required
Additional Details
—
—
More Pricing Information
Community Pulse
Optimizely Commerce Connect
Optimizely Configured Commerce
Considered Both Products
Optimizely Commerce Connect
Verified User
Anonymous
Chose Optimizely Commerce Connect
In my opinion, Sitecore is a developers and users' nightmare. Terrible UX. Way behind on the curve. Don't recommend.
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 Connect. We did not explore HubSpot for this project.
Optimizely Commerce Connect 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 …
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 …
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 …
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 …
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.
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 …
Episerver is a great product. I have implemented dozens of CMS systems and developed thousands of websites over my career. It is the overlay of Insite's eCommerce that has hobbled Episerver's functionality. Maybe that is helpful for the most rudimentary of users, but it is a …
Optimizely platform is more flexible and easier to administer. Optimizely support is more personal (although often too slow and unresponsive). Optimizely integrates directly with our ERP and external PIM to provide automatic updates.
We selected Optimizely B2B Commerce Cloud (when it was Insite Commerce) as they were specifically focused on manufacturing clients and the storefront and data management were very robust. The business model and cost were more in our price range as well, so an overall better …
I was not very involved with this process. It has been 3 years since we made a decision and I can't even remember the name of the other companies we were considering. I was in a different role then so I was less involved with the eCommerce department. I do remember really …
Optimizely B2B Commerce Cloud was the only solution that had a direct API connection to our ERP from day 1. The other solutions did have API building available but at a larger cost. The built-in WIS/Integration jobs in the Optimizely B2B Commerce Cloud platform are also a …
Very strong fit for mid-sized organizations that need more flexibility and customization as compared to canned or template-based offerings, but also want the efficiency and externalization that comes with a pre-existing, cloud-hosted platform (as compared to a full custom offering). Works well with a PIM and more mature catalog data in order to fully leverage the dynamic data capabilities.
I think that there are a lot of companies (us included) that are looking for a solution to fit into their current needs, versus looking for a solution that is going to solve all of their problems. For us, Optimizely B2B Commerce Cloud fits into the former in that situation where we have specific ERP needs, specific data needs, usability and user management needs, etc. and Optimizely B2B Commerce Cloud just happens to fit in there the most.
Web content management -- the interface is drag and drop and makes it very easy for business users to create product pages.
In site search with Episerver Find -- it is easy to promote attributes and make quick tweaks to fine-tune results.
Integrate with other systems -- we have integrated with our ERP, our product information management system, our digital asset management system and our marketing automation system to take advantage of investments we have already made in content and customer data.
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.
It deployed with a major bug in Guest checkout. It is now fixed, but we lost a lot of business because of it.
The pricing API is not working.
Support for multi-warehouse product availability would be helpful. If we have the product in stock in any warehouse, we should be able to book the order.
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 job functionality is one of the strongest benefits Optimizely offers. It allows a savvy user to quickly go in to a given job, see the job history to find errors and then even take the steps of a job, copy the code and paste it back into your source to diagnose a potential issue.
Quite flexible and easy to use for daily marketing user tasks, like updating page listings, promotions, and copy. More in-depth tasks like managing product attributes, rearranging product taxonomy placement, and CMS editing are not user-friendly and require a careful and detailed process to follow.
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
It's a mixed bag. The team has been very nice, but there has been an underlying feeling of condescension because we have complained or "caused trouble" over the inadequacy of the CMS component. Also, support for modifications or UI changes has been terribly slow. Understandably, COVID has made life hard for everyone, but there is an expectation that we complete our work immediately, but their team will "put it in queue" when we have a request or find a bug. Further, we certainly feel that we were sold a list of capabilities that we have not seen come to fruition. Finally, the change of ownership 3 times (Insite -> Epi -> Opti) over our implementation period has been both confusing and disruptive.
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
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 Connect. We did not explore HubSpot for this project.
We selected Optimizely B2B Commerce Cloud (when it was Insite Commerce) as they were specifically focused on manufacturing clients and the storefront and data management were very robust. The business model and cost were more in our price range as well, so an overall better value for the solution. The ability for the product data to be updated once on the catalog side as well as on the CMS website side was the benefit we saw with a small team of resources to support the product. However, there are definite drawbacks to having not gone with a more turnkey website CMS.