Disclaimer: This website requires JavaScript to function properly. Some features may not work as expected. Please enable JavaScript in your browser settings for the best experience.

HomeDev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideLegal TermsGitHubNuGetDev CommunityOptimizely AcademySubmit a ticketLog In
Dev Guide

Optimizely Commerce Connect system overview

Describes the subsystems and data model for Optimizely Commerce Connect 13, part of the Optimizely platform.

Subsystems

Optimizely Commerce Connect consists of an ecommerce engine with many subsystems, together with Optimizely Content Management System (CMS) for the creation and display of product content on the front-end website.

The ecommerce part of Commerce Connect is built on these components and frameworks:

  • Microsoft .NET Framework and ASP.NET
  • Microsoft Windows Communication Foundation (Catalog System)
  • Business Foundation (Customer Management)
  • Meta Data Plus (legacy Order and Catalog Systems)
  • Security and Permissions

These are the main subsystems of Commerce Connect:

  • Catalogs. Define catalog schemas, import existing catalogs, and define price lists.
  • Marketing and campaigns. Create campaigns, custom discounts/promotions, and define promotion policies.
  • Orders. Manage orders, connect payment and shipment gateways, customize order workflows, and manage taxes.
  • Customers. Create organization structures, set roles and permissions, and extend customer or organization objects.
  • Markets. Define multiple markets for market-specific features.

Data model

Below is a data model of the entities in commerce and the logical relationships they have to each other. The 1 to many relationship means that for each 1 instance of an entity there are 1 or more other related instances. An example is orders and order lines, where for every order there is at least one order line.

The1 to many (optional)_relationship means that it _can be related but does not have to be related. A good example is customers and organizations. Customers do not have to be associated with an organization, so the relationship is an optional one to many between organization and customer.

814

See also Commerce Connect class library for the REST API service layer.