¶¶Òõ

The following describes the information fields that may be displayed in the header of kitchen tickets. The system administrator determines which fields are displayed.

The following describes the information fields that may be displayed in the footer of kitchen tickets. The system administrator determines which fields are displayed.

Order items may have parent/child relationships.

For example, a combo meal include a parent item (e.g. Hamburger) and its child items (e.g. French Fries and Beverage). Parent/child item relationships are identified on kitchen tickets by their visual representation.

The parent item is displayed in bold text. The child items are displayed in plain text indented below the parent item.

In some parent/child item relationships, the child items may have modifiers and/or have child items of their own.

The kitchen displays support an infinite number of parent/child item relationship levels. However, the visual representation of the hierarchy does not extend beyond five levels.

If an order's parent/child item relationships exceed five levels, then those items are visually represented as fifth-level items.

The system administrator may configure XKM to automatically combine identical order items on the kitchen ticket. This feature conserves space and makes orders easier to read.

The order items are consolidated on a single line with the quantity displayed to the left of the item name.

If the order item quantity is updated at the Ordering application, the quantity on the kitchen ticket changes color to alert the kitchen staff.

In store environments where orders are composed of multiple seats, trays or bags, order items are segmented accordingly on the kitchen ticket to facilitate the delivery of the order to the customer.

Each segment on the order is identified by one of the following heading names: Bag, SeatÌý´Ç°ùÌýTray. The order items for each segment are listed below this heading.

The segment name may differ based on the order destination. For example, the segment name for Dine In orders may be Tray, while the segment name for Carry Out orders may be Bag.

Order items may be specially ordered or modified at the Ordering application.

For example, a customer might order a Hamburger and request the Extra Pickles modifier.

Order item modifiers are identified on kitchen tickets by their visual representation. Similar to child items, modifiers are displayed indented below the related item.

Order items that are members of a particular item category may be highlighted in a unique color on the kitchen ticket.

This optional feature enables the kitchen staff to easily identify particular items on an order.

For example, any order items that are members of the Chicken Item Category are highlighted in orange.

When the order item list is too long to fit in the space provided on a single kitchen ticket, the order item list is continued on another ticket.

The new kitchen ticket may be displayed on the next row/column of the display if the current row/column is full.

When an order spans multiple kitchen tickets, the kitchen tickets appear with a jagged edge. The jagged edge indicates that the order items on the tickets are part of the same order.

Kitchen may be configured to separate order items on the kitchen display based on their respective course.

When an order is made up of different courses (e.g. Appetizer, Entree, Dessert), the order items for each course are displayed on separate kitchen tickets.

Each ticket is associated with the same order number and the respective course name is identified in the ticket header.

Ticket headers may be configured to appear in a unique color to help the kitchen staff quickly identify the respective course.

When certain conditions arise or specific events occur, the kitchen display generates an alert and displays an indicator to notify the kitchen staff.

The order taker at the Ordering application may add a message to an order with special instructions for the kitchen staff. The message may be related to the entire order or a particular order item.