Back to Olo.com

Revel: Menu Mapping Instructions


Audience:

Menu Administrators, POS Specialists, Technical Teams

 

Description:

When you begin to map a menu to a Revel database within Olo Menu Admin, you will essentially be mapping to the barcodes that are present for each item and modifier choice. As you build out items within the Olo Company Menu, you would map the items and their modifiers to various entity types, which are all described below, under the “Mapping Instructions” section.

 

Helpful Links

 

 

Helpful Mapping Tool: The POS Menu Viewer 

Upon entering the Olo Company Menu via Dashboard > Menu > Manage Company Menu, you will see the POS Menu Viewer tool in the top right-hand section of the screen. This tool can be used to browse the POS database for a specified store. The POS data will show you the structure within the database of any POS item you choose**.

If you are unable to locate an item via the POS Menu Viewer, make sure that the item exists within the database of the store you are pulling the POS menu data from.

 

To use the POS Menu Viewer,

  1. Enter a specific store location (as you type, a drop-down list will present store locations; select the store location you wish to use)
  2. Type in the name of a menu item (as it is named in the POS database), or the barcode of the item. As you type, be sure to select the item from the drop-down list.
  3. In the event there are modifiers linked/associated with the item (or parent item), you can expand the tree by clicking on the “+” icon next to the POS item name.

PDE_Explorer_example.png

 

 

Mapping Instructions

 

Step 1: Mapping Items

Items within the Olo menu can be mapped to either one of the two entity types; “product” or “none”. They may have customer facing names/verbiage that is different than what is defined in the POS according to the brand's intentions.

  1. “Product” Mapping: Most items would be mapped as “product”, and those can be standalone items or could have modifiers associated with them (i.e. nested under them).

How to map:

a. Click Edit under the item, next to the verbiage that says “No mapping set” (which is default until mapping has been completed).

Edit_Button.png


b. The entity type should already be set to “product”. If not, make sure to click on the “Type” field and select “product” from the drop-down list.


c. To enter the barcode for the item, click on the “copy” option on the POS Menu Viewer and click on the “paste” option next to the Entity id field**. The barcode gets copied into the Entity id field. The barcode can also be typed in, or copy/pasted from a document (you can use keyboard shortcuts to copy paste off of a document).


**When using the copy/paste functionality off of the POS menu viewer, you cannot use the keyboard shortcuts for copy/pasting (eg: CTRL + C & CTRL + V). You have to click on copy/paste. Copy/pasting off of the POS Menu Viewer reduces errors that could be caused by the wrong ID being entered/typed into the Entity id field.

Adding_Item_Mapping_PDE.png

d. Once completed, click Save next to the Entity id field.


e. Continue on to Step 2: Mapping Modifiers if there are modifiers associated with the item. If not, the item is all set!

 

  1.   “None” Mapping: If the item at this level has no barcode associated with it, then it could be mapped to “None”, whereby no barcode needs to be entered into the “Entity id” field. This can be thought of as a shortcut to point to the next group of choices in the ordering flow on Olo.

For example, on the Olo Menu, there is an item whose price depends on the protein choice that the customer picks. In this case, since base cost is dependent on the protein choice;

  • The item within the Olo menu would be mapped to “None”
  • The protein choices 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 “product” since they are in fact the base items with associated barcodes.

    None_Mapping_Eg.png

 

!Tip!

When an item is mapped to none within the Olo menu, the item will not get sent down to the POS, since it does not have an associated POS ID. Only products that are mapped to specific POS IDs can pull prices that are configured in POS and will, as a result, get communicated to the POS.

How to map:

a. Click Edit under the item on the Olo menu, next to the verbiage that says “No mapping set” (which is default until mapping has been completed).

None_mapping_Edit.png

b. Click on the “Type” field and select “none” from the drop-down list.

None_mapping.png

c. Since we are mapping to “none”, you do not need to enter anything into the “Entity id” field. Leave the entity ID field blank.


d. Once completed, click Save next to the Entity id field.

e. Click on modifiers under the item, and click Edit on the modifier group containing the base product options.

None_mapping_done.png


f. Map the choices following the “
Product” Mapping instructions above.

 

Step 2: Mapping Modifiers

Modifiers can be mapped to either one of two entity types; "modifier" or "none"

  1. “Modifier” Mapping: Most modifiers would be mapped as “modifiers”, to the appropriate barcodes. 

How to map:

a. Click Edit under the modifier choice, next to the verbiage that says “No mapping set” (which is default until mapping has been completed).

No_mapping_modifier.png

b. Set the entity “type” to “modifier”.

c. To enter the barcode for the modifier, click on the “copy” option on the POS Menu Viewer and click on the “paste” option next to the Entity id field**. The barcode gets copied into the Entity id field. The barcode can also be typed in, or copy/pasted from a document (you can use keyboard shortcuts to copy paste off of a document).


**When using the copy/paste functionality off of the POS menu viewer, you cannot use the keyboard shortcuts for copy/pasting (eg: CTRL + C & CTRL + V). You have to click on copy/paste. Copy/pasting off of the POS Menu Viewer reduces errors that could be caused by the wrong ID being entered/typed into the Entity id field.


modifier_mapping_ID_NEW.png

d. Once completed, click Save next to the Entity id field.


  1.  “None” Mapping: If the modifier at this level has no barcode associated with it, then it could be mapped to “None”, whereby no barcode needs to be entered into the “Entity id” field.

    For example, on the Olo Menu, White Rice has been added as the default rice choice that comes with a burrito. If a customer went with this default option, that would not need to be sent down to the store. So in this instance, the White Rice would be mapped to “None”. 

    When a modifier is mapped to none within the Olo menu, if a customer were to place an order containing that modifier, the modifier will not get sent down to the POS, since it does not have an associated barcode. Only modifiers that are mapped to a specific barcode will get sent down.

    How to map:

    a. Click Edit under the modifier on the Olo menu, next to the verbiage that says “No mapping set” (which is default until mapping has been completed).

    None_Mapping_Modifier_Edit.png

    b. Click on the “Type” field and select “none” from the drop-down list.

    None_mapping_modifier.png


    c. Since we are mapping to “none”, you do not need to enter anything into the “Entity id” field. Leave the entity ID field blank.

    d. Once completed, click
    Save next to the Entity id field. The mapping section should look like the image below.

    Modifier_None_Mapping_Done.png


 

Other important information

  1. For any given item, there needs to be an entity mapped to “product”. If an item and its nested choices are only mapped to “none” and as “modifiers”, that will lead to order failures since there is no defined “product”.

  2. You cannot map an entity as a “product” and have another nested choice that is mapped to “product” as well. The nested choices would need to either be mapped to none or mapped as modifiers.

    However, if the item itself is mapped to “none”, then you could have multiple modifier groups at the first level that contain choices that are mapped to “product”. Brands utilize this option if there are modifier choices that need to get sent down to the store as items.

    Imp_info_point_2.png
    Imp_info_point_2_b.png


  3. When looking at the data that is pulled through the POS Menu Viewer tool, you will see the exact structure of the item (i.e. the modifier groups and the modifier choices that have been assigned to the item within the database). When creating menu items within Olo Menu Admin, you should pay close attention to the barcodes of the modifier choices, especially if you are to reuse a modifier group that was built for a different item.

    For example, under the “Bowl” item, there is a “Customize It” modifier group within the Olo menu that is also being used under other items. When reusing the modifier group, we would have to ensure that the mapping of the choices that have been entered into the Olo Menu currently matches the mapping of the choices that have been assigned to the item within the POS.

    a. Click on the “+” icon to expand the relevant modifier groups containing the choices within the database.

    Imp_info_point_3_a.png

    b. Check the barcodes that have been entered into the modifier group against the barcodes shown through the POS Menu Viewer. In this instance since the barcodes match, you can successfully use the modifier group under the “Bowl” item. If the barcodes assigned within the POS were different from those that were entered within the Olo Menu, that could lead to order failures.

    Imp_info_point_3_b.png

    Also, refer to this article to learn more about reusing existing modifier groups.

  4. Everything single item and modifier should be mapped to some entity type, in order for orders to be placed successfully.

 

Best practices to follow once menu mapping has been completed:

Didn't find what you need?

Submit a request to our Help Team and someone will
get back to you shortly.

Submit a request

Copyright © 2018 Olo. All rights are reserved.