Ok so which tutorial did you use? Custom percent one? Are you typing a percent and it is calculating it?
Try under your [ORDER TAGS]
{ORDER TAG NOTE}
[ORDER TAGS:Discount Custom Percent] is bad syntax it should just be [ORDER TAGS]
Ok so which tutorial did you use? Custom percent one? Are you typing a percent and it is calculating it?
Try under your [ORDER TAGS]
{ORDER TAG NOTE}
[ORDER TAGS:Discount Custom Percent] is bad syntax it should just be [ORDER TAGS]
i used @QMcKay tutorial
the thing is i am want to show the total price for the discounted amounts and total amount for rest
i have used order tag vlaue and orders:state but doesnt make a difference
if i use this how will it know to which order tag i am referring to ?
It doesnt have too. It will show all Order Tags. If they have a NOTE it will display it… if they dont it wont. Just add {ORDER TAG NOTE} to your regular [ORDER TAGS] format and put it where you want it showing up.
Maybe share your entire template I can help you.
this is what i am using:
27,33,32
Receipt No: {TICKET NO}
[ Table: {ENTITY NAME:Table}|Guest: {TICKET TAG:Guest}]
[ {TICKET TAG:SG}]
27,33,0
=
Date: {TICKET DATE}|Time: {TIME}
Cashier: {USER NAME}
{ENTITIES}
{NOTE}
=
QTY ITEM|TOTAL
=
{ORDERS}
=
[ Sub-Total:|${PLAIN TOTAL}]
{DISCOUNTS}
{SERVICES}
{TAXES}
[ Total Gift:|${ORDER STATE TOTAL:Gift}]
27,33,16
Total:|${TICKET TOTAL}
27,33,0
Amount Paid:|${TENDERED TOTAL}
[ Change Due:|${CHANGE TOTAL}]
=
{PAYMENTS}
[ CC Info: {TICKET TAG:CCtype} ({TICKET TAG:CCdigits})]
=
Thank You and Have a Nice Day!
[DISCOUNTS]
{CALCULATION NAME} %{CALCULATION AMOUNT}|${CALCULATION TOTAL}
[SERVICES]
{CALCULATION NAME}|${CALCULATION TOTAL}
[PAYMENTS]
Payment Mode:|{PAYMENT NAME}
[ORDERS]
– Default format for orders
{QUANTITY} {NAME}|${TOTAL AMOUNT}
{ORDER TAGS}
[ORDERS:Gift]
– Format for gifted orders
{QUANTITY} {NAME} GIFT
{ORDER TAGS}
[ORDERS:Void]
– Nothing will print for void lines
[ORDER TAGS:Value Meal]
– Format for order tags
* {ORDER TAG NAME}
[ORDER TAGS:Lunch Main Course]
– Format for order tags
* {ORDER TAG NAME} x {ORDER TAG QUANTITY}
[ORDER TAGS:Dinner Set]
– Format for order tags
* {ORDER TAG NAME} x {ORDER TAG QUANTITY}
[ORDER TAGS:Promo Discount]
* {ORDER TAG NAME}
[ORDER TAGS:Promo Drinks]
– Format for order tags
* {ORDER TAG NAME} x {ORDER TAG QUANTITY}
[ORDER TAGS:Dish Discount]
* {ORDER TAG NAME} | {ORDER TAG PRICE}
[ORDERS:Discount]
{QUANTITY} {NAME}|${TOTAL PRICE}
{ORDER TAG:Discount Custom Percent}
– [ORDER TAGS:Discount Custom Percent]
– {ORDER TAG NAME} {ORDER TAG NOTE:Discount Custom Percent}
[ORDERS:ExtraPrice]
{QUANTITY} {NAME}|${TOTAL PRICE}
* {ORDER TAG:Dinner Dessert}
[ENTITIES:Customer]
– Customer entity format
Customer: {ENTITY NAME}
Balance: $[=F(0-TN(‘{ENTITY Balance}’))
[ENTITIES:Layby]
– Customer entity format
Layby: {ENTITY NAME}
Balance: $[=F(0-TN(‘{ENTITY Balance}’))
[ENTITIES:Gift Certificate]
– Customer entity format
Gift Certificate: {ENTITY NAME}
Balance: $[=F(0-TN(‘{ENTITY Balance}’))
{ENTITY NAME}
Ok try
[ORDER TAGS:DIscount Custom Percent]
<J00> {ORDER TAG NAME} {ORDER TAG NOTE}
If you want something ommitted in an order tag unless it has a value then try this
[ORDER TAGS:DIscount Custom Percent]
<J00> {ORDER TAG NAME} | [{ORDER TAG NOTE}]
The ORDER TAG NOTE that is in brackets will only show if it holds value. you can not wrap the entire thing like you do on ticket. In format section you can wrap just the Tag. You also can only wrap one at a time.
PS I noticed you have no Justification set. Some tags do funky things if you dont.
EDIT: I was wrong about the bad syntax post above. I was reading too far ahead.
Actually rereading what you want this should work:
[ORDER TAGS:Discount Custom Percent]
<J00> {ORDER TAG NAME} {ORDER TAG NOTE} | {ORDER TAG PRICE}
Then if you want the order to show the actual amount after discount try this.
[ORDERS:Discount]
<J00> {QUANTITY} {NAME}|${TOTAL PRICE}
{ORDER TAGS}
<J00> |[{TOTAL AMOUNT}]
PS I noticed you have no Justification set. Some tags do funky things if you dont.
can show an example where to do justify so thtat i can improve thanks
The <J00>
is justification.
@kendash i have almost achieve my desired output thanku for ur support i have one more question.
i want to show only that order tag name that has a price like
order tag:oliva ori modifer
tag name: mushroom price 4
tag name: c price 0
would like to show mushroom only
[ORDER TAGS:Oliva Ori Modifiers]
{ORDER TAG NAME:Toppings Mushroom}
Well {ORDER TAG NAME:Toppings Mushroom} does not exist but {ORDER TAG NAME} does. I do not think you can filter the name but you can filter the Price.
ok thanks i also thought so
@Jesse today i found out one more thing
if i void the product with discounted price it will print in the receipt as i am showing the discounted states.
i think i will have to clear the state if item voided.
what do you say?
What do you mean by showing the state? States do not print on receipts.
OH I think I get what your saying. Yes if you void you should set it to clear the State. That makes sense. Void means it is no longer Discount and should have state cleared.
remember i am updating discount state value to discount if item discounted
so now if i put a discount on a product and later i void that product then on the receipt the voided product is showing with the discounted price and the subtotal is without that voided item
1 Insalata Caprese ($18.00) $12.60
**** DISCOUNTED 30.00% -----------------------------------(voided item)
@Jesse this is what i did this and its working
but i have one issue i am updating all the extra state to null whereas it should only null those state which were assign/updated…so the question what contraint i neeed yo put to know which state was active
Does it matter if it changes a state from nothing to nothing?
for time being it is not affecting anything
What I mean is it does not matter because if you did not have a state there… then updating that state to nothing means you still do not have a state
in that case its ok what if i cancel void then i have to update all the states wihtout knowing which state was active
You could store the State in a Program setting so if you cancel void it could read that setting. I mean store it when its first changed. So in the rule that adds/changes the state before you Voided it.. also ad an update Program Setting action and let it store that state for that ticket. Then if you ever cancel void it can read that setting to restore the states.
EDIT: Actually it should be stored on Ticket Closed so it can read the Ticket ID.