Automatic Print from Hold
Objectives
Set up automatic printing based on items placed on hold.
Prerequisites
Print server or exclusive use of kitchen display systems at community
Access to back office application
Instructions
Overview
This functionality allows communities to place items on hold and have them sent to the kitchen automatically based on a time set on the item level or based on the minimum time of all items.
Please note: Community must have a print server or exclusively use kitchen display systems for this functionality to work
Back Office Set-Up
Touchscreen Workflow
Determining Hold Until Date
Use Item Time
Any order items on hold will be checked to see if they have ‘Automatic Print From Hold’ set to ‘Enabled’. If any order items are found, a hold until date is populated on the order item based on the ‘Number of Minutes to Hold’ populated on the item.
Use Minimum Order Time
Any order items on hold will be checked to see if they have ‘Automatic Print From Hold’ set to ‘Enabled’. If any order items are found, the system will first check to see if any items on the order with a hold until date were already sent to a printer. If order items were previously sent, the system will set the hold until date as the current date/time for all eligible order items so the order items will print the next time the scheduled job runs.
If no order items with a hold until date have been sent to a printer, the system will determine a base send time and the minimum hold time to calculate the new hold until date.
If there are order items which currently have a hold until date set, the base send time will be set to the minimum of hold until date - hold time. For example, if existing order items have a hold until date of 12:05 and the items have hold times of 5, 8, and 10 minutes, the system will set the base send time to 12:00 (5 minutes before 12:05).
If there are no items with a hold until date set, the system will check if there are any items for the order that have been sent. If there are order items that have been sent, the system will set the base send time to the maximum successful print time. If no order items have been sent, the base send time will be set to the current date/time.
The minimum hold time will be the minimum item ‘Number of Minutes to Hold’ for all items on hold where ‘Automatic Print From Hold’ is enabled. For example, if items associated with the order have hold times of 5, 8, and 10 minutes, the minimum hold time will be 5 minutes.
All eligible order items will have their hold until date set to the base send time plus the minimum hold time.
Use Minimum Hold Time Examples
Scenario A
|
Step ID |
User Action |
System Action |
|
Summary: Entire order is entered in one POS session. All Main Course items’ prep time is less than the Pre-Main Course order to Main-Course delivery desired duration (therefore the sending of Main Course items should be delayed). Result: Pre-Main Course items sent right away. Main Course items automatically sent after delay. |
||
|
12:30 |
Server receives Pre-Main Course and Main Course order at table-side. Main Course items ordered include:
|
None |
|
12:34 |
Server enters all items into POS, puts Main Course items on hold and then touches “Send” (at 12:34pm). |
Requisition is sent for items that weren’t put on hold. Items that were put on hold are queued to be sent 8 minutes later (12:42pm).
Requisition does NOT show the Main Course items. |
|
12:42 |
None |
At 12:42pm, Items that were put on hold and queued are taken off hold and sent.
Requisition does NOT show previously requisitioned items (can be configured differently if desired). |
Scenario B
|
Step ID |
User Action |
System Action |
|
Summary: Entire order is entered in one POS session. Some Main Course items’ prep time is less than the Pre-Main Course order to Main Course delivery desired duration and some Main Course items’ prep time is more (therefore the sending of Main Course items should NOT be delayed) Result: Pre-Main Course and Main Course items sent right away but on two separate requisitions. |
||
|
12:30 |
Server receives Pre-Main Course and Main Course order at table-side. Main Course items ordered include:
|
None |
|
12:34 |
Server enters all items into POS, puts Main Course items on hold and then touches “Send” (at 12:34pm). |
Requisition is sent for items that weren’t put on hold. Items that were put on hold are queued to be sent 0 minutes later (12:34pm).
Requisition does NOT show the Main Course items. |
|
12:34 |
None |
At 12:34pm, Items that were put on hold and queued are taken off hold and sent.
Requisition does NOT show previously requisitioned items. |
Scenario C
|
Step ID |
User Action |
System Action |
|
Summary: Subsequent Send events. Result: See the “System Action” column |
||
|
12:00 |
|
Main Course items queued for 12:15 |
|
12:01 |
|
No change – Main Course items still queued for 12:15 |
|
12:02 |
|
Previous Main Course items still queued for 12:15. New Main Course item on indefinite hold. |
|
12:03 |
|
All Main Course items now queued for 12:15. Note: this demonstrates that a Main Course item configured for delayed send can’t be placed and kept on indefinite hold if subsequent Send is required. |
|
12:04 |
|
No change – Main Course items still queued for 12:15 |
|
12:05 |
|
Previous Main Course items still queued for 12:15. New Main Course item on indefinite hold. |
|
12:07 |
|
All Main Course items now queued for 12:09 (9 minutes after the order’s initial Send time) |
|
12:09 |
NOTHING |
All Main Course items are sent. |
|
12:10 |
|
New Main Couse item is sent. |