I'm new to Clover. I recently started working in a restaurant that uses it. This is my first time using a POS system, but I've worked as a programmer for many years. Yesterday Clover was experiencing network/server issues and, as a result, we ended up with errors on two tickets. The tickets were opened by the server on two different terminals that, because of Clover's network issues, didn't fully sync. Both tickets ended up as partially paid in Clover because of the sync problem when they should have been paid in full. Long story short, we made the problem worse trying to issue (bogus) payments and credits to make things go away. All of this could have been avoided had I been able, as Admin, to edit these orders. As a programmer, I'm totally shocked that there isn't some way to fix mistakes. It really makes for a terrible user experience.
Rob
supported this idea
·
I'm new to Clover. I recently started working in a restaurant that uses it. This is my first time using a POS system, but I've worked as a programmer for many years. Yesterday Clover was experiencing network/server issues and, as a result, we ended up with errors on two tickets. The tickets were opened by the server on two different terminals that, because of Clover's network issues, didn't fully sync. Both tickets ended up as partially paid in Clover because of the sync problem when they should have been paid in full. Long story short, we made the problem worse trying to issue (bogus) payments and credits to make things go away. All of this could have been avoided had I been able, as Admin, to edit these orders. As a programmer, I'm totally shocked that there isn't some way to fix mistakes. It really makes for a terrible user experience.