See below for configuration specific to 2.7 and 2.8 guest checkout enhancements for RTP|ONE.
Guest checkout can be enabled at the store level in Aspenware commerce.
To enable guest checkout at the store level:
Admin>Configuration>Settings>OrderSettings>Select Desired Store>Select Anonymous checkout allowed
It’s 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 which form shows first, or the traditional login firstbut the user can always toggle between them. This setting allows the admin to emphasize guest checkout over traditional login (if set to true), or to show traditional login first (if set to false).
The setting name is:
checkout.guestcheckout.preferguest
To create or modify this setting, select Administration>Configuration>All Settings (Advanced) and type the word guestcheckout in the search dialog.
If the setting already exists, this search will return the current settings for each store.
If the setting does not yet exist, add it using the ‘Add New Record’ form as shown in the screenshot below.
For multi-store configuration, be sure to enter a record for each store, with the desired behavior (True or False) for each, and Add New Record.
If the resort wants to be able to tell if the guest created in RTP|ONE was created from a guest checkout flow, the resort RTP admin needs to configure a new IPTypeCode for Guest Checkout.
This IP type can be named whatever the resort admin wishes, such as Guest Checkout or Guest.
Please provide your client services representative with the IPTypeCode so Aspenware may add it to the rtp-config.json for Unity for each store.
Alternatively, if the resort prefers to manage adding this node, they can do it themselves. They must ensure the application pool is recycled after editing and saving the rtp-config.json file. In the following screenshot, the IPTypeCode used for guest customers is 3014. The code used for resort environments will not be 3014 (it will be whatever the resort has configured). If the resort doesn’t want to identify these guests differently in RTP|ONE, the default person IPTypeCode of 1000 must be entered for this node.
IMPORTANT: for some resort administrators, IPTypeCode is not displayed in standard RTP|ONE administration, because it’s a poweradmin setting. If the resort admin can’t see IPTypeCode in RTP|ONE administration, contact your Client Services representative and an Aspenware staffperson can assist with this.
Turn on the option to save phone on the payment method, because for guest checkout customers, we don’t require a phone number on guest registration.
Admin>Configuration>Payment methods>select your active payment method>configure>select the checkbox for Requires Phone Number, and SAVE.
Configurable Language Strings
All the following language strings can be configured for Guest Checkout forms, buttons, and helper text.
checkout.guestcheckout.continuebuttontext
checkout.guestcheckout.description
checkout.guestcheckout.headerguest
checkout.guestcheckout.headerlogin
checkout.guestcheckout.modal.description
checkout.guestcheckout.modal.nobutton
checkout.guestcheckout.modal.title
checkout.guestcheckout.modal.yesbutton
checkout.guestcheckout.placeholder.email
checkout.guestcheckout.placeholder.firstname
checkout.guestcheckout.placeholder.lastname
checkout.guestcheckout.sectiontitleguest
checkout.guestcheckout.sectiontitlelogin
checkout.guestcheckout.switchtoguestregister.buttontext
checkout.guestcheckout.switchtoguestregister.description
checkout.guestcheckout.switchtologin.buttontext
checkout.guestcheckout.switchtologin.description
checkout.guestcheckout.validation.emailinvalid
checkout.guestcheckout.validation.emailrequired
checkout.guestcheckout.validation.firstnamerequired
checkout.guestcheckout.validation.lastnamerequiredThese language strings, like all, can be configured in Languages>Edit>String Resources