Contents

📌 Context & Assumptions

• BK DE is in the process of enabling loyalty on 02 Apr 2024. ✅

  • More details on the loyalty deployment here: [Archived] BK DE - Loyalty Enablement

• In terms of mobile ordering in the tech platform:

  • Delivery is available for a subset of stores (~150 BK DE Master Franchisee stores).

  • Click & collect, Dine In, Drive Thru and Table Service are not available.

• To enable delivery, RBI built an integration into “SIDES” (previously known as “Simply Delivery”).

  • When a guest places a delivery order:

    • RBI sends the delivery order to a SIDES tablet.

    • SIDES tablet is next to a delivery dedicated POS, located in the restaurant’s kitchen.

    • Team member manually keys in the order into the POS.

  • More details on SIDES integration flow here: /wiki/spaces/CA/pages/3402695725.

...

• Delivery fulfillment is done by own drivers. SIDES also takes care of driver management.

  • Team member will assign the order to an own driver. Drivers have a SIDES app which provides delivery instructions.

  • Note that SIDES has built an integration into UberDirect, which will allow 1P delivery orders to be delivered with UberEats drivers. BK DE is currently testing this integration.

📌 Goal

• All BK DE restaurants currently use Toshiba as the POS and BK DE will replace Toshiba POS with Oracle POS.

  • As part of that replacement, we need to ensure that stores with Oracle POS support Mobile Ordering and Loyalty.

    • The following service modes, POS Integration will be implemented:

      • Delivery

      • Click & Collect

      • Dine In

      • Drive Thru

      • Table Service

⚙️ Tech Requirements

Architecture

...

1. Oracle POS already has an integration with RBI via the Khumbu middleware using our PartnerAPI.

2. In Sanity → Vendor Config need to be updated to support the integration:

   1. Create new field Toshiba-Loyalty to support current setup (input offers and rewards) which it’s using as part of the Loyalty Integration with Toshiba, Acrelec and Tillster.

      1. Script to migrate PLUs from the current Partner field to Toshiba-Loyalty including the whole Menu structure (items, combos, modifiers)

   2. Use Partner field to store the Pick Up and Delivery PLUs for Oracle POS.

Integration Oracle Simphony POS

1. Defined to use the Transaction Services API Generation 2 for:

   1. Order Injection

   2. Price and Product Availability

   3. Heartbeat

Details on Oracle and Khumbu integration Oracle ordering /wiki/spaces/MS/pages/4055763454

2. Contact Oracle to activate the Transaction Services API Generation 2;

3. Create Store ID for both Staging and Production environment;

   1. Create new store on Sanity and set POS as Vendor Partner

4. Mapping of RBI service modes to Oracle Simphony’s (orderTypeRef)

5. Loyalty package need to be installed by Oracle following the guideline Oracle loyalty /wiki/spaces/MS/pages/4057661622

Configuration on Partner API

1. Process to create store (Staging, QA and Prod) on Partner API:

   1. /wiki/spaces/IN/pages/3930325043

Content Management

In Sanity, on Vendor Configs, all PLUs need to be set on Partner field.

📋 Project Plan

The project plan below outlines the following project deliverables:

1. Enable Oracle POS on BK DE - Loyalty Program

   1. For the pilot, focus on enabling loyalty at the front-counter (we will not have kiosk at this stage).

2. Enable Click & Collect for Oracle POS.

   1. We need to review the approach for Click & Collect service mode.

3. Enable Delivery for Oracle POS.

   1. We need to decide the approach for Fulfillment provider.

4. Enable rest of the remaining service modes for Oracle POS.

   1. Dine In

   2. Drive Thru

   3. Table Service

Project Deliverables

#3 Enable Delivery for Oracle POS

#4 Enable rest of service modes for Oracle POS (Dine In, Drive Thru and Table Service)

...

🗣️ Stakeholders

🤹‍♂️ Risks Management

...