Dev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunitySubmit a ticketLog In
GitHubNuGetDev CommunitySubmit a ticket


Defines terms for Optimizely Configured Commerce.

  • Admin Console – The backend administration that manages products, customers, users, carriers, promotions, and all other aspects of the platform.
  • Application Dictionary – Controls field names, field labels, field length, language options, and user role permissions. Managed in the Admin Console under the Administration section.
  • Attribute: A filter option that allows site users to filter product lists or search results by specific criteria. Common attributes include Color and Size.
  • Carrier – A shipping method or shipping organization site users can select to have product sent to them. Examples of carriers may include USPS, UPS, FedEx, or Flat Fee.
  • Category – Provide the basis for the site taxonomy. Products are assigned to categories, and categories are assigned to websites.
  • Content Management System (CMS) – Allows ISC_Content user roles to modify and publish the content that appears to site visitors. Content may be changed based on the visitor's persona, device, and/or language.
  • Customer – Represents an entity in the commerce exchange; for example, XYZ Interiors. Customers employ Users.
  • Elasticsearch – The default search engine for Configured Commerce 4.2+, configurable in the Admin Console under the Marketing section.
  • Enterprise Resource Planning (ERP) System – A business process management solution that provides an organization with multiple modules to manage the business and automate common tasks.
  • Integration Job – Tasks created in the Admin Console to move data from an external system to Configured Commerce and back again. Common integration jobs include integrations to ERP solutions, CDNs, or product information management system.
  • Microsite – A separate, self-contained site within a main or parent site. URL example:
  • Persona – A designation given to a user each time they access the commerce site. Content may be created to target specific personas. Commonly used Personas include a NonAuthenticated Persona, a location-based Persona, or a customer-based Persona.
  • Product – A single item or SKU managed in the Admin Console (directly or via an integration job) and displayed on the website.
  • Product Information Management (PIM) System – A data and asset management solution that contains comprehensive data for all of an organization's products.
  • Product Detail Page – The website page for a single item or SKU that includes indepth information about the product and allows the user to add the product to their cart.
  • Product List Page/Category Page – The website page that lists all items or SKUs that are assigned to a particular category.
  • Price Matrix – Integrates with an ERP solution to provide comprehensive and robust pricing capabilities without relying on a live connection to the ERP.
  • Search Engine Optimization (SEO) – Ensuring the best and most results possible appear when people use search engines to search for your organization or its products. B2B Commerce Cloud websites can be optimized using metadata and the robots.txt file.
  • Settings – Controls what the application can and cannot do. Settings may control functionality at the application level or at the website level.
  • Specification – A tab that appears on the Product Detail Page to provide more information about the selected product. Specifications are created and populated per product.
  • Subdomain – A site that lies within the same Root domain, but otherwise is separate from the main or parent site. URL example:
  • User – Represents a single buyer in the commerce exchange. Users are employees of Customers. In 4.3.1 and above, these users also are called Website Users.
  • User Role – A group of permissions assigned to a user. There are both internal roles and external user roles available in Configured Commerce.
  • Website/site – The visual representation and functional arm of the commerce solution. Users visit the website to view and purchase products.
  • Widget – A pre-configured content holder ISC_Content user roles may use to add content to website pages without having to develop page elements.
  • Windows Integration Service (WIS) – An integration connection that let Configured Commerce communicate between the client's ERP or backend solution and the commerce website.