This section will explore what terminals are, how they are made and how orders are routed in the system to arrive where you need them.
What are Terminals?
A terminal or a console is a staff-facing tablet that has been configured to receive orders and be able to send messages to guests. They generally have a fixed tab structure such as: orders, send message, management, terminal status and order count. From here the staff can see the incoming orders and process them.
Creating Terminals
To create a terminal, you will need to navigate to Tablets -> Terminals in the CMS and press 'Add'.
A new terminal page will open where you can name the terminal and edit its properties to adjust how it functions. You will need to change the 'Order Handling Method' to console.
You will also need to set the UI mode to the Console UI mode and not the UI mode that is used at the DPG level for guest-facing tablets.
Tick Printing Enabled and assign a message template category if required for the terminal you create.
What is a Route?
A route is a pathway that guides orders to an appropriate destination.
Routes can be assigned to DPGs, categoriesorindividual products depending on need.
Routes often navigate an order to a specific staff console, however, routes can also direct orders to email inboxes and directly into POS systems if an integration is present.
Routesteps
Each route will require at least one step. This determines where the order will go in this route. For example, a route could be created for F&B orders only and applied only to F&B products. This route may have a routestep to direct orders to a kitchen staff console.
Routes can hold multiple routesteps and thereby direct orders travelling along that route to go to multiple places. For example, you could create the first routestep for the order to go to 1 or multiple consoles, but have a second routestep present for orders to go to an email inbox. In this instance the order will navigate to both destinations but always the 1st routestep first.
Route Adjustments
Within each routestep you can determine whether the order will continue to the second routestep upon failure to reach the first step. Routes can also be completed if they successfully reach the first step meaning that the order would stop before needing to reach the second step.
Timeouts can also be set per routestep to ensure orders are noticed quickly if the order has become stuck somewhere along the route pathway.
Creating Routes
If you are looking to create a route, you will need to navigate to Company -> Routes in the CMS and press Add.
You will need to name your route and set the timeout period and press Save. Once saved the first routestep will appear. By clicking on it you can adjust the destination of the routestep and create other routesteps if necessary.
If you need any further guidance with routing, please reach out to Crave support for assistance.
Speak to Support
Connect with our support team to discuss any content or support requirements you may have.
