Scanner APP - Asks twice for Purchase Amount.
planned
Hermann
When you create a Discount / Rewards Card you have the option to Disable the Scanner APP asking for the purchase amount.
Even thought this function gets disabled the Scanner APP still asks twice for the Purchase Amount.
We understand that you do not have to type in twice the purchase amount and the second time when the Scanner APP asks for the purchase amount you can ignore it and just click the "Add" button.
It will be nice if the message did not display twice to improve speed in using the Scanner APP and improve useability.
Hermann
Just a Question: Why not "Hide" it when the Selection in the Dashboard is "Disabled" for "Purchase amount is requred in Scanner App". Also saw now that the word "requred" in "Purchase amount is requred in Scanner App" is a Typo.
Nadezhda Nagaeva
It will be implemented as follows: The entered purchase amount (for cashback, discount, stamp expense and forward expense cards) will be duplicated in the second window. But we will not remove it, it is a confirmation of the operation and it will remain.
T
Titouan Albouy
Nadezhda Nagaeva thx for reply
Daniel
Nadezhda Nagaeva can you at least give us the choice if we need another confirmation? Some do some don't. Please do not dictate us how to run our business. As mentioned before, the scanning process is the biggest disadvantage in Boomerangme and we are looking for ways to speed up the process and reduce the clicks
When using a POS scanner there is also no 2nd confirmation
Daniel
Please include a proper confirmation when purchase amount has been submitted
Nadezhda Nagaeva
planned
Daniel
"under consideration" since march 15th
Tomo TheDoorShield
Is actually awkward responding to the issue. Makes you feel like you don't care. Maybe is a complicated feature due to design?
S
SACHIN VASANI
Yep....many clients are finding this a nuisance. In a retailer environment its all about operations and speed. Don't understand why its taken this long to fix this. This is the basicsic core functionality of the product. The basis should work first
TuSystem
As far as I can see this hasn't been fixed yet, has it?
Martin
Where are they with this?
Akatek
+1
Load More
→