WhatsBar
- Completed
- 500+ automated tests
- 18 domain modules
POS and SaaS platform for bars: waiters order from their phones and every order prints at the right station.
- SaaS platforms
- Management and operations
The problem
In a busy bar, orders written on paper get lost, duplicated or sent to the wrong kitchen. And the owner only finds the gap when closing the till.
Who it is for: Bars and restaurants with separate floor, kitchen and bar.
What the system does
The waiter opens the table and sends each round from a phone app. The server reprices it, splits items by production sector, deducts stock through the recipe sheet and sends every ticket to the thermal printer of the right station. The owner follows the floor, revenue, stock and each waiter’s performance on the dashboard.
System screens
The screens stay in Portuguese, as in the system.
Modules
- Waiter app (PWA)
- Live floor map
- Kitchen display by sector (KDS)
- ESC/POS thermal printing
- Stock with recipe sheets
- Cash register and shifts
- Finance and reports
- QR code digital menu
- Multi-tenant plans and billing
What the screen is made of
Every screen above depends on decisions like these, made in the code and covered by tests.
| Part | Decision |
|---|---|
| Order | Idempotent: each round carries a key; resending after a 4G drop returns the same order, with no duplicate ticket. |
| Price | Always read again from the database on the server. The waiter’s screen displays it, never decides it. |
| Printing | Outside the order transaction: a printer that is off never blocks the sale, and the queue has an atomic lock between agents. |
| Bill | Summed per tab, never per table: what the previous guests ordered never shows up for the next ones. |
| Isolation | Establishment scope on every access; on-screen identifiers are locked and re-checked on the server. |
Technology
- Laravel 12
- Livewire 3
- Laravel Reverb
- PHP 8.2
- PostgreSQL / MySQL
- Tailwind CSS
- PWA
- Playwright
- PHPUnit
Integrations
- ESC/POS
- Cloudflare Turnstile
Stage
Completed
Completed. The screens come from a disposable database with the fictitious “Bar do Zé” created by the system’s own seeds, and one night of operation simulated through its domain services.
Want to see this system working?
We give a guided demo with demonstration data and talk about what it would solve in your operation.
Request a demo