Page Comparison

System Architecture

• Transactional emails are moved from Braze to AWS SES

• Switch to AWS SES to send transactional emails

• Create email input field in Sanity

• Set up email subdomain structure

• Transactional emails have the same content

• Emails are sent from SES instead of Braze. This can confirmed by looking at the email subdomain

Haris / Magdalena

Authentication and Authorization

• Guest authentication is enabled

• Loyalty accounts checks are removed for guest users

• Develop a Guest Auth token since guests don't have accounts in Cognito or User DB

• Remove loyalty account check for guest checkout users

• Verify token generation and validation for guest users

• No error is triggered due to missing loyalty account

Magdalena

Data Security and Compliance

• Secure and compliant data storage

• Guest Token actions are limited and controlled

• Implement configurable time period for storing Guest Order data

• Add security measures to limit guest actions, implement a guard to restrict Guest Token usage

• Decide and implement logic for Guest Token removal

• Guest order data is removed after set period

• Allowed actions can be performed with Guest token - e.g. priceOrder, validateCommitOrder, commitOrder, getOrder, etc

• Unauthorized actions can’t be performed with Guest token

Magdalena

User Experience and Interface

• Complete frontend flows for guests users

• Implement event tracking

• Remove 'Save Card' option at Payment step

• Add modal to allow users to ‘Continue as a guest’

• Adjust data displayed in the order confirmation page

• Add new events and assure data flow to mParticle and Amplitude

• Guest users can’t save card

• Guest user is able to add email in modal and place order for all service modes

• Confirmation page display correct information

Magdalena

Legal

• Required legal disclaimers for guest checkout are in place

• Create a static page with guest checkout terms and conditions

n/a

Melina