Limiting print bill function for the Waiters

I know this question has been raised before in the forum but after a thorough search, there is no defined approach on how to handle this.
I want to limit the number of times my waiters can print the same bill, I have realised that my waiters are reprinting the bills and using them on innocent customers. I want to limit the waiters to only print the bill once after posting the orders or after adding more items on the ticket, if the waiter drops the bill or misplaces the bill, the supervisor on the ground can reprint the same bill for the waiter.
I have tried to use the ticket lock function but my crafty waiters are able to manoeuvre around this and always have a way to reprint a bill.

Isnt this the point of the lock bill feature?
Just remove their ability to unlock bill.

and review the relation of the print automation command.

That is what i had practically done,but my waiters are crafty.Whenever you print the bill the print bill button “grey out” meaning for you to use it again you have to unlock the ticket,so i had have disabled unlock the ticket button. So what happens is the waiter will add an item on the said ticket and cancel the same item before submitting,this makes the print bill button to appear highlighted hence he can now reprint the same bill.
Hopes you understand,pardon me for my poor grammar

Guess you mean that i should change enabled states and visible states in my automation command.Let me try this and will let you know

i have tried this,i changed the states as you have indicated but still i can reprint the the same bill.

Tag the ticket in print bill rule and add a constraint on the rule too to not fire is the tag is not empty.

You would need to then create a way to either remote the tag or another print bill button without constraint but say set button to confirm admin pin so the copy can only be printed or tag removed by manager.
Or map button by user role. Whichever you prefer.

You could use a State Flow for printing. Create a ticket state called Not Printed and one called Printed. If ticket is in state Printed it can be constrained to not allow print.

I tell you step by step …

Create this actions and rules ;

First create a Ticket Tag

Then add an action

image

and

image

Then add these rules

Last step, edit your default Print Bill rule and add Custom Constraint Line

image

And try reprint the any ticket …

image

2 Likes

Thank you for your time, I have really followed what you have done, it seems to work but let me ask you something about the last rule, that is the default print bill rule.
By any chance, am I supposed to edit the actions called by the rule, you haven’t indicated how the new constraint will affect the initial actions!

hi sir,can you kindly demonstrate this,i will really appreciate

No any other changes, just add the relevant line.

1 Like

Personally I wouldn’t employ someone I knew was on the scam but each to their own I guess.

Thank you all for your much needed support this have really worked for me serhatoglu. The only difference is my set up is not displaying that final message on the screen however am capable of restricting the waiters from printing the bills at will,i guess this will also save us on the cost of buying thermal paper rolls

Try to change execute rule if: Match All

1 Like

Thank-you team for this tutorial, I have followed this tutorial to the detail however and am particularly concerned when the waiters want to add more items on a previous (Submitted)printed bill
Waiters have a way to reprint the same bill. Initially, when the waiters print the bill, the print bill button “grey out” meaning for you to use it again you have to unlock the ticket. So I disabled unlock the ticket button. What happens is the waiter will add an item on the said ticket and cancel the same item before submitting, this makes the print bill button to appear highlighted hence he can now reprint the same bill.
Please let know-how to restrict adding of items on submitted bills

Check user roles, beleive this is permitted by can unlock ticket permission.

Thank JTRTech this is what i wanted