Everything you need to know about restaurante do ze
restaurante do ze is a Brazilian restaurant management and ordering platform built for small to medium-sized eateries that don't want to deal with enterprise-grade POS systems. It runs primarily on a web dashboard with a lightweight mobile app for floor staff. The core idea is simple: you digitize your menu, track orders in real time, and handle payments without the bloat of bigger competitors. I ran into it when a friend asked me to help set it up at his place. What followed was about three weeks of trial and error before it actually behaved itself. Here is how it works, what goes wrong, and how you fix it.
restaurante do ze setup and configuration
The installation process starts at their portal. You create an account, pick a plan (there is a free tier with limited tables and no payment integration), then you install the POS app on an Android device or tablet. I have seen people try running it on iOS and it is not officially supported, so don't bother. After the app installs, you connect it to your device's Bluetooth printer. This is where the first headache appears. The printer pairing is flaky. The app will connect to some thermal printers and not others. If yours isn't printing order tickets after pairing, check the baud rate setting inside the printer config menu. Most generic Brazilian thermal printers default to 9600 baud. restaurante do ze expects 19200. Mismatching these two numbers causes the app to show a success message while nothing comes out of the printer.
Once the printer is working, you enter your menu. You can import from CSV, but the importer is basic. Headers need to match exactly: nome, preco, categoria. If you export from another system, you will likely need to rename columns before uploading.
Order flow and table management
When a customer sits down, the waiter opens the corresponding table in the app, adds items, and sends the order. The kitchen sees it immediately on a separate screen or tablet if you set one up as a kitchen display. No delays. This part works well. The sync between floor and kitchen is under ten seconds on a normal local network. The split-bill feature is one of the stronger points. You can divide a table by item, by head, or by percentage. I once had a group of eight people where four wanted to pay individually and the other four wanted to share two dishes. The app handled it without crashing, which is more than I can say about some of the POS systems I have used.
There is a limit on how many tables you can have open simultaneously depending on your plan. The free plan caps you at five active tables. If you are running a busy lunch service with more walk-ins, you will hit that ceiling fast and get errors trying to open new ones.
👉 Clique no botão abaixo para saber mais sobre o assunto!
Payment processing and integrations
Payments go through their integrated gateway or you can connect a third-party processor. The built-in option supports PIX, credit cards, and debit cards. PIX transactions settle almost instantly, which is critical for cash flow in a small restaurant. Credit card settlements take T+1 business days, standard for the region. If you want to integrate with iFood or Uber Eats delivery platforms, you need the paid plan. The free version does not support external order aggregation. This is a real bottleneck if you rely on delivery apps. I found out the hard way when orders started piling up on my friend's phone instead of the dashboard because he had not upgraded. He missed about twelve delivery orders in one Saturday afternoon.
Common issues and workarounds
The app crashes occasionally when loading the menu if you have more than two hundred items. The developer recommends splitting your menu into categories with fewer items each, but even that does not fully solve it. The workaround I found is clearing the app cache every Sunday night after closing. It resets the local database and prevents the crash from recurring during the week. Another issue is the report generator. It is functional but slow. Exporting a monthly sales report can take up to four minutes if you have a lot of transaction history. If you need the data quickly, use the API endpoint for reports instead of the dashboard export button. It is not documented prominently, but it exists and pulls data in under thirty seconds.
The backup system relies on cloud sync, which means you need a stable internet connection. During an outage, you can still take orders locally, but they will not sync until the connection returns. Any orders created during downtime will appear with a timestamp gap that messes up your daily reconciliation. I keep a simple spreadsheet where staff manually log orders when the app goes offline. It is not ideal, but it prevents confusion at end of day.
Who should and should not use this
restaurante do ze works well for family-run restaurants, food trucks, and small cafes that need a straightforward system without a lot of customization. It is not designed for chains, fine dining, or places with complex inventory and recipe management needs. If you need to track ingredient usage by recipe, calculate food cost per dish automatically, or manage multiple locations from one dashboard, this tool will fall short. The pricing is competitive for what it offers. The free tier lets you test the system before committing. I would recommend using it for at least a week with real orders before deciding whether it fits your operation. The trial period is generous enough to surface most of the edge cases without pressure.
Support is available via WhatsApp and email. Response times vary. During peak hours, expect delays of several hours. For urgent issues during service, the community forum has active users who often share solutions before the official team responds.
