Guest Checkout Optimization

Paying online should be easy. In times of digitalization, retyping details every time you order or buy something is definitely not the experience we'd like our Clients to have, right?

So here's a solution - Guest Checkout, now optimized.

Why is it useful?

• It is a timely and optimized call to action for Customers to increase the number of users with User Accounts

• It saves the data the User once entered, so that their order and payment experience is seamless

• It saves Users' personal data in case they want to return to the menu to make changes to their order or to create new orders from the same web browser

• It allows Guest Users to complete orders with minimal time by removing any unnecessary fields from the checkout form

• The optimized version of the form improves navigation logic in the app

How does it work?

1. After pressing the Checkout button, app User will see a Sign in/Registration pop-up
   - In case table number is not added for Dine-in table service, the User will see a table number input first. Then, they will be redirected to the Sign in / Registration pop-up
2. On the Sign in / Registration modal, the User will see all available registration options enabled for the app brand, including a separate button for a Guest Checkout page
   - The GDPR legal message is displayed below the guest checkout button
3. If the user selects to Sign in or Register an account, it will work as it usually does
   - After signing in, the User will be redirected to the registered checkout page
4. If the User selects to checkout as a guest, they will be redirected to the Guest Checkout page
5. Sign in / Registration pop up will appear every time after User presses the checkout button, given that they weren't logged in already
   

How can I configure what fields are required at guest checkout?

• There is a section in CMS on the Brand-level settings called Guest Order
• This section has the option to enable/disable the feature called Last name is required for Dine-In (FS), Dine-In (QS) and Takeaway Order Types. This option (flag) makes the last name mandatory (feature enabled) or optional (feature disabled) for these Order Types
  Please note: the default option for this setting is enabled

IMPORTANT: If your Brand would like to remove last name as a required field for guest checkout, you can disable this flag in the CMS for an even faster checkout experience for your guest users. However, please ensure proper testing is done to check if your payment processor requires last name to be collected for payments to be accepted

Guest Checkout page details

The Guest Checkout page contains several sections of information and these are:

• Contact information form
• Payment method selection
• Order summary overview
• Delivery address (Only available for Delivery Order type)
• Foodspot location (Only available for Foodspot order type)

Contact information form details

• Contact information form has three input fields:

  • Your name

  • Email

  • Country code + Phone number
    
    

• Your name field should allow a single word to be entered for Dine-in Table service Order Type if the CMS option Last name not required at checkout for Dine-in (FS), Dine-in (QS) and Takeaway is disabled and both first name and last name if it's enabled

• Country code + Phone number shouldn’t be shown for Dine-in Table service Order Type

• Country code will be filled in automatically, based on the location country of the restaurant where the food is ordered

• Country code can be changed by opening the country code drop-down list

• All contact information that the User entered when they last accessed the Menu App will be saved

• If some of the contact information fields are not properly filled in and the User tries to select a payment method, they will see an error message
  

Payment method selection details

• We have updated the layout (User Interface) of the Payment method section, so it looks 'cleaner' and easier to use

• You can find all the available payment methods for your brand

• If some of the payment information fields are not properly filled in and the User tries to place order, they will see an error message