Overview: Guest Checkout

Owned by Sarah Holst
Last updated: Oct 12, 2022
4 min read

This feature is supported for: 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.

This feature is not supported for: Resorts using Siriusware as a POS.

Key Terms

Guest Checkout

Enables guests to checkout without requiring the user to login with an established email/password.

Selective Guest Checkout

Enables resorts to define specific products that are eligible for Guest Checkout.

Anonymous Checkout

Term that is used interchangeably with “Guest Checkout”.

Feature Description

Aspenware offers the functionality for customers to checkout as a guest.  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.

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. 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.

 

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:

  1. Attempt to log in

    1. If ‘Yes’ is selected, the guest will be directed to the store’s login flow or identity if configured.

  2. Continue checking out as a guest

    1. If ‘No’ is selected, the guest will be directed to the next checkout screen.

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.

 

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.

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.