Where this comes from
It began with one shop and one question
Phlo POS was never meant to be a product. Years ago a retailer on the other side of the world needed a till, and nothing for sale could do what the situation asked: several currencies, several countries, and tax rules that changed at every border. So we wrote one.
That till is still in service. It has been ringing up sales for close to ten years, with tens of millions in turnover passing through it every year, across new stores, new tax rules and a lot of busy Saturdays. A till earns its keep by being unremarkable: it just has to be there when the queue is.
Then other counters started asking. A bar wanted to open tabs and print kitchen tickets. A shop wanted barcode scanning and a cash-up that added up at the end of a shift. Each time the answer was yes, and each time the engine underneath got better at being shaped into something specific.
Ten years
in daily service, still running
Tens of millions
in yearly turnover through one installation
Many currencies
across borders, in one system
That is the work Q-dev does: build the solution, not a licence to rent. Phlo, the framework underneath, is ours as well, so the till, the back office, the reporting and even a public menu card come out of one codebase. It is why a change at your counter is a few days of work instead of a request that waits for someone else's next release.