Product Configuration


  1. From the Catalog>Products page in Admin, click Add New to create a new product
  2. Under the Product Info section update the following fields
    1. Product name *
    2. Short description and Long Description
      1. Short descriptions allowed- appears on the right on the PDP above 'add to cart'
      2. Long descriptions are not supported on retail product detail pages.
    3. Email Content - This is the content that will display in the email for guests who purchase this product, and will not display on the product detail page.
      1. Click Tools, then Source Code, and paste/enter text.
      2. Save and close the source code, and add any additional formatting in the editor.
    4. SKU (PHC) - If there is only one RTP ONE Product Header for the retail item (if there are no size or color combinations), enter the RTP ONE Product Header in the SKU field at the product level. If the RTP ONE Product Headers are defined at the attribute combination level, which is the case for any retail product with more than one size or color, leave the SKU field blank at the product level. You'll configure the product header codes at the attribute combination level for any product with more than one size or color.
    5. Categories - A product can be organized under one or multiple categories. (See category configuration for Category set up.)
      1. Sub categories for retail (such as shirts, hats, accessories) are not formally supported, but might work depending on your configuration.
      2. Multi-category assignment can also be used.
    6. Published * - Check to publish the product. If the product is published and belongs to a published category, it will be accessible publicly.
    7. Keep 'Product Type'
    8. Change 'Product Template' to 'Retail product'
      1. If you do not have a 'Retail Product' template already set up, follow these one time configuration steps for your store:
        1. Configure a retail product template in Aspenware Commerce: Administration>system>templates>product template
          1. Name: Retail product.
          2. View Path: ProductTemplate.Retail
          3. Display order: any numeric value


    1. Keep 'Visible individually' checked
    2. Available start date - Define this if the product should only be available on the store for a set time period (e.g. Dec. 1 through Dec. 31). The available start date will be the date that the product becomes visible on the site.

Note: These time and date settings are based on GMT/UTC, not the store default timezone.

    1. Available end date - Define this if the product should only be available on the store for a set time period (e.g. Dec. 1 through Dec. 31). The available end date will be the date that the product is not visible on the site. (Core Product Only).


Note: These time and date settings are based on GMT/UTC, not the store default timezone.


  1. Under the Price section update the following fields: (It may be collapsed)
    1. Price - If the price is defined at the product level, specify it here. If the price is defined at the attribute combination level (e.g. Color, size, etc. levels), enter a display price, which will be displayed on the product card as the Starting at or default price.
      1. This is the price that will appear on the product card that displays within the category
      2. Should be the lowest advertised price or the price of the defaulted attribute combination.


      1. Discounts can also be set here, and both dollar and percentage off discounts are supported with retail products.
        1. Discounts must first be configured in order to be applied (please see the 'Promotions' section in the overall documentation)
      2. Set your tax category if your retail products require taxes
        1. Resorts using Unity can configure taxes by shipping location to apply the tax rate which applies to the shipping address entered by the guest.
          1. Taxes by shipping location are only supported with Unity.
          2. Resorts using RTP|Connect can use fixed rate taxes ONLY.
            1. Note: The default tax for the audit location used by the store in RTP|ONE will be applied to the order. .
          3. Configuration in both Aspenware Commerce and RTP|ONE is required to specify different tax rates by region, state/province, or postal code if taxes by shipping location are turned on
            1. The tax rates by region, state/province, or postal code must be configured exactly the same in both Aspenware Commerce and RTP|ONE.
          4. Please refer to the tax set up and rules in the Aspenware Commerce Configuration Documentation.







  1. Under the Shipping section update the following fields: (It may be collapsed)
    1. Shipping enabled - Check this box if the product is "shippable."
    2. Additional shipping charge- set this to be the price you wish to apply for shipping charges on the product if you are charging for shipping.
      1. It's possible to have different shipping charges for different products.
      2. Order-level shipping is now supported for retail products. Order-level shipping applies the highest-priced shipping charge, and only that one charge, to the entire retail order.
        1. Previously, line-item shipping fees were applied to retail orders, which was not optimal, since shipping charges for each line item were added together and applied to the order, resulting in over-charging shipping and guest complaints. Line-item shipping is no longer supported. Do not configure any retail products to 'ship separately'.
      3. In order to enable order-level shipping charges, Aspenware must configure your RTP|ONE shipping product header code in Unity rtp-config.json. Please provide your client services representative with the product header code for your general shipping product. (Must be set up prior to selling a product live)

  1. Under the Inventory section update the following fields: (It may be collapsed)
    1. Inventory method - Set to 'Track inventory by product attributes' if you wish to use the retail sync from RTP|ONE in order to update Aspenware Commerce inventory daily, from RTP|ONE on-hand inventory levels for each SKU/Product Header code.
      1. Note{*}: If you don't want to track inventory levels from RTP|ONE in Aspenware Commerce, it's not mandatory. You have the option to select "do not track inventory" if your resort doesn't run out of online inventory, or if you don't want to implement the retail inventory sync. If you choose not to track inventory, your fulfillment personnel will need to deal with oversold/out of stock orders in RTP|ONE.
    2. Display availability- If you are tracking inventory in Aspenware Commerce, check this, since it will provide meaningful messages to the guest if he/she tries to add more products to the cart than are available in on-hand inventory.
    3. Display stock quantity- If you are tracking inventory in Aspenware Commerce, check this, since it will provide meaningful messages to the guest if he/she tries to add more products to the cart than are available in on-hand inventory
    4. Leave all other fields as is except 'Allowed quantities.' You have the option to set this to allow a guest to add more than quantity 1
      1. If you wish set this to 1,2,3,4,5 or whatever quantities you want to support for add to cart
      2. Note{*}: This will not update as your inventory is sold/decremented from on-hand.
    5. If you wish to enable the retail inventory sync scheduled task, which updates inventory in Aspenware Commerce from RTP|ONE on-hand inventory nightly, Aspenware must configure your retail inventory location code in Unity rtp-config.json. Please provide your client services representative with the retail inventory location code you wish to use for the ecomm inventory location. (Must be set up prior to selling a product live)
      1. The retail inventory location code does not need to be the same as the sale location code. The sale location code can continue to be your existing ecomm location, and the retail inventory code can be any retail store, or the warehouse, if you have a retail warehouse location configured in RTP|ONE.

  1. The retail inventory sync is a scheduled task.
    1. If you wish to enable retail inventory sync, contact your client services representative to have the database updated with this scheduled task.
    2. It should be scheduled to run once a day, any time after the RTP|ONE overnight cycle completes. Because RTP|ONE inventory is updated from POS sales that day in the overnight cycle, the retail inventory sync task should run after the overnight cycle completes in order to get the most recent on-hand inventory numbers each day.
    3. Retail inventory stock quantities are displayed at the attribute combination level for each SKU (noted below)
    4. On the Inventory tab, be sure to check 'display availability' and 'display stock quantity' to enable meaningful messages to the consumer when he tries to add more inventory than is available in the Stock Quantity for that item.
  2. Under the Pictures section add images for the product
    1. Upload the file, and once uploaded, click Add Product Picture.
    2. Dimension recommendations for image sizes:
      1. A square photo that is 1x1 (recommended to be 600x600 pixels) and in .jpeg form
    3. The images you add here will display on the PDP as thumbnail options. They will also be available for association to the attribute values for color options, as described below.