Linking items with different portion sizes

[svtmook]

i have different ways of selling the same protein. 1 would be a dinner, 1 would be an add and 1 would be a'la carte.  What I want to be able to do, which i have done on other protein items that do not have a half size for different menu options, is be able to go on a count, add it in under one item and it cover all items that protein is in.

For example, i have a salmon dish, which is 1 whole salmon piece.  I have salmon add for a salad, which is 1/2 piece of salmon, and proteins can be ordered a'la cart, where it's again a 1/2 piece of salmon. If i go down to a 5 count on salmon, i have to go in and put a 4 ct on the dish, then 1 ct on the protein add and 1ct on the a'la carte.  Then adjust each count as things are sold to cover all orders and maximize use.

I know i can copy existing items into menu groups and have the group depict pricing and a count will carry over.  But if i put a 1ct on salmon, it's 1 count everywhere and not 2 count for the petite and a'la carte.  Is there a way to copy existing items into groups and have the item portion equate out to half or double?

[au79teahouse]

My approach to this would be to create a protein modifier item to keep tracking on inventory across different items. Probably not the best way to handle this type of situation but this is what works for me for now until toast implement something that can help track inventory count across items.

In your example,

- the salmon dish uses 1 whole salmon piece,
- Salmon as an add-on for salads, that uses 1/2 piece
- À la carte salmon, uses 1/2 piece

1. Create a modifier group for Salmon Dish that has the following configurations:

- Selecting a modifier from this group is: *Required
- Allow guests to select more than one modifier? *More than one modifier can be chosen
- What is the maximum number a guest can select? *2
- Can the same modifier be added to an item more than once?  *By default, the same modifier can be added more than once in this group (Overrideable on the modifier)
- Create a modifier item called "1/2 salmon" and then add the same modifier "2 times" to the modifier group. 
- Check the "default" box for both modifiers so when the salmon dish is rung up the modifiers are selected by default.

2. Create a "new" modifier group for Add-on and A la cart with the following configurations:

- Selecting a modifier from this group is: *Required
- Allow guests to select more than one modifier? *More than one modifier can be chosen
- What is the maximum number a guest can select? *1
- Can the same modifier be added to an item more than once?  *By default, the same modifier can be added more than once in this group (Overrideable on the modifier)

- add the same existing modifier item "1/2 salmon" to this modifier group.
- Check the "default" box for the modifier so when the add-on or a la cart is rung up the modifier is selected by default.

The workflow will be like the followings:

- When a salmon dish is ordered, system will deduct 2 servings from the count.
- When an add-on/ a la cart is ordered, system will deduct 1 serving from the count. 
- You set the quantity available by how many 1/2 salmon you have. If you 10 "1/2 salmon", you set the count to 10.

Noted that:

- the "1/2 salmon" modifier will be shown on the kitchen ticket as well as on the customer's receipt. You may want to change the modifier name and kitchen name so that it doesn't get too messy on the kitchen ticket and customer receipt. 

- this setup uses a “1/2 salmon” modifier to manage inventory. As a result, menu items still display as “available” even after the “1/2 salmon” modifier is depleted. Servers will still see salmon dishes, salmon add-ons, and salmon à la carte as “available” in the system. However, once they take the customer’s order, they won’t be able to complete the transaction because the system requires the “1/2 salmon” modifier — which is already out of stock. This creates a frustrating experience where the item appears available but cannot actually be sold and they have to go back to customers again.

- the only good news is that you only need to change the count once instead of 3 times at different places on the system. And the count is always accurate. 

[au79teahouse]

Just a quick update on this topic. It seems Toast is already working on the implementation on this.

[Rob]

Thanks for this update!