...
| Tip |
|---|
This feature is supported for: All supported product types Resorts using RTP|One as a POS. Both Identity and standard log-in checkout support guest checkout, however, if Identity is used for login, checkout, the setting ‘guestcheckout.preferguest’ must be set to true, meaning the guest will be prompted to create a guest checkout first but can choose to log in from the guest checkout page. |
| Warning |
|---|
This feature is not supported for: Resorts using Siriusware as a POS. |
Feature Description
Aspenware offers the functionality for customers to checkout as a guest. This feature can be used with any of our supported product types. This feature allows the guest to enter a minimum amount of information in order to check out and is designed to increase conversion. This feature is currently a store-wide setting and cannot be enabled only for customers checking out with certain products.
Aspenware will require the guest to enter their name and email before entering the checkout. If an authentication profile exists with the given email in RTP|One, the system will ask the guest if they’d like to sign in. If the guest chooses to sign in with the existing account, they will be redirected to the login screen. If the guest chooses to not sign in with the existing account, they will be directed to the standard checkout screens.
Guest accounts are created as customer accounts in RTP|One upon entry into the checkout page. These accounts are created with minimal information, name, and email profile. Upon completion of product-specific criteria in checkout (i.e. assignment, rental profile, billing address), more information will be added to the customer profile in RTP|One. These guest accounts can also be flagged as guests by configuring a special guest IPTypeCode for guest accounts in RTP|One.
If a user terminates the checkout session while using the guest checkout feature, they will be required to re-enter all of their information if they re-enter checkout as a guest.
...