Configured Commerce + CMS

Using Optimizely Configured Commerce with Optimizely Content Management System 12 (CMS 12) will serve existing and prospective Optimizely customers interested in a content-rich ecommerce storefront. Configured Commerce customers who want a more robust content management experience than the built-in Spire CMS provides. Configured Commerce customers could instead use CMS 12 to customize their storefront with blogs, industry case studies, customer forums, content, and product recommendations. Alternatively, CMS 12 customers in manufacturing and distribution could begin selling products using Configured Commerce out-of-the-box eCommerce functionality.

You will leverage functionality and features from Configured Commerce and CMS 12.

CMS 12 requests data from Configured Commerce when it serves a page. CMS 12 then calls the Configured Commerce API to pull products into CMS pages as product detail content blocks. Administrators and editors can use this block to create pages showing product information and go to the Configured Commerce catalog.

CMS 12 does not "pull" or "migrate" data from Configured Commerce into its data storage out of the box, unlike if you use Configured Commerce with CMS 12.

Use Configured Commerce native search indexing and faceting for products and Optimizely's Find to index other (non-product) content. These are two distinct search indices and mechanisms, and the Configured Commerce catalog does not index content into Optimizely's Find. However, site visitors have a single search experience where the search box queries search engines and aggregates the results.

Configured Commerce is natively headless, and CMS 12 is one possible head a customer can use as a C# SDK that works with Configured Commerce APIs within CMS 12's .NET API framework. Other aspects of the package are included in the starter kit, such as the CMS 12 search box behavior, but these are a minor part of the kit.