Creating a New Catalog
To being, navigate to SmarterCommerce|Catalog Management|Catalog and press Create a Catalog. Complete the information as described below. Next, define catalog nodes that will group similar items within your catalog.
Name | Explanation | Required | Requirements |
---|---|---|---|
Catalog ID | An identifier for the catalog. Internal use only. Use of “|” not allowed. | Yes | |
Name | Name of the catalog. This value is displayed on your website. | Yes | |
Image | An image that will be displayed on your website for this catalog. | No | |
Page | You might want to have a specific page to configure the catalog widget in a different way or maybe to add specific HTML content to the page. This optional value allows you to define if the catalog is going to be displayed on a specific page. The user can select the page to be used from the Site Pages. When using a specific page, the Catalog widget in this page must be configured to work with a specific catalog. (Designer property: Catalog ID) |
No | |
Sequence | When more than one catalog exists the catalogs will be displayed in ascending order based on the sequence number. | Yes |
Configuration
Name | Explanation | Required | Requirements |
---|---|---|---|
Retrieve Nested Items | In catalog structure when category nodes have child nodes under them that is referred to as nested. If your catalog is nested turn this option on to show products in the child nodes. | No | |
Configure On Each Category Node | This field is displayed when the Retrieve Nested Products option is on. There are two options to determine where products available in child nodes are displayed. The options are “Configure on each category node” and “Starting at level” and only one can be selected at a time. By selecting this option you can determine on each node how the nested products will display. |
No | |
Starting at Level | This field is displayed when the Retrieve Nested Products option is on. There are two options to determine where products available in child nodes are displayed. The options are “Configure on each category node” and “Starting at level” and only one can be selected at a time. By selecting this option you can determine at which level of the catalog the nested items will show. All levels before this will show only nodes. |
No | |
Attribute Filters | This setting is available when the "Starting at Level" option is on. This setting determines if attribute filters are displayed on intermediate category nodes. On - Shows filters on all nodes Off - Filters are shown only on the product listing node |
No | |
Navigation Links | Navigation links are enabled in final nodes or when the configuration is set to show products available in child nodes. This field is displayed when the "Retrieve Nested Products" option is on and the "Starting al Level” option is set to 0. |
No | |
Enable the Products Assembly Reference ID | Assembly products are those with many parts combined into one. Typically, images for assembly products have an exploded view where each part is numbered and then described using that number as a reference. When this setting is on the assembly reference ID field will be available. |
No |
Branch Plants
Name | Explanation | Required | Requirements |
---|---|---|---|
Branch Plant | If the Filter Products by Branch Plant Mode is set to "Filter by MCU" then these are the branch plants that will be used to filter. That means that only products that exist in these specific branch plants will be available in the catalog. |
No | |
Filter Products by Branch Plant Mode | When you create your catalog you relate items to the catalog nodes. This option allows you to further filter the catalog: Do Not Filter - show all items in the catalog Filter by Customer - Only show products that are related to the Customer’s assigned MCU Filter by MCU - Only show products that are related to the catalogs selected Branch Plant(s). |
Do not apply | |
Branch Plant Behavior for Add to Cart | When at least one branch plant is selected for the catalog this option is available. This option determines if and how the branch plant will affect the shopping cart header & lines in your JDE/ERP. This affects pricing, availability, sourcing, and revenue recognition for the product / transaction. Do Not Pass Branch Plant - Don’t send the catalog MCU to the shopping cart
header or lines Pass to Shopping Cart Lines Only - Send the catalog MCU to the shopping cart lines. This enables pricing, availability, and sourcing to always come from one specific branch for products within this Catalog. Kits are excluded from this logic. Pass to Shopping Cart Header and Lines - Send the catalog MCU to the shopping cart lines and the sales order header. This will enable pricing, availability, sourcing, and revenue
recognition to always come from one specific branch for products within this
Catalog. Kits are excluded from this logic. |
No |
HTML Content
Name | Explanation | Required | Requirements |
---|---|---|---|
HTML Content Section | Here you may choose to manually enter specific content for this catalog or use promotional (shared) content. You may use up to 3 pieces of content. |
No | |
Shared | Catalog HTML Content may either be catalog specific (you type the content here) or pulled from Promotional Content. If you want to use shared (Promotional) content select this option and then choose the shared content to use. | No |
Search Engine Optimization
Name | Explanation | Required | Requirements |
---|---|---|---|
Title for Search Engines | Title for search engine metadata. If this field is empty, then Catalog Id will be used. | No | |
Description | Description for search engine metadata. If this field is empty, then Name is used. | No | |
Keywords | Used for search indexes. Separate multiple works with a comma. | No |
More Options
Name | Explanation | Required | Requirements |
---|---|---|---|
URL | The URL for the page. Can be edited to make more friendly. | Do not apply |