...
Insert excerpt |
---|
| AE:Set-up Checklist |
---|
| AE:Set-up Checklist |
---|
nopanel | true |
---|
|
1. POS TASKS | |
---|
POS Task 1 1. Set up Subscription Product Headers and Hotlists Expand |
---|
|
|
Products that need age ranges assigned are created in POS and have age ranges added to POSConfigure subscription product headers in RTP|One as simple products that contain a single access component.
Configure 'Cancel' and 'Freeze' hotlists in RTP|One.
Configure subscription product headers with access.
Set up Freeze hotlist
Set up Cancel hotlist
2. Set up Validated Customer Procedure
Status |
---|
colour | Yellow |
---|
title | Prerequisite |
---|
|
| 2. INFRASTRUCTURE TASKS | |
---|
Infrastructure Task 2 - Expand |
---|
|
title | Example of Infrastructure Task |
---|
|
Confirm that the Azure function app is setup and configured to the desired frequency. -
Status |
---|
colour | Yellow |
---|
title | Prerequisite |
---|
|
| 3. COMMERCE TASKS | |
---|
Commerce Task 3 - Expand |
---|
| title | Example of Commerce Task |
---|
Confirm that the Aspenware Commerce products that will have inventory assigned to them are fully configured with the correct attributes - |
Status |
---|
colour | Yellow |
---|
title | Prerequisite |
---|
|
Language String, Setting, HTML widget, etc. Task 4 - Expand |
---|
| title | Example of Setting TaskEnsure the setting ‘ecommercesettings.productinventory.cachetime’ is set to your desired cache time - | Blue | title | optional |
Status |
---|
colour | Yellow |
---|
title | Prerequisite |
---|
|
---|
Configuration Task 5 - Expand |
---|
|
title | Example of Configuration Task |
---|
|
Inventory is mapped to product or product variant in the Inventory Pool plugin Red | Required | Code is entered
If using location in RTP, location code is entered
If multi day product, number of days is defined
If using non default lock time of 900 seconds, the desired lock time is configured.
Status |
---|
colour | Green |
---|
title | Detailed Setup |
---|
|
|
Prerequisite Tasks
...
POS Tasks
...
Prerequisite Tasks
Insert excerpt |
---|
| AE:Prerequisites Tasks Excerpt |
---|
| AE:Prerequisites Tasks Excerpt |
---|
nopanel | true |
---|
|
POS Tasks
Work with your Aspenware Representative on this RTP|One Pre-work to make sure all necessary parts are configured.
1. Set up Subscription Product Headers and Hotlists
Info |
---|
NOTE: These products should be gated from being able to be sold onsite as guests MUST purchase subscription products on the Aspenware Commerce store. |
Configure subscription product headers in RTP|One as simple products that contain a single access component. Because these are ongoing charges that are triggered from the Aspenware Commerce subscription tool to Payeezy or Square, the only charge that will be reconciled to RTP|One is the first deposit charge paid when the order is first placed. Subsequent monthly charges are not sent back to RTP|One. Therefore, the product pricing setup in RTP|One is very simple.
Configure two hotlists in RTP|One. When a charge fails, or when membership is frozen or canceled, subscription access is hotlisted with either the Cancel or Freeze hotlist, depending on the reason. Hotlists are also removed when subscription statuses go back to “active.”
Configure subscription product headers with access.
Info |
---|
NOTE: Only supports later hotlisting a single access code, so only one access component should be assigned to subscription products. |
Set up Freeze hotlist
Set up Cancel hotlist
Info |
---|
NOTE: The cancel hotlist code will be set to RTP|One in the event that a subscription is canceled by an admin OR if the card on file fails a monthly payment. If clarification is needed as to whether the guest is still in the window where they can update their card and re-activate their access, check the Aspenware Admin tool to see if the Subscription status for the enrollment is failed-declined or canceled. If it is failed-declined, the guest can simply update their card in my account to remove the hotlist. |
2. (Optional) Set up Validated Customer Procedure
Commerce offers resorts the option to allow guests who are subscribers to be eligible to redeem free or steeply discounted products that they must redeem online, in advance, to “reserve” their spot. If your resort subscription is set up this way, work with your Aspenware representative to map a strategy of creating redemption products in both RTP|One and in Aspenware Commerce that “validate” only customers who have active subscription access (not hotlisted) are able to check out with these free “reservation products.” They will work with you to create a custom validated customer procedure that can be set up to work for online and in-person reservations. Aspenware can also add additional restrictions to this validation, examples we’ve set up in the past include, only allow a subscriber to reserve a single product type per day so that subscribers don’t over-consume inventory. They will also work with you on rules and guidelines for creating these validation product headers in RTP|One and Aspenware Commerce. Considerations include:
Validated Customer Procedure - Like validated prompt but allows restriction on assignment. These require custom SQL and Aspenware support.
Custom configuration can be added to the RTP|One stored procedure that prevents assigning the same person the same product type on the same day in subsequent orders.
Can be built in a way to use onsite
Redemption product header creation may be required (for onsite redemption, add the same validated customer procedure as used online.)
Infrastructure Tasks
Infrastructure Task that must be completed first. Remove section if not required
...
Expand |
---|
title | Example of content within a section |
---|
|
From the Aspenware Commerce Plugins>Age Range page in Admin, click View Add Range Types in the upper right corner. Click Add Age Range Type. Enter a name and description for the age range type. To set the date used to compare the customer’s age to the required age range, select: Calculate from Trip Start (this age range type is likely already configured), or Calculate from Today’s Date (age range based on purchase date), or Specify the Calculation Start Date; the customer’s age on this date will be used to determine if they are eligible for the product based on the age ranges
Click Add. Age Range Types can be edited and inactivated, but they cannot be hard deleted without contacting Aspenware. Age Range types that are set to Calculate from Trip Start or Today’s Date will never need to be edited, unless you would like to edit the name. Age Range Types that are calculated from a fixed date however, will need to be edited each year to adjust for the current year.
Hint: Age Range Types should also be adjusted year over year. If age ranges are calculated based on Trip Start, then they will not need to be updated. Once completed for all required age range types move on to create Age Range. |
...
Insert excerpt |
---|
| AE:Like this Page Excerpt |
---|
| AE:Like this Page Excerpt |
---|
nopanel | true |
---|
|
...
DELETE CONTENT AFTER THIS LINE
go to the Glossary page and add the key terms Excerpt Include that you added for your configuration guide.
...