4 ms·
I'd add this to your list: - optimize the system to run in true realtime - most self checkouts I used have perceptible latency of a few seconds between one sca
by yalok 2y ago
I'd add this to your list:
- optimize the system to run in true realtime - most self checkouts I used have perceptible latency of a few seconds between one scan and the next one - usually lagging behind of how fast a person can scan all their items, if they are positioned conveniently. Also, after all scanning is done, going to payment has its own delay. The system has to be very responsive...
- Animats 2y agoThat's usually "cloud POS", where every little event goes to some faraway shared server. I recently tried to eat at Roam, on Union Street in San Francisco. But they could not sell me a burger. Their cloud POS system (from Toast, naturally) had failed. So they were out of business until Toast got around to fixing the server end. They couldn't even accept cash - the cloud controls the cash drawer.
- Semaphor 2y agoThat sounds horrible, none of the ones I tried (3 different stores, technically also Ikea, but that was several years ago, and I can’t remember how it worked) have that issue.
- Eddy_Viscosity2 2y agoThis lag is one of the most frustrating things of self checkouts. The manned checkouts don't have this. Its bleep, bleep, bleep, one item after the other. But the self checkouts have that damn refractory period after a scan to recover itself and be ready for the next scan. It's also true of any of the other actions like for payments needing sometimes five button presses each with long pauses. Like just have 'Pay Cash', 'Pay Debit/Credit' as two separate buttons and if you hit 'Pay Debit/Credit', the card reader is ready to go. Oh, even worse is when they give voice instructions, but you can't proceed until its finished talking.