Technical Teams, Customer Success Teams, and Client's POS programmer
The objective of this article is to outline the available 86ing features with the Olo MICROS integration.
“OUT OF ITEM”
By design, Olo reads the Micros "out of item" database flag every time the Olo price updater is run. This is set to automatically run 2 times every day. If an item is 86'd in Micros at the time the price updater runs, it will be 86'd on Olo. To un86 (or 68) this item, set the item to be available in Micros and run the Olo price updater.
Optionally, Olo can check for 86'd (out of item flag in Micros) items at your desired frequency. Please open a support ticket to have this feature enabled. You will need to provide the cadence (every x minutes). If an item is 86'd in Micros, the item will be 86’d on Olo after “x minutes”. To un86 (or 68) this item, set the item to be available in Micros, the item will be 68’d on Olo after “x minutes”.
NOTE: We do not recommend setting this cadence to be lower than 10 minutes to avoid burdening the Micros database.
“MISSING/INVALID PRICE RECORD"
By design, if an item is mapped in the Olo menu and the item in Micros does not have a valid price record, then it will be 86’d on Olo. If the item does not have a price record linked, or if the effective to and from dates/times are not valid, the item will be 86’d on Olo.
“SET MISMATCHES 86'd"
Optionally, Olo can automatically 86 any item that is recognized as a mismatch between the Olo menu and the local Micros database. This is a configurable setting and not one commonly used. Please open a support ticket to have this feature enabled. When enabled, all mismatches will be 86’d on Olo. To resolve any of these mismatches, you would correct the issue in the Micros, reload the Micros database (via the Micros Control Panel), and run the Olo price updater. If the mismatch is due to an error in the Olo menu, you would correct the issue in the Olo menu, and run the Olo price updater.
Here are examples of Mismatches:
- If an item is mapped as a condiment in the Olo menu and it is an item in Micros, it will be seen as a mismatch. Olo looks at the "condiment membership group" in the menu item setup to determine if an item is a condiment. If this field is NULL, then Olo assumes this is an item, not a condiment, and it will be labeled as a mismatch. This is also true in the reverse. If an item is mapped as an item in the Olo menu and it is a condiment in Micros.
- If an item or modifier is mapped in the Olo menu and the item or modifier does not exist in the Micros database, then it will be seen as a mismatch. This is also true if the mapping ID was incorrectly entered, and that ID does not exist in the Micros database.
- If an item is mapped in the Olo menu and the item in Micros does not have a tax class linked in its Menu Item Class, then the item will be reported as a mismatch.
- If an item or modifier is not mapped in the Olo menu, but the item or modifier exists in the store menu, then it will be returned as a mismatch. This would be resolved in the Olo menu via the Olo Dashboard.
There is an 86 report available in the Olo Dashboard for reference.
NOTE: If an item or modifier is 86’d manually through the Olo Menu and is available in the Micros, then when the price updater runs (automatically or manually) or the store is set up to frequently check at X minutes, then the item or modifier will always be un86’d on Olo.