Note |
---|
This page is a draft. |
Info |
---|
This page details the approach to Oracle configuration in both the RBI platform and the POS. |
Content
Contents
Table of Contents | ||
---|---|---|
|
Oracle POS Technical Requirements
Oracle is one of the RBI-approved POS that our franchisees can use in their markets. The following requirements apply:
Uses Oracle Symphony version 19.7 or above.
Uses Simphony Transaction Services Gen2 (STS Gen2) as the cloud service.
Symphony runs locally on the restaurant POS, while STS Gen2 is the cloud component that the POS connects to. STS Gen2 allows orders from the RBI platform to be sent to restaurants.
...
Overview
This page summarises the menu structure and identifier standard that must be followed by Franchisees to make the Oracle configuration compatible with the RBI Digital Platform.
Menu Configuration
Oracle Symphony offers multiple ways of configuring a menu. The following guides detail how a menu must be configured to be RBI-compliant.
...
In summary, Menu Item Masters contain the Oracle PLU. Each PLU has one ore more definition sequences, and each definition sequence has one or more price sequences.
...
So the Menu Item Object Number alone isn't enough. We also need the Definition Sequence and Price Sequence to fully specify the item's price and availability.
You can find the menu configuration guides here: Oracle Config - Menu.
Unique Identifiers
The reason we use a unique PLUs (Product Look Up code) for the menu structure (by combining PLU, Price Sequence and Definition Sequence attributes) is that the RBI Platform needs unique PLUs internally to function as expected – it will determine both price and availability of the menu item. Internally, the RBI Platform will concatenate each attribute, separated by a dash, to create a unique PLU.
...
For menu items:
Price Sequence to distinguish between service modes, where 1 is Pickup and 2 is Delivery. It is also possible (but not recommended) to use Definition Sequence to distinguish between service modes.
Definition Sequence to be always 1.
For modifiers:
Price Sequence to distinguish between service modes and Add/No modifiers (details here). It is possible (but not recommended) to use different Menu Item Master ID’s than those mentioned in the linked documentation. It is also possible (but not recommended) to use Definition Sequence instead.
Definition Sequence to be always 1.
Take the Whopper:
In Oracle, the Whopper might have an Object Number of
1001001
.If it's sold In-Restaurant with a specific price and availability, it might have a Definition Sequence of 1 and a Price Sequence of 1.
So, the correct mapping for the In-Restaurant Whopper in RBI Digital would be:
1001001-1-1
.
By understanding these unique identifiers and how they're combined, you can accurately configure your POS system to ensure correct pricing and availability for all your menu items in RBI Digital.
More details can be found in each sub-section of the Oracle Config POS - MenuConfiguration documentation.
Note |
---|
The approach above needs to be the same for all structures – i.e. you can’t use PLUs to distinguish service modes for items and definition sequences for combos. |
...