Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Contents

Goals

Channel

In scope

Out of scope

POS (Instore)

  • Guests can earn and redeem points at the counter for Toshiba and rPOS stores

  • Other POS

Kiosk (Instore)

  • Guests can do the following at Tillster, Acrelec and Smoothr kiosks:

    • User identifies their loyalty account in the Kiosk and pays in the Kiosk

    • Once the user identifies, all subsequent rewards/offers selection happens in the Kiosk

    • User identifies their loyalty account in the Kiosk and pays in the POS counter (both rPOS and Toshiba)

    • User identifies their loyalty account and pays in either Kiosk or counter, then goes to counter and cancels the order. This should result in a refund and withdrawal of points. TBC if we want to cover this use case in January or roll out later

  • Pay at counter for POS different than rPOS and Toshiba

App / Website (Online)

  • Guests to have access to open and closed offers at the same time

  • Stackable offers (open and closed): guests can use more than one offer on the same order (in-store and online)

  • Guest checkout – not a dependency for this project

Projects

Project

Scope

Out of scope

Status

Details

Define the Loyalty programme

Non-technical activities required to enable the Loyalty programme.

Technical and/or software development work (covered in other projects)

IN PROGRESS

Project 1. Define the Loyalty programme

Migrate BK DE to the new Loyalty platform

Currently BK DE uses the legacy platform (CBA) and we need to move to the new Loyalty platform, while retaining the existing CBA features that do not exist on Loyalty: open offers, upsells, marketing tiles.

POS or Kiosk integrations (these remain the same)

IN PROGRESS

Project 2. Migrate BKD to new Loyalty platform

Toshiba integration

Develop the integration required to allow guests to earn loyalty points when they make purchases, and to redeem loyalty rewards.

IN PROGRESS

Project 3. Integrate Toshiba POS with Loyalty

rPOS integration

Same as above for rPOS.

NOT STARTED

Project 4. Integrate Tillster Kiosk with Loyalty

Tillster integration

Same as above for Tillster.

NOT STARTED

TO BE ADDED

Acrelec integration

Same as above for Acrelec.

NOT STARTED

TO BE ADDED

Smoothr integration

Same as above for Smoothr.

NOT STARTED

TO BE ADDED

Timelines

Project 2 timelines are updated. All other projects are placeholders.

May2023JunJulAugSepOctNovDecJan2024Current DateOnlineIn-store
Program & Comms
Migrate BKD to new Loyalty platform
Toshiba Integration
rPOS Integration
Tillster Integration
Smoothr Integration
Data

Program definition (tiers...)

Design app & email assets

Add assets in Sanity/Braze

Create in-store marketing

Localise staff guidebook

Program T&C & FAQ

Blocked for holiday

Marketing tiles

Redeem open offers in the Loyalty platform

Upsell offers

Offer migration

Agency training (Sanity)

Loayty Environment Setup

Testing

Testing

Testing

Testing

Personalised offers in kiosks

Testing

Contingency

Production testing

Solution design

Sanity to support open offers

Loyalty Integration

Lab testing

Test in 1 store

Enable in all stores

Content setup (Sanity)

Content setup (Sanity)

Lab testing

Test in 1 store

Enable in all stores

Approve kiosk flow

Loyalty, Toshiba & rPOS Integration

Lab testing

Test in Toshiba store

Test in rPOS store

Enable in all stores

Approve flow design

Develop integration

Lab testing

Test in Toshiba store

Test in rPOS store

Enable in all stores

Build Amplitude Dashboard

Define KPIs

Monitor performance

Loyalty Events Setup (CRM)

Status Keys

We use the following status keys across to report progress across every project:

  • NOT STARTED work on this item has not started yet

  • IN PROGRESS work on this item has started and is progressing to plan

  • WAITING development done, awaiting deployment or completion of a dependency

  • AT RISK work on this item has started and is at risk of delaying

  • DELAYED work on this item is delayed, however it is not causing a major impact

  • DELAYED work on this item is delayed and it is causing an impact on project due dates or other dependencies

  • BLOCKED cannot move on this item until a dependency is resolved

  • COMPLETED item has been completed

  • WON'T DO this item will not be developed

  • No labels