LINGA — Feature Request Forum

+2

The modifier quantity should not be displayed in the kitchen receipt.

cvydyam 3 months ago in POS / RESTAURANT POS updated by Hardy Singh 1 month ago 1

The modifier quantity should not be displayed in the kitchen receipt.

+2

Checkout Process on POS & CDS

pkrolikowska 3 months ago in POS updated by Hardy Singh 1 month ago 0

Partner has addressed how complex and back and forth the process is between a Cashier and Customer on a POS & CDS set up. Partner would like the process to be smoother and the cashier shouldn't have to walk the customer through the checkout on the CDS per his recent experiences. Occurs the same on iOS and Android.

Partner suggests that once the card button has been hit on the merchant side, the customer should be able to present their payment method on the device, then the tip screen should appear, then a submit or continue button, lastly the receipt screen. This would make the checkout process much smoother and less confusing.

+2

Hide Modifiers and Modifiers groups from POS

Mark Amaral 3 months ago in POS / RESTAURANT POS updated by Hardy Singh 1 month ago 0

Can we make a reverse of the hide. I have a customer that wants a more dumbed down version of their Modifiers for there Kiosk and Online ordering. So I want ot make new Modifier groups to be only seen from the Kiosk and Online but not show up for the normal employees.

+2

sign out

matt dorzok 4 months ago in POS updated by Hardy Singh 1 month ago 0

We need to be able to disable the sign out button on the FOH,

Servers keep signing out and manager does not know how to sign in

+2
Planned

Add Tax for flexible Gratuity in UK

Milenko 5 months ago in POS / RESTAURANT POS updated by Product Engineering 7 hours ago 1

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.

+2

More control of payment timeout

CoCard Onboarding 8 months ago in POS updated by Hardy Singh 1 month ago 1

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.  

+2

Retrieve Failure Payment flow change to prevent double charging customers

Brad Bryant 9 months ago in POS updated by Hardy Singh 1 month ago 1

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.

+2

Prompt for Tip on preauth transactions

Kyle C 10 months ago in POS updated by Hardy Singh 1 month ago 1

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

+2

Optional Pre-auth Pop Up

Jason G 11 months ago in POS / RESTAURANT POS updated by Hardy Singh 1 month ago 0

It would be amazing to have the option to turn on the automatic pop up function to pre-auth a tab.  Some cash-heavy bars spend a lot of time pressing cancel.  Since we can add it to the check options panel at the bottom of the screen, the pop up may not be needed for some bars.

+2
Under review

Digital tipping screen to show after payment processed

Ryan Nicley 12 months ago in POS updated by Hardy Singh 1 month ago 3

It would be very nice to have the option to show the digital tip screen after the payment is processed on an iPad or tablet instead of only being able to show it before the payment is processed. Some of our customers feel like it's out or order in the payment process.