Home
Documentation
HCL Commerce is a high-availability, highly scalable and customizable e-commerce platform. Able to support hundreds of thousands of transactions per day, HCL Commerce allows you to do business with consumers (B2C) or directly with businesses (B2B). HCL Commerce uses cloud friendly technology to make deployment and operation both easy and efficient. It provides easy-to-use tools for business users to centrally manage a cross-channel strategy. Business users can create and manage precision marketing campaigns, promotions, catalog, and merchandising across all sales channels. Business users can also use AI enabled content management capabilities.
Samples
Topics in the Samples category highlight the various samples that are provided with HCL Commerce.
Store samples
HCL Commerce includes sample storefront designs that illustrate the use of the remote store model.
Next.js starter store
The Next.js store offers customizable features for storefronts using the Next.js framework. It uses the same data template as the ReactJS stores 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 Elasticsearch for search functions.
B2B Next.js starter store
The Next.js store application is enabled for B2B e-commerce. The sample B2B storefront is called Ruby B2B. The B2B Next.js store features include B2B features, in addition to all of the available features in the B2C storefront, with the exception of guest-user shopping flows.
Organization Management
Buyer Administrators access and control a structured list of organizations in a tabular format.
Edit Organization Details
Buyer Administrators for the Ruby B2B organization can use the Edit organization page to view and edit organization details.

Documentation
HCL Commerce is a high-availability, highly scalable and customizable e-commerce platform. Able to support hundreds of thousands of transactions per day, HCL Commerce allows you to do business with consumers (B2C) or directly with businesses (B2B). HCL Commerce uses cloud friendly technology to make deployment and operation both easy and efficient. It provides easy-to-use tools for business users to centrally manage a cross-channel strategy. Business users can create and manage precision marketing campaigns, promotions, catalog, and merchandising across all sales channels. Business users can also use AI enabled content management capabilities.
- Getting started
  HCL Commerce has different advantages for business users, administrators and developers. HCL Commerce targets each of these roles with a tailored set of offerings so that each of your users can get maximum benefit.
- Installing and deploying
  Learn how to install and deploy HCL Commerce development environments and HCL Commerce production environments.
- Migrating
  Before you migrate to HCL Commerce Version 9.1, review this information to help plan and execute your migration.
- Operating
  Topics in the Operating category highlight tasks that are typically performed by business users, customer support representatives, to complete their day-to-day tasks in the operation of the HCL Commerce site.
- Integrating
  Topics in the Integrating category highlight the tasks that are commonly performed for using HCL Commerce in combination with other products.
- Administering
  Topics in the Administering category highlight tasks that are typically performed by the Site Administrator, to support daily operations of the HCL Commerce site.
- Customizing
  The topics in the Customizing section describe tasks performed by an application developer to customize HCL Commerce.
- Tutorials
  HCL Commerce provides many tutorials to help you customize and understand your HCL Commerce instance and stores.
- Samples
  Topics in the Samples category highlight the various samples that are provided with HCL Commerce.
  - Store samples
    HCL Commerce includes sample storefront designs that illustrate the use of the remote store model.
    - Aurora starter store
      The Aurora starter store showcases the latest in storefront features, and models best practices in store development, demonstrating a wide scope of retail scenarios. Simplify your responsive B2C or B2B web store implementation and reduce your time-to-market by using the Aurora starter store as your development base.
    - Extended sites starter store
      Use an extended sites starter store to get started on setting up an extended sites solution that will allow your selling organization to provide unique storefronts for different enterprise customers or showcase a number of branded storefronts.
    - Reference React stores
      The Store SDK includes a reference B2C (Emerald) store application and a reference B2B (Sapphire) store application. Use these Reference Store applications to develop and deploy your own React Store applications.
    - Next.js starter store
      The Next.js store offers customizable features for storefronts using the Next.js framework. It uses the same data template as the ReactJS stores 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 Elasticsearch for search functions.
      - B2C Next.js starter store
        The Ruby store (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.
      - Multiple Extended Site (eSite) access
        The Next.js store supports multiple eSite access with a single deployment.
      - Locating a nearby store using the Store Locator feature
        The Store Locator feature allows the shopper to easily locate a physical store of their choice by using online maps. This feature is especially designed to enable them to physically pick up the products bought online, from a store of their choice.
      - Multiple Payment for the Next.Js Store
        Shoppers buying products in Next.js stores can pay a part of the total cart value by using various payment options such as cash on delivery or credit cards with the introduction of the multiple payment option.
      - Multiple Shipment for Next.Js store
        Shoppers purchasing products via react-based stores could only place an order for a single shipping address can now choose a multiple shipment option when placing an order. This document provides information on the multiple shipment facility provided to shoppers for the Next.js stores.
      - Using the Buy Online Pickup In Store (BOPIS) feature
        The BOPIS feature allows the user to pick up the products purchased online from a physical store of their choice, without any pickup charges.
      - Multiple languages for Next.js store
        The Next.js store applications (Ruby and Ruby B2B) support multiple languages.
      - Product compare feature
        The product compare feature allows you to compare items from the Product Listing Page (PLP) in tabular form on a dedicated screen.
      - Kit details page of Next.js store (B2C and B2B)
        A kit is a collection of items that are sold together as one catalog entry. The default layout for the page displays the kit name, image, price, short description, long description, descriptive attributes, and more. Users can check inventory availability for the kit and add the kit to their cart or current order.
      - Bundle details page of Next.js store (B2C and B2B)
        The Bundle page displays various combinations of items (bundles) in tabular form, which allows you to select attributes for products and their variants. The default layout for the page displays the bundle name, image, price, short description, long description, descriptive attributes, and more. Users can check inventory availability for the components in the bundle and add the bundle to their cart or current order.
      - Checkout
        The checkout page displays the shipping and payment details for the items in the shopping cart.
      - Enable the guest shopping
        In the Next.js store, you can enable guest shopping for customers. The steps involve enabling the related policies and guest shopping flex flow in the Management Center for HCL Commerce. You can then verify that guest shopping is enabled by browsing the store catalog and placing an order as a guest customer.
      - Disable the guest shopping
        In the Next.js store, you can disable guest shopping for customers. The steps involve disabling guest shopping flex flow in the Management Center. You can then verify that guest shopping is disabled by attempting to browse the store catalog and place an order as a guest customer.
      - B2B Next.js starter store
        The Next.js store application is enabled for B2B e-commerce. The sample B2B storefront is called Ruby B2B. The B2B Next.js store features include B2B features, in addition to all of the available features in the B2C storefront, with the exception of guest-user shopping flows.
        Registration of new organizations and buyers
        The Registration page of a Ruby B2B is a dual-purpose page that supports the registration of both buyers and organizations.
        Product details
        Customers use the B2B product details page to view details about a product. The layout that is assigned to the page displays the product name, price, full image, short description, the defining attributes, and more.
        Requisition Lists
        Users can use Requisition Lists to periodically reorder the same items. User can add frequently ordered items to a private or shared requisition lists. To use this feature on Ruby B2B store, user must navigate to Account settings and click Requisition Lists in the Order Management section.
        Recurring Orders
        In the Ruby B2B store, Recurring Orders allow users to create automatic orders for products on a schedule.
        Organization Management
        Buyer Administrators access and control a structured list of organizations in a tabular format.
        Create new organization
        Buyer Administrators for a B2B organization can use the New Organization page to create suborganizations. Buyer Administrator can also select roles that can be assigned to buyers who belong to the new organization.
        Edit Organization Details
        Buyer Administrators for the Ruby B2B organization can use the Edit organization page to view and edit organization details.
        Buyer Management
        The Buyer management involves administering buyer accounts and access within an organization. This involves tasks like creating, editing, enabling/disabling accounts, and maintaining control over assigning roles to new buyers who register.
        Buyer and Order approval
        In the Ruby B2B store, Buyer Administrators can manage and approve registered buyers through the Buyer Approval page.
  - Access control policy samples
    The following access control policy samples show you how some basic access control policies can be used in the development environment, so that you can quickly test new resources. They are not designed to be used as-is on an HCL Commerce production environment, as they do not provide adequate resource protection.
- Compliance
  The following section describes how you can leverage HCL Commerce features and functionality to help your site be compliant with different privacy and security standards.
- Securing
  These topics describe the security features of HCL 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 HCL Commerce site performance.
- Troubleshooting
  Topics in the Troubleshooting section highlight common issues that are encountered with HCL Commerce, and how they can be addressed or mitigated.
- Reference
  Topics in the Reference section contain all of the HCL Commerce reference documentation.

HCL Commerce Version 9.1.15.0 or later

Editing Organization details

Buyer Administrators for the Ruby B2B organization can use the Edit organization page to view and edit organization details.

About this task

The Edit organization page is structured into various sections. Buyer Administrators can expand a section, edit the information, and save the changes using Finish button.

Note: The Cancel button redirects Buyer Administrators to the Organization Management page.

Approvals: This section allows Buyer Administrator to enable or disable order approvals and buyer approvals. Approval types are inherited from the parent organization by default. The selected approval settings also determine the individuals authorized to approve orders or buyer registrants within the current organization.

Order approvals: Users who belong to the current organizations order approval group can approve orders.
Do not inherit order approvals: Select Do not inherit order approvals if the parent organization has order approval roles, and the child organization no longer requires them.
Note: The organization is assigned the role of Order approvals to approve new orders in the store. A Buyer Administrator has an edit role of the organization set to Do not inherit order approvals. Pending orders should be either approved or rejected first. Failing to do so will prevent the approval or rejection of pending orders at a later stage. Once the Do not inherit order approvals role is assigned, the organization cannot view pending orders for approval.
Buyer approvals: Users who belong to the current organizations buyer approval group can approve orders.
Do not inherit buyer approvals: Select Do not inherit buyer approvals if the parent organization has buyer approval roles, and the child organization no longer requires them.
Note: The organization is assigned the role of Buyer approvals to approve new buyers in the store. A Buyer Administrator has an edit role of the organization set to Do not inherit buyer approvals. Pending buyer approval requests should be either approved or rejected first. Failing to do so will prevent the approval or rejection of pending buyer requests at a later stage. Once the Do not inherit buyer approvals role is assigned, the organization cannot view pending buyer requests for approval.