#1 Implement Oracle POS on Loyalty Program

Due to Loyalty Program launch on Apr 2, 2024, our approach will be implemented Oracle on Loyalty some weeks after Loyalty Program launch in order to avoid increase the complexity/risks prior the launch.

For the Oracle pilot store, enabling loyalty at the front counter (we will not have kiosk).

Milestone

Outcome

Work Required

How to test

Owner

Effort (weeks)/ETA

Status

Milestone

Outcome

Work Required

How to test

Owner

Effort (weeks)/ETA

Status

1

Store created in staging and configured for Partner API.

  • Sanity - create a new store in Staging - 22773.

  • Set Vendor as Partner.

  • Configure rest of required fields – lat/long, opening hours, etc.

  • Store is available in Sanity.

  • Store can be seen in the staging store locator. Orders can’t be placed.

  • Store is available in Sanity.

  • Store can be seen in the staging store locator.

  • Orders can’t be placed at this stage.

Sanity doc here: https://staging-bk-menu.de.rbi.tools/desk/orderLevelContent;restaurants;restaurant;1a8eb756-cae2-4968-a385-711deff45b39%2Ctemplate%3Drestaurant

@Fagundes, Silvia

1,5 week

ETA:
Mar 26, 2024

done

2

PLU fields for Oracle are available in Sanity.

A new POS vendor config is created in Sanity to store Toshiba PLUs.

Partner fields are available for Oracle PLUs.

  • Toshiba-Loyalty field is available and PLUs are migrated from Partner field.

  • Partner field is empty.

@Lopes da Costa, Valentina

@Yildirim, Semih

4 weeks

ETA:
May 6, 2024

done

3

All vendors need to change the integration to read the new Vendor Config field.

  • After Loyalty Launch

Toshiba, Tillster, Smoothr, Acrelec need to change the integration the integration to read this new Vendor config field Toshiba-Loyalty

  • Communicate all vendors to change the integration which today they use “supportingPos” : “Partner”, they need to change to “supportingPos”: “toshibaLoyalty”.

  • Vendors execute the change on their side.

  • Test that the configured PLUs for offers and rewards are working in-store. Display the rewards on the BKD app coming from Partner field.

@Fagundes, Silvia

+ Vendors

Vendors will work on the change in April.

ETA:
May 6, 2024

done

Communication done
4

Enable Loyalty on POS

Loyalty available on Oracle POS

  • Loyalty package is available in BK DE’s Oracle POS lab.

@Fagundes, Silvia

+ Oracle Stefan

1,5 week

ETA:
May 10, 2024

done

5

Content Management Readiness

All content needs to be set in Sanity for Oracle

  • Input PLUs for offer and rewards in Partner field.

  • Test that the configured PLUs for rewards are working in-store. Display the rewards on the Oracle POS.

@Fagundes, Silvia

+ David&Martin

Dependency on milestone 3.

ETA:
Jun 11, 2024

TBC with Lionel.

in progress

6

Test E2E Integration - Loyalty flow (Staging)

In store flow - able to show the Offers, Rewards and allow users to place orders.

  • Test every single reward and place an order via Front Counter in order to validated if the order injection process is working.

  • BKD will provide a spreadsheet to follow the test progress for each reward.

  • Test Store Availability

  • Test Price & Product Availability

    • BKD App display the rewards

    • Test every single Reward is being checked out with successfully.

  • Test Order Injection for Offers and Rewards

  • In-Store Testing - Front Counter)

@Fagundes, Silvia

+ Engineering

+ BK DE Team

+ Oracle Stefan

1 week

ETA:
Jun 18, 2024

in progress

7

Rollout to Production

Order injection on Oracle is ready in Production, all products, offers and rewards are working as expected via Mobile Ordering.

  • Oracle to install loyalty package on POS in production

  • Migrate Sanity document POS rewards from Staging to Production

  • BK DE Ops to train store personnel & Oracle on Loyalty how to use the POS

  • Test Store Availability

  • Test Price & Product Availability

    • BKD App display the rewards

    • Test every single Reward is being checked out with successfully.

  • Test Order Injection for Offers and Rewards

  • In-Store Testing - Front Counter

@Fagundes, Silvia

+ Engineering

+ Oracle Stefan

+ BK DE Team

1 week

ETA:
Jun 19, 2024

Not started

Status Keys

We use the following status keys across to report progress:

  • 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

Notes

Date

Action

Notes

Owner

Status

Date

Action

Notes

Owner

Status

1

Apr 8, 2024

Project Check-point:

  • POS is running under single-tenant structure?

  • Enable integration, need to provide the info below:

    • Simphony Store ID

    • Employee ID from Simphony

    • Simphony URL