What would be the best way to let the kitchen know that a starter is to come with the main course. At the moment i have a grouped all my products so that i can control which order they are printed and the heading (Starter, Main etc).
Is there any way to select a starter and then press a button which would change the product tag from Starter to Main so that it is printed in the mains section?
Thanks
Yes this is doable, I have done this on mine, show how you are setting the grouping at the moment?
Its similar to my setup by looks of it,
You would need a automation command button mapped to order level.
That will have an update order state action in in.
How you select a state is up to you, you could use the automation command values list of the command/button, use an ask question and follow with a second rule (which is what I have).
You could have several buttons to have change to starter, change to main etc buttons.
The key bit is your updating the order course state.
[LAYOUT]
<div style="Family-weight:bold;font-size:20px">
<L00>Date:{TICKET DATE}
<L00>Time:{TIME}
<L00>
<EB>
<C24>Table:{ENTITY NAME:Table}
<L00>
<L01>Persons:{TICKET TAG:No. Of Customers}
<L00>Ticket No:{TICKET NO}
<EB>
{ORDERS}
<L01>
<L01> NOTE: {NOTE}
<L01>
<L01>
<L01>
<L01>
[ORDERS]
<J01>{QUANTITY} {ITEM TAG:KitchenName} {PORTION:- }
{ORDER TAGS}
[ORDERS:PRODUCT TAG:Kitchen Group=Drink]
-- do not print drinks
[ORDERS GROUP|PRODUCT TAG:Kitchen Group:Menu,Appetiser,Starter,Main,Sides,Rice,Nan,Sundries]
<L00>
<C12> {GROUP KEY}
<F>=
<L00>
[ORDERS GROUP|PRODUCT TAG:Kitchen Group:Drinks]
-- do not print drinks key
[ITEM TAG:KitchenName:Drinks]
-- do not print Drinks orders
[ORDER TAGS]
-- Format for order tags
<J00> {ORDER TAG NAME}
[ORDERS:Void]
-- do not print voided orders
{ORDER TAGS}
<L01>{NOTE}
<BEEP>
<B33>
Currently the products are grouped by Product Tag:Kitchen Group
is this what you wanted to see @JTRTech ?
Oh, ok, the linked topic refereed to order states…
You cant change product tag order by order.
You will need to group by state of kitchen course.
Set the course state on an order added rule and then setup the button/rule to change the state.
Ok I think i will have to attempt this another night. Will this mean that when i send the order to print it should show the following:
–Starters–
1 Starter
1.Starter
–Mains–
1 Main
1 Main
1 Starter (this being the starter moved from starters section)
–Side–
etc?
Yer, thats how mine works.
You will need to use something like order state KitchenCourse=Starter to allow the course to be set on each order because {ITEM TAG:x} cannot be changed on a per order basis like what you need.
So you template grouping will need to group by order state KitchenCourse rather than product tag.
Ok ive had a look at the link above and the courses2.zip.
This seems to need you to select all starters and then the course. is there any way to have it so that whenever i select a starter, it automatically becomes a starter course unless i specifically want to change it to a main course?
Also i dont need the courses screen so do i just deactivate it in the entity screen?
I’ve not installed that config file.
Mine uses item tag also but an order added rule to set a state on adding.
If you follow my sugestion that’s what I’ve been explaining how to do.
Ok im gonna need some help doing this.
I first create the states eg Starter, Mains, Desserts
Then have the order added rule to set the state on adding (can you show me an example of this)
I think i got it, im using the above file and there is a product tag which is default course which needs me to specify the kind of course a product is. This seems to automatically set the dish to a certain course.
So i have managed to get the states working and am now working on getting a print template. I have the following at the moment:
[LAYOUT]
<div style="Family-weight:bold;font-size:20px">
<L00>Date:{TICKET DATE}
<L00>Time:{TIME}
<L00>
<EB>
<C24>Table:{ENTITY NAME:Table}
<L00>
<L01>Persons:{TICKET TAG:No. Of Customers}
<L00>Ticket No:{TICKET NO}
<EB>
{ORDERS}
<L01>
<L01> NOTE: {NOTE}
<L01>
<L01>
<L01>
<L01>
[ORDERS]
[ORDERS GROUP|ORDER STATE:Course]
<L00>
<C12> {GROUP KEY}
<F>=
<L00>
[ORDERS:Starter]
- {QUANTITY} {NAME}
{ORDER TAGS}
[ORDERS:Main]
<L01>{QUANTITY} {ITEM TAG:KitchenName} {PORTION:- }
{ORDER TAGS}
[ORDER TAGS]
-- Format for order tags
<J00> {ORDER TAG NAME}
[ORDERS:Void]
-- do not print voided orders
{ORDER TAGS}
<L01>{NOTE}
<BEEP>
<B33>
I have got side dishes which need to go on the order so what is the best way to get these added on? do i create a new Order state for sides or do i define the sides as mains. How would i sort these to get them in the correct order?
I curently use the following on my current template:
[ORDERS GROUP|PRODUCT TAG:Kitchen Group:Menu,Appetiser,Starter,Main,Sides,Rice,Nan,Sundries]
<L00>
<C12> {GROUP KEY}
<F>=
<L00>
would it work if i added this to the above template?
You would translate course item tag to a state with a rule like this;
This is the course button;
And this is the action which updates;
What would the action for Generic Update Order State look like?
would i use the above action?
NO, do not mess with the Status state what ever you do, youll propper mess things up if you having to ask 
I just have most actions as full [:] fields but state name and state would be the ones needed in this use.
Thank you @JTRTech, i have got this to work.
Just a quick question, What do the [:] fields do?
Thanks for your help once again
[:xxxx] in the action settings allow that field to be ‘carried’ to the rule where the action is used.
I use allot of generic actions which I reuse again and again in many rules rather than have lots of actions.
I prefer it this way as you can see the values/expressions being set in the rule without having to go back to action and updating them is easier - also debugging is allot easier when you get stuck as everything is in front of you 
Ok I have got everything working regarding the courses but im having problems with the kitchen printout.
[LAYOUT]
<div style="Family-weight:bold;font-size:20px">
<L00>Date:{TICKET DATE}
<L00>Time:{TIME}
<L00>
<EB>
<C24>Table:{ENTITY NAME:Table}
<L00>
<L01>Persons:{TICKET TAG:No. Of Customers}
<L00>Ticket No:{TICKET NO}
<EB>
{ORDERS}
<L01>
<L01> NOTE: {NOTE}
<L01>
<L01>
<L01>
<L01>
[ORDERS]
<J01>{QUANTITY} {ITEM TAG:KitchenName} {PORTION:- }
{ORDER TAGS}
[ORDERS GROUP|ORDER STATE:Kitchen Group:Appetiser,Starter,Main,Sides,Rice,Nan,Sundries]
<L00>
<C12> {GROUP KEY}
<F>=
[ORDERS GROUP|PRODUCT TAG:Kitchen Group:Drinks]
-- do not print drinks key
[ITEM TAG:KitchenName:Drinks]
-- do not print Drinks orders
[ORDER TAGS]
-- Format for order tags
<J00> {ORDER TAG NAME}
[ORDERS:Void]
-- do not print voided orders
{ORDER TAGS}
<L01>{NOTE}
<BEEP>
<B33>
The order tags are not printing and im getting the drinks printing onto the kitchen copy. Can someone take a look at this for me and tell me what im doing wrong? (im sure many things )