If you really want to automate this in that detail you should setup a kitchen screen and mark orders as preparing & served.
When you know which orders are still preparing in kitchen you can notify kitchen for table changes (not only for merge). You’ll only notify orders that has preparing state.
Ticket merging function is useful at payment stage. While customers sitting on table you shouldn’t merge tables as people may want to pay their own tickets. If all tickets gets paid at once you can merge tickets.
this action should be called when we press merge tickets,
but there is no merge ticket automation command as it is built in
so in which event should i call the action
as @emre stated merging is useful for payment only so i was thinking that whats the point of adding two tickets people. This will in return effect the total number of people in reports.
so i thought of just adding another ticket tag similar to people. i approached this way but its not working.
@madiha you should recall settings with {:SETTING} tag. @Jesse nested tags as {:{TICKET NO}} to benefit from a feature that allows you to name settings with ticket printing tags. For your case {OrdNO} tag resolves to nothing so it tries to access to a setting named nothing.
