This article covers simple processing of kitchen tickets for items that are all the same course. If you serve food in courses see Processing kitchen orders with courses.
Every kitchen order will go through the following statuses: New > In Progress > Ready > Collected (removed from the view). Each status is indicated by a different colour header and a progress bar with the current status highlighted.
If you don't require your orders to go through the above statuses, you can enable orders to clear in one press. This will set the order to collected as soon as you press it once.
Note: If you do want tickets to go through the statuses, but have the occasional ticket you would like to clear, you can press and hold on the next button, which will automatically mark it as collected.
1. New
A new order is indicated by an orange header with the first step of the status bar (order pad icon) highlighted .
2. In progress
When a user presses the arrow in the top right of a new ticket, it will move to in progress. The header will change to purple and the second step of the status bar will be highlighted to indicate the order is being prepared.
3. Ready
Once an order has been prepared the user will press the arrow in the top right of the ticket again, which sets the order to Ready. This sends a message to the EPOS iPads so the front of house staff can see that a food order is ready to be taken to the table.
4. Collected
When an order has been collected to be taken to a table, the user will press the arrow in the top right of the ticket again to mark the order as collected. The ticket will disappear from the view, but will still be available to view under the complete orders tab at the top of the screen.
If you serve dishes as they are ready, you can mark individual items as away on the kitchen screen. To do this just press on the item and press Mark as Away.
Any items you have marked away will display with a strike through them & the header will change to yellow.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article