When batching out, Clover should have an option to be able to print all transactions out that are included in that batch.

This is something that First Data terminals can do like the FD130 or the Verifone VX520. A merchant presses batch out or closeout and the batch report prints and lists every single transaction by amount and last 4 digits of cc.

I have lost sales of Clover devices just because this functionality is lacking. In one case, I was giving the merchant a free Flex, and he didn't want it after he found out he can't print a detailed batch report, only a summary total. He asked me for a VX520 terminal instead.

Please have this added to Clover and have First Data (who owns Clover) look at their own FD130 terminals to see how the detail batch report functionality works.

This should be an easy and quick programming change by Clover that would be very well received by merchants.

It could simply be a "setting" on the Closeout app that a merchant can check off to print "detail" when closing out.

Per Clover support, each invoice has an expiration period of 180 days. It would be great to be able to change that to whatever my business needs are. Say my customer policy is to pay the invoice within 30 days, it would be helpful to set that expiration time frame myself. Alternatively, give us the ability to delete an open invoice! If my customer pays by another form of payment, will that open invoice just sit there in my dashboard for 180 days until it expires? In that example it would be so helpful to either delete the invoice or maybe change the status to "paid" or "closed", etc.

Make the Void Report (and the Void Function) Useful!

While I'm glad we finally have a report that logs all Voids, we still need major Void and Void report upgrades:
1. Logging a void is helpful, but owners and managers need to know WHY something was voided. We need to be able to create and assign Void reasons or codes, ESPECIALLY for restaurants.
2. The current VOID function is almost worthless, because it ONLY works immediately after a payment has been made. Virtually all major competing POS systems and credit card terminals allow voiding of items and payments up until batch submission. Merchants rarely know a payment even needs to be avoided the moment after. I believe the majority of our Voids on Clover come from people who hit the Void button by accident.
3. Voids need to prompt for a Manager or Admin code, EVEN when performed by an Admin or Manager, to prevent the major problem we have with accidental voids

Multi-Location Inventory management functionality is subpar compared to the existing functionality in individual location dashboards.

We urgently need export/import functionality for bulk item, categories, labels and location assignment editing. We have 2000 items that has to be centrally managed (via Multi-location dashboard) and synced between all locations. It is unrealistic to go and change 2000 items from begin with.

Also it is unrealistic to Multi-location manage items from Web dashboard only. Individual clover terminals at different locations has to offer a feature to edit according properties for location, category, label assignment and those shall propagate to all other locations if selected.

The Clover Mini can be used as customer facing terminal attached to the Clover Station 2018 or to it self the Clover Mini. Some merchants are using the Clover Mini as a merchant facing terminal instead of the station 2018. It is a known issue with Clover Support that the Clover Mini EMV card slot gets damaged when using metal cards. The ability to attach a relatively inexpensive EMV/CTLS customer facing terminal to the Clover Mini would effectively and efficiently protect the more expensive Clover Mini from being damaged and buy the hardware team time to review / redesign the Clover Mini EMV card slot. Currently the merchant is being exposed to EMV Liability Shift or chargebacks due to key entry of transactions. Plus, there is additional charges for the swap and time waiting anxiously for the arrival and setup of the new Clover Mini. Clover Support sometimes states that the LTE may resolve this issue but merchants with non LTE Clover Mini's would not benefit.