My mom had all the prices in her head. That worked well enough when she was the person running the register. It made it much harder for anyone else to take her place.
My parents ran a small shop, and Mom was the owner and operator. She used a manual cash register and knew what everything cost. I helped enough that I had probably memorized about 80 percent of the prices myself, but I was too young to reasonably be left running the place alone.
That left the business depending on one person’s knowledge and availability. If Mom needed to be somewhere else, finding somebody to stand behind the counter was only part of the problem. That person also needed to know what to charge.
Her workweek could run to 60 or 80 hours once you counted the bookkeeping and trips to fetch supplies and inventory. As a family, we wanted to reduce that workload. I thought a point-of-sale system might let someone else handle the register without needing to memorize everything first.
Sometime between 2011 and 2014, we went live with uniCenta.
Putting the prices into a system gave us a way to teach register duty to someone else. It was a practical improvement, even though the software itself gave us plenty of trouble.
In the version and setup we used, I remember rounding errors in calculations, particularly sales tax, and barcodes that never worked quite right. The system was buggy and unreliable, but it did the job well enough to show us that the idea was useful.
Those problems also changed what I expected from a POS. Accurate arithmetic and reliable behavior mattered every time somebody rang up a sale. If we couldn’t trust the calculation, someone had to investigate it while still trying to run the business.
Investigating was often the difficult part. When uniCenta did something unexpected, we had to guess at what had gone wrong. Had we configured something incorrectly? Was there bad data? Had an operator made a mistake, or was there a bug in the software?
I came away from that experience wanting a meticulous audit trail. The operator and the person supporting the system needed enough information to retrace what happened and work out the cause. Being able to see the final number was not enough when the question was how the system arrived at it.
I eventually switched the shop to SambaPOS. In our experience, it was much more accurate and stable, and it worked far better for the business.
Supporting it taught me another lesson. Making configuration changes was difficult. A system could work impressively during a sale and still take too much effort to adjust or support afterward. I began to see ease of configuration as part of whether a product was practical to live with.
The difference a POS made to our family was that register duty could be delegated. The shop could stay open without Mom or me in the building. A medical emergency, a family emergency, or a vacation no longer meant that one of us had to be there simply because nobody else knew the prices.
The reduction in Mom’s workload came from several changes working together. We leaned more on deliveries for supplies and inventory, which reduced the need to go out and fetch them. We hired a capable manager who could operate the POS without us beside them. We also shortened our opening hours on weekends and in the evenings.
The POS made the register easier to hand over. The manager gave us someone capable of taking it on. Deliveries and shorter hours addressed other demands on Mom’s time. Together, those changes reduced the workload and stress.
The result we cared about was having more flexibility and making the shop less dependent on Mom being present. The software helped us make that possible alongside the changes we made to staffing, purchasing, and opening hours.
The shop kept using SambaPOS until my parents closed the business permanently. Their need to retire, combined with the frustrations caused by the pandemic closures, brought that part of their working lives to an end.
Those experiences stayed with me as I went on to work in IT and eventually build Brisk. I had already seen why an operator needed a system they could rely on, and why the person supporting it needed clear records and a manageable configuration.
At the time, though, I was trying to help my mom get some of her week back. Being able to hand the register to somebody else was our reason for putting a computer there.