Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

Table of Contents

Setup Checklist

Insert excerpt
AE:Set-up ChecklistAE:
Set-up Checklist
nopaneltrue

1. POS TASKS

POS Task 1

Configure a new IPTypeCode

Status
colourRed
titleRequired

Expand
titleExample of POS Task
Products that need age ranges assigned are created in POS and have age ranges added to POS

Status
colourYellow
titlePrerequisite

2.

INFRASTRUCTURE

COMMERCE TASKS

Infrastructure Task 2 -

Settings

Configure ordersettings.anonymouscheckoutallowed.

Status
colourRed
titleRequired

Expand
titleExample of Infrastructure Task
​Confirm that the Azure function app is setup and configured to the desired frequency. -

Configure checkout.guestcheckout.preferguest.

Status
colourRed
title

Required

Status
colourYellow
titlePrerequisite

3. COMMERCE TASKS

Commerce Task 3 -

REQUIRED

Configure ordersettings.anonymouscheckoutbyproduct.

Status
colourRed
title

Required

STRONGLY RECOMMENDED

Expand
titleExample of Commerce Task
Confirm that the Aspenware Commerce products that will have inventory assigned to them are fully configured with the correct attributes -

Language Strings

Configure checkout.guestcheckout.switchtologin.description

Status
colour

Red

Blue
title

Required

Status
colourYellow
titlePrerequisite

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

optional

Configure checkout.guestcheckout.modal.title

Status
colourBlue
titleoptional

Expand
titleExample of Setting Task
​Ensure the setting ‘ecommercesettings.productinventory.cachetime’ is set to your desired cache time -

Configure checkout.guestcheckout.modal.description

Status
colourBlue
titleoptional

Status
colourYellow
titlePrerequisite

Configuration Task 5 -

1. Enable Anonymous Checkout

Status
colourRed
title

Required Expand
titleExample of Configuration Task
Inventory is mapped to product or product variant in the Inventory Pool plugin

REQUIRED

2. Configure Guest Checkout Register vs. Traditional Login

Status
colourRed
title

RequiredCode is entered

REQUIRED

3. Configure Selective Guest Checkout

Status
colourRed
title

Required

If using location in RTP, location code is entered

Status
colourRed
titleRequired

If multi day product, number of days is defined

Status
colourRed
titleRequired

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

STRONGLY RECOMMENDED

4. (Optional) Enable Phone Number Capture

Status
colourBlue
titleoptional

Status
colourGreen
titleDetailed Setup

Prerequisite Tasks

Insert excerpt
AE:Prerequisites Tasks ExcerptAE:
Prerequisites Tasks Excerpt
nopaneltrue

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

...

Distinguishing guests created in RTP|One through guest checkout rather than through traditional authentication can be useful for operation and fulfillment staff and for reporting. If knowing whether a guest created in RTP|One was created from a guest checkout flow is desired, the resort RTP admin needs to configure a new IPTypeCode for Guest Checkout, or use an existing “guest” IPTypeCode. When the new IPTypeCode is defined in RTP|One, send this code to your Aspenware representative so they can enter it in the config file for the Unity instance used by the store(s).  

...

Info

NOTE: If IPTypeCode is not displayed in standard RTP|One administration, it’s likely not being accessed from a poweradmin account.  If IPTypeCode cannot be viewed in RTP|One admin, work with your Aspenware representative to configure this.

If guests should not be distinguished from standard authentication guests, your Aspenware representative will need to define 1000 (which is the default Person IPTypeCode in RTP|One) in the config file for guest checkout. 

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

Insert excerpt
AE:Setting, Language String and/or HTML Widgets for this featureAE:
Setting, Language String and/or HTML Widgets for this feature
nopaneltrue

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. Step 1 Header

  2. Step 2 Header

1. Step 1 Header

  • First bullet should provide navigation instructions i.e. Catalog >Attributes >Product attributes

    1. Sub-bullet for step 1. Every step and click should be detailed so that someone could follow with little prior experience.

      1. Sub-bullet for step a. Include screenshots of the step and use skitch to mark up screenshots. It can be downloaded here: https://www.techspot.com/downloads/5705-skitch.html

Expand
titleExample 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:

    1. Calculate from Trip Start (this age range type is likely already configured), or 

    2. Calculate from Today’s Date (age range based on purchase date), or

    3. 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.

Image Removed

 

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.

Info

Note: When possible use notes, warnings, and hints within info panel macros. See https://aspenware.atlassian.net/wiki/pages/resumedraft.action?draftId=781156460 for more details on these.

2. Step 2 Header

  • First bullet should provide navigation instructions i.e. Catalog >Attributes >Product attributes

    1. Sub-bullet for step 1

      1. Sub-bullet for step a

...

DELETE CONTENT AFTER THIS LINE

go to the Glossary page and add the key terms Excerpt Include that you added for your configuration guide.

To add the feature terms to the Glossary, navigate to the glossary and add a header for your feature using an H2. Select the + and then select …view more. Search for Excerpt Include and in the Page Containing the Excerpt search for “Configuration: [FEATURE]” select to hide panel, preview and add.

How-to Guide of this page can be found here: [Internal] Configuration page Setup Guide

...

The following settings are used in the configuration of this feature. Please see the Detailed Setup Guide below for more information on configuring these settings and how those configurations influence the behavior of the Guest Checkout feature.

Setting

Value

Store

ordersettings.anonymouscheckoutallowed

True - Enables guest checkout

False - Disables guest checkout

This can be configured at the store level.  If you have multiple stores, input the store this applies to.  Otherwise, leave blank.

checkout.guestcheckout.preferguest

True - Prefer guest checkout

False - Prefer traditional login

Note

IMPORTANT: “True” is required for Resorts utilizing Identity.

This can be configured at the store level.  If you have multiple stores, input the store this applies to.  Otherwise, leave blank.

ordersettings.anonymouscheckoutbyproduct

True = Enables guest checkout for the product

False = Disables guest checkout for the product

This is the setting for configuring guest checkout at the product level. Note that guest checkout must also be enabled at the store level for this to work.

Language Strings

To update language strings on the Guest Checkout page, configure the following language strings from  Configuration > Languages > English > String Resources , search for the following strings and add them if they don’t exist. See full list of language strings for guest checkout in the Language Strings Library

String Resource

Value

Details

checkout.guestcheckout.switchtologin.description

Have a RESORT account?

Describe option to switch to login

checkout.guestcheckout.modal.title

We found an account for you

Modal title text if an authentication profile found for entered email. 

checkout.guestcheckout.modal.description

An account exists for this email. Would you like to sign in to your account?

Modal description text if an authentication profile found for entered email. 

Detailed Setup Guide

Insert excerpt
Detailed Setup Guide Excerpt
Detailed Setup Guide Excerpt
nopaneltrue

  1. Enable Anonymous Checkout

  2. Configure Guest Checkout Register vs. Traditional Login

  3. Configure Selective Guest Checkout (Optional, but Recommended)

  4. (Optional) Enable Phone Number Capture

1. Enable Anonymous Checkout

Note

IMPORTANT: This setting will mark all products in the store as Guest Checkout products. Continue on in Step 3 to set specific products as Guest Checkout products. Whether you are using guest checkout store-wide or only for specific products, this setting must be checked.

There are two methods for configuring this setting:

METHOD 1:

  • Go to Configuration > Settings > Order settings > Expand the Checkout section.

  • Check Anonymous checkout allowed.

  • Click Save. (Note that you will need to toggle from “Basic” to “Advanced” on the Order Settings screen.

    Image Added

METHOD 2:

  • Go to Configuration > Settings > All settings (advanced)

  • Search for ordersettings.anonymouscheckoutallowed

  • Click Edit.

  • Change Value to True to enable guest checkout, False to disable guest checkout.

  • Click Update.

    Image Added
Note

IMPORTANT: If you have a multi-store environment and the rules for guest checkout are different across stores, ensure these settings are defined independently for each store. Add the settings more than once and assign the setting uniquely per store.

2. Configure Guest Checkout Register vs. Traditional Login

It’s possible to configure whether the guest checkout register form or the traditional login form is shown first when guest checkout is enabled for a store. This allows the admin to emphasize guest checkout over traditional login (if set to true), or to show traditional login first (if set to false). 

  • Go to Configuration > Settings > All settings (advanced)

  • Search for checkout.guestcheckout.preferguest

  • Click Edit.

  • Change Value to True to display guest checkout first, False to display traditional login screen (see examples in the table below.) For resorts using Identity, this value MUST be set to True.

    Image Added
  • Click Update.

Setting

Value

Store

Example (Click to enlarge)

checkout.guestcheckout.preferguest

True - Prefer guest checkout

False - Prefer traditional login

Note

IMPORTANT: “True” is required for Resorts utilizing Identity.

This can be configured at the store level.  If you have multiple stores, input the store this applies to.  Otherwise, leave blank.

True

Image Added

False

Image Added

3. Configure Selective Guest Checkout (Optional, but Recommended)

While this is an optional step, nearly all resorts will choose to utilize the Selective Guest checkout feature. Guest checkout may be enabled either globally within the store or by individual products. The following steps need to be completed IN ADDITION to the steps above to enable Selective Guest Checkout. This will limit guest checkout to carts that contain only products that are guest checkout eligible.

This feature works by enabling two additional settings (after enabling Anonymous Guest Checkout (see above)).

Enable Selective Guest Checkout at the Order Level

This enables selective guest checkout at the order level. There are two methods for this:

METHOD 1:

  • Go to Configuration > Settings > Order Settings

  • Scroll down to the Additional Order Settings section

  • Check “Selective Guest Checkout”

    Image Added
  • Scroll to the top of the Order Settings page and click Save (This will enable selective guest checkout which makes guest checkout only available for carts that contain selective guest checkout-eligible products.)

METHOD 2:

  • Go to Configuration > Settings > All settings (advanced).

  • Search for ordersettings.anonymouscheckoutbyproduct.

  • Click Edit.

  • Change Value to True to enable selective guest checkout, False to disable selective guest checkout.

  • Click Update.

Enable Selective Guest Checkout at the Product Level

  • Then, go to Catalog > Products and click Edit on the desired product.

  • Scroll to and expand the Additional Product Settings drop-down.

  • Check Selective Guest Checkout.

  • Scroll to the top of the page and click Save.

Info

NOTE: This product when purchased on its own or purchased with other Guest Checkout Products will now direct non-logged-in customers through the Guest Checkout Flow.

...

4. (Optional) Enable Phone Number Capture

  • This setting will turn on the option to save a phone number during checkout’s payment screen. This is beneficial as guest checkout customers are otherwise not prompted to enter a phone number.

  • Go to Admin > Configuration > Payment methods > select your active payment method > Configure > select the checkbox for Requires Phone Number

  • Click Save.

...

...