Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Error rendering macro 'excerpt-include' : No link could be created for 'Add-ons'.

Setup Checklist

This section is a comprehensive and high level summary of all tasks and prerequisites required for this feature to function properly. This section is purposed for use after an administrator is familiar with configuring this feature as an “audit” checklist. For detailed set-up instructions, jump down to “Prerequisite Tasks” and “Detailed Setup Guide” and then follow up with this checklist to ensure all steps are completed.

1. POS Tasks

RTP - The add-on product must be a fully configured product in the POS system and able to be sold in ONE|Resort.

  • Product is active REQUIRED

  • Approproiate Security level is set at or below the Aspenware User security level REQUIRED

  • Appropriate Sales Location for Aspenware assigned REQUIRED

  • Required Component(s) are added REQUIRED

  • Appropriate Sales Channel for Aspenware added REQUIRED

  • Pricing date ranges and/or pricing seasons are valid REQUIRED

  • Rules (ie Customer Required, PUB/Skiosk, etc) added to the product OPTIONAL

PREREQUISITES

Siriusware - The add-on product must be a fully configured Item in the POS system and should be able to be sold on Sales.

  • Add-on Item is priced for the current season REQUIRED

  • Add-on Item is available to be sold from Web Sales REQUIRED

  • Add-on Item is added to the Item Tree being used by the Online Salespoint REQUIRED

  • Add-on Item is set up as either: REQUIRED

    • A standalone DCI OPTION 1

    • Required modifier Item added to main DCI OPTION 2

PREREQUISITES

2. Infrastructure Tasks

Unity - Connectivity between Aspenware Commerce and the POS system has been fully established through Unity. REQUIRED

PREREQUISITES

3. Aspenware Commerce Tasks

Core Product Configured

  • A fully configured and functioning published product must be created in order to associate an add-on product to it. REQUIRED

  • A hidden add-on category exists. REQUIRED

PREREQUISITES

Feature Setup

1. Create an add-on product

2. Create an attribute that will house the add-on connection to the core product REQUIRED

3. Associate the add-on to an existing core product through an attribute REQUIRED

DETAILED SETUP

Prerequisite Tasks

This section describes all requirements that must be completed before you can begin setting up this feature. Once these tasks are complete continue to the next section.

1. POS Tasks

RTP - The product must be a fully configured product in the POS system and able to be sold in ONE|Resort.

  • General tab

    • Product is active

    • The appropriate Security level is set at or below the Aspenware User security level.

    • Optionally set the Validate Customer Procedure if needed for features such as Arrival tablets

  • Sales Locations

    • Appropriate Sales Location for Aspenware is assigned

  • Components

    • Required Component(s) for the product have been added.

  • Sales Channels

    • The appropriate Sales Channel for Aspenware has been added.

  • Pricing

    • Pricing date ranges and/or pricing seasons are valid.

  • Rules

    • Optionally add any rules the product may require (ie Customer Required, PUB/Skiosk, etc) added to the product

Siriusware - The Item must be a fully configured product in the POS system and should be able to be sold on Sales.

  • Salespoint Type

    • Item is available to be sold from Web Sales

  • Restrictions

    • Available Sales Dates has the Item priced for the current season

  • Items

    • Item is added to the Item Tree being used by the Online Salespoint

    • Add-on Item is set up as either:

      • A standalone DCI (example: a rental add-on to a ticket)

      • Required modifier Item added to main DCI (example: accept or decline insurance)

2. Infrastructure Tasks

  • Connectivity between Aspenware Commerce and the POS system has been fully established through Unity. This should have been completed during the implementation of your store.

3. Aspenware Commerce Tasks

  • Create a core product.

  • Create a hidden category for add-ons if one does not already exist.

NOTE: For steps to create a core product see: Configuration: Product Shell

4. Settings, Language Strings, and/or HTML Widgets for this Feature

This feature may require updates to the following settings, language strings and/or HTML Widgets. Learn more about how to update and create Settings, Language Strings, and HTML widgets follow the links to the respective section.

  • This setup does not require additional setup for Settings, Language Strings, or HTML widgets.

Detailed Setup Guide

This section describes all required steps to set up the feature after prerequisite tasks have been completed.

NOTE: It is recommended to save often by clicking Save and Continue Edit in the top menu bar. This will ensure your work is saved in the event you accidentally close or navigate away from the page.

HINT: Image examples below can be clicked to enlarge for easier viewing.

1. Create an Add-on product

WARNING: Add-ons have additional limitations to be aware of:

  • Short & Long descriptions are not available for add-ons

  • Email description will not appear on order confirmation emails

  • The category of an add-on should almost always be assigned to a hidden category

  • Product images do not apply but icon images can be applied to add-ons at the attribute value level on the core product

2. Create an attribute to house the add-on product

3. Associate the add-on to the core product

  • Navigate to the core product Catalog > Products > click Edit next to the product you wish to associate with an add-on.

  • Navigate to Product attributes > Add a new attribute.

  • Complete the fields in the Info dropdown on the Add a new attribute screen.

NOTE: The following fields can vary depending on the appearance desired on the PDP. Below provides the most commonly used combination for add-ons.

  • Attribute: Select the attribute created in step 2.

  • Text prompt: Enter “[Add On]” (most commonly used)

  • Is Required: Leave unchecked (most commonly used)

  • Control type: Select “Checkboxes” (most commonly used)

  • Display order: Leave as “0”

  • Enable linked attribute: Leave as “Not Set”

  • Save and Continue Edit:

  • Once saved, click the Add a new value button > on the pop-up window click the Attribute value type > select “Associate to product” > then click the blue Associate a product button.

  • In the next pop-up window type the name of the add-on product that you created in Step 1 in the Product name field> click Search > click Select next to the add-on product.

  • On the initial pop-up window, the name of the add-on product should appear next to the Associate a product button and the remaining fields can be completed:

    • Customer enters quantity: Leave unchecked

    • Product quantity: Leave as “1”

    • Name: Enter the name you want the add-on to display as on the PDP. Use a “|” the same as you would with other attribute values depending on how you want the add-on displayed on the PDP.

    • Is pre-selected: Mark as checked if you want the add-on to be preselected on the PDP. Leave as unchecked if you want the add-on to start as unselected on the PDP.

    • Display order: Leave as 0

    • Picture: If you don’t want an icon image next to the add-on on the PDP, leave the radio button selected as “no picture”. If you do want an icon image next to the add-on, select from images you have added to the core product. (Product icons will be scaled to 40x40).

    • Save: Click the Save button.

  • Navigate to the core product’s PDP and the add-on will now appear.

Like this page? Click the like button below. Don't like this page and/or want to give feedback about this page, leave a comment below and Aspenware will address to improve this article.

  • No labels