...
If the products don’t require member assignment, the guest adds to cart, enters his payment information, and he’s done! The customer and order records are still created in RTP|ONE for the ‘anonymous’ guest. Furthermore, the resort can choose to create a new IPTypeCode to identify these guests in RTP|ONE as ‘guest checkout’ customers.
For purchase flows which that require member assignment, we’re still capturing all required customer details, such as birthdates for age-restricted products, on the assignment step. See 2.7 - 2.8 Release Guides - the Configuring Guest Checkout Documentation for more information.
...
Retail
...
Retail inventory synchronization with RTP|ONE inventory stock levels is also possible at the SKU/product header code level as a daily scheduled task. For Unity resorts, tax by shipping location is also available (this valuable feature is not possible with RTP|Connect). See 2.7 Release Guides the Retail Documentation for more information.
...
Order-level discounts
...
With this release we focused primarily on enhanced functionality for the LS Retail Check-in screen including book, cancel, and move tee times. In addition, we have changed the way check-in works so that all RTP customers can be easily searched for and selected on the right hand side screen. We also addressed a few issues on the ecommerce booking side, including check-out for members, and month-to-month tee time discrepancies, including loading the proper first available tee time. See below for more information as well as our release guidelines Golf Documentation for additional implementation instructions.
...