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 2 Next »

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

POS Task 1 REQUIRED

 Example of POS Task

Products that need age ranges assigned are created in POS and have age ranges added to POS

PREREQUISITE

2. INFRASTRUCTURE TASKS

Infrastructure Task 2 - REQUIRED

 Example of Infrastructure Task

​Confirm that the Azure function app is setup and configured to the desired frequency. - REQUIRED

PREREQUISITE

3. COMMERCE TASKS

Commerce Task 3 - REQUIRED

 Example of Commerce Task

Confirm that the Aspenware Commerce products that will have inventory assigned to them are fully configured with the correct attributes - REQUIRED

PREREQUISITE

Language String, Setting, HTML widget, etc. Task 4 - OPTIONAL

 Example of Setting Task

​Ensure the setting ‘ecommercesettings.productinventory.cachetime’ is set to your desired cache time - OPTIONAL

PREREQUISITE

Configuration Task 5 - REQUIRED

 Example of Configuration Task

Inventory is mapped to product or product variant in the Inventory Pool plugin REQUIRED

Code is entered REQUIRED

If using location in RTP, location code is entered REQUIRED

If multi day product, number of days is defined REQUIRED

If using non default lock time of 900 seconds, the desired lock time is configured. OPTIONAL

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.

POS Tasks

  • POS Task that must be completed first

Infrastructure Tasks

  • Infrastructure Task that must be completed first. Remove section if not required

Commerce Tasks

  • AW Commerce task that must be completed first

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.

Settings

  • AW Commerce Settings that must first be completed

Language Strings

  • AW Commerce Language Strings that must first be completed

HTML Widgets

  • AW Commerce HTML Widgets that must first be completed

Detailed Setup Guide

  1. Configure Regular (Non-SheerID) Validated Prompts

  2. Step 2 Header

1. Configuring Regular (Non-SheerID) Validated Prompts

When a customer checks out with a product or product plus attribute value 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 code can only be applied a single time on the Personalization step and cannot be used for multiple household members in the same order unless it's set up as a “Validate On Checkout Assignment” prompt. If in RTP|One it is set up for more than one-time use, it can be used again for subsequent orders. 

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 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. Codes can be multi-time use or single-time use. 

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. 

Note: Stored procedure updates in RTP must take place in order for the validations to take place. Please email ski-support@aspenware.com to set these up in advance of configuring these prompts in Nopcommerce. 


  1. From the Aspenware Commerce Plugins>Product Prompts page in Admin, select to add a new prompt

  2. Enter the following details

    1. Text - Prompt text (visible to customers)

    2. Code - RTP prompt code

    3. Prompt type - set to Text string

    4. Validate On Checkout Assignment - Check if prompt in RTP is setup to check valid customer assignment. Do not check if the guest should enter a code. 

    5. Is Validation prompt - set to True

    6. Is Required - set to True

    7. Prevent Duplicates - this disables the ability to use the same prompt value again within the same transaction.  Recommended for single use vouchers.  

  3. Click Add


  1. Next Click View Assigned Product Prompts and click Add Product Prompt Assignment

  2. Choose the desired product from the list of products

  3. From the Product Attribute drop down select All if the same validation prompt applies to the entire product, or if a validation prompt should only be assigned to one attribute selection, select the attribute to assign the prompt to. 

  4. Click Add


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