I know there are thousands of ways to do the same thing with samba, which is one of the reasons why I love this program so much. (The possibilities are literally endless) But here is my idea of how I am wanting to implement a To-Go Feature into our already beautifully running program… We have 3 Entity Pages, One that has a map of our bar, one that has a map of our main dining area, and the other is a map of our patio. I want to add in another entity page, which Im quite familiar with how to do, this is where I get stuck though… This entity/entity page I will be creating will only be for To-Go Orders and so I want it to automatically say
To-Go on this kitchen tickets, same way it says table number but instead it says to go. that way we dont have to use up another table and we dont have to keep putting it as a ticket note. Is this possible or can you think of a better way?
How do you curently define to-go? Have you chosen to use say ticket type, department, tag etc? Just to know what your already have.
As for the entity screen, what kind of details do you take for to-go? Were you thinking to use customer entities or just a ticket tag for name?
If not using entities or saying that either way a ticket list widget filtered to Togo tag or something might work well.
They call in their order, pick it up and take it home. 
If you mean how do we do it in the computer, we just use a regular entity (usually one of the patio or unused bar seats) and we use a ticket note to indicate that it is a to go order.
We dont need the customers name or information We write that stuff down with pen and paper, We just need a quick way to tell the kitchen that the order will be to go. Since our kitchen printer displays the entity number/name I figured we could create a To-Go Entity that would replace table # on ticket with To-Go but our options are endless here. Ticket Tag may work as well, if you’ll shed light on how that works. Like I said we just need a good way to tell the cook to box up the order instead of putting it on a plate. Understand?
A very basic option would be a single to-go entity of table type.
Do they pay at time of ordering then?
Depending on the size of the order, 9 times out of 10 though they pay when they pick up and on busy nights we may have 3 or 4 to go orders at once so we would likely put 5 entities on this one page to be sure there is enough. As long as the printer will indicate that its “To-Go” in place of the table number. We may just create some extra entities and add in a ticket tag linked to an automation instead if there is a way to do that. I’m going to give my boss the option and see which one He likes better.
You could be bit more creative but that would certainly work.
You can have multiple tickets on one entity FYI which is why I said about tag for name then the 5 tickets would be listed under entity with tag on each,
But guessing you have select entity as ticket creation method so would either select to go and add ticket or could make a custom entity screen and add a button to it to create a new ticket which prompts for customer name which is used for tag.
Oh wow I definitely like the sound of that. I wasn’t thinking of something that complicated but it would definitely work. So how would we go about doing this? Start out with creating a new entity screen for to go orders but what comes next? I have not even explored this part of samba yet beyond creating the entity screens and entities for different sections of the restaurant.
I use simple ticket tags for it.