Gratuity is being calculate differently in UK and we need this changed ( or given possibility to change it via Back Office ) so can make sure it calculates Gratuity on the totals, tax included.

Can you please add a section on reports that display the Discount, Comp, or Void reasons on it?

Can you please add an extra section on the sales reports that show the total credit card bank deposit amount?.  Right now you have to manually add up 5 different numbers on the report in order to get this number.   The customer should be able to easily check and balance their bank deposits with the Linga reports and right now they have to manually add the following information up to come up with the deposit amount.  Please contact us if you would like further details / examples. 

1.Payment Summary

Credit Card

2.Other payment

online payment

3. Tip/Gratuity

Credit card

4. Tip/Gratuity

Online tip

5.(MINUS) Refunds

Non/cash refunds

Need all reports to be able to be run for a specific time period or day part.

If we could define day parts - Breakfast 6am-9am, lunch 11am-4pm, Dinner 4pm-12am, then run a report by day part so see all sales, discounts, payments etc

Allow more control of the time the Linga POS software waits for a response back from the PAX

This is useful for clients that have slower internet connections or unstable connections. or even a S300

This will help in situations where the payment shows as failed in the POS but did process in the Terminal.  

We need to have the option to only enter in the customers first name and phone number in BO. You can do this on the POS, but if you want to add customers in BO, you have to enter in more than just the first name and phone number. If you enter the information on the POS incorrectly and you want to edit the customer info you have to enter a last name and email address and not all merchants have this info nor do they want to have to enter this.

Currently, there appears to be a critical flow issue with the handling of failure payments for POS stations that use dedicated EMV terminals like the Pax A35.

When a payment fails to make it to the POS for whatever reason the POS overlays a red ribbon over where the payment should be and a text box pops up asking users to swipe the payment. At this point the transaction stays in the Batch on the Pax device but is not visible on the copy of the batch on the POS. If the user swipes the red ribbon the payment is checked for on the Pax device and is taken care of. However if the user selects Delete the payment is deleted only on the POS side, but is left on the Pax Batch. This gives the appearance to the user that everything is taken care of and the user will go ahead and attempt to charge the customer again. However at the end of day, when the user submits the batch there are now 2 charges being submitted leading to double charging the customer which ultimately becomes chargebacks for the merchant.

Currently everything hinges on the text box which pops up when the error comes up. There are many problems with using this as the solution.

1. The only interaction users would typically have with the payment is deleting it to refund the customer. The pop up only appears once so if they cleared that message too fast, or just didn’t understand what it meant they will likely try the delete method to remove the failure payment.
2. The correct option(Retrieve) is hidden and dependent on an action, whereas the option which can lead to double charges(Delete) is plainly visible and is allowed to be done before the correct action.
   1. Should consider making sure it is not selectable at all. I don’t know what the purpose would be for allowing that to be visible when it is a double charge risk.
3. Users get fairly numb to the textboxes. I see employees just exit out of that text box as soon as it pops up. They assume it’s the same knowledge they’ve done hundreds of times to remove a payment. This is made worse by the high volume of errors that the Pax A35 produces(particularly with Tap to Pay).

Overall when it comes to the flow of the Failure payments I would like to see Linga make it easier to perform the right action and harder to perform the wrong action. I think this can be handled easily within the design of the app rather than relying on the text box.

Add Enroll date and last visit date in Customer export file when exporting customer data from Back office and also when uploading the customer data to back office. 

This columns can be marked as optional field when uploading the customer data to back office.

Currently if pre auth is enabled you can not tip on CDS with the preauth transaction.

Customer must sign paper and tip added to batch screen manually

The "notes" are a nice touch; however, it would make more sense for it the show on the schedule instead of the employee having to click on the shift and search for it.