Show the Settings of the Printer …
Show the Settings of the Task Editor Widget …
It would be easiest if you simply deleted all of the KD setup elements:
Then import the DB Tools file from my previous post. It contains all of the above elements, pre-configured.
Then verify the Print Job Mappings.
I just did exactly as above, and it works.
Yuppppyyyyyyyyyyyyyyyyyyyyy…
I get through 
@QMcKay
But One thing my kitchen display is scattered, see if you could help…
You cannot use the same Printer Template that you would use for printing Orders on a Printer to Paper (ie. a Ticket Printer).
Printing on Paper (Ticket Printer) and Printing to a Task Editor Widget (Task Printer) are different. They are not compatible. The Task Printer does not understand the Tags (ie. <L00>) like a Ticket printer does.
You need to use a Template like is included in the DB Tools file, specifically something like this:
[LAYOUT]
{ORDERS}
[ORDERS]
++{ORDER DATE} {ORDER TIME} {ENTITY NAME:Table} {ENTITY NAME:Customer}
(Id={NAME}-{ORDER UID})
(TID={TICKET ID})
(Color=#FF333333)
<bold>[=('{QUANTITY}'>1 ? ('{QUANTITY}'+' ').substr(0,2) : ' ')] {PRODUCT NAME}</bold>
[='{PORTION}'=='' ? '' : '<font Consolas> <color #FF55FF33><size 17><bold>{PORTION}</bold></size></color></font>']
{SORTED ORDER TAGS}
[ORDERS:Gift]
++{ORDER DATE} {ORDER TIME} {ENTITY NAME:Table} {ENTITY NAME:Customer}
(Id={NAME}-{ORDER UID})
(TID={TICKET ID})
(Color=#FF333333)
<bold>[=('{QUANTITY}'>1 ? ('{QUANTITY}'+' ').substr(0,2) : ' ')] {PRODUCT NAME}</bold>
[='{PORTION}'=='' ? '' : '<font Consolas> <color #FF55FF33><size 17><bold>{PORTION}</bold></size></color></font>']
{SORTED ORDER TAGS}
[ORDERS:Void]
++{ORDER TIME} {ENTITY NAME:Table} {ENTITY NAME:Customer}
(Id={NAME}-{ORDER UID})
(Color=#FF550000)
XXXXX VOID XXXXXXXXXXXXXXX
<bold>[=('{QUANTITY}'>1 ? ('{QUANTITY}'+' ').substr(0,2) : ' ')] {PRODUCT NAME}</bold>
[='{PORTION}'=='' ? '' : '<font Consolas> <color #FF55FF33><size 17><bold>{PORTION}</bold></size></color></font>']
{SORTED ORDER TAGS}
[SORTED ORDER TAGS:VIP Discount]
-- do not print
[SORTED ORDER TAGS:Happy Hour Discount]
-- do not print
[SORTED ORDER TAGS:Pizza Crust]
-- do not print
[SORTED ORDER TAGS:Pizza Sauces]
<size 14><color LightSalmon><font Consolas> [=('{ORDER TAG QUANTITY}'>1 ? {ORDER TAG QUANTITY} : ' ')] {ORDER TAG NAME}</font></color></size>
[SORTED ORDER TAGS:Pizza Meat]
<size 14><color #FFCCCCFF><font Consolas> [=('{ORDER TAG QUANTITY}'>1 ? {ORDER TAG QUANTITY} : ' ')] {ORDER TAG NAME}</font></color></size>
[SORTED ORDER TAGS:Pizza Veggies]
<size 14><color #FFCCFFCC><font Consolas> [=('{ORDER TAG QUANTITY}'>1 ? {ORDER TAG QUANTITY} : ' ')] {ORDER TAG NAME}</font></color></size>
[SORTED ORDER TAGS:Pizza Cheese]
<size 14><color Yellow><font Consolas> [=('{ORDER TAG QUANTITY}'>1 ? {ORDER TAG QUANTITY} : ' ')] {ORDER TAG NAME}</font></color></size>
[SORTED ORDER TAGS:Pizza EXTRAS Small]
<size 15><color #FF55FF55><font Consolas> [=('{ORDER TAG QUANTITY}'>1 ? {ORDER TAG QUANTITY} : ' ')] {ORDER TAG NAME}</font></color></size>
[SORTED ORDER TAGS:Pizza EXTRAS Medium Whole]
<size 15><color #FF55FF55><font Consolas> [=('{ORDER TAG QUANTITY}'>1 ? {ORDER TAG QUANTITY} : ' ')] {ORDER TAG NAME}</font></color></size>
[SORTED ORDER TAGS:Pizza EXTRAS Large Whole]
<size 15><color #FF55FF55><font Consolas> [=('{ORDER TAG QUANTITY}'>1 ? {ORDER TAG QUANTITY} : ' ')] {ORDER TAG NAME}</font></color></size>
[SORTED ORDER TAGS:Condiments]
<size 14><color #FFFFCCCC><font Consolas> [=('{ORDER TAG QUANTITY}'>1 ? {ORDER TAG QUANTITY} : ' ')] {ORDER TAG NAME}</font></color></size>
[SORTED ORDER TAGS:SideServings]
<size 14><color Orange><font Consolas> [=('{ORDER TAG QUANTITY}'>1 ? {ORDER TAG QUANTITY} : ' ')] [='{ORDER TAG NAME}'.replace('SIDE ','')]</font></color></size>
[SORTED ORDER TAGS GROUP|Sauteed,OTS,ADD,SIDE]
[SORTED ORDER TAGS GROUP:ADD]
<size 14><color LightSalmon> ~~~ ADDONS ~~~</color></size>
[SORTED ORDER TAGS GROUP:Sauteed]
<size 14><color LightSalmon> ~~~ SAUTEED ~~~</color></size>
[SORTED ORDER TAGS GROUP:OTS]
<size 14><color LightSalmon> ~~~ ON THE SIDE ~~~</color></size>
[SORTED ORDER TAGS GROUP:SIDE]
<size 14><color LightSalmon> ~~~ SIDES ~~~</color></size>
i used that one too check third and fourth bill from left hand side.
why its showing one order in two physical bills??
What do you mean? I don’t understand what you’re asking.
It is designed to show each Order individually. That means you submit 1,2,3,4,5 Orders on a Ticket and it creates a display that shows each of those Order individually on it’s own Task Card. That is the point of a Kitchen Display.
It is not designed to show an entire Ticket, because that is not helpful for a Kitchen Display. If you want to see entire Tickets with all the Orders on the Ticket, you have many options, like Ticket Lister, Ticket Explorer, Open a Ticket, etc.
See when i select 2 items like Pakora and chicken tikka masala from my categories in one ticket its showing in two different blocks. Why its not coming in one block as 1 order.
You don’t understand the point of the KD.
It is designed to show each Order in a different Task Card (block).
A Ticket is not an Order. Orders are the things you add to the Ticket like “Pakora” and “chicken tikka masala” … those are Orders on a Ticket.
The KD is doing exactly what it was designed to do… display Orders individually, not Tickets.
So how can we bring these two orders or how many items customer order in one ticket?
Q told you what you can use, if you dont want the orders on a ticket separating then do not use this KD tutorial
Wait, doesn’t we have task printer Group By feature? I believe I saw emre post it.
Ok I understand …
@QMcKay
Could u please tell me how to add a department name in a ticket like it’s a take away or dine in ticket. How to classify these two tickets?
Sorry about my English and I frustrated u…
Thanks alot
Heres a quicker way without using departments that Q has documented
No I want take away and dine in in seperate departments because in dine i have to apply taxes and take away is tax free.
Use the Forum Search function and start a new Topic for your questions.
You can still do that as one department using the ticket tag method and using different price definitions
So when the ticket tag is Dine In the dine in price lists are used and when To Go is selected then the to go price list is used istead
There are different ways to do what you want, i suggest searching the forum to see what else has already been documented that could help you
Hello @QMcKay
I’ve already done this setup a couple of times and almost ever it worked, but not now…
I have a problem with the order states when i make an order with 1 product all its working fine, but when i make an order with more of 1 from one product then the state is not updating from “FPrinting” to “FPrinted”…
And i have checked the rules and actions but not found an error…
but in the Kitchen Display it looks right …
I’am using now the beverages setup for food and that works…
I just came across this tutorial and downloaded the zip file to test. I imported the file into SQL, opened Sambapos to change the database connection and then opened the program. The Kitchen Display entity screen is there and all the rules, actions, printers, etc. are included per the tutorial but nothing happens when I close a ticket. By the way I also prefaced all the food items with Food. Any suggestions from anyone?