Oracle - Order Injection Test
This page summarizes the results of the order injection tests performed using the Oracle lab located in Miami on Feb 28, 2025.
App ordering indicates whether the order was successful from an app point of view.
POS injection indicates whether the order was successful from a POS point of view, including correct behavior.
All orders contain a single Whopper.
All orders were testing using lab
9000
in BK MX staging.
Glossary
ORB = Order Ready Board. Screen used to display order status to guests in the restaurant. It has 2 columns – “Preparing” and “Ready”.
KDS = Kitchen Display Screen. Set of screens in the kitchen which indicate restaurant members what to prepare. Each ‘station’ (fryers, drinks, sandwiches, expeditor) has its own screen.
DSS = Dynamic Service System. It’s an improved order assembly process – restaurants remove the heating chute, add labels/stickers to most items, make everything to order and add an expediting table. The expediting table introduces the role of the expeditor, who puts together the order and ensures all items are there. This improves order accuracy.
So when an order is placed,
Customer receipt is printed.
Each station will print one sticker per menu item (e.g. sandwich station print sticker with Whopper). Each sticker contains the sales channel, one product and its condiments.
The landing table will print a controller sticker will all items in the order.
Test results Feb 28, 2025
Document with Khumbu comments: https://docs.google.com/spreadsheets/d/1ELtnpSGuUYFapav4jMUGuMF4NOuLvV1lDhzcs5IJHYo/edit?gid=0#gid=0
Service mode | Payment method | Time firing | Evidence / Comment | App ordering | POS injection | Expected behavior | |
---|---|---|---|---|---|---|---|
1 | Pick up / Dine In | Credit card | Now | App: POS:
|
|
| - |
2 | Pick up / Dine In | Credit card | Future | App: POS: receipt prints
|
| (missing ORB) | Order appears on ORB at selected time. |
3 | Pick up / Dine In | Cash | Now | App: POS: DSS stickers print
|
|
| Order is only sent to KDS and ORB once it’s paid, even if selected time is “Now". |
4 | Pick up / Dine In | Cash | Future | App: POS: paying order
|
|
| - (Selected future time for unpaid orders doesn’t matter as order can only be fired when paid) |
5 | Drive Thru | Cash | n/a | App: POS: DT open orders page
|
|
| - (Is customer receipt sent to a separate DT printer?) |
6 | Drive Thru | Credit card | n/a | App: POS: DT open orders page
|
|
| Same as cash drive thru, but no need to pay the order as it’s already paid. Team members can look up the order and fire it to the kitchen. |
7 | Table service | Credit card | n/a | App: POS: receipt/DSS
|
|
| - |
8 | Table service | Cash | n/a | We should disable cash payment for table service, there’s no use case. App: POS: DSS stickers
|
|
| Order is only sent to KDS and ORB once it’s paid at the front counter. |
9 | Delivery | Cash | Now | App: POS: paying order and manually firing
|
| (manual firing) (fire command TKI) | Order is fired to kitchen even if unpaid. Driver will collect the money. |
10 | Delivery | Credit card | Now | App: POS: open orders page
|
|
| Order should be sent to KDS/ORB/DSS when firing command is received. |
11 | Delivery | Cash | Future | Not enabled in BK MX | - | - | - |
12 | Delivery | Credit card | Future | Not enabled in BK MX | - | - | - |
Lab setup