Skip to end of metadata
Go to start of metadata

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

Compare with Current View Version History

« Previous Version 4 Next »

This document is currently being discussed between BK DE and RBI and it has not been finalized.

Contents

Constraints

Assumption that the following scenario is not desired:

  • Oracle rolled out on a given restaurant with Loyalty integration

  • SIDES processing 1P delivery orders

  • Deliverect processing 3P delivery orders

The above is possible but requires staff at the restaurant to maintain two tablets. There are advantages of doing the above:

  • Decoupling the Oracle rollout from enabling 1P delivery on Deliverect (ie. makes it possible to rollout Oracle before Deliverect)

  • Crew could be trained in using Deliverect ahead of time (via 3P delivery)

  • It is not possible to have Deliverect handling 1P delivery orders on restaurants that use Toshiba because there is no order-level integration between RBI and Toshiba.

  • It is also not possible to send orders from RBI to the Deliverect tablet because there is no order-level integration between RBI Deliverect.

Outcomes

  • Deliverect is handling 1P and 3P delivery for BK DE

  • Toshiba to be replaced with Oracle in all restaurants

  • 1P orders to be injected automatically on restaurants that use Oracle

Scope

  • 3P Delivery

    • Deliverect integrated with all the aggregators that BK DE works with to receive delivery orders

    • Deliverect automatically injecting delivery orders on Oracle (none of the above goes through RBI systems)

    • Assumption that the Deliverect tablet is needed for driver management and for fallback in case orders fail to inject

  • 1P Delivery

    • Integration for ordering (Oracle and RBI) so that orders can be injected to Oracle

    • Integration between Deliverect and RBI, so that Deliverect knows that an order has been placed and can dispatch a driver

      • Driver availability

      • Order Delivery

      • There is no ordering integration, the ordering piece is handled by RBI in the same way we handle pickup orders

    • This integration already exists (e.g. for BK UK)

Milestones

Milestone

Description

Activities

3P delivery working

BK DE is able to process 3P orders in Oracle

  • Configure menu in Oracle

  • Configure menu in Deliverect

  • Configure Deliverect / Oracle / Aggregator integration

  • Switch off SIDES

Driver availability working

When guests input an address in the Guest App, the RBI Platform confirms with Deliverect which nearby restaurants have drivers available.

  • Share RBI API keys with Deliverect

  • Configure Deliverect with access to the RBI Platform

  • Enable a few restaurants in Staging

  • All test case passing

Ordering working

Ordering integration between RBI and Oracle. This is needed so that 1P delivery orders that originate in the RBI Guest App are sent directly to the Oracle POS.

  • Menu structure finalised

    • Including how to handle Pfands

  • Menu configured:

    • Oracle POS on the BK DE lab

    • Sanity on RBI Staging

  • All test cases passing

Delivery assignment working

When guests place a delivery order in the Guest App, the RBI Platform asks Deliverect to assigns a delivery driver.

  • Configuration would have been done in Milestone 1

  • Configure one item in Oracle and RBI (requires parts of Milestone 2)

  • Run a simple order injection test

  • All test cases passing

First restaurant live with 1P Delivery

Ensure that the 1P delivery process works end to end and troubleshoot whatever necessary before rolling out to more restaurants

  • Configure Deliverect in Production

  • Configure RBI in Production

  • Set up the menu in Oracle (Production)

  • Publish the menu in Sanity (Production)

  • Enable one restaurant

  • Test & troubleshoot

All restaurants live with 1P Delivery

Ensure that restaurant staff is trained in how mobile orders are integrated with Oracle and Deliverect. Then enable 1P delivery in all desired restaurants

  • Train restaurant staff

  • Enable 1P delivery in all desired restaurants on the RBI Platform

Questions

  • Is pre-ordering required from the beginning? This is a feature that currently exists with SIDES, but does not exist on the Deliverect/RBI integration (and it is not clear whether Deliverect supports it)

  • Does BK DE use their own drivers for aggregator orders? If they do not, the Deliverect tablet is not needed for driver management

Notes

  • Volumes:

    • Current volume of 1P delivery orders: 4k per week, 16k per month

    • Total 5M per month, if we assume 20 EUR average basket size, 250k orders in total (230k 3P)

    • So 1P is ~ 6.5% of the total delivery orders

    • Pre-orders are about 300 per week/1,200 per month, so 0.5% of the total

  • Process to roll out Deliverect (because we can’t support more than one delivery management platform at the same time):

    • Switch SIDES off on all restaurants

    • Assumption that at this stage the Oracle/RBI integration is ready

    • Deliverect would have been previously configured to work for all BK DE restaurants

    • Switch on Deliverect for select restaurants (on RBI) and test

    • If successful, roll out to more restaurants (e.g. 50%)

    • If successful, roll out to all restaurants

  • Our delivery integration with Deliverect does not support pre-ordering. Unclear if Deliverect supports pre-ordering at all. We are currently developing this feature for Homeria

  • No labels