Info |
---|
This is the home page |
...
for all the |
...
Oracle requirements |
...
/wiki/spaces/TRX/pages/5037850633
Items to discuss
...
Item
...
Oracle explanation
...
Combos
...
Same PLU for different sizes of the same combo. For example, the “Whopper Combo Large” and “Whopper Combo Medium” have the same PLU.
...
To calculate the combo price:
Add the prices of: combo price + main item price + side 1 price + side 2 price.
Any premium comboslot will have a price > 0. Non-premium comboslots will be priced at 0.
To get the price from Oracle’s /menus
payload:
...
For the combo:
Retrieve the
menuItemRef
in theComboMeals
objectUsing the
menuItemRef
, find the menu item that defines the combo and get its price for the applicabledefinitionSequence
. That is the combo price.
For main item and sides:
...
The comboGroup with "isMainGroup":true
contains the main item. The comboGroup with "isMainGroup":false
contains the sides.
...
Service mode
...
Same PLU for both in-restaurant and delivery service modes. Different pricing is managed through definitionSequence
.
definitionSequence
= 1 is in-store.definitionSequence
= 2 is delivery.
Not all items have both definitions (e.g. some items aren’t sold in delivery).
...
Sugar tax
...
Can we add it as a surcharge to the product? E.g. Classic Coca-cola should already have the sugar tax included in the priceSequence
.
...
Bottle deposit (Pfand)
...
Delivery fees (bag fee, service fee, etc)
...
Pre-ordering
...
Fiscal
Is this standard across markets? E.g. in BK MZ in the commit call we need to send the following information:
Code Block |
---|
"extensions": [
{
"displayName": "DocumentId",
"appName": "Harmonized",
"dataName": "DocumentId",
"dataType": "strings",
"data": "1",
"options": []
},
{
"displayName": "DocumentType",
"appName": "Harmony",
"dataName": "DocumentType",
"dataType": "strings",
"data": "01",
"options": []
} |
...
related to Menu. |
Child pages (Children Display) | ||
---|---|---|
|