Home
Documentation
This Help Center provides documentation on all aspects of the HCL Commerce+ product, from installation and deployment to operating and customization.
Extending
Using Commerce+'s xC programming model, you can use HCL-provided extension points to extend existing Commerce logic. You can implement these extensions with the xC Customization toolkit provided by HCL. Commerce+ also provides Packaged Business Capability integrations that extend the product's reach and functionality.
Developing stores
Commerce+ offers customizable features for storefronts using the Next.js framework. Commerce+ supports headless commerce to use any front end storefront.
Ruby storefronts
The Ruby storefront offers customizable features for storefronts using the Next.js framework. It uses the headless store data template and supports business-to-consumer (B2C) and business-to-business (B2B) use cases. The store includes pages for browsing, shopping, checkout, and account management, and uses Elastic for search functions.
GDPR/Privacy Policy
Commerce+ provides the GDPR (privacy policy) enablement process.

Documentation
This Help Center provides documentation on all aspects of the HCL Commerce+ product, from installation and deployment to operating and customization.
- Overview
  Welcome to the HCL Commerce+ overview. Explore these feature overviews to learn how Commerce+ operates. Refer to the related links listed at the end of each topic to access expanded product documentation.
- Deploying
  This section provides details on deploying HCL Commerce+. It explains how to download the Docker images and Git bundles that comprise the product, how to create a minimal environment, and how to plan for a full deployment. It details supported software versions, patches, and configurations to ensure the platform performs well.
- Migrating
  The following topics show how to migrate an existing HCL Commerce Version 9.1 environment to Commerce+. The process consists of an initial migration of your database contents. This is followed by a code migration. Both are fully described.
- Operating
  The topics in this section focus on tasks that are performed by business users, marketers, and customer support representatives to connect with partners and attract and satisfy customers.
- Administering
  The site administrator performs the tasks needed to support day to day operations of the Commerce+ site.
- Extending
  Using Commerce+'s xC programming model, you can use HCL-provided extension points to extend existing Commerce logic. You can implement these extensions with the xC Customization toolkit provided by HCL. Commerce+ also provides Packaged Business Capability integrations that extend the product's reach and functionality.
  - Customizing
    The topics in the Customizing section describe tasks performed by an application developer to customize Commerce+.
  - Developing stores
    Commerce+ offers customizable features for storefronts using the Next.js framework. Commerce+ supports headless commerce to use any front end storefront.
    - Stores in Commerce+
      Commerce+ supports different types of stores. The assets of these stores can be edited using the Commerce Lab.
    - Ruby storefronts
      The Ruby storefront offers customizable features for storefronts using the Next.js framework. It uses the headless store data template and supports business-to-consumer (B2C) and business-to-business (B2B) use cases. The store includes pages for browsing, shopping, checkout, and account management, and uses Elastic for search functions.
      - Creating a custom storefront
        You can create a server-side rendered storefront using the Commerce+ Next.js Store SDK. The Next.js Store SDK allows your front end development of a storefront using an easy extension paradigm.
      - Ruby B2B storefront
        The Ruby B2B storefront is enabled for B2B e-commerce. The sample B2B storefront is called Ruby B2B. The Ruby B2B storefront features include B2B features, in addition to all of the available features in the B2C storefront.
      - Ruby storefront (B2C)
        The Ruby storefront (B2C) is built on the Next.js framework, ensuring seamless browsing, easy navigation, and secure transactions. Notably, this new storefront provides server-side rendered pages to assist with Search Engine Optimization (SEO) and page previews.
      - Ruby storefront B2C and B2B features
        Commerce+ offers various features for Ruby storefronts (B2C and B2B) listed on this page.
      - GDPR/Privacy Policy
        Commerce+ provides the GDPR (privacy policy) enablement process.
      - Multiple Extended Site (eSite) access
        The Next.js store supports multiple eSite access with a single deployment.
    - The Customer Service Hub
      The Customer Service hub, also known as the CSR tool, provides your Customer Service Representatives (CSRs) an authority to manage Accounts and Orders for a selected store.
    - Remote store toolkit
      You can migrate store development environments to Open Liberty and a modern Java Development Kit (JDK) by using Commerce+ remote store dev kit migration to standardize environments and minimize reliance on legacy tooling.
- Securing
  These topics describe the security features of Commerce+ and how to configure these features.
- Performance
  Topics in the Performance section describe the means by which to plan, implement, test, and re-visit the optimization of Commerce+ site performance.
- Troubleshooting
  Topics in the Troubleshooting section highlight common issues that are encountered with Commerce+, and how they can be addressed or mitigated.
- Reference
  Topics in the Reference section contain all of the Commerce+ reference documentation.

GDPR/Privacy Policy

Commerce+ provides the GDPR (privacy policy) enablement process.

Storefront acceptance of the policy can be enabled or disabled using the Store Management tool inside the Commerce Lab for a given store from the Configurations tab.

Usage of the feature requires the presence of an e-marketing spot named PrivacyPolicyModal_Content. This is placed at the SAS level and used via inheritance.

The e-marketing spot must include three content objects named (in this sequence):

PrivacyModalPersonalInfoVersion1.0
PrivacyModalMarketingVersion1.0
PrivacyModalAnalyticsVersion1.0

Note: Each content items may include storeName as a placeholder, which will be replaced with the store name when the privacy policy is fetched.

Note: The number at the end of the first content item's name describes the policy's version number and should be updated if a change is made so that a new prompt is issued at the storefront for notification.