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 |
SOW Validation
Confirm SOW to Tillster & get ETA
Review the linked SOW & provide comments
Please mark “complete” once you have reviewed
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)
Scope defined | Scope of the project has been agreed between BK DE, Tillster and RBI |
|
| Anna |
| ||||||
2 | Test environment ready | A testing environment has been provided to Tillster for them to develop and test against |
|
| Valentina |
| |||||
3 | Integration developed | Integration from Tillster |
to RBI Loyalty (via Loyalty Middleware) is developed and tested in Staging environments. |
|
|
|
TBC (CSM)
Valentina Silvia |
| |||||||||
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 |
|
| Silvia BK DE: TBC |
| ||||
5 | Personalised offers on Kiosk | Tillster kiosks are able to show and allow users to redeem personalised offers |
|
|
Tillster dev team
Valentina
4
Valentina |
| |||||
6 | Integration readiness (Production) | New version of Tillster |
Kiosk (loyalty-enabled and with personalised offers) is working in Production in at least one store. |
|
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
|
Silvia BK DE |
: TBC |
|
Info |
---|
Note: going live with loyalty will happen on a different project because we need to coordinate Mobile ordering and In-store (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 selectedThis means the
loyalty engine id
, not thesanity 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