Nobody wants to update a POS system "in realtime" - meaning while someone is actively using it and processing transactions. Just like nobody wants prices of ite

Nobody wants to update a POS system "in realtime" - meaning while someone is actively using it and processing transactions. Just like nobody wants prices of items to change mid-transaction. It is impossible to explain these kinds of events to customers (sorry, but five of your eight Cokes are 20 cents more because we happened to be too slow to scan them and a price change came in between). In countries employing strict fiscal rules governing electronic cash registers - which are more and more on a global scale - stuff like that may even be illegal to do. This is one of the reasons why that entire "cloud" SaaS thing is a bad fit for PoS systems to start with. It doesn't stop cloud apologetes to still develop and market such systems and customers who drank the cloud kool-aid to buy them, but what people actually want in that business when push comes to shove is a locally-installed system that is seamlessly offline-capable in all its core features, can send transactions out and receive new master data in real-time while network connectivity is available and can be updated easily and ideally via a centrally controllable and plannable process. And that have actually been bog-standard features for PoS systems for at least a decade or two, long before all that "push everything into the cloud" hype started.