[ANDROID] KITCHEN TICKETS PRINTING - "Order Summary" vs "Item Summary"

Introduction: 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 9-station store conversion to Linga, but have some reservations.

Background:

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) to allow Line Cooks to see the full ticket for timing, but differentiate those items that they need to be cooking.

Problem:

1) The ITEM SUMMARY items will repeat the items already listed above within the ORDER SUMMARY causing confusion among line cooks mostly, but also utilizes 25% more paper or better. This is unacceptable for high-volume full service establishments where kitchen output is directly related to the efficiency of the line...being able to read tickets from a distance and clearly, quickly decipher next-steps is mission critical.

2) The kitchen tickets' ITEM SUMMARY also includes things that are totally irrelevant, like drinks that are also directed to the remote bar service well printers. Imagine what this looks like for a party of 6 or more with appetizers and entrees...the tickets are LONG and confuse cooks with unnecessary items.

Solution:

i. A simple solution is create a logic that will not allow any items from the ORDER SUMMARY to be duplicated within the ITEM SUMMARY. Additionally, certain categories should be able to be excluded; e.g. Beer, Wine, Liquor, etc.

ii. 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.

Conclusion:

EITHER of these proposed resolutions would be wonderful...whichever is faster, frankly! After 25 years in the business using Aloha, Squirrel, Toast, Micros, Rpower, SkyTab, Digital Dining, and Clover POS...frankly I was shocked to see this clunky of a solution from the founders of Benseron. It is, however, better than nothing.