English Boards > Support

Receipts, Split Bills and Payment screen

<< < (2/2)

emre:
It is a shortcut for typing 1/x of the remaining amount. For a $20 ticket typing 10 or pressing 1/2 button does the same thing.

Do you think it should do something different?

lemmings:
Hello Emre

I have spent some time implementing Actions and Rules and can now split bills and print receipts for individual payments made customers.

The trouble I still have is getting an Auto printed receipt, it works but will only Auto print on first split payment and not on any remaining payments.  I was able to get round this by creating an Action and Rule to execute a Print Job each time a payment is received and this works.

I think I will be removing the 1/2, 1/3, 1/4 and 1/n buttons as there still does seem to be a logical process when these buttons are pushed and I cannot find either Action, Rule or Trigger which relates to these buttons.

The users seem confused by these buttons when trying to split a bill in four, as you have to push 1/4 first time, then 1/3 next time and finally 1/2 next time to get 4 equal payments.  Splitting individual items on the tickets into new tickets is actually easier but unfortunately if two people just want to split the bill in 2 it works but I think the process could be more logical.

I have never coded in C# but have used VS for VB so I may have a go at implementing something for our purposes which seems more logical - perhaps its a UK thing (splitting bills by 2 or 3 people that it).

Can you just confirm that it is correct for the Auto Print to only work with the first payment only ?

Thanks for your help in advance.

emre:
Hello lemmings. On V3 version I totally removed all autoprinting features that configured from printjob screen. It may seem a workaround but the right solution will be using actions. That feature basically implemented for auto printing from fast food screen and cash register integration. We send printout to com port to operate cash registers. Since these features used for many different purposes on splitting case it may not work fine. I hope to implement easier access to payment data from actions on V3.

You are right for some people 1/x buttons are confusing. Some people thinks it should always split total ticket amount. Some people thinks it should split remaining amount. On our first implementation it was splitting ticket amount so multiple clicking to 1/x buttons was generating same value. Now it splits remaining amount so it can be used on half paid tickets.

For easier usage we added a pink button under that column which always shows and updates the last tendered amount. So after splitting ticket amount with 1/x buttons using that button for next payments might be a solution.

Please let me know your progress on modifications. I'd like to know what will work best for you. So I can try to improve it for make it work fine on all cases.

Navigation

[0] Message Index

[*] Previous page