Everything a shift involves.

Floor plan, bills and payment

You see your room’s layout on screen: which table is occupied, how long it has been open, what it owes. At a shift change nobody has to ask what happened on table seven.

• Floor plan split into sections — which table is busy, and for how long
• Split payments — some in cash, the rest on a card
• Voids: the reason, the time and who did it are recorded
• Two devices cannot corrupt one bill — the second change is rejected
• A "bill please" flag — the table says it is waiting

The ticket prints the instant the order is saved

Each station gets its own printer: hot kitchen, cold kitchen, bar, till. The ticket goes to whichever station the item belongs to; the bartender never has to read the kitchen’s ticket.

If one printer fails the others do not sit and wait. The broken one holds its own queue and prints what is waiting, in order, once it is fixed.

• A separate printer per station
• Turkish characters print correctly (WPC1254)
• The cash drawer opens with the ticket
• Reprints say on the ticket which one they are a repeat of
• One printer failing does not stop the others

A menu change is not a trip to the printer

Every table has its own code. The customer scans it and the current menu opens. The moment you change a price the menu has changed.

The menu is public, but a table’s code cannot be guessed, and the address grants nobody the right to place an order. The QR menu only reads.

• No app to install
• Photographs, allergen and ingredient notes
• Hide a sold-out item with one tap
• Different menus and prices per branch

A table is never promised twice

You take the phone booking at the till: the time, the party size and the table. A second reservation that clashes on the same table is rejected by the system — no evening ends with "but I gave that table away too".

On the floor plan a held table reads "RESERVED" with its time. A waiter cannot think it is free and seat somebody else. When the guest arrives, one tap seats them and opens their bill; the rest is ordinary service.

• Clash checking — a table is given once for a given time
• Guest book: found by phone number, with their notes and how often they have been in
• No-show records — how often each guest failed to arrive is on their card
• Deposits: the amount taken is recorded and comes off the bill automatically
• The reserved table and its time appear on the floor and waiter screens

Shifts, leave and clock-ins in one register

Employment records, annual leave balance, weekly shift plans and actual clock stamps live in the same module. No separate Excel roster, no “who is in today?” on WhatsApp.

Staff see their own shift; managers approve leave and write the schedule. Clock-in can follow shift hours automatically or with one PIN tap — late arrivals can ask the manager for approval.

• Roster: start date, annual leave entitlement, weekly off days
• Leave book: pending, approved, rejected — balance stays live
• Shift schedule: weekly view, quick fills from templates
• Time stamps: clock in/out, approval flow outside shift hours
• Salary field is encrypted behind its own permission — not everyone needs to see pay

Ingredients move with the sale

"How much coffee have I got?" should not be a spreadsheet question. Define the recipe and stock comes down on its own as the order is paid. Counts and waste live in the same ledger.

• Recipes and automatic deduction: Attach an ingredient list to each menu item. When the payment closes, the quantities leave stock — you never write a goods-out note by hand.
• Stocktakes: Run a periodic count and the system shows the difference. Approving the count corrects the stock.
• Low-stock warnings: A notification for anything past its critical threshold. You know before the kitchen tells you it has run out.
• Movement ledger: In, out, waste, count correction — the reason and the time of every movement are recorded.
• COGS report: The cost of goods sold is reported, so you see profitability product by product.

From the till to the ledger, without retyping

The day’s sales land in the books on their own — one Z summary line per trading day. You do not have to sit down in the evening to assemble the file for your accountant.

• Cash, bank and accounts: Cash and bank accounts kept apart; supplier and customer balances with their statements. Who you owe and who owes you, on one screen.
• Income and expenses: Rent, staff, purchases. Category by category, and which line moved the month.
• Purchase and sales invoices: Enter a supplier invoice, record its payment, and let the account balance update itself.
• P&L, VAT, cash flow: Four ready reports: profit and loss, a VAT summary, cash flow and account balances. Whatever your accountant asks for is usually inside one of them.
• Reconciliation: Does the money in the drawer match the figure in the system? The end-of-day reconciliation shows the difference the same day.
• Recurring expenses: Rent, electricity, subscriptions: define them once and they post to the ledger every month on their own.

Measurement, not guesswork

The difference between "I think this month went well" and "revenue is up 18% and voids halved" is knowing what to do next. It is all ready the moment you close the day.

• Day summary: Revenue, number of bills, average spend and the value of voids. You see it on one screen as you close the till, and whether the count balanced is obvious there.
• Revenue over time: By day, week, month and year. Compare this week with last, this month with the same month a year ago — that is the only way to tell a seasonal dip from a real one.
• Payment split: Cash, card and online, separately. If the cash in the drawer does not match the cash in the report, the gap shows up the same day.
• Waiter performance: Who opened how many bills and took how much. The average falls out of it, so bonus and rota conversations happen over numbers rather than impressions.
• Void tracking: Every void records its value, its reason, its time and who did it. It is the shortest route to finding where the loss leaks out — and the record cannot be deleted.