This article covers a Bloomreach Experience Manager version 12. There's an updated version available that covers our most recent release.

Configure StarterStore

This Bloomreach Experience Manager feature requires a standard or premium license. Please contact Bloomreach for more information.


The Starter Store allows the integration of commerce backends and the customization of behaviors through configuration.

Use Available Commerce Backend Configurations

Currently, the Starter Store includes out-of-the-box configurations for the following commerce backends:

Using the above commerce backends only requires specifying the physical connection properties in conf/, as described on each configuration's documentation page linked above.

The goal is for the Starter Store to eventually provide configurations for all popular commerce backends.

Configure a Different Commerce Backend

To integrate a different commerce backend, the following three items must be configured:

  • Commerce Connector
    Maintained in a Connector Set document in the CMS application and containing metadata to access commerce backend's services.
  • Mapping Model Bundle
    Maintained in a resource bundle document in the CMS application and mapping the commerce backend's data structures to generic Starter Store data structures.
  • CRISP Resource
    Spring bean configuration stored inside a module configuration in the content repostory, configuring the commerce backend service physcial connection properties.

Contact BloomReach if you require assistence configuring your commerce backend or if you want to stay up to date on which backend configurations are planned to be added to the Starter Store.

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?