Configuration: Configuring Guest Checkout

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.

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

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

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

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

• Go to Configuration > Settings > Order settings > Expand the Checkout section. Check “Anonymous checkout allowed” and Save.

• From this same Checkout Settings page, expand Additional Order Settings. Check “Selective Guest Checkout” and Save.

• Alternatively, to turn on Guest Checkout, enable the setting below from Configuration > Settings, search for the following setting ordersettings.anonymouscheckoutallowed. 

• It’s also possible to configure whether the guest checkout register form shows first, or the traditional login form is shown first when guest checkout is enabled for a store, using a setting.  Administrators can choose to either show the guest checkout form first, or the traditional login first.   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).  Configuration > Settings, search for the following setting: checkout.guestcheckout.preferguest

Setting	Value	Store	Example (Click to enlarge)
checkout.guestcheckout.preferguest	True - Prefer guest checkout False - Prefer traditional login 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 False

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

Detailed Setup Guide

1. Enable Phone Number Capture

• Turn on the option to save a phone number on the payment method, because for guest checkout customers, aren’t required to enter a phone number on guest registration.

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

• Click Save.

2. Mark Product as a Guest Checkout Product

• Go to Catalog > Products and click Edit on the desired product. Expand the Additional Product Settings drop-down. Check “Selective Guest Checkout” and scroll to the top of the page and click Save.