Re:The Aloha point-of-sale system
by EsotericAlgo on Saturday February 29, 2020 @04:38PM
(#22453281)
One story that comes to mind is the difficulty of change management. It’s possible to configure Aloha locally but beyond a certain number of locations a configuration tool called Configuration Center is used. It basically stores configuration information on a server (as a tree with the rough idea of inheritance) that stores connect to and pull down into the various configuration formats used.
In the tool there isn’t a concept of approvals. We had an admin disable receipt printers at all stores. There wasn’t a reliable global refresh so we had 10 people logging in remotely (through another horrible tool that was a front end for a reverse VNC connection) and calling stores to reset their configuration which brought their system down for 2 to 10 minutes during a Friday lunch rush.
We fixed this with process but NCR made it easy to shoot oneself in the foot.
Re:The Aloha point-of-sale system
by veggieburglar on Saturday February 29, 2020 @03:43PM
(#22452965)
It's great for front of house staff but the inventory control/back of house feature set is extremely limited (disclaimer: I moved off of using Aloha day to day in 2016).
I remember designing my own POS/inventory tracking concepts, and thinking back on it, knowing what I know now after about the same amount of time as a professional developer as I spent in restaurants, I’m impressed with how well it performed IME.
So for all the pain I’m sure you felt, still, hats off to you!