Menu Administrators, POS Specialists, Technical Teams
Provide mapping guidance with the Olo Menu Admin Tool and Xenial integration
As you map out items within the Olo menu to a Xenial database, you would map the items and their modifiers to various entity types, which are all described below.
“None”: If a product or modifier has no PLU associated with it, then it could be mapped to “None”, whereby no PLU needs to be entered into the “Entity id” field.
Example of item "none" mapping:
For example, on the Olo Menu, there is a French Fries item, and the price of the French Fries depends on whether a customer picks a regular or small portion. In this case, since the base cost is dependent on the portion size;
- The item within the Olo menu would be mapped to “None”
- The size options would be set up as modifiers under the item (within the Olo company menu, but they can exist as items in the POS), and be mapped as “item” since they are in fact the base products with associated PLUs.
Example of modifier "none" mapping:
For example, on the Olo Menu, Brioche Bun has been added as the default bun choice that comes with a burger. If a customer went with this default option, that choice would not need to be sent down to the store. So in this instance, the Brioche Bun would be mapped to “None”.
When an item or a modifier is mapped to "none", it will not get sent down to the POS. Only items and modifiers that are mapped to an associated PLU will get sent down.
- "item": Main items and a modifier would need to be mapped to an "item" entity type if it resides under a product that has been mapped to "none".
- "modifier": A modifier of a parent item should be mapped as a modifier. The modifiers need to be mapped as a single PLU, exampe: 1234
Olo's Menu Viewer tool makes it easy to identity modifiers, as they exist under a Type "ModifierCollectionGroup" like the screenshot below:
- "choice": A parent item that has choice items available for selection, and are shared between other products without price variation will need to be mapped as a "choice" entity. Olo's Menu Viewer tool will show when a component is available based on the Type showing as "BundleComponent" like in the screenshot below:
- "parent_choice": A parent item that has choice items available for selection, and are shared between other products but has price variation will need to be mapped as a "parent_choice" entity. Olo's Menu Viewer tool will show when a component is available based on the Type showing as "BundleComponent" like in the screenshot below:
A "parent_choice" selection will need to be mapped with the Parent ID mapped first, followed by a comma, then the choice ID. Example: 6789,123