A catalogCommerce: a top-level container for catalog entries such as categories, products, and variants (SKUs). consists of products and variants (SKUStock Keeping Unit; corresponds to a specific type of product with specific characteristics. For example, a product line of shirts have individual variations/SKUs that include size, color, and collar size.s) organized into a structure based on product categories or nodes. Products and variantCommerce: a variant or SKU corresponds to a specific type of product with specific characteristics. For example, a product line of shirts have individual variations/SKUs that include size, color, and collar size.s in the catalog have associated information such as pricing, markets, inventories, warehouses and assets, such as images and documents.
A productCommerce: various forms of merchandise that you can display and purchase from the public site, including products, variations/SKUs, bundles, packages and dynamic packages. can exist in one or more catalogs. Catalogs are independent from one another, and you can create as many catalogs as you want and assign them to one or more websites. You often import product catalogs from other integrated systems, but you also can create them manually.
Further, you can define the dates that each catalog is available so that you can prepare future revisions to items and pricing, and review them in advance of the release date to the site.
This documentation describes examples from the sample catalog delivered with the Episerver Commerce sample site. Your installation may look different from the sample catalog.
You can structure a catalog in a number of ways. For example, you may have various brands or product lines, and each brand or product line can have its own catalog. Or, a retailer may have multiple suppliers, and you can segment each supplier into its own catalog. The catalog is the top-level container for all types of catalog entries. See Creating a catalog entry for information about types of catalog entries.
You can define your own meta-classes and meta-fields for both catalogs and orders in the Administration part of Commerce Manager. For example, if you create a meta-class called Wine, you can add meta-fields—such as color, taste, vintage and maturity—that are characteristics for a wine catalog.