Back to Olo.com

Fixing Menu Mismatches


The Mismatch Report on the Dashboard will help identify any discrepancies between the POS IDs that have been entered into the Olo menu and the POS IDs available within a stores database. You can check for mismatches at the store level and the brand level. Mismatches are identified when items and modifiers are added to store menus and either the automatic price updater runs or a manual price update is completed at the store or brand level.

  1. Accessing mismatches at the store level

  2. Accessing mismatches at the brand level

 

Causes of mismatches and resolving them

  1. Unmapped items and modifier choices

    If there are unmapped items and choices in the Olo menu that have been added to a store menu, they will return as mismatches.

    At the store level, these mismatches will appear with no entity type or POS ID listed within parenthesis, as highlighted below.

    Store_no_mapping_ex.png

    At the brand level, unmapped items and choices would show up on the mismatch report with no POS ID listed under the Entity ID column, and no entity type specified within the Entity Type column, as highlighted in the image below.

    CM_no_mapping_ex.png

    Resolution: Ensure that all items and modifiers that are in your Olo company menu are mapped, especially if they are going to be added to a store menu. You can utilize "none" mapping in instances where there are no specific POS ID's associated with certain items and modifiers. Items and modifiers that are added to live store locations need to be mapped to some entity type, and cannot be left with "no mapping set".


  2. POS discrepancies

    Although an item or modifier is mapped to the correct POS ID within the Olo menu, that POS ID might not exist within a stores database. For example, the Corned Beef Hash is mapped to item ID 1000, and while item ID 1000 may exist in most store databases, it may be missing from the database of certain stores.

    At the store level, you will see the entity type that has been assigned to the item within the Olo company menu, along with the entity ID that the item is currently being mapped to.

    Discrep_Store.png

    At the brand level, you will see the entity ID that the item is currently being mapped to, along with the entity type that has been assigned to the item within the Olo company menu.

    Discrep_CM.png

    Resolution: Check the database of the store where the item or modifier is mismatching, to make sure that the POS ID for the item or choice does, in fact, exist within the store's POS database.


  3. Incorrect entity type

    In some instances, items and modifiers may be mapped to the wrong entity type. For example, a modifier choice may be incorrectly mapped to an "item" or "product" entity type, instead of being mapped to "mod", "modifier", and "condiment" (depending on the POS the menu is being mapped to). Since the modifier choice exists within the POS as a "modifier", mapping that ID to an "item" entity type will lead to a mismatch.

    For example, the Broccoli has been set up as a modifier within the POS database, but on the Olo menu, it is being mapped as an item. This is going to be a mismatch since the POS ID for the broccoli does not exist as an item ID within the POS.

    incorrect_entity_mod.png

    Resolution: Make sure that all of the products and modifiers within the Olo menu are mapped to the correct entity types. If you want to learn more about entity types and mapping specifics for your brand's POS, refer to the relevant articles published in this menu mapping section.


  4. Incorrect mapping IDs

    An item or modifier within the Olo company menu might be mapped to an ID that does not exist within any stores database, and this menu mapping misconfiguration will show up as a mismatch as well.

    For example, the POD ID for the Hamburger item within the POS is 4000562. But by error, the POS ID was entered as 4000656. Since ID 4000656 does not exist within the store's database, it will show up as a mismatch.

    Incorrect_mapping_ID.png

    However, if ID 4000656 existed within the database in reference to a different item (such as a Taco, for example), then mapping the Hamburger to ID 4000656 would not show up as a mismatch since the item ID does, in fact, exist within the POS database, although it does not relate to the Hamburger. Based on this example, if a customer were to order a Hamburger on the Olo menu, the store will receive an order for a Taco, since that is the ID the Hamburger is being mapped to.

    The same applies to modifier choices that are mapped with the incorrect POS ID as well. For certain POS systems, modifiers would need to be mapped to a modifier group ID as well as a modifier choice ID, along with a mod code (in some instances). Make sure that each of the IDs entered for a modifier is correct. If you want to learn more about modifier mapping specifics for your brand's POS, refer to the relevant articles published in this menu mapping section.

    Resolution: Use the POS Menu Viewer tool available within the Olo Company Menu, to pull the POS database when mapping new items and modifiers. Refer to this article to learn more about using the POS Menu Viewer tool. It is important to note, however, that the POS Menu Viewer may not work with certain POS systems.

 

POS Specific Mismatch Resolution Documentation

Aloha
Prices not updating and mismatch reporting
False mismatches


Micros
Resolving Micros mismatches

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 © 2019 Olo. All rights are reserved.