Menu Items are where we connect to the ‘sales’ world, by creating a sales profile for every item you sell.
Adding Menu Items allows you to sell, and you should be guided by your EPoS system - i.e. the two need to mirror each other with items and costs. Menu Items can be added into Kitchen Cut before you actually begin to sell the items. So, these are there when your EPoS system sends them to us.
It's important to note what's happening here. You are essentially 'Pairing' together the information that exists on EPOS (the PLU/SKU/item code) with the Source Item (the recipe or ingredients in Kitchen CUT) that needs to deplete every time that code is sold.
- Starting for the first time, log into your account dashboard
- Click on POS > Menu Items.
- If you already have a live EPOS integration, you will see items listed under the 'Unpaired' tab. These are the items that have been sold so far, but that don't yet have any established meaning in Kitchen CUT - ie. the system has logged the PLU code (item code), and then you need to tell it what to do when that item is sold again. To do this, we will Create, or Pair the menu item. Just click Actions > Edit.
- If your EPOS integration isn't live yet, you can still get started with Pairing your menu items anyway. Just go to POS > Menu Items, and select Add New.
CREATING A MENU ITEM:
- Once you arrive at the config form, you can add in your basic info:
- Add in your item name (as it would appear on the till) - if working from the Unpaired list this will already be populated.
- In the 'Item code' field assign an EPOS/PLU/SKU code - if working from the Unpair list this will already be populated.
- Now define the item as a Menu Item (Modifiers are covered below)
- Assign a Sales Category - this will tie the item to both a Category and Class e.g. Singha Beer = Bottled Beer & Beverage (add sales categories in Settings > Sales > Sales Categories).
- Add to the Location Hierarchy, i.e. select locations that will be selling the item
- Now there is a choice to define what kind of Menu Item this is:
This ties the menu item to a source product e.g. an item bought in that is sold whole (e.g. bottle of wine).
This ties the menu item to a source recipe from Menu Costing, e.g. a single sales profile which links to a recipe and many sub recipes underneath.
- Set your Selling Price (to include tax)
- Add any images of the item
- Check you are happy with your Profits
Multi-line recipes in detail
- These are basic recipes - so no need to build complex nested recipes for simple creations.
- Notice the ‘Source Item’ section has changed and now allows you to add either a) ingredients, or b) other menu items.
- The result being you can create simple recipes as shown in the screenshot below.
- Any allergens linked to either will populate as exepected.
You’re now ready to add sales, whether through the App, from a batch file or direct from your EPoS tills . . .
NOTE: Do keep in mind the following scenarios that can be configured in Menu Items:
1 - Same code and same recipe with a different price across different locations.
2 - Same code with different recipe with different prices across different locations
It is important to understand the mix of code with location makes each item unique.
Creating a modifier can reflect a few different ordering events:
Swapping an ingredient - specifying a customer choice.
The screenshot below shows that we wish to substitute the normal ‘Skin on Fries’ we serve with ‘Sweet Potato Fries’. There is no difference in selling price, but you will notice that during the transaction, we will be ‘adding back’ the ‘skin on fries’ whilst using the ‘sweet
Giving an instruction to the kitchen.
The second scenario is simpler as we are purely instructing the kitchen, no bun with the order, therefore add a bun back into inventory.
Adding upsell revenues
The third scenario is a progression from the second but we purely add an additional selling price. See the screen shot below, note the modifier name, the recipe makeup and the financials.