Ticket Destinations – Kitchen Routing

Ticket destinations control where orders are sent – to the right kitchen, bar or station. Manage them under Admin → Bongning (Ticket routing).

What is a ticket destination?

• A logical place where tickets are sent (e.g. "Kitchen", "Bar", "Dessert")
• Linked to a device (KDS screen or ticket printer)
• Menu items are assigned to the right destination

Create a ticket destination:

1. Go to Admin → Bongning (Ticket routing)
2. Click Add destination
3. Fill in:
   • Name (e.g. "Kitchen", "Bar", "Dessert")
   • Type – KDS (digital screen) or Printer (physical ticket)
   • Device – Which KDS screen or printer receives tickets
4. Click Create

Per-station settings of its own: Under Redigera (edit) on a destination there are three settings that concern courses. All three inherit the restaurant default unless you set something of your own.

With Hel beställning vid första framningen, the station receives its own items on the tab's first fire ticket: the selected course marked FRAM (FIRE), the others VÄNTAR (WAITING). Later firings show only the course being fired. A station with waiting courses only receives the information without a FIRE command. Rows held with Vänta are excluded.

Bara vid framning cannot be combined with Bara FRAM + rättnamn + bord on the same station – the station would never see what to cook. The POS refuses to save and tells you why.

Two things worth knowing: the notification list shows printer destinations only – a KDS station sees the course status in real time anyway. And a station cannot notify itself; the database refuses.

Types of ticket destinations:

Assign menu items to destinations:

1. Open a menu item under Menu → Products
2. Select Ticket destination in the dropdown
3. Save the item

Default per menu group: Under Meny → Menygrupper (menu groups) each group can have a Bongdestination för nya artiklar (ticket destination for new items, the pencil on the group). New products in the group and its submenus get it filled in, so you don't have to choose each time. Existing products don't change, and the product's own choice always takes precedence over the group's.

You can also ask AI Boss, for example "Everything under Food should go to the kitchen, including what we add later". AI Boss then links the products in the group and its submenus to Kitchen and sets the group's default. If a submenu has a default of its own it stays, and AI Boss tells you.

Example setup:

How it works:

1. Staff places an order with pasta and a cocktail
2. The pasta is sent to "Kitchen" (KDS screen)
3. The cocktail is sent to "Bar" (ticket printer)
4. Each station receives its items. If you switch on Visa andra stationers artiklar på bongen (show other stations' items on the ticket) for a destination, its tickets get a footnote listing the items on the tab that have been sent to other stations, as a reference. The footnote's heading is set in the ticket template. Below the switch, under Ta med artiklar från (include items from), you choose which stations the footnote includes, for example the kitchen and the pizza station but not the bar. With all of them ticked, stations you add later are included too

Tips:

• Assign a destination to every item that needs sending to kitchen or bar. Unrouted items can be skipped; the POS can be configured to ask staff for a destination when sending manually
• An item can only have one ticket destination
• Test by placing a test order and verifying the ticket arrives at the right place