Page Comparison

\uD83D\uDDD3 Date

...

• Review the complexities and challenges

Designs

Figma: Burger King https://rbidigital.slack.com/archives/C05RQBE90C9/p1694083887304829

\uD83D\uDDE3 Challenges

1. Storing User Data- cognito-

   Based on the 2023-08-24 Guest checkout PoC works we go with the approach of not creating the User entity in the Cognito and DB. All Guest data will be stored in the Order DB entry.

...

3. Decision on whether to allow a user to checkout as a guest with an email that's already registered

4. Legal copy for terms and conditions + Privacy Policy for a new static page

   1. Decision on consent- storing
      

      

5. User may be unable to inform the kitchen they have arrived if they abandon the confirmation page -User does not have any order reference number, and once confirmation is closed they cannot click I arrived, they have no way to retrieve this page. One solution is to send a unique link via email to retrieve the confirmation page, however this would require the token to be passed which increases the complexity. Another solution is to include a warning modal upon exit.

6. Instrumentation and adding appropriate events to track success metrics

7. Still a few non-critical designs and design adjustments are pending

8. Support Tool adjustment is not required at this moment as DE market users VR Payments directly to perform Customer Support actions, however it’ll be required for the loyalty launch if Support tool is intended to be used from that time on for refunds etc.

9. How to store user data on the FE, prevent certain functionalities that are dedicated for registered users (for example: loyalty, currently there’s a bug- skip requesting user account data for loyalty)

10. Adjusting whole frontend to serve guest user (so far adjusted only for registered users)

11. Other Frontend items…

12. Sign in flow

Additional considerations:

...

...