STRUCTA
The restaurant, run from one system
Tables, orders, the kitchen display, and the day’s numbers — one modular workspace instead of a POS, a spreadsheet, and a group chat. Each person on your team sees only their station.
The floor, the kitchen, and the books
Everyone signs into their own station; everything lands in the same records.
The floor
A visual floor plan with live status — free, occupied, reserved. Seat a table, open its tab, add dishes from the menu; the total updates as you go.
The kitchen
Dishes a server adds appear on the kitchen display in seconds, oldest ticket first. The kitchen taps each dish as it’s plated; low-stock ingredients are flagged right on the ticket.
The books
Close and pay is one atomic step. Payments are recorded for your reports (you keep your card terminal); voids and reopens need a manager PIN and land in the audit journal.
Tuesday, 12:42 — mid-lunch
Recreated from the real product with sample data — nothing the app doesn’t do.
Or just watch it run — 90 seconds of the live app, unedited: seating the 13:00 party, the kitchen display, and the assistant closing a tab with the manager’s confirmation.
The details that matter on a real floor
- Recipes draw down inventory automatically as dishes sell.
- Voids and reopening a closed order require a manager PIN — every attempt is logged.
- Order history keeps every past bill, by day.
- The whole app works in English, Spanish, and Russian — staff pick their language.
- Runs in the browser on devices you already own: the host stand, a tablet, the kitchen screen.
Restaurant questions, answered
Is Structa a POS?
It runs the POS job: open a table’s tab, add dishes, close and pay, keep every past bill. Payments are recorded for your books — card processing stays on your current terminal, with your current rates.
What does the kitchen display run on?
Any screen with a browser — a tablet on the pass or a wall-mounted display. Tickets appear within seconds of a server adding dishes, and the board clears itself daily.
Does inventory really follow recipes?
Yes. You attach a recipe to a dish, and every sale draws the ingredients down. When an unprepared dish would run past your stock, the ticket shows a warning.
How long does setup actually take?
Enable modules, create roles, invite staff — that part is minutes. Entering a full menu is the longest step (about an hour for ~40 dishes); send us a spreadsheet and we’ll load it with you during onboarding.
Can my servers see the revenue numbers?
Only if you put Reports in their role. The front desk can run bookings all day without ever seeing a dollar figure — that’s the point of role-scoped workspaces.
Does it work offline?
Yes — the floor keeps working. If the Wi-Fi drops mid-shift, a signed-in tablet keeps showing tables, orders and the menu, and staff keep taking orders and settling checks; everything syncs automatically when the connection returns, dated to when it actually happened. Signing in and the AI assistant still need a connection.
Not a restaurant? Salons, gyms, and clinics run on the same modules →