Owner
Every screen
- Revenue, till and reports
- Team, permissions and connections
- Approves comps and refunds
Operating panel for restaurants
They came once. Next time, greet them by name.
Zahter runs your floor, kitchen, reservations and till from one panel. Every closed bill is written to the guest's card. When that guest sits down again, your server's screen already shows what they like, what they're allergic to, and the first thing to say.
On the server's screen (translated)“Welcome back, Murat Bey. The lamb chops again?”
Straight talk: Zahter is in early access and built for restaurants in Turkey. We have no customer logos or reviews yet, so we don't show any. We show the panel as it is instead: every screenshot here comes from the live demo, in Turkish, because the English interface is planned but not built.
The heart of it
Knowing your guests shouldn't depend on one good waiter's memory.
Your best server knows the regulars. Then they take a week off, the shift changes, the team grows. Zahter gives that memory to the whole team.
- First visit
When the guest is seated, the host asks for a phone number. A known number is recognised as it's typed. If not, a card opens with name, allergies and birthday. Guests who'd rather not share are seated anonymously.
- Every bill is a visit
Each closed bill is recorded: party size, table, what was eaten and drunk, what was paid. Every number on the card is calculated from these records. No hand-kept counters.
- The moment of recognition
When a known guest sits down, a gold-edged card opens on the server's screen: visit count, last visit, allergies, an upcoming birthday and "the usual". One tap adds it to the bill.
Honorifics (Bey and Hanım, the Turkish Mr. and Ms.) are never guessed; the team writes them on the card.
Roles
Everyone sees their own job. Nothing more.
Staff pick their name and sign in with a four-digit PIN; the screen is built for their role. Servers don't see revenue. The kitchen sees only its own rail and stock. Five wrong PINs lock sign-in for 30 seconds.
Manager
Everything except team settings
- Approves comps, discounts, voids
- End-of-day cash count
- Shift plan and corrections
Host
Floor, reservations, guests
- Seating and opening cards
- Waitlist
- No-show alerts
Server
Floor
- Orders, bill and payment
- Requests a comp; it applies with a manager's PIN
- Never sees what a guest spends
Kitchen
Kitchen and stock
- Ticket rail, station filter
- Stock entry, without prices
- Allergies and VIPs printed on the ticket
Service flow
Mid-service, nobody has to chase anybody.
Floor, kitchen and host work from the same record. When the bill closes, that same record goes to the till and to the guest's card.
Red means one thing: someone is waiting on you. A late ticket, a table asking for the bill, a reservation that hasn't shown. The only exception is allergies, because that's a safety warning.
Floor plan
Several rooms, drag-and-drop layout. Each table shows one of six states: free, reserved, ordering, in the kitchen, eating, waiting on you.
Kitchen display
Oldest ticket on the left. Tickets turn red after 12 minutes. Station filter and a running portion count.
Reservations and waitlist
Table-by-time grid, clash check, table suggestions. A waiting party is seated at the smallest free table that fits.
Courses and fire
Starters go straight to the kitchen. Mains hit the rail when the server fires them.
Move and merge
Move a table with all its tickets, comps and reservation. Merge two tables into one bill.
Stock and recipes
Each portion sold comes off stock through its recipe. When an ingredient runs out, the dish drops off the menu by itself.
Screenshots show the Turkish interface. An English interface for the panel is planned, not built yet.
Till and leakage
Wherever money slips out, it leaves a trail.
No comp, void or discount goes through without a reason. Each one lands in the till with who asked, who approved, when and why.
Comps · voids · discounts
The server asks, the manager approves with their own PIN. A reversed entry isn't deleted; it stays struck through.
Split the bill
One bill, equal shares or item by item. Each share can be paid a different way; the last share absorbs the rounding.
Refunds
Managers and owners only, reason required. Reduces revenue and the guest's spend for that evening.
End-of-day cash count
Expected, counted and difference shown as you type. A difference over 50 TL needs a note.
Shifts and hours
Everyone clocks their own shift. Late arrivals, no-shows and staff cost on one page.
Tip sharing
The pool is split by the rule you choose: by hours worked, equally, or with a server share.
Suggestions
It suggests, shows why, and says what it doesn't know.
There's no AI in Zahter. Suggestions are plain rules counted from your own records, and each card shows where its numbers come from. If an effect hasn't been measured, it says "not measured" instead of inventing a percentage.
Daily briefing
One screen before service: who's coming, allergies, birthdays, the portions the kitchen should prep.
Campaign ideas
Ideas like "fill Wednesday evening": who to invite, when, and why. The message draft is ready; you send it.
Price suggestions
Menu engineering: Stars, Plowhorses, Puzzles, Dogs. It never changes a price by itself.
No-show risk
A score for every reservation, with what pushed it up and by how much.
Covers forecast
From reservations and the same weekday in past weeks: expected guests and staff, hour by hour.
Review replies
A reply draft based on the rating and the words in the review. You copy it and post it yourself.
The guest's screen
Guests see the menu, their table and their place in line on their own phone.
The restaurant's guest page opens in the browser. Nothing to download.
QR menu in 5 languages
Turkish, English, German, Russian and Arabic, with Arabic right to left. You add the translations to your menu.
Allergen filter
The EU's 14 allergens. Guests pick what to avoid and dishes that don't fit are flagged.
Order from the table
Orders from the table's QR code go to the kitchen. One tap calls the server.
Booking and deposits
Tonight's free slots are visible. You set the deposit rule: amount per person, refund window.
A personal waitlist page
Waiting guests see how many parties are ahead. The page tells them when their table is ready.
Reviews and loyalty
Star reviews; stamp or points loyalty, VIP perks and a birthday treat.
Integrations
Talks to the tools restaurants in Turkey already use.
The panel lists 79 Turkish integrations in 16 categories. 20 have a working connector; the rest are marked "coming soon", and restaurant demand decides which comes next.
We don't use brand logos without a partnership agreement, so we write the names. Each provider needs your own account.
Turkish fiscal cash registers (ÖKC) bridge
IngenicoBekoHuginProfiloVerifoneTokenPAVO
Payments, accounting, delivery apps
iyzicoPayTRParaşütYemeksepetiGetir YemekTrendyol GoMigros Yemek
Reaching guests
Google Business ProfileNetgsm SMSWhatsApp BusinessBrevoMailchimpWebhook
Coming soon (examples)
Bank POS terminalsMeal cardse-Invoice providersLogo, MikroTripadvisorİYS
iyzico and PayTR are Turkish payment providers; Paraşüt, Logo and Mikro are Turkish accounting software; İYS is Turkey's national registry for marketing-message consent.
Privacy and trust
Guest data, with the guest's consent.
Knowing a guest only counts if the guest is happy to be known. The rules live inside the panel; they aren't left to the team's good intentions. They are designed around KVKK, Turkey's personal data protection law.
Notice comes first
A card only opens once the team marks that the guest was told how their data is used. Marketing consent (İYS) is a separate box.
No consent, no campaign
Campaigns only reach guests who opted in. Reply "DUR" (Turkish for STOP) on WhatsApp and consent is withdrawn automatically.
Deletion on request
If a guest asks, their card is deleted; their visits stay in revenue without a name.
No number leaks
The guest page never reveals whether a phone number is on file. Typing someone else's number tells you nothing about who your customers are.
Nothing sends itself
Campaign ideas, win-back messages and review replies are drafts. Nothing goes out until you send it.
Roles and PINs
Each role sees only the screens its job needs. Comps, refunds and the cash count need permission.
Where it stands today
What's ready, what's being built.
A restaurant joining early access should know up front what it can use today and what it's waiting for.
Ready In the panel today
- Guest card, visit history, recognition card
- Floor, kitchen, reservations, waitlist
- Till: comp approval, bill splitting, refunds, end-of-day count
- Stock and recipes, shifts, tip sharing
- Briefing, campaigns, pricing, no-show risk, forecast, reviews
- Guest page: QR menu, booking, deposits, waitlist
- Connectors for 20 integrations
In progress For a real installation
- A data server, so the server's tablet, kitchen screen and host stand see the same moment. Today the demo keeps data in a single browser.
- Role rules enforced on the server
- Keeps working when the internet drops
- Multiple locations, a mobile app
- An English interface for the panel
The order is set by what early-access restaurants need.
FAQ
Questions you probably have
How much does it cost?
There's no list price yet. Zahter is in early access; we talk about your restaurant's size and needs and make an offer from there. How early access works
Can I use it outside Turkey?
Not yet in any practical sense. The panel's interface is Turkish, prices are in Turkish lira, and the integrations, fiscal cash register bridge and consent rules are built for Turkey. If you run a restaurant elsewhere and this interests you, write to us anyway; it helps us decide what comes next.
Is the panel available in English?
Not yet. The staff panel is in Turkish today; an English interface is planned. The guest-facing QR menu already works in five languages: Turkish, English, German, Russian and Arabic.
What devices does it run on?
It runs in the browser on a computer, tablet or phone. Nothing to install. Today data is kept in a single browser; several devices working together is in progress.
Does it work with my cash register?
The panel has a bridge connector for Turkish fiscal cash registers (ÖKC) from Ingenico, Beko, Hugin, Profilo, Verifone, Token and PAVO. It pairs with a computer in the restaurant using a 6-digit code. The register maker's approval process may apply; we look at it together during setup.
Do you use AI?
No. Suggestions are calculated from your own records with explicit rules, and every card says why. If something hasn't been measured, the screen says "not measured".
How is guest data protected?
A card only opens once the guest has been informed, marketing consent is kept separate, and a guest's card is deleted on request. Our privacy texts are drafts and haven't been reviewed by a lawyer yet. Privacy and data
Does my menu get translated automatically?
No, you enter the translations on the menu screen. It shows which dish is missing which language.
Let's set up your restaurant together.
Write to us about early access; we'll listen to what you need and set Zahter up for your restaurant with you.