Versions Compared

Old Version 1

changes.mady.by.user Silva, Carlos

Saved on

compared with

New Version Current

changes.mady.by.user Silva, Carlos

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Note

This page is work in progressTimelines and status are being managed on this Monday board.

Milestones

Milestone

Name

Outcome

Work required

How to test

Owner

Status

1

Scope defined

Scope of the project has been agreed between BK DE, Tillster and RBI

  • Review and approve Tillster’s SOW

  • Ensure that the expected kiosk customer journey is accepted by all parties

  • SOW outlining the scope of the project

Anna

Status
colourBlue
titleIN PROGRESS

2

Test environment ready

A testing environment has been provided to Tillster for them to develop and test against

  • Set up Loyalty testing environment in Staging

  • Share credentials with Tillster

  • Tillster to confirm they can access and use the test environment

Valentina

Status
titleNOT STARTED

3

Integration developed

Integration from

Toshiba POS

Tillster to RBI Loyalty (via

Partner API

Loyalty Middleware) is developed and tested in Staging environments.

Toshiba

  • Tillster to develop the integration. This includes cash payments and specific UI changes for Germany market

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

Toshiba

  • Tillster 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

Valentina

Silvia

Status
colourBlue
titleIN PROGRESS

4

Integration readiness (Staging)

The Tilster > RBI Loyalty integration has been thoroughly tested by the business in Staging and all identified issues have been fixed

  • Tillster to configure offers and rewards in their systems

  • Configure offers and rewards in Sanity

  • Test that the offers/rewards are working in the RBI app

  • Test that the offers/rewards are working in store (Lab Kiosk)

  • All testing to be done in the BK DE Lab and RBI Staging

  • Kiosk instance to be available in the BK DE Lab

  • Selected BK DE people would be given access to the RBI app so that they can test the mobile order flow on their devices

Silvia

BK DE: TBC

Status
titleNOT STARTED

5

Personalised offers on Kiosk

Tillster kiosks are able to show and allow users to redeem personalised offers

  • RBI to develop changes in the Loyalty Middleware to support personalised offers

  • Tillster to develop changes in the loyalty integration to support personalised offers

  • Configure personalised offers in Sanity

  • Assign them to specific test users (RBI)

  • Check that those personalised offers show up on the kiosk after the user signs in on the kiosk

Valentina

Status
titleNOT STARTED

6

Integration readiness (Production)

New version of Tillster Kiosk (loyalty-enabled and with personalised offers) is working in Production in at least one store.

Toshiba

  • Migrate POS offers/rewards from Lab to Production

  • Migrate Sanity offers/rewards content from Staging to Production

  • Tillster to deploy the loyalty-enabled version of their

POS

TBC (CSM)

BK DE Testers

  • kiosk software 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

  • Selected BK DE people to be given access to Loyalty on the RBI app in Production

  • Test that the configured offers and rewards are working in the app and in-store

  • Toshiba POS must be enabled in the chosen test stores to test cash payments

Silvia

BK DE: TBC

Status
titleNOT STARTED

Info

Note: going live with loyalty will happen on a different project because we need to coordinate Mobile ordering and In-store (Toshiba and all of the Kiosk providers plus Toshiba) [insert link]

Notes

  • In order to show Personalised Offers in the Kiosk:

    • Tillster will need to start sending the loyalty id of the offer selected

      • This means the loyalty engine id, not the sanity id (what they use today to query rewards and offers). We may need to teach them how to find this value and not mix it up with the config offer's loyalty id/sanity id

    • RBI will need to expose this new field and when Tillster sends it, we use the new id they send to tell engine what offer is being redeemed