Back to Olo.com

Focus: Menu Mapping Instructions


Audience:

Menu Administrators, POS Specialists, Technical Teams

Description:

As you build out products and modifiers within the Olo Company Menu, you would map each of them to various entity types, which are all described below, under the "Mapping Entity Types" and “Mapping Instructions” sections.

 

Helpful Links

 

  

Mapping Entity Types

  1. "None": If a product or modifier has no POS ID (or PLU) associated with it, then it could be mapped to “None”, whereby no POS ID 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.

    Product example: On the Olo Menu, there is a product that is priced in the POS on the protein choice that the customer picks. In this case, the base cost is dependent on the protein choice so the product itself would be mapped to "none", and the protein choices would be mapped to "item".



    Modifier 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 choice would not need to be sent down to the store. So in this instance, the White Rice would be mapped to “None”. This is explained further within the "None Mapping" section of modifier mapping.



  2. "Item": Any product within the Olo menu that has an associated POS ID (or PLU) would be mapped as "item". Certain modifiers can also be mapped to "item" in some scenarios, which are explained in the “Mapping Instructions” section below.

    item_example.png
     

  3. "Modifier": Modifier choices built on the Olo menu that have associated POS IDs (or PLUs) should be mapped to "modifier", especially if the price assigned to the modifier within the POS needs to pull through to the Olo menu. The appropriate PLU for the modifier choice should be entered into the entity ID field. The modifier PLU will always contain a tilda (~).

    A modifier that is currently not priced within the POS can also be mapped as "modifier", but if a price is ever added to the modifier choice, it will start to pull through to the Olo menu. If you do not want pricing for a modifier choice to pull through, map the choice to "focus-free-modifier" (described below).

    Modifier_Example.png

    Modifier_Example_2.png

  4. "Focus-free-modifier": Any modifier choice built on the Olo menu that has an associated POS ID (or PLU) can be mapped to "focus-free-modifier", especially if you do not want pricing for the modifier choice to pull through to the Olo menu from the POS. The appropriate PLU for the modifier choice should be entered into the entity ID field. And the modifier PLU will always contain a tilda (~).

    focus_free_Modifier_Example.png

    focus_free_Modifier_Example_2.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”. They may have customer facing names/verbiage that is different than what is defined in the POS, according to the brand's intentions.

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

How to map:

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

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


item.png


c. Enter the item ID for the product into the "Entity id" field

item_mapping.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 product is all set!

 

  1. “None” Mapping: If the product at this level has no POS item ID associated with it, then it could be mapped to “None”, whereby no item ID 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 a product that is priced in the POS on the protein choice that the customer picks. In this case, the base cost is dependent on the protein choice so the following technique should be used:

  • The product within the Olo menu would be mapped to “None”
  • The protein choices would be set up within a choice group as modifiers, nested under the product within the Olo company menu.
  • Note that these Olo "modifiers" (or choices) can exist as items in the POS database. This is because the parent in Olo is mapped to None, which means that it is just a shortcut to point to a group of items the guest can choose from.
  • The "modifiers" in this group will be mapped as “item” entity in Olo because they point to Item IDs within the Focus POS. 

    None_Mapping_Eg.png

 

Tip: When a product is mapped to none within the Olo menu, the product 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 the POS and will, as a result, get communicated to the POS.

How to map:

a. Click Edit under the product 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 product, and click Edit on the modifier group containing the base product options.

None_mapping_done.png


f. Map the choices following the
"item” Mapping instructions above.

 

 

Step 2: Mapping Modifiers

Modifiers can be mapped to either one of three entity types; "modifier", "focus-free-modifier", 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. “Modifier” Mapping: Most modifiers would be mapped as “modifier”, to the appropriate modifier ID. 

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

    Modifier_Mapping_edit.png

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

    Modifier_Mapping.png

    c. Enter the modifier ID for the choice, into the "Entity id" field

    Modifier_Mapping_ID.png

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


  2. “Focus-free-modifier” Mapping: Modifiers can be mapped as “focus-free-modifier”, to the appropriate modifier ID.

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

    focus_free_Modifier_no_mapping.png

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

    focus_free_Modifier.png

    c. Enter the modifier ID for the choice, into the "Entity id" field

    focus_free_Modifier_mapping.png

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


  3. “None” Mapping: If the modifier at this level has no POS ID associated with it, then it could be mapped to “None”, whereby no Focus POS ID 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”. 


    Tip: When a modifier is mapped to none within the Olo menu, the modifier will not get sent down to the POS, since it does not have an associated POS ID. Only modifiers 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 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.


Other Important Information

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

  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”, “modifier”, and/or "focus-free-modifier", that will lead to order failures since there is no defined “item”.

  3. You cannot map an entity as an “item” and have nested choice under it that is mapped to “item” as well. The nested choices would need to either be mapped to "none", "modifier", or "focus-free-modifier".

  4. You are able to share modifier groups between products. Refer to this article to learn more about sharing existing modifier groups.

  5. The only special character that can be entered into the entity id field is a tilda (~). No other special characters are allowed (- / , * @ ! % & etc).

 

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.