HomeDev guideRecipesAPI ReferenceGraphQL
Dev guideUser GuideGitHubNuGetDev CommunitySubmit a ticketLog In
GitHubNuGetDev CommunitySubmit a ticket

Configured Commerce + CMS

Using Optimizely Configured Commerce with Optimizely Content Management System.


Using Optimizely Configured Commerce with Optimizely Content Management System (CMS) will serve existing and prospective Optimizely customers interested in a content-rich e-commerce 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 to customize their storefront with blogs, industry case studies, customer forums and content and product recommendations. Alternatively, CMS customers in manufacturing and distribution could begin selling products quickly using Configured Commerce's out of the box eCommerce functionality.

Key functionality and features

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

Product data

CMS requests data from Configured Commerce when it serves a page. The CMS 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 that show product information and browse the catalog contained in Configured Commerce.

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

Search functionality

Use Configured Commerce's 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 both search engines and aggregates the results.

Headless architecture

Configured Commerce is natively headless and CMS is one possible head a customer can use as a C# SDK that works with Configured Commerce APIs within CMS's .NET API framework. There are other aspects of the package that are included in the starter kit, such as the CMS search box behavior, but these are a minor part of the kit. This same C# API SDK serves as the basis for Optimizely's Configured Commerce Mobile App SDK, which leverages the cross-platform Xamarin framework to enable e-commerce clients to develop custom mobile apps as a front-end to the headless Configured Commerce solution.