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 |
3. COMMERCE TASKS | |
Settings Configure ordersettings.anonymouscheckoutallowed setting. OPTIONAL Configure checkout.guestcheckout.preferguest setting. OPTIONAL Language Strings Configure checkout.guestcheckout.switchtologin.description OPTIONAL Configure checkout.guestcheckout.modal.title OPTIONAL Configure checkout.guestcheckout.modal.description OPTIONAL | PREREQUISITE |
Enable Guest Checkout at the Store Level REQUIRED | 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. 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
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 this setting is defined independently for each store. Add the setting 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 |
checkout.guestcheckout.preferguest | True - Prefer guest checkout False - Prefer traditional login | 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 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
1. Enable guest checkout at the store level
Go to Admin > Settings > OrderSettings > Select Desired Store.
Select Anonymous checkout allowed
IMPORTANT: If you have a multi-store environment and the rules for guest checkout are different across stores, ensure this setting is defined independently for each store.
Turn on the option to save a phone number on the payment method, because for guest checkout customers, we don’t require 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.
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.