If you've got enough variables, then it's worth it
Overall Satisfaction with Oracle CX Sales (formerly Oracle Engagement Cloud and Oracle Sales Cloud)
We chose to implement Oracle CPQ for our separate e-commerce platform on top of Oracle Commerce Cloud. It's being used across the entire organization to replace a home-grown custom solution for a wide variety of product lines that can be customized to extreme levels. We'd like to be able to offer more products and variations on our e-commerce site rather than relying on manual quotes and sales representatives, but we're limited by manpower and bandwidth to manually program in a lot of variables.
Pros
- Allows us to offer a variety of options without manually programming in each individual product
- Allows us to utilize a product feed with features and variants, which can also play well with Google Product Listing Ads (Google Shopping)
- Maintenance does not necessarily require hard programming knowledge, so marketing communications can help maintain
Cons
- Significant setup time, cost, and maintenance. We have to use an implementation partner
- Does not always play well with other software, even Oracle software. While this is improved and being further improved, that it was a third party acquisition means things sometimes require a little extra care
- Additional setup documentation and first walkthroughs would be helpful, especially if it was all in one place
We debated a few different options, including a home-grown custom program, uCommerce, and just using only Oracle Commerce Cloud. Since we had already decided to use Oracle Commerce Cloud over uCommerce, the integrations available between OCC, Oracle's ERP system, and Oracle CPQ definitely seemed like the easiest option with the greatest benefits. However, the cost/benefit of Oracle CPQ was more apparent when we were ready to launch more complex configurations across all of our product groups.
Comments
Please log in to join the conversation