Add configurable time period of storing the Guest Order data in the database. Configure to 10 year for DE
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 a guard that allows to use of the Guest Token only for the allowed actions
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.
Save Card Option Removed at the Payment step
Added Modal to continue as a guest
Image RemovedImage Added
Adjusted data on the confirmation page
QA Testing
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-908
F
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-949
F
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-959
F
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-941
M
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-947
M
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-957
M
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-956
M
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-912
W
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-1010
W
Status
colour
Blue
title
Work in Progress
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 which does not exist for guest users
QA Testing
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-1006
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-909
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-962
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-1006
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-909
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-962
Status
title
To do
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
Image RemovedImage Added
Implement tracking events to flow to Amplitude
E2E QA Testing
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-948
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-1015
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-1003
Status
title
To do
...
Future Enhancements
Context
Ability to handle guest checkout orders in the direct tool
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-910
Melina clarified that refunds are managed directly via VR Payment’s dashboard so there’s no need to handle guest checkout orders in the Support Tool
Orders are identified in VR Payment’s dashboard using the order time, store ID and order value
Allows guests users to create account after placing order
After enabling loyalty, we could offer guests to create an account by displaying the points that could have been earned.
Allow guests users to opt in for email marketing communications
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-1008
Allowing guests to opt in for marketing communications would allow us to increase our contactable user base
However, this requires checking with legal to ensure compliance with GDPR and local regulations
Image RemovedImage Added
Allow operators to enable/disable guest checkout directly in Sanity and manage other related configurations
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-1009
Initially the feature will be controlled via Launch Darkly to perform A/B testing
Once the feature is stable, we will look at moving the configuration into Sanity