Contents

Project Overview

Executive Summary

BK DE uses a local provider called SIDES (formerly Simply Delivery) to deliver food to their guests.

SIDES consists of a tablet, integrated with the RBI platform, which lets restaurant staff know when they receive delivery orders. SIDES is not integrated with their current POS (Toshiba), which means that restaurant staff must enter delivery orders into Toshiba manually.

SIDES is also not integrated with BK DE’s future POS (Oracle) and BK DE decided to replace SIDES with Deliverect (which supports Oracle) instead of pursuing an integration between SIDES and Oracle.

The purpose of this project is to replace SIDES with Deliverect in all stores that support 1P delivery which means user will place delivery orders in our App.

Project Type

Implementation and rollout of technical changes.

Project Scope

Current Technology Stack

Composed of:

Oracle POS

Note that Deliverect will only be rolled out in restaurants that already have Oracle as their POS.

SIDES tablet to receive delivery orders from RBI App and ~~3P delivery partners (Uber Eats and Liferando)~~ assign drivers to orders
SIDES driver app to tell drivers when they have been assigned a delivery order
Deliverect tablet and driver app for delivery orders received by Liferando, on a single store - Oracle POS.

Proposed Changes

The main changes are:

Replacement of SIDES with Deliverect for driver management. This will make use of the existing integration between RBI and Deliverect, with no development required. It consists of RBI injecting delivery orders into Deliverect, which allows restaurant staff to assign these orders to drivers.
Delivery orders to be injected into Oracle by the RBI platform. This change requires software development (see details under Order Injection below).

Out of Scope

Rolling out Deliverect in restaurants that are still using Oracle;
Rolling out Deliverect in restaurants that do not support delivery.

Market-Specific Requirements

Order injection

Preliminary section, will require more detail after Discovery Session (05th Nov)

When guests place a delivery order via the Guest App, the RBI Platform will use the Partners API to inject the order contents into Oracle POS. This requires translation of Parter API payloads into the corresponding Oracle payload, which will be accomplished by using Khumbu.

Khumbu will act as an interface between Oracle and RBI in two different flows:

When an order is placed via the Guest App, Khumbu will convert the RBI payload to the format expected by Oracle;
When Oracle generates events that are relevant for RBI (e.g. pricing, change of status), Khumbu may need to convert the response to a format that RBI expects.

Stores with Oracle POS

Use Khumbu integration

RBI already has an integration with Oracle POS (Transactions Services v2) via the Khumbu middleware, leveraging our Partner API. This integration will also covers Click & Collect service mode.

Stores with Toshiba POS

Use Deliverect tablet

Currently Deliverect does not have a Toshiba integration so we need to use a Deliverect tablet.

BK DE Deliverect.png

Menu structure

Clarification of menu requirements needed.

Content Team is setting PLU as following:

Sanity > Vendor config field Toshiba-Loyalty uses for Toshiba POS, Tillster, Smoothr and Acrelec (Kiosk);
Sanity > Vendor config field Partner used for Oracle POS;

Loyalty integration: all vendors changed the integration to “supportingPos”: “toshibaLoyalty”.

Technical Requirements

As today, SIDES is managing 1P Delivery orders and SIDES does not have Order Injection on Toshiba POS.

Scenario As-Is

Screenshot 2024-10-23 at 12.17.25.png

Scenario Transition period (Transition time SIDES > Deliverect)

In order to accommodate Deliverect in the same flow as SIDES, our Platform needs to develop a routing logic to direct incoming delivery orders under SIDES and Deliverect at the same time until SIDES be decommissioned.

Scenario TO BE (Fully transitioned SIDES > Deliverect)

After fully onboarded Oracle restaurants

Screenshot 2024-10-23 at 14.44.53.png

Phase	Description
1	Enable RBI <> Oracle ordering integration Configuration RBI <> Khumbu Content configuration (PLUs) Menu test
2	Enable Deliverect integration in 1 store: Configuration RBI <> Deliverect Restaurant training
3	The transition from SIDES to Oracle-Deliverect in all restaurants Handle sunsetting period where both systems co-exist (routing logic to direct incoming delivery orders under SIDES and Deliverect)
4	SIDES decommissioned Deactivated SIDES custom integration

Discovery Session

Date/Time 05th Nov 2024; 2 pm to 5 pm CET.

Participants

RBI	Silvia Fagundes, Sistla Sumanth, Elona Toma, Daniela Teixeira, Carlos Silvia, Valentina Lopes, Anton Benet, Marco Fernandez, Jean Marrara
BK DE	Malte Wolters, Krystian Kwiatkowski, Oliver Mielentz, Tomasz Klutkowski, Raik Alt

Agenda

Opening and Agenda Review
1. Welcome and introductions (RBI team/BK DE)
2. Recap of objectives and agenda
Objectives
1. Present the current 1P Delivery architecture (slide 1)
2. Discuss Oracle POS rollout in Q1-2025 to define whether a transition period between SIDES and Deliverect will be necessary (slide 2)
  1. Depending on the velocity of Oracle POS implementation, we might develop a “routing logic” to direct incoming delivery orders under SIDES and Deliverect at the same time until SIDES is decommissioned.
  2. What are the high-level steps to leverage this scenario?
3. Decommissioning SIDES integration (slide 3)
  1. Deactivated SIDES custom integration.
Next Steps
Closing and Thank You
1. Summarize the key points