RayL
August 11, 2014, 8:29pm
1
When I close ticket after voiding a item it sends the kitchen the order again without item saying voided. So kitchen thinks its a new order. I need it to print voided items to the kitchen. below is my template
<EB>
[LAYOUT]
<T>Ticket
<L00>Date:{TICKET DATE}
<L00>Time:{TIME}
<L00>Table:{ENTITY NAME:Table}
<L00>Ticket No:{TICKET NO}
<T>
{ORDERS}
[ORDERS]
<L00>- {QUANTITY} {ITEM TAG}
{ORDER TAGS}
[ORDERS:VOID]
<L00>- {QUANTITY} {ITEM TAG}|**Void**
{ORDER TAGS}
[ORDER TAGS]
-- format for order tags
<L00> * {ORDER TAG NAME}
[LAYOUT]
<T>
<EC>
<L00>Ticket# {TICKET NO}
<L00>{TICKET DATE}
<L00>Table# {ENTITY NAME:Table}
<DC>
<T>
<DB>
Jesse
August 11, 2014, 10:01pm
2
You would need to update display state on pressing void button to read void instead of kitchen.
RayL
August 13, 2014, 12:40am
4
ok I’m gonna try explain this the best i can since i’m new to sambapos. When order is submitted, the kitchen printer prints the ticket(Kitchen printer template). The problems becomes if something needs voided off the already submitted ticket. If item on the order becomes voided its sends the ticket again but don’t say voided but my templates above i thought accounts for the voided item. I hope that explains my situation a little better.
thanks
Ray
QMcKay
August 13, 2014, 1:06am
5
I understand what you’re saying. I don’t see why it wouldn’t work. Curious though, why are you using {ITEM TAG}
instead of {NAME}
?
[ORDERS:VOID]
<J00>{QUANTITY} {NAME}|***VOID***
{ORDER TAGS}
RayL
August 13, 2014, 1:07am
6
kitchen don’t know english so using item tag to print in spanish to the kitchen.
QMcKay
August 13, 2014, 1:10am
7
Interesting… it isn’t working for me either.
RayL
August 13, 2014, 1:16am
8
I hate to say this but i sort glad that i’m not the only one. Maybe someone else will chime in a let me know what i’m doing wrong.
QMcKay
August 13, 2014, 1:18am
9
In fact, neither of these are working…
[ORDERS:GIFT]
<J00>{QUANTITY} {NAME}|**FREE**
{ORDER TAGS}
[ORDERS:VOID]
<J00>{QUANTITY} {NAME}|**VOID**
{ORDER TAGS}
1 Like
RayL
August 13, 2014, 1:21am
10
its got to be something i’m doing wrong. I can’t imagine that voided a item to the kitchen not working wouldn’t have been noticed before today.
emre
August 13, 2014, 1:24am
11
Order tags Order States are case sensitive. Is it configured as VOID
or Void
?
1 Like
QMcKay
August 13, 2014, 1:27am
12
That’s it @emre … these now work:
[ORDERS:Gift]
<J00>{QUANTITY} {NAME}|**FREE**
{ORDER TAGS}
[ORDERS:Void]
<J00>{QUANTITY} {NAME}|**VOID**
{ORDER TAGS}
1 Like
RayL
August 13, 2014, 1:29am
13
i posted my template at the very top emre. When you say order tag are you meaning were it says [ORDERS:VOID]? I’m trying to figured all the terminology ya’ll use. I’m a programmer by trade so i think i can catch on pretty quick.
emre
August 13, 2014, 1:30am
14
Sorry I’ve meant Order State. You can find more info about order states here
###What is a State?
State is a general SambaPOS feature that defines operational properties of things. SambaPOS have three different types of states.
Entity State
Ticket State
Order State
###Updating States
We change state of things by using these actions.
Update Entity State
Update Ticket State
Update Order State
There is no need to define states somewhere. State changing actions accepts any values. If you define states under Management > Settings > States you’ll be able to define color…
… and order tags here
You can use Order Tags to define modifiers for menu items. With SambaPOS V4 you can define global, product group based or product based order tags. Let’s see how it works.
I’ll start by defining Global Modifiers. They will work for all products in my menu. Navigate to Management > Tickets > Order Tags and Add a new order tag group.
[image]
Just give a name to Order Tag Group here. We’ll see other settings on next topic.
Switch to Order Tags page to add your modifiers.
[image]
… and add …
QMcKay
August 13, 2014, 1:33am
15
@RayL , I simply changed [ORDERS:VOID]
to [ORDERS:Void]
in my Kitchen Template.
@emre , is this the Rule we need to match? This is a State, not a Tag.
emre
August 13, 2014, 1:36am
16
Yes. Sorry it is 4.35 AM here. Iol
emre
August 13, 2014, 1:43am
17
… also not required but configuring states will be a good habit for future reference. Auto complete will work on rules and you’ll have some control on how it displays to users on reports and on tickets. For example you can hide states on ticket that we use for implementing promotions, coupons, … etc from non-admin users.
QMcKay
August 13, 2014, 1:52am
18
Dude, go to bed! Have a good sleep and rest well!
hi how can i print all line after void item ,like your ticket
hi how can i print all line after void item ,if i voided print only void item
QMcKay
August 16, 2014, 3:34pm
21
You would need to create a special Printer Template to print only voided items.
Create a new Printer Template (or clone a working one).
Here is a "normal " Kitchen Order Template:
[LAYOUT]
<T>ORDER
<J00>{TICKET DATE} {TICKET TIME}| #{TICKET NO}
{ENTITIES}
<F>-
{ORDERS}
[ORDERS]
<J00>{QUANTITY} {NAME}|{PRICE}
{ORDER TAGS}
[ORDERS:Gift]
<J00>{QUANTITY} {NAME}|**FREE**
{ORDER TAGS}
[ORDERS:Void]
<J00>{QUANTITY} {NAME}|**VOID**
{ORDER TAGS}
[ORDER TAGS]
<L00> {ORDER TAG QUANTITY} {ORDER TAG NAME}
[ENTITIES:Table]
<L00>Table: {ENTITY NAME}
[ENTITIES:Customer]
<J00>Customer: {ENTITY NAME}
Now remove the elements that you don’t want to appear on the print-out, something like:
[LAYOUT]
<T>ORDER
<J00>{TICKET DATE} {TICKET TIME}| #{TICKET NO}
{ENTITIES}
<F>-
{ORDERS}
[ORDERS]
-- do not print normal orders
[ORDERS:Gift]
-- do not print Gift orders
[ORDERS:Void]
<J00>{QUANTITY} {NAME}|**VOID**
{ORDER TAGS}
[ORDER TAGS]
<L00> {ORDER TAG QUANTITY} {ORDER TAG NAME}
[ENTITIES:Table]
<L00>Table: {ENTITY NAME}
[ENTITIES:Customer]
<J00>Customer: {ENTITY NAME}
Then you need to:
Create a Print Job
that uses your new Template.
Create an Automation Command
(button) to use to execute the Print Job, and map it to the Ticket so it is visible.
Create an Action of type Execute Print Job
, and select the Print Job
that you defined above.
Create a Rule to capture Automation Command Executed
, and add the Action that you defined above.