Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 12 Next »

This page is a draft.

This page details the mechanism used to ‘fire’ orders, that is, send orders to the kitchen for preparation. It also includes the order preparation statuses that Oracle sends to the RBI platform.

Contents

Overview

When guests place delivery, take out and eat in orders, they can decide whether they want to place the order for “Now” or later in the day.

RBI order type

Scheduling options

Delivery, Take Out, Eat In

Now or later

Table service

Only ‘Now’. No time selection.

Drive Thru

No time selection, requires manual firing. More details below.

If the order is placed for the future, it will be injected into the POS using Oracle’s pickupTime attribute.

pickupTime indicates the time requested for the order to be collected. Oracle will automatically fire the order to the kitchen based on the pickupTime and adding the configured preparation time.

For example, if a guest schedules an order for 4:30 PM and the configured preparation time is 5min, Oracle will fire the order at 4:25 PM. This ensures that the order is ready at the requested time.

Operators must configure preparation time using the serviceLevelTime value.

Oracle configuration

To configure serviceLevelTime:

  • Enter Oracle Simphony EMC

  • Select the Enterprise or the Zone where Order Type Parameters are set

  • Then open the Setup / Taxes and Order Types / Order Type Parameters tab

  • And set the Service Level Time for all Order Types that will be used with Future Orders

image-20241127-201233.png

Orders originating from the RBI platform that have been paid are considered ‘closed' by Oracle. Operators cannot manually modify or fire closed orders from the POS. However, unpaid orders (e.g. cash orders) are considered ‘open’ by Oracle and operators can modify them and manually fire them from the POS.

image-20241127-081917.png

To see open orders in the POS:

[guide to see open orders in the POS]

Drive thru orders

The RBI platform sends Drive Thru to the POS with a pickupTime attribute set several hours in the future. This way, guests can ask for their order to be prepared only when they arrive at the restaurant. Operators must manually fire drive thru orders.

Unpaid drive thru orders

For unpaid drive thru orders (e.g. cash), the order will appear as an open order on the left panel of the drive thru screen.

image-20241127-082209.png

When the customer arrives, the operator double clicks on the order. The order can now be modifier or fired.

image-20241127-082431.png

To fire the order, the operator clicks on the TOTAL button and selects the desired payment method.

image-20241127-082614.png

Upon selecting a payment method, the operator will see a modal asking if the order should be fired to the kitchen at that moment.

image-20241127-082818.png

The operator clicks on “Send Now”. The order will be sent to the kitchen.

image-20241127-083221.png

The operator selects the payment method again and the receipt is printed.

Exact screen configuration may differ in each market.

Paid drive thru orders

[ TBD ]

Order preparation statuses

Oracle informs RBI of the following order statuses:

  • Uninitialized - order not started.

  • Submitted – indicates that the order has been sent to the kitchen for preparation.

  • Prepared – indicates that the order has been prepared and is pending packaging.

  • Packaged – indicates that the order has been packaged and is ready for pick up.

Oracle does not inform the RBI platform about orders voided at the POS. If an order needs to be voided, please refund the customer immediately. The payment made in the RBI platform will not be refunded.

  • No labels