...
The reason we use a unique PLU’s PLUs for the menu structure (by combining PLU, Price Sequence and Definition Sequence attributes) is that the RBI Platform needs unique PLU’s PLUs internally to function as expected. Internally, the RBI Platform will concatenate each attribute, separated by a dash, to create a unique PLU.
For example, for an item with product reference ID 100137, price sequence 1 Menu Item Master ID 200137, definition sequence 1 and price sequence 2 (Delivery) and definition sequence 1, the following PLU will be generated: 200137-1-2-1.
Our recommendation is to use:
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.
More details can be found in each sub-section of the Oracle Config - Menu documentation.
| Note |
|---|
Note that the 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. |
| Note |
|---|
Note that the deviations are❗not recommended❗unless it is mandatory since the Deviations from the proposed structure are not recommended. The recommended approach will results in a faster rollout , and less issues, and new features will be built based on the recommended structure. |
...