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

• 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

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.

Open

Menu structure

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

Open

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

Key Stakeholders

Timelines

Potential Risks

Dependencies

Success Criteria

Approvals Required

Additional Information