@JohnS, point me to right direction…
I have tried to configure manually as a test run before configuring it onto my live setup,
the issue I’m having is that kitchen tickets is not displayed under kitchen screen
Why would you want to combine Customer Tickets and Kitchen screen, the kitchen screen shows all tickets to be prepared. Combining Tables and Customers or another screen for Ready orders would be more helpful I think.
i am planning to have one tablet in kitchen which always show the kitchen screen.
if there’s some take away, i need some signal to our chef either by unread count on top of the customer ticket or just combined it with the kitchen entity to be in queue.
yea would be good if can combining tables and customers on another screen for ready orders as well would be great
When you close a ticket with new orders, the Ticket Status should change to Waiting. Check your Ticket Closing Rule.
It should have an Action to Update Ticket Status from New Orders to Waiting
Very good question. In theory we should be able to as we are only changing ticket and item states and using a Ticket lister widget with an Automation Command button.
Attached is a V3.0.34 database (SQL Express 2012) setup with Kitchen Display.
Setup V3.0.34 on a new system and copy over the database. You may need to stop SQL Server (SAMBAPOS) in services.msc to copy the database into C:\Program Files\Microsoft SQL Server\MSSQL11.SAMBAPOS\MSSQL\DATA folder.
@JohnS, I am implementing in training mode “kitchen display”. Is there any simple way to show in “Pizzaria” pizzarias´s orders and in “Restaurante” restaurante´s orders?
So far I can see both orders in boths entities screens…