...
Guest checkout can be enabled at the store level in Aspenware commerce.
To enable guest checkout at the store level:
Admin>Settings>OrderSettings>Select Desired Store>Select Anonymous checkout allowed
Optional: 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.
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.
If the resort doesn’t care about identifying these guests differently in RTP|ONE, they don’t need to configure a different IPTypeCode.
If they choose resort chooses not to use a unique IPTypeCode, Aspenware or the resort website administrator needs to enter the IPTypeCodeGuestCustomer in rtp-config.json as 1000 (which is the default Person IPTypeCode in RTP|ONE).
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.
...