Has anyone ever tried to do Printing via Group Tags? Is that even a thing?
Example:
Same as any other products there are two Group Codes - Salads and Mains. Both of them go to the station 1 printer.
However, sometimes Salad is tagged as a Starter and ideally it should go to printer station 2. Because stations 2 makes sure all the starters are out way before mains.
After searching the internet, was unable to find a direct answer to your question. However, a poster on this form, @Shivan, posted something similar to your query.
The humanoid version of this poster can confirm the using Product Tags does work on his receipts.
</end computer voice>
Ai_Bob
Heavy emphasis on the A.
Little emphasis on the i.
At first I thought you were taking about Custom Product Tags, which you can easily use in print jobs in the Product Tag column (in the syntax TagName=TagValue, also allows comma separated lists of tags).
However what you are asking for is more to be able to print based on an Order State, as I would assume this is how you would store your group?
You won’t be able to filter at the print job, but you could filter what gets printed, and it may take some tweaking but you could in theory print the same thing to multiple printers then filter what should or should not print on each printer using order group [ORDERS GROUP|ORDER STATE:x] on the printer template
States would be the way to go id say.
I manage my print mapping completely via state based on a custom product tag.
So where products are printed is based on several custom tags ie; kitchen print, bar print, bar print into which any value is added, usually put ‘Y’.
On order added a state for each print type is set to true or false and then print job actions are set to filter to corasponding print state of true.
As such you would be able to overide printing or not using automation to change that print state, so if you change a main order from kitchen course main to starter as part of automation to update grouping onscreen and kitchen course state you can also update print states.
Yes, Group Tag purpose would be just for the staff to visualize what they are doing, and grouping in Starters or Mains or whatever.
I guess managing order states and running different print jobs depending on the order state is what I had in mind. But I didn’t really want to commit to that idea unless anyone pitches in something they attempted.