In this tutorial I’ll show you how to log specific events inside tickets. In this sample I’ll log payments so you can review later which user received payments.
We’ll start by creating a Display Ticket Log action. This action is useful to display logs.
We need another action to add logs inside tickets. I’ve configured Category and Log values as variables since I’ll send these values from another rule.
Create a new Automation Command for Display Log button. We’ll use this button to display logs. For this sample I’ve mapped this button to ticket. You can customize it not to display for regular users.
Basic configuration is ready. Now we need to think what we need to log inside tickets. In this sample I’ll log payments. So I’ll handle Payment Processed rule to add logs.
I’ve typed Payment as Category so if I need to create additional logs I can categorize log items. Log content is a free text area and you can use any rule parameters, printer tags or other additional values to generate log content. That will simply store payment amount, payment type and append Paid word to log. You can use better formatting for your needs.
On a sample ticket I’ve added two payments. Both $5.
Thanks @emre. Just one more question. Here I saw frauds being done after the print bill (assume that the cashier can unlock the ticket) because they printed bills then after receiving the money from the customers they made changes to tickets. So I want to capture that log between print bill and the print receipt if there is any changes to the ticket
Would it be possible to add credit card logs to this?.. like last 4 digits of card and type of card?.. Could it also be able to add amount paid and change due to the log as well?.. Mybe even when the cash drawer was opened?
