Think you’ve gone about it the wrong way. Probably would have been better using menu switching and custom menu item buttons like Richs retail setup.
If you insist on using custom nav menu you would need to make it reopen the ticket it just closed.
the route your taking might seem simpler but is going to create all sorts of additional issues.
You solve getting back to menu by closing ticket.
Even if you setup reopening the previous ticket you next issue will be ticket flow… If using a kitchen printer youll need to creat custom flow to prevent sending each set of items when ticket is closed.
Also if you want cancel for customer youll need to create custom void flow as orders will be submitted.
There was a self service topis a while back but cant find it.
My reconmendation would be custom menu with menu switching and full screen ask question prompts.
This route keeps single ticket session so saves printing and cancel issues
You would havesay a menu for each set like you do but create a main menu which has only the 4-5 selection buttons you show on nav screen shot.
You then setup a full screen ask question say start new order or something which creates new ticket and switches to main menu.
Youll then need a final ticket closing rule to restart the process by bringing back the ask question.
So basically what you’re saying is a button to ask “Do you want to place an order now?” and trigger it on Login and “Yes” will create a ticket and then he can choose which menu he wants, and the buttons will just “Display Ticket” (Btw, how do I set the Display Ticket ID?)