Closing Ticket (Over Rule States)

V5 Question
1

Hello Everyone!

Thanks for helping people like me throughout… :slight_smile: here is another one!

I am trying to close the ticket so that it over rules all the kitchen states. There are some menu items that are available over the counter and not required to go to kitchen (Slice, Pops, Dips Etc.). I am sure it is possible using some ticket constrains and mapping. but not sure what will be the right constrain for item and category. (could be wrong that is why i am opening a topic here for help and suggestions)

If the Slice, Dip or Pop is added to the ticket from Pickup Department it should close after the settle payment screen and shall not follow the kitchen prep screen…!

I am not sure what you guys will need from me but if someone can direct me i can paste it here…

Here is my overall setup!

PickUp Department:

image
image1725×918 149 KB

Delivery Department:

image
image1734×917 146 KB

Kitchen Display:

image
image1726×918 98.2 KB

2

Think this is where a state based print mapping comes in handy.
I dont use mapping for any of my print jobs other than terminal->printer.
Orders use a KPrint=Print type state with print and printed and use this rate than the default option of status.
This means that in theory you could include a No value if you want to bypass or printed obviiusly but anything other than Print would work which you can constrain on order adding.
I set these as a default on order added based on a product tag.
This flow also allows for things like hold ticket where you can manipulate the custom state in was that would be risky on default status state.

3

Thanks @JTRTech will try something today!