Arithmetic/Mathematical Values in Modifiers

[earthdiego]

This is a feature that Aloha POS has had for ages.

Use case: Shot Pours, Doubles, etc.

Situation: Guest asks for a double whiskey. Standard double whiskey pour is 3oz (two portions of a 1.5oz serving size)

Problems:

• The only way to ring in a double to indicate via KDS or printed ticket to the bartender is to ring in the whiskey twice, and either creating a $0 value double button or manually typing in "double" as a note to indicate that the guest has ordered a double and that is not two separate orders.
• The way we are using "Neat" (or "rocks)  modifier is to make it a $2 up-charge. The problem with this is that not all spirits are priced the same. For instance if there was a spirit that costs $100 to the guest, each 0.5 oz is worth $25. The difference between a standard pour ($100, 1.5oz) and a neat/rocks pour ($125, 2oz) is $25 whereas a drink that costs $10 to the guest obviously would be way less.

Solution: Allow mathematical values in the price input for modifiers.

Examples:

• Double Modifier: [ *2  ] -- this will take the price and multiply by 2
• Shot Modifier: [  /2. ] -- this will take the price and divide by 2
• Neat Modifier:[  ((x*0.25)/1.5)  ] -- this will calculate the ratio to increase the price per 0.25oz

Of course there can be buttons to make this step more user friendly such as a button to replace a value X with "item price" or use common symbols such as "%"

Other solution could be to have an option where you can designate Fluid Oz/Milliliter values for Standard Pour / Neat Pour / Rocks Pour / Shot Pour and have default built-in modifiers provided by toast that creates the calculation.

I believe the first solution would be the most flexible with perhaps even a way to toggle "advanced mode" so standard users cannot access it unless prompted.

[au79teahouse]

I don't think there is an update on this feature. If you don't mind, I will copy and re-post this to the other post for feature request. It is said that Toast engineers/developer constantly review that post and hope they will bring this feature up to their roadmap  for future implementation soon.