Max number of open guest checks

[Kenyonl]

We have run into an issue with keeping tickets open. We run a large bar and we keep several hundred tickets open at any given time. All servers use the same login since we do tip pooling. Therefore, we have discovered an interesting and quite painful system limit that I am hoping someone can assist with. I recognize the operational questions that this whole scenario raises. However, our situation is quite unique.

The system only allows us to show 176 total open guest checks at any one time. The list is in alpha order so by 2pm we can only see up to the letter M. Since the server cannot find a ticket for Mr. Smith they open another ticket for him. It makes for a mess at the end of the evening. Does anyone know of a way to increase this limit?

 

[pmegan]

It sounds like Posi has an open check filter, which Micros doesn't offer to the best of my knowledge. It is a nice feature, but it has limited usefulness so they probably won't bother with it.

There used to be a standard SIM floating around that allowed you to start/pickup checks by swiping a CC, but that disappeared when PCI rules came into effect. To do that you have to read and save CC info into memory which is a no-no. I don't think that would help in this instance though. Chances are the servers don't have the guest CC with them every time they pick up a check. Same with the barcode. In order to scan a check specific barcode you would need a printed copy of the check, in which case you'd have the check number anyway.

In my opinion the best way to deal with this is still what I posted above. Have the servers sign in with their own ID so their checks sort to the top of the open check screen and pool tips using cashier totals. If a server has more than 176 legitimately open checks there are bigger issues than this one. Also, I know Kenyonl said that there are guests that stay from noon until 8pm, but my guess is that the servers are holding onto checks that should be closed until the end of their shift, or a lull in business, and that's making the problem worse.

 

[PosGuyUS]

I think if I had more than a few screens worth of checks, I'd want a search feature. Much faster to touch search, J O, and touch the check for John than scrolling down a bunch of pages and searching for the checks that start with Jo. Also, the further into the alphabet, the more time that takes. You might has well just print out the checks so you have the check numbers and use the open by check number button.
Scanning a barcode is much faster, a lot of cashiering type places use it but otherwise, not a popular faster. Starting a check with a CC swipe doesn't necessarily break any PCI rules, depends on what is stored. We don't store the CC number in memory, it just grabs the name off of track 1 and if we're doing a CC preauth, it's leaving a token in the system. Same thing as swiping a card for the check total and not closing it. Sounds like the SIM was just not written correctly.

 

[hosehead78]

Very true @PosGuyUS, however the big issue here is that they use a single cashier number for a very large amount of Checks. If multiple cashier accounts were used you wouldn't necessarily have this issue, because you can set the accounts up to only see their checks or all checks (based on position). We'll see how this is handled, as I am curios as to why this is happening.