Utilize the Menu Maintenance page to create new menu items and map them to a menu set.
Preparing Your Menu Items and Menu Set Data
Before importing or adding menu items to Decision Logic, it's important to get a full data pull of all menu items in your Point of Sale database into an excel sheet so that you can correctly build menu sets and account for all of the following situations:
Duplicate Menu Item Descriptions with different POS IDs
Although a common occurrence in the point of sale, Decision Logic does not support having the same menu item description with 2 different POS IDs on the same Adding Menu Data Menu Sets in Decision Logic. To solve this, there are 2 options:
Rename one of the duplicates in Decision Logic prior to importing via excel or when manually creating the menu item.
When you build the recipes, you can build the recipe for 1 item and then copy the recipe into the duplicate item.
Create an additional Menu Set that could contain the same-named menu item description using the different point of sale, this solution will require maintaining an additional menu set long term.
Duplicate POS IDs with different Pricing
We cannot have the same object # with 2 different prices in Decision Logic. If we did, you would have double depletion on that item. To solve this please pick a price and delete the row that has the price that you don’t need.
Incorrect menu item category
If your Menu items have not been created with the correct category, fix this in the point of sale and then reassign the menu item to the correct category in Decision Logic via the User Interface or in the import template prior to importing.
Incorrect Menu Item pricing
If your Point of Sale menu item has the incorrect price, you should correct the price in your point of sale system first.
Collecting Menu Item Information from the Point of Sale
Ask a Point of Sale administrator to use the query below to return the information needed for Menu Item Import out of micros. Results will look like this Example Micros Menu Item Export.csv