Open topic with navigation

Creating product types and catalogs

IMPORTANT: Ektron has discontinued new development on its eCommerce module. If you have a license to eCommerce, you will continue to receive support, but if you need to upgrade, contact your account manager for options.

After you configure the eCommerce site, build eCommerce products in the following order:

Creating product types

Create a separate product type definition for each category of catalog entries that you sell. For example, you might have a product type for movies, another for books, a third for electronics, and so on.

When thinking about creating new product types, the most significant differences are the Class field and the content page, which defines the XML Smart FormAn Ektron-defined Web page that contains XML (hidden from the end user) to display content, and receive, verify, and save user input. for products you will create for a Product Type.

Product classes

A catalog entry’s product class affects customers’ purchasing options.

  • Kit. Lets a customer (site visitor) select from any number of free-text options. Options can increase or decrease the overall price. See also: Creating a kit.

    Example: A computer whose price changes as a customer selects RAM, hard drive, monitor, and so on.

  • Bundle. A catalog entry consisting of several other catalog entries bundled together. Its pricing, shipping, images, and so on, are independent of the individual items. See also: Creating a bundle.

    Example: A living room set: couch, end tables and lamps. Instead of buying each item separately, the customer buys all for a “package” price.

  • Product. Simple or complex catalog entries. A complex product is a “wrapper” that provides links to related simple products. Each simple product has its own SKU, price, inventory data, and so on. See also: Creating a complex product.

    Example: A movie in 3 formats and prices:

    • VHS ($12.95)
    • DVD ($14.95)
    • Blu-ray ($17.95)
  • Subscription. A catalog entry which can provide access to designated site pages, and may billed on a recurring basis. See also: Creating a subscription.

    Example: website content that is only available to subscribed members

How product types affect the creation of catalog entries

Catalog folders generally contain the same kind of catalog entries, such as DVDs or digital cameras. Some information applied to a catalog folder is inherited by all entries in the folder.

After you create product types, apply appropriate types to existing catalog folders using the Catalog Properties screen’s Product Types tab. Then, when creating a new catalog entry, you first go to a catalog folder. Next, click New and choose a product type assigned to the folder. See also: Assigning a catalog folder’s product type

A product type determines the following aspects of the associated catalog entries:

There are 2 steps to creating a product type.

Step 1: Defining properties, attributes, and media defaults

To create a product type:

  1. Go to Workarea > Settings > Commerce > Catalog > Product Types > New > Product Type.
  2. Click the Properties tab.
  3. Enter a unique product type title in the Title field. The title identifies this entry on the View Product Types screen. Also, when creating a new catalog entry, users must pick a product type from the catalog’s New menu.
  4. Enter a description for the product type in the Description field.
  5. Select a product class from the Class drop-down menu. For information about how class types affect how products are displayed, see Creating a kit, Creating a bundle, Creating a complex product, and Creating a subscription. In some cases, you will need to perform additional steps on other screens.
  6. Click the Attributes tab.
  7. Click Add Attribute. The Add Attribute dialog box appears.
  8. Enter an attribute name in the Name field, such as color.
  9. Choose a data type from the Type drop-down menu.
    • Text
    • Date
    • Number
    • Yes or No (boolean)
  10. Click OK. When a customer views the chair’s product page, the customer sees the attribute text below the thumbnails.
  11. Click the Media Defaults tab.
  12. Click Add thumbnail. The Add thumbnail dialog box appears.
  13. Enter a name for the thumbnail in the Name field.
  14. Specify the size if the thumbnail in pixels using the Width and Height fields.
  15. Click OK.
  16. Click Save. The XML Smart Form editor appears, as described in Step 2: Creating the content page.

Creating a kit

A kit is a type of catalog entry that allows a customer to select from free-text options, which can affect the item’s price. The options can also be placed into logical groups.

For example, if a catalog entry is a laptop computer, one group may let you enter options for RAM, another for operating system version, and a third could present hard drive options.

There is no limit to the number of groups you can add, nor the number of options in a group. All groups and options are simple text, created on a kit’s Items tab as needed, and can accommodate a price modifier. The following example shows how to set up chair color combinations.

In this example, the options do not affect the price. Here is how the options appear on a product page.

Consider another example in which the price does change. In this case, use the Item screen’s Price Modifier field to adjust price based on the chair frame. For example, if the chair frame is teak, the sale price increases by $25.00.

Other chair materials might adjust the price.

  • Wrought Iron. $0.00
  • Aluminum. +$15.00
  • Steel. -$10.00

Note how the Price Modifier can either increase or decrease the sale price. Here are these options on the product page.

The chair’s base price is $79.99, and the teak frame increases it to $104.99.

Creating a bundle

A bundle consists of several simple products. You would use it to combine several existing products into one “umbrella” catalog entry. That entry captures pricing, SKU number, shipping, and inventory information for the bundle. The information for the individual entries that make up the bundle are not affected when one is ordered.

As an example of a bundle using furniture, assume your eCommerce site sells a chair, a table, and an ottoman separately. You also sell them together as a set.

Use a bundle to define the set, add pictures, pricing, and so on. On the bundle’s Items tab, you select the individual catalog entries that make up the bundle.

Here is how this bundle looks on a product page.

Creating a complex product

A Complex Product is similar to a bundle in that one catalog entry serves as an “umbrella” for other entries. However, unlike a bundle, a customer must select one of the catalog entries. So, the price is that of the selected entry, not the umbrella item.

The advantage of a Complex Product is its ability to consolidate several related items under one title, yet lets customers choose the item they want. Because each item under the umbrella is its own catalog entry, it is priced and tracked separately.

For example, a site sells movies in 3 formats: VHS, DVD, and Blu-ray. Each is priced differently. To accommodate this, create catalog entries for the movie in each format, assigning images, SKU number, pricing, dimensions, and so on. Then, create a Complex Product, make its title the title of the movie, and use the Items tab to select the catalog entries of the individual formats.

The Product List or Product Search control displays the Complex Product, which is the movie title. When a customer selects that, the customer sees the product page, which lists the format and price of each assigned catalog entry. The customer can only choose one.

Unlike the Kit or Bundle, a complex product does not have its own product class. Instead, you create a catalog entry whose product class is Product, then assign other catalog entries to it via the Items tab. As soon as you assign one catalog entry via the Items tab, the original catalog entry is converted to a Complex Product.

Note that the price of the “umbrella” product appears on the Product List and Product Search server controlA server control uses API language to interact with the CMS and Framework UI to display the output. A server control can be dragged and dropped onto a Web form and then modified.s. This can be misleading, since the price of individual items within the complex product can vary.

You cannot apply tier pricing to a complex product. See also: Tier pricing

Creating a subscription

A subscription is a good or service which

  • can be billed on a one-time or a recurring basis
  • places users who purchase it into a designated membership group, letting you grant them access to private content

Examples include

  • content only available to members who purchase a subscription
  • a gym membership
  • a book club, in which a customer makes the same payment and receives a different book each month
  • anti-virus software that expires after 12 months
  • a 3-year maintenance contract on a digital television, payable yearly

If you use the recurring billing feature (a series of scheduled payments), the bill can be generated for any number of months or years, but no other time increments. Each payment must be the same for the subscription’s term. The term begins when a customer submits the order.

Customers cannot apply a cart-level coupon to a subscription-based catalog entry. See also: Creating a coupon.

Creating a subscription-based catalog entry

Creating a subscription is the similar to creating a regular catalog entry:

  1. Create a subscription-based Product Type. On the Product Type screen’s Class drop-down, select Subscription.
  2. Assign the Product Type to a catalog folder. See also: Creating a catalog folder.
  3. In that folder, create a catalog entry for each subscription.
  4. On the Pricing tab, enter the cost.

    If using recurring billing, enter the term of the subscription. To learn about Recurring Billing fields, see Entering recurring billing information.

    If this product does not use recurring billing, click No at the Use Recurring Billing drop-down. To learn about the Unit Pricing fields, see Entering a catalog entry’s price information.

  5. On the Items tab, assign membership and Ektron user groups. See also: Assigning groups to a subscription-based catalog entry.
  6. If a subscription provides access to Ektron content, use its folder Permissions screen to grant permission to the membership and Ektron user groups you defined in Step 5. See also: Subscriptions involving Ektron content.

Subscription-based products do not support tier pricing. See also: Tier pricing.

Entering recurring billing information

IMPORTANT: Due to differences in the way payment gateways work, you should test recurring payments with your gateway before processing live transactions.

The Pricing tab’s Recurring Billing area of a subscription-based catalog entry lets you determine if a subscription is billed on a one-time or a recurring basis. If recurring, it helps you define the terms.

To set up recurring billing:

  1. Select Yes from the Use Recurring Billing drop-down. The recurring billing term begins when a customer submits an order, and is based on a number of months or years.
  2. Select a time interval from the Billing Cycle drop-down.
  3. Enter a number of Billing Intervals for which a customer is charged. For example, if a customer should be charged once a month for 12 months, complete the screen as shown above. If a customer purchases the item on June 1, 2013, the person's credit card will be billed on the first of each month from June 1, 2013 to May 1, 2014.

As another example, if a customer should be charged once a year for 3 years, complete the screen as shown.

If a customer purchases the item on June 1, 2013, the person's credit card will be charged on the following dates.

  • June 1, 2013 (purchase date)
  • June 1, 2014
  • June 1, 2015

Assigning groups to a subscription-based catalog entry

You must assign a membership user group to a subscription-based catalog entry. Optionally, you can assign an Ektron user group. You assign groups via the subscription’s Items tab.

See also: Membership groups

So, as part of setting up a subscription, you must either create new membership and (possibly user) groups, or use existing groups.

All users (identified by their email address) who purchase the product are automatically added to one of the groups. Ektron checks a user’s email address to determine if the user is an Ektron or a membership user.

  • Ektron users are added to the group defined in the CMS Author Group field
  • Non-Ektron users are added to the membership group defined at the Member Group field

Subscriptions not involving Ektron content

If a subscription does not involve access to Ektron content, the membership group provides a list of customers who purchased the subscription. You can use the list to manage the accounts, notify them when the subscription is about to expire, and so on.

Subscriptions involving Ektron content

If a subscription involves access to Ektron content:

Create a folder and enable one or more subscription-based product types on its Product Type screen.

Place the subscription products in that folder. Customers shop for and purchase this content on your website as they do all products, via eCommerce server controlA server control uses API language to interact with the CMS and Framework UI to display the output. A server control can be dragged and dropped onto a Web form and then modified.s.

Then, create a regular content folder in which to create the confidential content. Next, use the content folder’s Permissions screen to grant the subscription user groups access to that folder.

See also: Managing folder and content permissions and Assigning membership permissions

Step 2: Creating the content page

After you complete and save the Add Product Type screen, a new screen lets you enter XML Smart Form information. On this screen, you set up fields to collect information for the content page of catalog entries based on this product type.

The content page appears on the Product server controlA server control uses API language to interact with the CMS and Framework UI to display the output. A server control can be dragged and dropped onto a Web form and then modified., describing this catalog entry to customers. The process of creating a product type content page is the same as creating an XML Smart Form, described in Adding a Smart Form configuration.

Editing a product type

  1. In the Workarea, go to Settings > Commerce > Catalog > Product Types.
  2. Click the product type that you want to edit.
  3. See Step 1: Defining properties, attributes, and media defaults.

NOTE: You cannot edit a Product Type’s Class.

Viewing an attribute's published status

Each attribute has a publication status. To view attribute status, go to Settings > Commerce > Catalog > Product Types, select a product type and click the Attributes tab.

  • Active. Attribute can be assigned to catalog entries
  • Inactive. Attribute already assigned to one or more catalog entries, but can no longer be assigned. To make an attribute inactive, click the corresponding Mark for Delete ().
  • Not Published. Attribute has been created but Product Type not saved yet
  • Active (marked for delete with strike through). Attribute will be deleted when Product Type is saved.

You can delete an attribute only if it is not applied to a catalog entry. If you try to delete an attribute applied to a catalog entry, it is marked “Inactive.” Inactive attributes can no longer be assigned.

Deleting a product type

Prerequisite

The product type is not assigned to any catalog entries.

  1. In the Workarea, go to Settings > Commerce > Catalog > Product Types.
  2. Click a product type you want to delete.
  3. Click Delete ().
  4. Click OK.

Although you cannot delete a product type that is being used, you can prevent users from creating new catalog entries based on it. To do this, go to each applicable folder’s Catalog Properties > Product Types screen and remove that product type.

Creating a catalog folder

Prerequisite

One or more product types.

A catalog folder is a special kind of Ektron folder designed to hold eCommerce entries. Its unique icon () distinguishes it from other folder types. If you are familiar with content folders, much of that information applies to catalog folders. See also: Setting up your CMS folder structure

A Catalog folder's properties screen has several tabs/screens. The following screens are the same as regular content folders.

The unique screen is Product Types. See also: Assigning a catalog folder’s product type.

Like content folders, the following catalog folder information can be inherited from its parent or uniquely set for each catalog. You can only make changes after creating the catalog.

Assigning a catalog folder’s product type

A catalog folder’s Product Types screen lets you identify product types upon which catalog entries can be based. For example, you created a lawn mower Product Type, and want only lawn mowers to be entered in a catalog folder. In this case, open a catalog folder’s Product Types tab, break inheritance if necessary, and select Lawn Mower as the catalog’s only product type.

Then, when an Ektron user creates an entry in this catalog, the user must use the Lawn Mower product type.

Deleting a catalog folder

Prerequisite

No catalog entries in the folder have been placed on an order

  1. Go to the folder that you want to delete.
  2. Choose Delete > This Catalog.
  3. Click OK.

Searching a catalog folder

Searching a Catalog folder is the same as searching any other type of Workarea folder. This procedure is described in Searching the Workarea.

Creating a catalog entry

Prerequisite

One or more catalog folders.

A Catalog entry is the eCommerce term that describes a product sold on your website. It is similar to content in the rest of Ektron, so those concepts also apply to catalog entries.

Catalog entries are built from Ektron XML Smart Forms, so use the same content and folder structure as other Smart Forms. See also: Working with Smart Forms

Catalog entries share the following features with regular content:

Catalog entries also have unique information:

Because there is so much information to provide about managing catalog entries, this section takes 2 approaches:

Creating/updating catalog Ee

  1. For information about the catalog entry screens, see Tabs on the catalog entry screen) The required fields are:
    • content Title
    • Properties tab > SKU Number
    • any fields on the content screen that your Ektron administrator has designated as required
  2. Check in or submit/publish the content.

After signing in to your website, you can also update a catalog entry’s information from there using the context menu.

If a new catalog entry is similar to an existing one, you might find it quicker to copy the existing entry then edit the fields that are different. Moving a catalog entry is the same as moving content. See Moving or copying content

Deleting a catalog entry

Prerequisites

Best Practice 

Avoid deleting catalog entries due to the affect on your website. For example, if you delete an entry from your staging site, then run eSync, that entry is removed from all active carts on your live site. Instead of deleting entries, you should archiveThe state of content upon reaching its end date. What happens next is determined by your choice at the content's Schedule tab > Action on End Date options field. Choices are * Archive and remove from site (expire) * Archive and remain on site * Add to CMS Refresh Report them using the Properties tab’s Archived checkbox.

If you want to prevent customers from purchasing an item, but you cannot delete it because it has been placed on existing orders, you have 2 options.

To delete a catalog entry:

  1. Go to the catalog folder that contains the entry.
  2. Click the entry.
  3. Choose Action > Delete. A warning message appears.
  4. Click OK. The catalog entry is deleted.

Tabs on the catalog entry screen

Menu options on the catalog entry screen

  • Action Menu
    • Save. Saves the catalog entry without leaving the editor. It is a good idea to save your work frequently.
    • Check in. Save and check-in the document. This action returns the changed content to the database and exits the editor. It does not submit the content into the workflowA core element of Ektron, workflow lets you set up a sequence of approvers who control the publication of content to your website.. Rather, it allows you and other users to continue changing it.
    • Submit/Publish
      • Submit the content into the workflow. This action also returns the new or updated content to the database and exits the editor.
      • Publish the content to the website. Only the last approver in the workflow sees this button. If no workflow is assigned to the content’s folder, every authorized user sees this button. See also: Approving content for publication This action also returns the changed content to the database and exits the editor.
    • Undo checkout. Exit screen and do not save changes made since you began editing this catalog entry.
  • Change Menu
    • Comment. Enter comments on changes made when editing a catalog entry. The comment also appears on the View Content and Content History screens. Use it to help distinguish one version from another.
    • Template. A folder’s default template is automatically applied to all content in the folder. However, you can change a content item’s template to any of those assigned to the folder.

Entering a catalog entry’s content

The Content tab displays the content page of this catalog entry’s product type. Because the format is customized for your system, this documentation cannot explain how to respond to the fields.

To learn about working with the editor, see Editing in Ektron.

Entering a catalog entry’s summary

Creating summaryA short description that supplements a content item's title on a Web page. Content authors compose a summary when creating or editing content. Server controls and widgets can display a content title and summary to attract readers to the full story. Summaries can include images and text formatting. information for a catalog entry is done the same as with any other type of content.

Entering a catalog entry’s properties

The Properties screen collects eCommerce-specific information about your catalog entries:

  • SKU. Enter a unique SKU code for this catalog entry. This is a required field that does not accept a value of zero (0) or a space character.
  • Number of Units. If this item has a quantity other than one (1) for internal record-keeping purposes only, enter that number.

    For example, a 12 pack of soda. Set Quantity is 12 to represent the number of units. But a customer still orders 1 of the item.

    The quantity is not used when this item is ordered, nor does it affect inventory levels. It is used for clerical purposes only.

  • Tax Class. Select the catalog entry’s Tax Class. See also: Configuring eCommerce tax screens.
  • Archived. Check this box if you want to archiveThe state of content upon reaching its end date. What happens next is determined by your choice at the content's Schedule tab > Action on End Date options field. Choices are * Archive and remove from site (expire) * Archive and remain on site * Add to CMS Refresh Report this catalog entry. When archived, customers can no longer see nor order it. Also, Ektron users cannot view an archived catalog entry in its catalog folder via the View Folders screen. To view it, open its catalog folder then select View > Archive.

    To make the entry available again on your website, open its archive folder, edit the entry by unchecking the Archived check box, and publish it.

    A catalog entry can also be set to Archived status if it reaches its expiration date and its Schedule tab > Action on End Date field is set to Archive and remove from site (expire).

  • Buyable. To let customers add this catalog entry to a shopping cart, check this box. Otherwise, uncheck it.

    If a product is not buyable, it can still be seen by customers, but its product page does not display an Add to Cart button.

  • Dimensions—Used to calculate packaging containers and shipping costs. See also: Packages
    • Tangible Item.

      Check this box if the item is tangible, that is, it has dimensions, weight, and will be shipped to a customer. Examples of non-tangible items are services, warranties, and downloadable software. If a catalog entry is tangible, you must enter its height, width, length, and weight.

    • Height. Enter the catalog entry’s height. The units of measure are specified in the web.config file’s ek_measurementsystem property.
    • Width. Enter the catalog entry’s width.
    • Length. Enter the catalog entry’s length.
    • Weight. Enter the catalog entry’s weight.
  • Inventory. eCommerce’s inventory system is a provider model, allowing you to connect with third-party inventory systems.
    • Disable Inventory. Check this box if you do not want to track inventory activity for this catalog entry. As examples, it is a service contract or a subscription to confidential content on your site.
    • In Stock. Enter the number of items on hand for this catalog entry. This number is automatically adjusted when an order containing this entry is submitted. For example, there are 100 items in stock. When an order for 10 is submitted, the In Stock value changes to 90. If the amount placed on an order exceeds the In Stock amount, the customer see this message “The item ... is not available for purchase. Please remove from cart before submitting order.”
    • On Order. The number of items that have been ordered but not yet delivered appears.
    • Reorder. Enter the In Stock quantity at which you need to reorder this item. When the In Stock quantity reaches this level, an event is triggered which can be used by an external inventory system to generate a new order.

Entering a catalog entry’s price information

Use the Pricing screen to enter price information for catalog entries.

  • Currency selector. Use this drop-down to select a currency for the prices. See also: Alternate currency pricing. Only enabled currencies appear. See also: Enabling currencies .
  • List Price. Enter the catalog entry’s list, or manufacturer’s suggested retail, price. The list price appears on most eCommerce controls but is not used in any calculations.
  • Our Sales Price. Enter the catalog entry’s sale price. This price is used to calculate line item totals, coupon discounts, shipping costs, and so on. The sales price appears on most eCommerce controls. .
  • Add Pricing Tier. See also: Tier pricing.
  • Recurring Billing (appears only for subscription-based products). See also: Creating a subscription.

Alternate currency pricing

By default, the Pricing screen converts prices to every enabled currency using the exchange rate. Customers who select a non-default currency see these prices. See also: Defining and updating exchange rates .

The Float checkbox (checked by default) indicates that prices change as the exchange rate changes.

If you do not want to float a catalog entry’s price, but instead fix it for a currency, select the currency, uncheck Float, edit the price, and publish. From then on, if a customer selects that currency and catalog entry, the price set on this screen is used. The exchange rate is ignored.

For example, a television costs 700 Euros, regardless of its cost in US dollars or the exchange rate. To incorporate this, do not check the Float checkbox.

When you first select EUR on the Pricing screen, the default currency’s prices are converted using the exchange rate. For example, the television’s sale price is $1000 US dollars, and today’s exchange rate is .7811. When you select Eur from the Pricing screen’s currency selector, the television’s cost is set at 781.10 Euros. You change the price to 700.00 Euros.

From that point on, the Euro price only changes if an authorized user accesses this screen and changes it manually.

Tier pricing

eCommerce supports tier pricing, that is, a pricing schedule that adjusts according to order quantity. Typically, the price is reduced as more items are ordered. For example, if a visitor orders 1-5, items are $10.00 each; 6-10, $9.00 each; 11 or more, $8.50 each.

Tier pricing is not supported for subscription products, nor for complex products.

To set up tier pricing:

  1. In the Workarea, open the catalog folder containing the entry to which you want to apply tier pricing.
  2. Edit the catalog entry.
  3. Click the Pricing tab
  4. Click Add Pricing Tier. The Tier Pricing screen section appears.

  5. In the left column, enter the quantity of items above which the tier price is used.
  6. In the right column, enter the price to be used when an order quantity exceeds the number in the left column.
  7. Enter as many tiers as necessary.

NOTE: To remove a tier, check the box to its left, then click Remove Pricing Tier.

Tier pricing and non-default currencies: when floated

If a non-default currency is floated, then that currency’s pricing tiers mirror the default currency’s pricing tier values. The amounts are adjusted by the exchange rate.

These values appear on pricing screen in view-only mode and cannot be changed.

If pricing tiers are set up for the default currency and the user unchecks the Float box, the user is notified that the pricing tiers can now be edited. Next, Tier Pricing fields are loaded with the existing values but the user can change values, remove existing tiers, and add new ones.

Tier pricing and non-default currencies: when not floated

If a non-default currency is not floated, its pricing tiers are independent of the default currency’s. That is, they do not exist initially regardless of whether they exist for the default currency. If the user clicks Add Pricing Tier, Tier Pricing fields appear and let the user enter number of units and corresponding tier price per unit.

If pricing tiers are set up for a non-default currency and the user checks the Float box, the pricing tiers are changed to mirror those of the default currency. If the default currency has no pricing tiers, then that currency has none. You cannot independently edit a non-default currency’s pricing tiers if Float is checked.

Entering a catalog entry’s attributes

Attributes are additional pieces of information that help describe a catalog entry. Attribute fields, data types, and default values are created as part of a Product Type. When you create a catalog entry, you base it on a product type. The product type’s Attribute information is imported to the catalog entry. Like metadata that follows Ektron content, if a catalog entry is moved to another folder, its attributes stay with it.

To illustrate the concept, the following attributes are applied to furniture in Ektron’s sample site.

In the Workarea, you select a catalog entry then click the Attributes tab to enter or modify attribute values. If no attributes are assigned to the product type on which a catalog entry is based, you will not see an Attributes tab when working with that catalog entry. You could change model year to 2009, or style to Woodland. You cannot however change fields, field names, or data types.

On your website, a catalog entry’s Attribute field names and values appear by default on the Product server controlA server control uses API language to interact with the CMS and Framework UI to display the output. A server control can be dragged and dropped onto a Web form and then modified..

Entering a catalog entry’s media

Use the Media tab to add product images that appear on the following server controlA server control uses API language to interact with the CMS and Framework UI to display the output. A server control can be dragged and dropped onto a Web form and then modified.s.

  • Product (the smallest thumbnail may appear)
  • Product List
  • Product Search
  • Recommendation

See also: Using images in eCommerce.

Adding a new image

  1. Click the Media tab.
  2. Click Add New Image. The add New Image dialog box appears.
  3. Enter an image Title (required).
  4. Enter the image’s Alt text (required).
  5. Click Browse and go to the image you want to add.
  6. Click Upload. The image is uploaded to the siteroot/uploadedimages folder and you are returned to the Media tab. The uploaded image appears on the screen, below any existing images.
  7. Determine if you want the image’s smallest thumbnail to appear on the Product server control by selecting Yes or No next to Gallery Display.
  8. If you want to designate the image as the product icon, click Set as Product Icon.

Image thumbnails and product icons are described in Using images in eCommerce.

When an image is uploaded to the Media tab, the original image and any thumbnails associated with it are added to the Library. For example, if you add an image named “TestImage” (actual file name: “case.jpg”) with a 150px and 50px thumbnails, you see the following entries in your library (File Name - Path):

TestImage - /~siteroot~/uploadedImages/case.jpg

case[filename]150 - /~siteroot~/uploadedImages/case[filename]150.jpg

case[filename]50 - /~siteroot~/uploadedImages/case[filename]50.jpg

If you assign several images to an eCommerce catalog entry, and want to allow searching for that catalog entry by image file name, the search only works with the first image assigned to the catalog entry.

Editing an existing image

NOTE: You cannot change an existing image. If you need to do this, delete the image you do not want, then add the correct one. You can only edit the Title and Alt Text.

  1. Click the Media tab.
  2. Move the cursor to the field that you want to edit.
  3. Click the pencil icon to the right of the field.>—Image—

  4. Update the text as needed.
  5. Click OK ().

Determining thumbnail size

When you create a catalog entry, you base it on a Product Type. The selected product type’s Media Defaults information determines the sizes of thumbnails created for each image assigned to the Media tab.

  • If the image is less than both thumbnail dimensions (height and width), it appears full size.
  • If the image is greater than the thumbnail’s dimensions, the image is reduced proportionately, scaling its dimensions to the thumbnail size.

The default image

If you do not assign an image to a catalog entry, but one is assigned to appear on a server control, the following default image is used.

If you want to change the default image, edit the following file: 

siteroot/WorkArea/images/application/Commerce/productImageBackground.gif

Entering a catalog entry’s items

Use the Items tab to add additional information to the current entry. You can only choose a catalog entry whose language matches the language of the original item. It is used in these situations:

  • to select the catalog entries that make a product into a complex product.
  • to select the catalog entries that make up a bundle.
  • to select the groups and their options that make up kits.
  • to select a subscription-based catalog entry’s user groups. See also: Assigning groups to a subscription-based catalog entry.

Folder view menu options

New Menu

  • Catalog. Create a new catalog folder underneath the current one. See also: Creating a catalog folder.
  • product types assigned to folder. Create a new catalog entry based on one of the displayed product types. Your product types may not match the following product types. Product types are assigned to a catalog’s via the Product Types screen. See also: Creating product types.

View Menu

Delete Menu

  • This Catalog. Lets you delete a catalog folder.
  • Entries. Lets you delete a catalog entry within a folder. You cannot delete a catalog entry that has been placed on any order. The order’s status is irrelevant.

Action Menu

Content view menu options

Action Menu

  • Edit. Edit the catalog entry.
  • Delete. Delete a catalog entry.
  • Link Search. Locates all content that includes a Quicklink to the displayed catalog entry. This feature is useful before deleting a catalog entry, because it informs you of every entry that will include a “dead” link if you delete that entry. You should then edit those catalog entries and remove or change the obsolete Quicklinks.
  • Add Task. Assigning and managing tasks

View Menu

Reports Menu

Editor view menu options

Action Menu

  • Save. Save the content without leaving the editor. It is a good idea to save your work frequently.
  • Check in. Save and check-in the document. This action returns the changed content to the database and exits the editor. It does not submit the content into the workflowA core element of Ektron, workflow lets you set up a sequence of approvers who control the publication of content to your website.. Rather, it allows you and other users to continue changing it.
  • Submit or Publish. Submit the content into the workflow. Publish the content to the website. These actions also return the new or updated content to the database and exits the editor. Only the last approver in the workflow sees this button. If no workflow is assigned to the content’s folder, every authorized user sees this button. See also: Approving content for publication
  • Undo Checkout. Close the editor without saving changes.

Change Menu

  • Comment. Briefly describe the content, or comment on changes made when editing content. The history comment appears on the View Content and Content History screens.
  • Template. Lets you specify one or more templates for catalog entries in this folder. These entries use the specified template when appearing on your website. See also: Working with templates

Displaying catalog entries on your website

The eCommerce Module provides the following server controlA server control uses API language to interact with the CMS and Framework UI to display the output. A server control can be dragged and dropped onto a Web form and then modified.s for displaying catalog entries on your website.

Open topic with navigation