Dine In or Takeaway Help

[Shivan]

When Take Away is selected, the TAKEAWAY tag and Order No tag is automatically put on the ticket.
When Dine In is selected, then they go to table entity screen, they choose a table, and only when a table is chosen, samba tags the ticket with Dine In.

So the order is defined by Ticket tags, which are previously defined either by Tables Entity or If there is not table entity, its automatically set to Take Away.

You can refer to the rules set to make this happen in my other post

How to remove a ticket tag when another is selected

Thanks QMcKay… I managed to get the ticket tags working. Except now when a table is selected, the Order No ticket tag still shows with Dine In tag. Order No tag shows when take away is pressed and Dine In tag is auto removed, but when table is selected, Order No is still showing even though in my rule it set to clear it. Here is my Dine In Rule [image] Here is my Take away rule [image] However, If only one Clear All Tags is put instead of 2, it only clears one of them, not both. If I put t…

[JTRTech]

Sorry, misread the question, you asking where to put print actions not the tag actions as already dont that.

The default event for kitchen printer is ‘Ticket Closing’

[Shivan]

So something like this?

Sorry i’m such a newbie when it comes to rules haha. I’m still learning a lot about how these rules work and how I can use them to set the system up exactly how either I or a client of mine wants it.

Thanks for bearing with me till now.

[JTRTech]

Your constraint is wrong.
Should be {TICKET TAG:<tag name>} Equals <tag value>

[Shivan]

like this?

[JTRTech]

If those are the tag name and values then should do the job.

You need to make sure these new rules are above/before the default closing rule as that changes states to submitted and print actions are looking to print new so if they fire after they wont do anything as there wont be any New orders.

[Shivan]

Alright I’m trying it now. I’ll keep you posted. Finally got one big part done, this is the second last part of the setup left. I’m excited

EDIT: One more question, if the kitchen doesn’t have an order to be printed, will it make any difference? Or will it only execute kitchen if there is an order for the kitchen within the DINE IN ticket(as an example)?

[Shivan]

Well, It works ! It prints according to Ticket tag, it’s awesome. Thanks to everyone for your support and patience dealing with my newbie brain. It has really helped me learn and understand samba a lot more now. I’m at the last milestone before I make minor tweaks to the setup I’ve put together. I can’t wait to finish it and show the results. It might look simple, but I found the setup could be ideal for many restaurants and fast food or coffee places or even bars and bistros that have diners and take away options. I’ll be open to suggestions. Can’t wait to share my work :).

Thanks again, it could not have been done without all your help.

[Wood_Stone]

Hi
sir iam trying the same approach but my button does not work can you please help or direct me to correct tutorial thanks

[Jesse]

@Wood_Stone

Ticket Tag - Simple Example for: Dine-In / To-GO

This is a simple implementation of a Ticket Tag that I use to toggle between “Dine-In” orders and “To-Go” orders. I prefer this method instead of separate Departments and Ticket Types, since it’s implementation is very easy to do and simple to observe. Operational Flow: [image] Tickets showing Ticket Tag: [image] Automation Command to toggle the Ticket Tag value: [image] Action to set the Ticket Tag value. In this example, the Ticket Tag is named “SG” (StayGo). [image] Action t…