Settings and activity
37 results found
-
1 vote
Thank you for submitting your Idea to UserVoice.
Terry(Clover)
shared this idea
·
-
5 votes
Thank you for submitting your Idea to UserVoice.
Terry(Clover)
supported this idea
·
-
1 vote
Currently, due to space constraints on the Kitchen Display System (KDS) ticket header, we are only able to display a single unique identifier for each order. For orders originating from the Dining app, we prioritize showing the table number, while for orders from the Register app, we display the order number. This approach helps the kitchen identify the order's destination - whether it's for dine-in, takeaway, or deliver, within the limited space available.
We understand that having both table number and order number visible would significantly improve clarity and workflow, especially for full-service restaurants like yours. Your feedback is valid, and we recognize the inconvenience this may cause.
Please rest assured that we’ve noted this request and will be reviewing it with our engineering teams for future updates. We’re committed to improving the experience for all our restaurant partners and will keep you informed as we explore solutions.
…
Terry(Clover)
supported this idea
·
-
3 votes
Thank you for submitting your Idea to UserVoice.
Terry(Clover)
supported this idea
·
-
2 votes
Terry(Clover)
supported this idea
·
Terry(Clover)
shared this idea
·
-
12 votes
Terry(Clover)
supported this idea
·
-
3 votes
Thank you for submitting your Idea to UserVoice.
Terry(Clover)
supported this idea
·
-
4 votes
Terry(Clover)
supported this idea
·
-
4 votes
Terry(Clover)
supported this idea
·
-
5 votes
Terry(Clover)
shared this idea
·
-
20 votes
Terry(Clover)
supported this idea
·
-
1 vote
Terry(Clover)
shared this idea
·
-
1 vote
Thank you for submitting your Idea to UserVoice.
Terry(Clover)
shared this idea
·
-
2 votes
Thank you for submitting your Idea to UserVoice.
Terry(Clover)
shared this idea
·
-
22 votes
Thank you for your feedback on this issue. Clover does support partial authorization at the point of sale as required by most card networks. Rather than complex variations based on card type, MCC, and other parameters we have adopted a common implementation where the merchant is guided through a partial authorization workflow; e.g.
A $53 payment is attempted and the card is approved for $51.50
- This card has been approved $51.50
- The remaining amount dues is $1.50
- How would like to proceed; void initial payment or take next payment
We support these capabilities at the request of our acquiring partners to reduce costs associated with downgrades, non-participation fees, and the like.
Terry(Clover)
supported this idea
·
-
1 vote
Thank you for submitting your Idea to UserVoice.
Terry(Clover)
shared this idea
·
-
3 votes
Terry(Clover)
supported this idea
·
-
7 votes
Terry(Clover)
shared this idea
·
-
6 votes
Terry(Clover)
shared this idea
·
-
5 votes
Terry(Clover)
supported this idea
·