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 | |
|---|---|
Configure a new IPTypeCode REQUIRED | PREREQUISITE |
2. COMMERCE TASKS | |
Settings Configure Anonymous Checkout setting. REQUIRED Configure checkout.guestcheckout.preferguest setting. REQUIRED Language Strings Configure checkout.guestcheckout.switchtologin.description OPTIONAL Configure checkout.guestcheckout.modal.title OPTIONAL Configure checkout.guestcheckout.modal.description OPTIONAL | PREREQUISITE |
1. Enable Phone number capture for checkout for all guests OPTIONAL 2. Configure Selective Guest Checkout (Product Level guest checkout) 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
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).
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
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.
IMPORTANT: This setting will mark all products in the store as Guest Checkout products. Continue on in configuration 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.
Alternatively, to turn on Guest Checkout, enable the setting below from Configuration > Settings, search for the following setting ordersettings.anonymouscheckoutallowed.
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. |
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.
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  |
IMPORTANT: If you are using Identity for authentication, this setting to prefer guest checkout must be set to True. If you use standard login, it can be set either way.
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
This section describes all required steps to set up the feature after prerequisite tasks have been completed.
1. (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.
IMPORTANT: Guest checkout can be configured as a store-wide configuration, or it can only apply to specific products. The following steps must be taken to enable selective guest checkout that will only be enabled for certain products.
2. (Optional) Configure Selective Guest Checkout
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 three settings. Two are at the global level and one is at the product level. After enabling Anonymous Guest Checkout (see above), complete the following:
Go to Configuration > Settings > Order Settings
Scroll down to the Additional Order Settings section
Check “Selective Guest Checkout”
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.)
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
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.
