Home
User Guide
The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.
Developing
The topics in the Developing section describe tasks performed by an application developer.
Customizing WebSphere Commerce
You can extend the WebSphere Commerce product to fit your business needs. This topic describes the prerequisite skills and required knowledge that you need to customize business logic. After you have the required knowledge, use WebSphere Commerce Developer to take tutorials that guide you step-by-step through various customization scenarios.
Catalog subsystem
The catalog subsystem is a component of the WebSphere Commerce Server that provides online catalog navigation, partitioning, categorization, and associations. In addition, the catalog subsystem includes support for personalized interest lists and custom catalog display pages. The catalog subsystem contains all logic and data relevant to an online catalog, including catalog groups (or categories), catalog entries, and any associations or relationships among them.
Catalog entries
Catalog entries represent merchandise in an online catalog that often includes a name or part number, a description, one or more offer prices, images, and other details. A catalog entry can be a product, item, package, bundle, or dynamic kit.

Catalog entries

Catalog entries represent merchandise in an online catalog that often includes a name or part number, a description, one or more offer prices, images, and other details. A catalog entry can be a product, item, package, bundle, or dynamic kit.

Catalog entries can be a single item (atomic) or composed of several other catalog entries (composite). When atomic, a catalog entry is an individually orderable entity that needs no further SKU resolution. When composite, a catalog entry represents unresolved products, packages, or bundles that may need additional information before becoming atomic entities.

Certain catalog entries may need further processing before being added to an order. An example is resolving a product into an item through SKU resolution, performed by the ResolveSkuCmd task command.

If necessary, you can create new CatalogEntry type objects that do not fit into one of the existing Product, Item, Package, Bundle, or DynamicKit models.