Page Comparison

• Creating Guest Token- To place an order as a Guest users require to have be authenticated on our platform. In order to do that we need to create a Guest Auth token. We can’t follow the current path for collecting it because Guests don’t have accounts in Cognito and in the User DB entries.

• Preventing the guest user from seeing app content dedicated for registered users only

• Add a security layer limiting actions allowed for the orders with Guest token. Actions allowed for example: priceOrder, validateCommitOrder, commitOrder, getOrder, etc

• Add configurable time period of storing the Guest Order data in the database. Configure to 10 year for DE

• Added Modal to continue as a guest

  

• Adjusted data on the confirmation page

• QA Testing
  

25 Oct 2023

• Accommodate new transactional email communication with AWS SES instead of Braze

• Decide and execute when guest token should be removed, so no other order can be made with that token to guarantee anonymity

• Prevent error appearing on the success page due to loyalty account request and price call

• Review the tracking event coverage and naming conventions

• QA Testing

01 Nov 2023

• Create a new static page for guest terms and conditions and link it in the flow

• Change copy to “choose payment' instead of “add payment” at the /cart/payment page
  

  

• Save Card Option Removed at the Payment step

  

• CTA Button Adjustment - Sign in/ up more prominent:

• Remove Favorite option for guest users:

• Implement tracking events to flow to Amplitude

• E2E QA Testing

22 Nov 2023