Follow

Normally, items and options within the online ordering system are “mapped” to their corresponding items and modifiers within the MICROS system. However, due to mis-configuration, sometimes items are not mapped.

By default, our integration will fail to send these unmapped items to MICROS, as we have no way to connect them. Exception items provide a better option, by giving our integration a place to send these unmapped items.

Many restaurants have the concept of an “open” item and modifier, where it is not strictly defined. Daily specials are often just sent in as “Open Food” because they change frequently and it would be cumbersome to reconfigure the POS every day. When a customer has a custom special request, a server often uses a “Special Instructions” modifier that allows them to type special notes to the kitchen. We can leverage these open items/modifiers.

Example Exception Item Configuration (Open Food) 

The following screens detail an example Open Food item, used for exception items. 

mceclip0.png

mceclip2.png

Note: The Menu Item Class must be an “item” class, not a “modifier” class.mceclip3.png

mceclip1.png

Note:  These settings vary considerably from one restaurant to another. The key setting is under General Options. Condiments should beunchecked

 

Example Exception Item Configuration (Open Modifier/Special Prep)

mceclip4.png

mceclip5.png

Note: The Menu Item Class must be an “modifier” class, not an “item” class.

mceclip8.png

mceclip9.png

 

Note:  These settings vary considerably from one restaurant to another. The key setting is under General Options. Condiments should bechecked

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.