Aspenware Commerce can leverage RTP|One Customer Validation Procedures to enable offering special products only to guests who meet certain criteria (products purchased, access profiles, age, days skied, years loyal, etc.) Guests do not necessarily have to enter “codes” in order to validate as these prompts can be validated on Customer Assignment. Aspenware can help and quickly turn around such validation procedures.
This feature is supported for: Resort using RTP|One for POS.
This feature is NOT supported for: Resorts using Siriusware for POS.
Key Terms
Validated Prompt
A validated prompt is a prompt that a guest receives during the personalization step of the checkout process that leverages the RTP|One customer validation procedures to ensure that certain eligibility criteria are met before the checkout process is complete. Optionally, guests do not have to enter “codes” in order to validate as these prompts can be validated on Customer Assignment.
Feature Description
A validated prompt can either be set up as a “Validate On Checkout Assignment” prompt for prompts that check guest eligibility or require a code entry that is checked on the Personalization step, a check is performed to ensure the code is valid and not expired.
If a validated prompt is set up to require a “code” entry
When a customer checks out with a product or product with a particular attribute value selected that is set up with validation prompt restrictions, they will see a verification section on the Personalization step of checkout. The customer will be unable to continue past Personalization until they enter a valid verification code.
A prompt can be configured to either restrict the same code from being used multiple times within the same order or to allow it. If it is configured to restrict duplicate entry, a code can only be applied a single time on the Personalization step and cannot be used for multiple “line items” in the same order. If it is configured to allow duplicate code entry, a code can be entered multiple times for various eligible “line items” within the same order. If a code is intended to be a single-time use code, one that should only apply to a single product, it is recommended to configure the prompt to prevent duplicate entry.
Codes can be multi-time use or single-time use. If a validated prompt is set up as a single-time use in RTP|One, then once the customer checks out for their order, the code is marked as used and cannot be applied a second time if it is set up for one-time use.
NOTE: If using single-use codes, consider using voucher functionality instead of validated prompts, as the guest flow and admin setup flow are easier. To help decide between using validated prompts and vouchers, review the decision matrix guide here.
Below is an example of both a successful and failed code entry check within checkout.
If a validated prompt is set up to validate on customer assignment
Product Prompts in Aspenware Commerce can be set to “Validate On Checkout Assignment”. If a product is assigned to a validated prompt that is set up this way, it takes the legwork away from the guest needing to enter a code and rather only allows “eligible” guests to be assigned. In the example below, the validated prompt will check to make sure the logged-in user is a current “member” and, therefore, eligible to take advantage of the “member’s only” product.
This can be set up to validate assignment when assigning products on the assignment step of checkout, or it can be set up to ensure assignment to a valid user is a required step before adding to the cart, as it is set up in the example below.
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.