Web Mister AI · Product family

One stroke.Floor to ledger.

The till, the pass, the store room and the books are one system, not four that reconcile on Sunday. A shift closes and the entry is already posted — tagged to its branch, its cost centre and the channel it came through.

See the intelligence Walk the floor

The Single Stroke — the Web Restaurant & Café product mark

/app/restaurantLive restaurant dashboard · real product

The Web Restaurant & Café dashboard — sales, margin, inventory value, and operational alerts for expiry and shortages

0
screens in the pack
0
operating sections
0
accounting core

What is actually in the box

A working restaurant, not a price list.

Eighty-two screens across nine sections — from the moment an order is rung up to the moment its cost lands in the income statement.

The floor

Restaurant dashboard
Point of sale
Kitchen display (KDS)
Tables
Floor plan editor
Reservations
Delivery & platforms

The menu

Items & recipes
Menu & modifiers
Combos and meal deals
Price lists
Assembly formulas (BOM)
Service charge

The store room

Restaurant inventory
Waste & spoilage
Shortages & reorder
Stock balances
Internal transfer
Adjustments
Physical stocktake
Valuation

Money & people

Shifts & closing
Day close
Gift cards & stored value
Sales by channel
Tips & commissions
Cashier performance
Payroll run
Trial balance & income statement

The identity

The Single Stroke

One unbroken line draws the saucer, the cup and its handle, then releases as steam that curls twice and ends in a point of light — the service, from setting down to carrying away.

01
The Saucer
The table is set. Nothing has been ordered yet.
02
The Cup
The order takes form — an item, a modifier, a price.
03
The Handle
It is carried: fired to the pass, plated, served.
04
The Rising Point
The shift closes, and the service becomes an entry.

Platform

A till that closes its own books.

Most restaurant software sells, then exports a file for the accountant. Web Restaurant & Café is a restaurant-shaped surface over one shared accounting core — the sale, the stock movement and the journal entry are the same event, written once.

The shift is the unit
Open a session, sell against it, take cash in and out, then close it and read its summary. Day close posts the result to the ledger rather than printing it for someone to retype.
Recipes make cost real
An item is not a price with a name. It is a recipe, and selling it moves the ingredients out of stock — which is what makes food cost a measured number instead of an estimate.
Channels settle separately
Dine-in, takeaway and each delivery platform are tracked as channels, with platform commission settled rather than absorbed into a lump.
One entity, one payroll
HR and payroll are deliberately not forked. They stay at establishment level and open inside the restaurant shell, because a branch is not a separate legal entity with a separate payroll engine.

Point of sale

Ring it up. It is already accounted for.

The counter runs on the platform's shared POS engine — sessions opened and closed, cash in and out, discounts, returns and stored value. Nothing about the money is a separate spreadsheet.

The session is the unit
Open, sell, take payments in and out, close, read the summary. The till is part of the accounting system, not a drawer beside it.
Every sale carries its channel
Dine-in, takeaway or a named delivery platform — recorded at the sale, so the channel report is a read rather than a reconstruction.
Stored value that is a liability
Gift cards are carried as a stored-value obligation with its own report, not as cash received and forgotten.

/app/restaurant/pos

The pass and the floor

The kitchen sees the order, not a printout.

Tickets land on the kitchen display as they are fired, and the floor is a map you edit rather than a list you memorise — tables, zones, reservations and their state in one view.

A display, not a printer
Orders arrive at the pass with their modifiers and their timing, and clear when they are served.
The floor is editable
A plan editor for zones and tables, so the map matches the room after it is rearranged rather than a month later.
Reservations against real capacity
Bookings are held against the same tables the floor is using, so a full room cannot be double-sold.

/app/restaurant/kds

Menu & recipes

A dish is a recipe, not a price.

Every item resolves to ingredients and quantities. That is what lets the system move stock when a plate is sold, and what lets it tell you the plate stopped being profitable three weeks ago.

Recipes drive consumption
Selling a dish depletes its ingredients at their recipe quantities, so the store room reflects the pass without anyone keying it.
Modifiers and combos included
Add-ons and meal deals carry their own cost, rather than being priced as if they were free.
Assembly formulas
Prepared components — a sauce, a dough — are built once and consumed by the dishes that use them, aggregated per ingredient rather than per line.

/app/restaurant/recipes

The store room

What left the shelf, and what should have.

Sales say how much ought to have been consumed. Inventory says how much actually was. The difference is where a kitchen quietly leaks, and the system reports it per item and per shift.

Waste is recorded, not absorbed
Spoilage and waste are their own entries against their own accounts, so margin does not silently swallow them.
Shortages before service
Reorder points against real balances, so the missing ingredient is known before the ticket is fired, not during it.
Valuation from movements
Movement-based valuation with landed cost — the inventory figure on the balance sheet is the one the store room shows.

/app/restaurant/waste

Shifts & closing

The day closes into the ledger.

Day close is not a report. It reconciles the sessions, settles the channels and posts the result — so the income statement is current the next morning without anyone assembling it.

Sessions reconciled first
Cash counted against cash expected, per session and per cashier, before anything posts.
Platform commission settled
Each delivery platform's commission is separated from revenue rather than netted into it.
One posting, fully tagged
Branch, cost centre and channel travel with the entry, so a report never has to guess where a figure came from.

/app/restaurant/day-close

Restaurant intelligence

Three engines, and each shows its denominator.

No chat box bolted onto a database. Three deterministic engines run where a kitchen actually loses money — a menu priced once and never re-checked, and stock that leaves without a sale behind it. Neither needs an AI provider or an API key, so nothing leaves the system to produce them.

Live plate cost

Re-computes each dish from its recipe and today's purchase prices, compares it to the previous period, names the ingredient responsible, and proposes one action. The target is a 65% margin — a 35% food cost — and it will not recommend a rise above 10%; beyond that the answer is to move the dish off the front page, not to charge more for it.

A menu is priced once and then forgotten while supplier prices move weekly. The dish that earned 65% may be losing today, and nothing says so, because the cost is a stored number rather than a computed one.

An ingredient with no current price makes the cost a lower bound, not a final figure: the margin is returned as null and the coverage is declared. If the recipe unit and the price unit differ, the ingredient is rejected outright — no silent conversion adds kilograms to grams. Drift is measured only across ingredients priced in both periods.

Theoretical consumption gap

Sales say how much should have been consumed — dishes sold times their recipes. Inventory says how much actually was. The difference, per item and per named shift with its supervisor, turns “there is waste somewhere” into “the waste is this item, in this shift”.

Waste does not announce itself as one large number. It looks like a normal number, slightly wrong, repeated across every service.

Units are never summed across each other: 0.2kg and 200g do not become 200.2. Where one item appears in two units within a shift the row returns a unit mismatch and no figure at all. A shift with no recorded stock movement is reported as unmeasured, not as zero waste — “no difference” and “not measured” are different statements. The display threshold hides rows but never removes them from the totals, and the number hidden is declared.

The cross-vertical twin

Registered against the restaurant scope and deterministic like the other two, it models this pack against the other trades on the same ledger — a clinic, a pharmacy, a hotel — in one shared currency of truth.

A vendor who sells only restaurant software has no second vertical to compare against. The source file calls this the moat that cannot be copied, and it exists only because every pack posts into one core.

Comparisons are presented as candidates for review, never as verdicts, and never as an instruction to change how the kitchen runs.

All three are deterministic and produce candidates for a manager to review — never an automatic decision, and never a price change applied on their own.

/app/restaurant/reports

Architecture

Separation you can point at.

These properties hold because of how the data is written, not because of a policy asking people to be careful.

Its own permission set
Restaurant resources are a separate namespace, so access to one product grants nothing in another.
Guarded twice
A server-side guard runs before any data loads, mirroring a database guard on every write. Hiding a button is not isolation — a direct call still lands.
Scope on every call
Browser calls carry the product scope, so the invoice and its journal entry are tagged at the database rather than by the interface.
Separation of duties
Approvals and duty separation are configured per establishment, and the audit log records who changed what, when, and from which value.

Described from the product's own access-control implementation. No compliance certification is claimed.

Part of the Web Mister AI family

One core. Many counters.

Web Restaurant & Café is one product in the Web Mister AI family, sharing the accounting core with every other pack. That shared core is why a shift close lands in the same statements as a pharmacy's dispensing or a hotel's night audit — and why the platform can compare them at all.

Web Restaurant & CaféAccounting (ERP)ClinicPharmacySalon & SpaHotel & ApartmentsSchool & KGTraining CentreFuel StationsCar RentalHR & Payroll

Products listed are packs present in the platform's registry, each marked ready. Web Restaurant & Café is the product described on this page.

Get started

See it run one service.

The fastest way to judge this is to follow one ticket — rung up at the counter, fired to the pass, drawn out of the store room, and posted when the shift closes.

Explore the platform

Request a demo

One stroke.Floor to ledger.