# The bar's wi-fi went down. Now what? The internet in a bar or restaurant goes down. That is the reality of operating in São Paulo. This article sets out what a serious system has to do offline, and what can wait for the connection to return. - **Published:** 14 March 2026 - **Reading time:** 7 minutes - **Category:** Technology - **Author:** The Oasys team It is not a question of whether the internet goes down. It is a question of when. And by the law of the bar universe, it goes down on Friday at 9pm, with a full house, in the middle of the biggest tab of the night. Anyone who operates in São Paulo knows it: the internet in bars and restaurants is unstable by nature. The right question is not how to avoid the outage. It is what your system does when the outage happens. ## Why the bar's internet goes down so often It is not bad luck, it is infrastructure. Most venues run on a shared connection, the same network as the customers, the waiters, the background music and the camera. At peak, everyone pulls bandwidth at the same time. The router, almost always the one the telecoms company handed over, was not built to carry dozens of simultaneous devices. Add to that a commercial address on a busy street, old wiring, and the fact that the telecoms company does not treat a bar as a priority. The result is predictable: the connection wobbles exactly when you need it most. ## What breaks in a cloud-only system A system that depends 100% on the internet turns into a stone when the connection drops. And then the night stops in a specific and painful way. The waiter cannot enter the order. The tab does not reach the kitchen. You cannot print, you cannot close a bill, you cannot take a card on the integrated terminal. The queue grows, the customer complains, and the team runs back to the paper notepad, losing everything the system was supposed to organise. When the internet comes back, the second pain arrives: somebody has to type in by hand everything that happened in the dark. That is where orders go missing, bills come out wrong and the cash-up does not balance. ## What offline-first really means The engineering answer to this has a name: offline-first, or local first. The idea is easy to explain and hard to build: the system runs on the device, not in the cloud. It stores the data locally and works normally with no internet. When the connection returns, it synchronises on its own, with nobody typing anything again. The practical difference is enormous. In a cloud system, the internet is the floor. If the floor goes, everything falls. In a local-first system, the internet is only the bridge for synchronising. The bridge can go down and the operation carries on from the riverbank, waiting for it to come back. ## What has to work offline, and what can wait Not everything needs to work without internet. This is the honest division. It has to work offline, because it is the heart of the operation: - Opening a tab and entering items on it - Routing the order to the kitchen and to the bar - Closing a bill and calculating how it splits - Printing the tab and the bill It can wait for the internet to come back, because it does not stop the night: - Tax invoicing (the invoice goes out asynchronously when the connection returns, so the customer is not left waiting) - Dashboards and reports - Synchronisation between devices If the core of the operation survives the outage and the rest synchronises afterwards, the internet going down becomes an annoyance rather than a crisis. ## How to assess a system on this Before signing with any system, ask the supplier a direct question: what happens if the internet goes down right now, in the middle of service? If the answer is vague, along the lines of it rarely goes down, or we recommend a good connection, be suspicious. That is responsibility pushed onto you. The right answer is specific: the waiter keeps entering orders, the kitchen keeps receiving them, bills keep closing, and synchronisation happens on its own when the connection returns. Ask to see it. Ask them to switch the wi-fi off during the demonstration and show you a tab being entered anyway. A serious system is not afraid of that question. ## Why we are writing about this Oasys was designed local-first because it was built by looking at the real operation in São Paulo, not the operation on a slide. The waiter enters the order on the device and it reaches the kitchen even with no internet. The tax invoice joins a queue and goes out when the connection returns. Nobody types anything twice. Good internet helps. But your night cannot depend on it. It is the system that has to hold up, not you. ## See also - [All insights](https://oasysai.com.br/insights) - [For botecos, the neighbourhood bar](https://oasysai.com.br/para-voce/botecos) - [For bars](https://oasysai.com.br/para-voce/bares) - [For snack bars](https://oasysai.com.br/para-voce/lanchonetes) --- This is the English markdown representation of https://oasysai.com.br/insights/wifi-caiu-offline. The rendered page is in Brazilian Portuguese and is the authoritative version.