Kitchen Receipt Templates
Kitchens with several cook stations need the ability to see what one another is doing so the meal is prepared on time, when not using a KDS
Below is the way Oracle Res 3700 and Simphony operate.
In this example the kitchen as 3 printers and 3 cook stations
Cook Station w/Printer 1 cold food
Cook Station w/Printer 2 Proteins
Cook Station w/Printer 3 Pasta, rice, fryer, baked food
Order
Filet with House Salad and baked potato
Cook Station 1
House Salad (Colored Black)
Filet (Colored Red)
Baked Potato (Colored Red)
Cook Station 2
Filet (Colored Black)
House Salad (Colored Red)
Baked Potato (Colored Red)
Cook Station 3
Baked Potato (Colored Black)
House Salad (Colored Red)
Filet (Colored Red)
This is the layout that Oracle has used for years helps a busy kitchen run extremely efficient.
I have all my current customers asking for this as the staff is used to it this way and lost sales due to this lack on function.
Customer support service by UserEcho
We have a total of 15 very high-volume Italian/pizza bar-restaurants with an average of 8 workstations per unit. We have just completed our first store conversion to Linga, but have some reservations.
Linga's Android system DOES have two sections of the ticket they have called "ORDER SUMMARY" (station-specific items only) and "ITEM SUMMARY" (all ticket items w/o modifiers). The problem is: 1) ITEM SUMMARY items will repeat the items already listed within the ORDER SUMMARY. 2) the kitchen tickets ITEM SUMMARY also includes things that are totally irrelevant, like drinks that may be otherwise directed to the remote bar service well printers.
The simple solution is create a logic that will not allow any items from the ORDER SUMMARY to be duplicated within the ITEM SUMMARY.
The better solution would have been to never create that funky system in the first place, and do what every other POS does... get rid of the sections and have station-specific items in bold w/ mods, the rest of the items regular font w/o mods.