1

Loyalty setup

Loyalty platform is technically ready, with no impact on guests or operations

• Create the Loyalty back end in all environments (Staging, QA, Production)

• Configure webhooks on Sanity and Terraform

• App should continue to work as today

• Look into database and ensure that new users have a Loyalty ID associated with their account

Valentina

3

Redeem Loyalty offers

As a test user, I can place an order using the BKD app where the offer data comes from the Loyalty platform, and the experience does not change to what happens today. Excluding upsells, marketing tiles and personalised offers.

• Display offers on the BKD app coming from Loyalty

• For signed out guests: if offer is open, display the static code. If offer is closed, ask the guest to sign up or sign in

• For signed in guests: display the QR code with the embedded Cognito ID (both open and closed offers)

• Configure selected test users in Launch Darkly

• Observe that my list of offers contains open offers, closed offers and no personalised offers

• When I view an open offer, the behaviour is the same as today

• When I view a closed offer while signed out, I am prompted to sign up or sign in

• When I view a closed offer while signed in, the behaviour is the same as an open offer

• I can place an order and redeem an offer that is configured in Loyalty

Valentina

4

Upsells

As a test user, I can see an upsell to another offer when I click on an offer that has an upsell configured on the Loyalty platform

• Development work required on Sanity, BE and FE to support upsells

• Manually configure upsells on the Loyalty platform by copying from CBA

• Configure selected test users in Launch Darkly

• Click on an offer that has an upsell configured, upsell shows up

• Add the upsold offer to the order

• Complete the order and ensure the user journey matches what we have today with CBA

Valentina (development)

Silvia (configuration)

5

Marketing tiles

As a test user, I can see marketing tiles on my offers page

• Development work required on Sanity, BE and FE to support marketing tiles on the offers page

• Manually configure marketing tiles on the Loyalty platform by copying from CBA

• Configure selected test users in Launch Darkly

• Check that marketing tiles show up in the offers page, and in the position that was configured in Sanity

• Click on a marketing tile

• Ensure the guest gets taken to the path configured in Sanity for that marketing tile

Valentina (development)

Silvia (configuration)

6

Personalised offers

As a test user, I can see current and past personalised offers on my offers page. “Past” means offers that were assigned to an user in CBA

• We already support personalised offers for web and apps (not Kiosk), so no development work required. Kiosk will be handled in the Loyalty project which comes after this one

• Ensure the migration script can be executed multiple times

• Run the migration script to assign personalised offers to specific users in the Loyalty platform

• Configure selected test users in Launch Darkly

• Assign a personalised offer in CBA

• Run the migration script

• Ensure that the personalised offer becomes configured in Loyalty and appears on the users' offers page

• Assign a different personalised offer on Loyalty

• Ensure that the second personalised offer appears on the users' offers page

Valentina

7

Rollout

BKD is using open offers on the Loyalty platform for all stores and users. There is no CBA component in use. Loyalty features continue to be switched off

• Configure Braze webhooks to connect to Loyalty instead of CBA

• Run the personalised offers script one more time in Production

• Enable the Loyalty (open offers) flag(s) to all users in Production

• Regression testing in Production prior to rollout (including events)

• In-store testing by BKD prior to rollout

• Smoke test after rollout

QA Team

BKD

Integration developed

Integration from Toshiba POS to RBI Loyalty (via Partner API) is developed and tested in Staging environments.

• Toshiba to develop the integration

• RBI to support with questions and issues that might arise during development

• Toshiba team will have access to both Postman to make integration calls, and testing versions of the apps to test the effects of loyalty calls.

TBC (CSM)

2

Integration tested

New version of Toshiba POS (loyalty-enabled) is working in Production in at least one store.

• Toshiba to deploy the loyalty-enabled version of their POS to at least one store in production

• RBI to enable loyalty for specific test users in the RBI apps, to test the loyalty user journey

• BK DE to conduct testing of the loyalty user journey in Production

TBC (CSM)

BK DE Testers