Ok technically that is the order things happen. I just meant that the ticket creation is initiated by adding the first item to the ticket.
I have added a create ticket action but It creates another problem for me. because it is a new ticket, I cannot open other tickets assigned to tables.
I think I am going to have to remove default menus from my departments and tickets and use some rules to reset the menu to my default on user login, ticket closing and the close ticket rule. Hopefully that will cover everything.
I merely meant it to confirm that it was ticket creation not order adding that was causing the change on menu, not that it was going to be a solution.
I think we got the ability to read current menu in a {:xxxx} type tag not so long ago (but might be wrong on that) which could mean you could combat the default menu reset on ticket created with a short flow which remembers the menu before.
Thank You, Using it for Take away menu as in our premises take away meals are cheaper than to dine in, So this saves me changing the price all the time someone orders take away
Are you using price lists? If not would be most efficient way if menus are same with different prices as only have 1 product with the different prices rather than two whole sets of prices.
Then set the price list based on whatever event you want. custom menu button with automation command, normal button, ask question on ticket created, ā¦ options are almost limitless.
This is great. How did you make it so the fast buttons change when selected? You mention something in your writeup about this but when I change the color in the edit product property, it just changes the color permanently.
I found a funny thing that might be a bug:
I followed this tutorial and set up a button to switch to a menu where I plan to put most often sold products. It works like a charm but on a small screen where there is a separate screen for adding orders it adds the buttons as if it was a product. See here please:
I have two Menus - āMenuā and āTopā, both with Fast Menu category. I added a Custom Button to each of them and added āChange Top Menuā as an Autommation Command to the Menu custom button and āChange Menu Menuā to the Top custom button.
So Iām adding names to be able to visualize automation commands that adds products to ticket but for automation commands that does not add products it makes no sense to add to list. I need to understand if it should appear on selection list or not. hmmā¦
OK. On next update youāll be able to prevent these commands to appear in the list by setting quantity to 0. Thank you very much for reporting the issue.
Here is a sample. Sorry for Turkish but all pink items are toppings of ice cream and green button is āOKā button. See how Iām adding ice cream (dondurma) product by choosing toppings (order tags) and click āOKā.
All buttons are custom buttons but pink buttons (toppings) will appear in the list but green button wonāt as Iāve set quantity to 0.
