Must need new glasses as I can’t seem to figure out how to do this, but i’m sure it’s in SambaPOS by default!
Scenario:
Customer A comes in and sits on Table 1, orders food but wants to wait for customer B to arrive before service.
Customer B arrives and orders her food on the same Table.
Therefore 2 tickets would have printed overall, one for customer A and one for customer B both on table 1.
At the moment i’m getting around this by:
Adding customer A to table 1
then when customer B arrives, i put him on table 2, then click merge tables to table 1, which then produces 2 tickets for table 1.
I’m sure there must be a more straightforward way…Add Ticket does create a new ticket, but it does not retain the table number for some reason.
(I understand there are other ways, such as the advanced split payments @Jesse , but I wanted to try both ways and see what works for my situation).
If you start with a new ticket adding an order before selecting table 1.
If you already have a ticket before selecting table one it will keep the tickets separate.
If you select the table first it will open either the single ticket or if you already have multiple obviously the ticket list.
Start customer B’s ticket before selecting table 1 and it will go on as second ticket straight away.
That’s what I thought, attached a gif below of what is happening. Won’t automatically retain the table, have to manually select table 2 in this case.
Looked at rules, but couldn’t find any for “Add Ticket”.
I assume something else in my setup is conflicting it?
Restored default database and as you all said it works. So I assume i’ve definitely changed a rule somewhere, but don’t know which!
Same is also happening with “Move Ticket”, it creates a new ticket, but not under any table whatsoever. Have to then manually click “select table”.
I checked every rule one by one in comparison (one using the default database, and the other via teamviewer on my system). Couldn’t see any obvious differences to default rules or any rules missing.
Screenshots attached of ticket created and entity selected/updated. Regards.
2nd screenshot has error…highlighted ticket closing rule…in fact it is showing ticket created.
Hmm still can’t seem to find it. Not quite sure how “add ticket” works and where the rules are for it.
Will have to try and rebuild the setup again and see step by step when the add ticket stops working.
