Configuration: Simple Add-On Products
- Marty Niessen
- Jenni Buonanni
- Sarah Holst
Setup Checklist
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.
| Prerequisite |
Siriusware - The add-on product must be a fully configured Item in the POS system and should be able to be sold on Sales.
| Prerequisite |
2. Infrastructure Tasks |
|
Unity - Connectivity between Aspenware Commerce and the POS system has been fully established through Unity. Required | Prerequisite |
3. Aspenware Commerce Tasks |
|
Core Product Configured
| Prerequisite |
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
1. POS Tasks
RTP|ONE - 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
Detailed Setup Guide
Create Add-On Product
Create Attribute to House the Add-on Product Connection to Core Product
Associate Add-on Product to the Core Product
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 Add-On Product
To create an add-on product, follow the steps to create a product shell: Configuration: Product Shell
Assign the add-on product to a hidden category.
No attribute value(s) should be added to the attribute on the add-on product attribute editor screen.
2. Create an Attribute to House the Add-On Product Connection to the Core Product
To create an attribute, follow the steps in section 1 of the associated guide: Configuration: Product Attributes
3. Associate Add-On Product to the Core Product
Go to Catalog > Products, find the desired Core product, and click Edit to open the Edit product details page.
Scroll down to the Product attributes section. (Click the + if collapsed.)
Click Add a new attribute to open the Edit product attributes page.
Complete the following fields in the Info dropdown on the Add a new attribute screen.
Select the Attribute to house the connection between the core product and add-on product, created in step 2.
The Text prompt field enables additional information to be given to the user interface about how and where an attribute is displayed. [Add On] is typically added to these products so that the add on selection appears in a separate “Upgrade Your Experience” box.
Leave Is Required unchecked (most commonly used)
Control type is usually configured as “Checkboxes”
Display order should be set so that add ons are after core attributes in the list
Leave Enable linked attribute as “Not Set”
Click Save and Continue Edit.
Once saved, click the Add a new value.
In the modal, for the Attribute value type, choose “Associate to product.”
Then, click Associate a product.
In the modal, type the name of the add-on product that you created in step 1 in the Product name field.
Search for the product. Once found, click Select next to the desired add-on product.
On the initial modal, the name of the add-on product should now appear next to the “Associate a product” button, and the remaining fields can be completed:
Leave Customer enters quantity unchecked
Leave Product quantity as “1”
Enter the Name you want the add-on to display as on the PDP. Separate the attribute title and description with a pipe (|), (e.g. VIP Package | Includes dinner, drink tickets, meet the pros). If no description is necessary, title the product with a | and space only after the value name. (e.g. General Admission | )
Check Is pre-selected 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.
Leave Display order as 0, unless there are multiple attribute options that should be ordered.
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).
Click the Save button.
Go to the core product’s PDP and the add-on will now appear.