Versions Compared

Key

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

...

Milestone

Name

Outcome

Work required

How to test

Owner

1

Integration developed

Integration from Toshiba POS Tillster kiosk to RBI Loyalty (via Partner APIMiddleware) 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 RBI apps to test the effects of loyalty calls.

TBC (CSM)

2

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

Tillster dev team

Valentina

3

Integration tested

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

  • Toshiba Tillster to deploy the loyalty-enabled version of their POS 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

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

TBC (CSM)

BK DE Testers

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]

Details

  • 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