Home
Documentation
This Help Center provides documentation on all aspects of the HCL Commerce+ product, from installation and deployment to operating and customization.
Administering
The site administrator performs the tasks needed to support day to day operations of the Commerce+ site.
Inventory management
Use the HCL Commerce+ Inventory to manage your inventory and access your Inventory Locations (ILs), where your inventory is physically stored and is delivered or shipped from.
Managing system personas for Inventory
Inventory Packaged Business Capability (Inventory PBC) uses persona-based access control and centralized Identity and Access Management (IAM) integration to secure inventory data.

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.
  - Member groups
    A member group is a grouping of members - users, organizations, or other member groups - used for various business purposes. Two kinds of member groups exist: implicit and explicit. An implicit member group contains users that share common attributes and are therefore considered members of a specific member group. An implicit member group specifies criteria or attributes that users must satisfy in order to be considered members of that member group. You can also explicitly exclude certain users although they satisfy the criteria. An explicit member group contains explicitly assigned users, who may or may not share common attributes. A member group can be both implicit and explicit at the same time.
  - Inventory management
    Use the HCL Commerce+ Inventory to manage your inventory and access your Inventory Locations (ILs), where your inventory is physically stored and is delivered or shipped from.
    - Managing system personas for Inventory
      Inventory Packaged Business Capability (Inventory PBC) uses persona-based access control and centralized Identity and Access Management (IAM) integration to secure inventory data.
    - Configuring a store for the Inventory
      Perform the following steps after creating a store in an Inventory environment. The store's default inventory location is created in the PBC.
    - Mapping physical stores to Inventory locations
      If a physical store is to map to a new inventory location, create the new location in the Inventory. While you create and manage physical stores in the Commerce+ database, you create and manage inventory locations in the PBC.
    - Inventory thresholds
      The HCL Commerce+ Inventory enables inventory thresholds to be set and modified by business users. Thresholds are used to monitor when there are too many or too few of a specific SKU at a specific Inventory Location. Use threshold settings in order to effectively monitor and react to changing inventory conditions.
    - Managing ATP allocations and order splits
      This document outlines the end-to-end flow for reserving order items using the ATP (Available to Promise) system, focusing on the processes for both on-hand inventory and backordered items. This includes detailed steps on how the system interacts with the Inventory PBC API to manage inventory efficiently, ensuring optimal customer satisfaction.
  - Approvals
    Accurate, secure transactions require that a second individual approve some electronic marketplace actions before they proceed. This individual, called an approver, can accept or reject requests to perform a specific action. During the organization registration process, the organization administrator selects the business processes for which they want to enable approval. This is done by signing up for the appropriate approval member group during membership registration. The organization administrator also populates the approver member groups. Only users within these groups have the authority to accept or reject requests to perform those actions for which approval has been enabled.
  - System Administration
    Commerce Lab allows you to manage transport, messages, scheduler, Connectors, registries, and security policies.
  - Staging environment
    An Commerce+ staging environment is a runtime environment where business and technical users can update and manage store data and preview changes. The changes can then be propagated to the production environment.
  - Workspaces
    Workspaces provide a powerful and flexible way to manage and preview changes to your e-commerce website without affecting the live production environment.
  - Commerce+ database
    As a site administrator, maintain the Commerce+ database and ensure that any Commerce+ utilities and processes that load and retrieve data from the database is configured to connect to the database properly.
  - Extracting and loading data
    Commerce+ provides utilities for preparing and loading data into a Commerce+ database. The loading utilities are flexible and you can continue to use these utilities when you customize the Commerce+ schema.
  - Administering Search
    HCL Commerce+ Search provides the core search capability for Commerce+, enabling product indexing and retrieval for customer queries across the storefront. It supports guided navigation, landing pages, and dynamic merchandising, helping shoppers quickly find relevant products while giving merchandisers tools to influence search results.
  - Logging services
    Commerce+ maintains a detailed set of logs related to a variety of processes and functions. These logs are available upon request.
  - Business events
    Each time that a command triggers a business event, a record is added to the BUSEVENT database table to persist data from the event. Event listeners and external systems (such as the Marketing component, a back end order management system, or an external analytics system) can use this data to perform further processing.
  - Business Object thresholds
    Applying limits on business operations reduces the risk of system attacks where unbound conditions might result in system failures.
- 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.
- 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.

Managing system personas for Inventory

Inventory Packaged Business Capability (Inventory PBC) uses persona-based access control and centralized Identity and Access Management (IAM) integration to secure inventory data.

Role-based permissions and organizational scoping keep internal operations secure, authorized, and auditable.

Objectives

Data security: Prevents unauthorized modifications and restricts visibility based on explicit user permissions.
Organizational scoping: Restricts user data access within the designated organization scope.
Auditability: Attributes all permission-based actions to a verifiable user identity for a secure operating model.

Supported Personas and Capabilities

Inventory PBC evaluates incoming user identity, organization, and persona claims to enforce access tiers.


Persona	Description	Allowed Actions	Restrictions
Inventory Manager	Internal administrative persona responsible for inventory operations.	View, create, edit, and update statuses for received inventory. View and update organized inventory. View and adjust available inventory between locations or stores. View and edit SKU configurations and overrides. Create and update expected inventory. Update purchase order statuses.	None.
System Administrator	Manage the inventory and location service.	Site Administrator role can call Inventory PBC APIs while working with the Commerce Lab. For more infromation, see Inventory Dashboard and Inventory Management for more information.	None.

Technical Mechanisms

Identity and Role Integration
Inventory PBC integrates with enterprise identity providers, such as Auth0, Azure AD, Okta, or equivalent centralized IAM platforms. For every incoming request, the interceptor evaluates:
- User identity claims
- Organization assignment
- Persona or role claims
Scope Enforcement and Security Boundaries
- Organization-scoped access: Permissions are bound to the assigned organization scope of the user. You cannot view or alter inventory if you are an unauthorized user for an organization.
- User interface and API enforcement: The user interface automatically hides restricted components. If you attempt an unauthorized action through an application programming interface (API) or direct endpoint access, Inventory PBC denies the request.