| Term | Definition |
|---|---|
| Attributes | Properties that define a product and its stock keeping units (SKUs). For example, Name, Description, Material Type, Color, Size, etc. |
| Bundles | Allows merchandisers to group related products so that they can be presented and sold together. Bundles require that the consumer/buyer purchase the entire bundle. See also collections. |
| Catalog | A container for the set of information about individual products and stock keeping units (SKUs) for a store. |
| Catalog Editor | Defines and manages products and stock keeping units (SKUs) throughout the Commerce site and submits them to the catalog manager for approval. |
| Catalog Manager | Creates, manages, and approves changes to catalogs. |
| Collection | A group of related products (similar to bundles). However, in a collection, an end-user can choose to purchase only a subset of products in the collection and is not required to purchase the entire set of products as is the case in bundles. See also bundles. |
| Group | Products can be associated with one another as a Group. When products are part of a group, they are presented separately in the Product List Pages but when the customer visits the Product Detail Pages (PDP) for a product, the products in the group can also be easily purchased. |
| Master Catalog | The product catalog for a store from which any Sales Catalogs would inherit products and stock keeping units (SKUs). Products and SKUs are entered in the Master Catalog first, but may subsequently have different/overriding values in a Sales Catalog, while inheriting the Master Catalog properties. |
| Omni-channel | A multichannel approach to sales that seeks to provide consumers with a seamless shopping experience, whether shopping online (on a desktop or on a mobile or tablet device), by telephone, or in person at a physical store (https://searchcio.techtarget.com/definition/omnichannel). |
| Product | A good/service/idea that has a combination of tangible and intangible attributes and can have multiple variants which are referred to as stock keeping units (SKUs). In Infosys Equinox Commerce, the consumer/buyer evaluates a product (e.g. a men’s dress shoe available in black and brown and in sizes from 10 to 15), but actually purchases a SKU associated with the product (e.g. a black colored version of the dress shoe in size 12) rather than the product itself. |
| Product Data Enrichment | The process of providing contextual and useful product data and imagery to help consumers make quick and informed decisions about purchasing products, to increase the likelihood of a sale. |
| Project | A container/wrapper entity to hold changes made to a Catalog. New and updated catalog content must pass through the Project approval workflow process before it is reflected in the store’s catalogs. |
| Project Notes | Comments entered by project editor or approver to add context to project actions. |
| Project Workflows | Make business processes more efficient by managing and tracking the human tasks involved with a process and then providing a record of that process when it completes. |
| Sales Catalog | A subset of the Master Catalog, meant to provide a flexible display structure that allows a Catalog Manager to create a catalog that suits a store’s particular requirements. |
| Stock Keeping Unit (SKU) | A particular variant of a product which is available for purchase by a consumer/buyer. |
| Variant | A version of a product that differs in some respect from other versions of the same product. For example, a shoe called “Oxford Classic” is a product available in different colors and sizes (variants). |
Revision History
2019-04-30 | MA – Page created and content uploaded.
