| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
| 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. |
Key Terms
| Excerpt |
|---|
Guest CheckoutEnables guests to checkout without requiring the user to login with an established email/password. Selective Guest CheckoutEnables resorts to define specific products that are eligible for Guest Checkout. Anonymous CheckoutTerm that is used interchangeably with “Guest Checkout”. |
Feature Description
Aspenware now 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. Guest checkout can be configured as a store-wide configuration, or it can only apply to specific products. Selective Guest Checkout allows resorts to define whether Guest Checkout is enabled store-wide for all products or if Guest Checkout should only be enabled on a per-product basis.
| Info |
|---|
NOTE: Guest Checkout can be configured to be required for all products, no products, or specific products. As a result, when a guest enters checkout with both products classified for Guest Checkout and products not classified for Guest Checkout, then the guest will be required to login. |
Entering Guest Checkout
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 . This minimal information is required so orders can be searched for in the POS. Optionally the guest can also choose to log in if they believe they already have an existing account.
...
| Info |
|---|
NOTE: Once the “Next” button is clicked and the guest is successfully directed to the checkout screen, a new account is created into the POS. The account “Type” in RTP|One will be labeled as “Guest Checkout Customer”, this can be used to assist with merges if needed. |
Existing Account Prompt (Reducing Duplicate Account Creation)
To help reduce creating duplicate accounts in the POS, if the guest enters an email that exists within an existing authentication profile in the POS, then the guest will be prompted with options to either:
Attempt to log in
If ‘Yes’ is selected, the guest will be directed to the store’s login flow or identity if configured.
Continue checking out as a guest
If ‘No’ is selected, the guest will be directed to the next checkout screen.
...
| Info |
|---|
NOTE: This prompt will not appear unless a matching Authentication Profile email exists in the POS. |
When a customer proceeds as a guest, 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.
Checkout Steps
Checkout can utilize other Aspenware Commerce features such as requiring assignment, age rules, etc. The guest can Manage their Group by adding Group Members and/or age to member profiles during checkout.
...
| Note |
|---|
WARNING: Since the guest account is not associated with an existing account in the POS, no age will be pre-populated in checkout. Aspenware Commerce will prevent the Head of Household from being given an age that is under 18+ but it will not force the guest to assign the Head of Household an age and it will not prevent the guest from signing a waiver without an age nor will it prevent signing for a Group Member that is a minor. |
Order Completion
Upon order completion, the newly created Guest Checkout customer will receive the order information in the POS. Since Guest Checkout does not create an Authorization Profile in RTP|One, the guest will not have login information for future purchases.
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.
Section Links
| Child pages (Children Display) | ||
|---|---|---|
|
Insert excerpt