I’m trying to read ORDER STATE in my Kitchen Display, was not able to access {ORDER STATE:Status} nor {ORDER STATE MINUTES:Status} for some reason.
I have also tried reading order state using {ORDER STATE TOTAL:Status} without success.
Any idea why?
{TICKET STATE:Status} and {TICKET STATE MINUTES:Status} worked fine without any problem, but just not ORDER STATE data.
ORDER STATE:Status is updated to New when new order added to ticket, and updated again to Submitted before tick closing.
Also have tried reading ORDER STATE:Display, again without success. ORDER STATE:Display is updated to Kitchen when order added to ticket, which is filtered on the Kitchen Display ticket lister widget, and it’s working fine.
I could not figure out what’s wrong with the way I’m accessing ORDER STATE data, any help would be much much appreciated.
Thanks in Advance.
Result from reading with {ORDER STATE:Status}
Result from reading with {ORDER STATE TOTAL:Status}
Rule for loading and reading ORDER STATE info in Kitchen Display
Ok so lets look at your scenario… the kitchen display your using is a Ticket Lister… You can easily check the Ticket State of tickets. Lets say you want to use Order State… well which order is it going to read from when you have more than one order on the ticket? Answer is SambaPOS has NO idea what order you want to read Order State from.
To do what you want to do is possible with v5 and the new Task Based Kitchen Display but you will not be able to use Order State to filter the tickets in a Ticket Lister. You can filter by product and Ticket tag however.
You can use Order Filter setting to filter Order states to show specific orders on a ticket that match the expression.
I see what you are saying Kendash. I thought it might work since Ticket Lister was able to filter by ORDER STATE, and I read how @rnunez was able to use {ORDER STATE MINUTES} in order filter
Anyhow, even if SambaPOS has no idea which order I want to read, tickets in the Kitchen Display ticket lister shouldn’t just disappear off the screen right?
By the way, I thought {ORDER STATE TOTAL} was added so SambaPOS can read states in all orders within a ticket correct?
Basically all I wanted to do is to use {ORDER STATE MINUTES:Status} to track ticket age, so ticket age doesn’t affect by TICKET STATE , which can change from Unpaid to Paid while orders are being prepared.
Our takeaway workflow is like a reverse of a typical restaurant operation. Orders in most cases does not change through out the lifetime of the ticket, but TICKET STATE does. Most tickets are paid in full first then orders are submitted to kitchen , and for phone in orders are submitted to kitchen before ticket while ticket is unpaid.
Order stare total gives the total amount for orders with a specific state. What you need is a separate ticket state just for what your trying to do. Instead of using Status make a new state and define its flow then use that state for your screen reporting.
My restaurant operates similar we are mostly quick service.
Thanks for your suggestion @Jesse, I’ve added a new TICKET STATE for kitchen display and solved the problem. Thought might be cleaner without any a whole lot of ticket tags and states, which eats up the ticket display space.
Btw, is it possible to hide particular ticket state on the ticket display screen?? I have “Show on ticket” unticked, but it’s still showing up.
