Back to Olo.com

Brink: Menu Mapping Instructions


Mapping a menu to a Brink database can be an easy task, especially given the tools available within Olo Menu Admin to assist throughout the mapping process. 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 Mapping Tool: The POS Menu Viewer

Upon entering the Olo Company Menu, you will see the POS Menu Viewer tool at the top right-hand corner. This tool can be used to browse the POS database for a specified store. The POS data will show you the structure of any product you choose**.

**If the item also exists within a modifier group in the POS, the POS Menu Viewer will not be able to pull the POS data for that item as an a la carte item. Also, 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, or the POS ID for a menu item. As you type, be sure to select the product from the drop-down list.
  3. To view the modifiers associated with the item (if any), click on the “+” icon next to the item name

PDE_Explorer_example.png

  

Mapping Instructions

 

Step 1: Mapping Products

Products within the Olo menu can be mapped to either one of the two entity types; “item” or “none”.

  1. “Item” Mapping: Most products would be mapped as “item”, and those can be standalone products or have modifiers associated with them.

    How to map:


    a. Click Edit under the item, next to the verbiage that says “No mapping set”.

    No_mapping_-_product.png

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

    c. To enter the POS ID for the product, click on the “copy” option on the POS Menu Viewer and click on the “paste” option next to the Entity id field**. The POS item ID gets copied into the Entity id field. The POS ID can also be typed in, or copy/pasted from a document (you can use keyboard shortcuts to copy paste off of a document), especially if you are unable to locate the ID via the POS Menu Viewer. It may be best to double check that the ID does exist within the store's database if you are not able to locate it.

    **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.


    Item_ID_copy_paste.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 product. If not, the item is all set!

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

    For example, on the Olo Menu, there is a Mac & Cheese item, and the price of the Mac & Cheese 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 POS item IDs.


Modifier_item_mapping.png

When an item itself is mapped to none, it will not get sent down to the POS, since it has no associated POS ID. Only items with an associated POS ID will get sent down to the POS. In this example, the "regular" and "small" options will get sent to the POS as items, since they are mapped to POS item IDs.

How to map:

a. Click Edit under the item on the Olo menu, next to the verbiage that says “No mapping set”

Item_NONE_mapping.png

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

Item_None_mapping_2.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.

Enter_modifier_mapping.png

f. Map the choices following the Item” Mapping instructions above.

 

 

Step 2: Mapping Modifiers

The same as with products, 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 Brink modifier group ID and the modifier ID. The modifier group ID indicates the grouping that the modifier choice belongs to, within the POS database.

    How to map:

    a. Click Edit under the modifier choice, next to the verbiage that says “No mapping set”.

    Modifier_Mapping_Edit.png

    b. Set the entity type to “modifier”

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

    When mapping a modifier, there should be no spaces between the modifier group ID and the modifier ID, they should ONLY be separated by a comma.

    **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.png

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

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

    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 a modifier is mapped to none, it will not get sent down to the POS. Only modifiers that are mapped as “items” or “modifiers” will get sent.

    How to map:

    a. Click Edit under the item on the Olo menu, next to the verbiage that says “No mapping set”.


modifier_none_mapping_edit.png

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

modifier_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. The mapping section should look like the image below.

mod_none_mapping_saved.png


 

Important Notes

  1. If you would like to add in a mod code to the mapping, it should be added after the modifier ID.

    mod_code.png


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

  3. If an entity is mapped as an “item”, you cannot map another entity under that as an “item” as well. The nested choices would either need to be mapped as “none” or be mapped to “modifier”.

  4. As modifiers are being built out and mapped within the Olo menu, pay close attention to any modifier restrictions/requirements that must be met, in order for the POS to accept a valid order for an item.

  5. Everything single product 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.