Verity for restaurants
A restaurant settles and re-settles itself every night. Verity keeps the orders, the stock they consume, the people on shift and the money they produce on one record, so the day can be understood while it is still running.
Works alongside your existing billing setup. Nothing has to be switched off.
Verity / Service
LiveRevenue today
₹2.14 L
Average order
₹1,150
Prep stock
4 low
On shift
17
Needs attention
Illustrative figures. Verity shows your own service in this shape.
How the business runs
A restaurant runs on a very short cycle. Stock arrives in the morning, gets prepped, gets sold across two services, and whatever is left either carries to tomorrow or goes in the bin. Every commercially important thing that happens — what sold, what it consumed, who was on the floor, what was wasted, what the night made — happens inside about twelve hours, and almost none of it is written down in a form that can be compared with last Tuesday.
The billing system knows what was ordered. It does not know that the order consumed four hundred grams of a protein bought at a price that went up eleven percent this month. The roster on the wall knows who was meant to be in. It does not know that Section 3 ran two people short from half past seven and that the average table time went up by nine minutes as a result. Each of those facts exists; none of them are connected.
That disconnection is why restaurant decisions are made on instinct. Menus are changed because a chef believes a dish is not pulling its weight. Staffing is set because Fridays feel busy. Suppliers are kept because switching is a hassle. All of those may be correct, and none of them can be checked.
Verity connects the order, the item it contains, the stock that item consumes, the supplier that stock came from, the person who served it and the revenue it produced. They are records in one system with one history, so the question "which dishes made money last month, and what did they cost to run" is a query rather than an evening with a spreadsheet.
What Verity calls these things
What gets in the way
Everything a restaurant struggles with comes back to the gap between what was sold and what it consumed.
Consumption is invisible until it is a shortage
Ingredients leave stock without leaving a record. The first sign that something is wrong is a server telling a table the dish is finished.
In Verity Stock movement is recorded against the orders that consume it, so a line running low shows up before service rather than during it.
Nobody knows what a dish actually costs
Menu prices are set once and then left alone while ingredient prices move every month. The dish that was your best margin two years ago may be your worst now.
In Verity Ingredient cost is recorded against purchases, so the movement in what a dish consumes is visible against what it sells for.
Wastage is absorbed, not measured
Prep that did not sell, returns and spoilage are dealt with quietly at the end of service and never appear in any number anyone looks at.
In Verity Wastage is a recorded movement like any other, so it can be compared across days, sections and items instead of being felt as a general sense that too much is going out.
Rosters are set on habit
Staffing is planned from a template and adjusted by memory, without reference to what the equivalent day actually produced in covers or revenue.
In Verity Attendance and shifts are records connected to the service they covered, so staffing decisions can be made against what the same day did last month.
Regulars are recognised, not recorded
The staff know the couple who come every second Friday. The business does not, so nothing happens when they stop coming.
In Verity Guests and corporate accounts are records with their history, so the drop-off in a regular or an account is something you can see.
Multiple outlets report in multiple formats
Each kitchen counts differently, sends its numbers in its own shape, and the group picture is assembled by someone every Monday.
In Verity Outlets are locations that roll into the business, so the group view is the same records rather than a reconciliation of five reports.
The complete system
Verity is one system. These are the parts of it a restaurant works with, described in service terms rather than software terms.
Orders
Orders are records with their items, their timing, the section and server that handled them and the stock they drew down.
Why it matters here The order is the only event in a restaurant that touches everything else — revenue, stock, labour and the guest. Recording it properly is what makes the rest answerable.
In practice A Friday service is 186 covers made of 640 items. Those items are what tell you the prawns will not last through Saturday.
Inventory
Stock is held with its supplier, cost and location, and moves as it is received, prepped, consumed by orders or written off as waste.
Why it matters here Restaurant stock is perishable and mostly unbranded. What matters is not a count on a shelf but the relationship between what came in, what sold and what was thrown away.
In practice Receiving twelve kilos, selling the equivalent of nine and logging one as waste leaves a two-kilo gap. That gap is the number worth looking at.
Records
Menu items are records with their components, so a dish is connected to the ingredients it consumes and the price it sells at.
Why it matters here Menu engineering only works if the cost side is current. A recipe held as a document is out of date the first time a supplier raises a price.
In practice A biryani sells 340 times a month. The record shows what those 340 plates consumed and what that stock cost across the same period.
Suppliers
Suppliers are relationships with their orders, deliveries, prices and outstanding balances, connected to the stock they provide.
Why it matters here Most restaurant purchasing happens by phone and is never compared. Which vendor is late, which one has crept up on price, and what is owed are all knowable from the order history.
In practice The vegetable supplier’s prices are up nine percent over four months while the fish supplier missed two deliveries. Both are visible from the same records.
People
Staff, roles and responsibilities are modelled once, and every order, prep step and stock movement shows who owns it.
Why it matters here A restaurant is run by whoever is on tonight, and almost nothing about a service is interpretable without knowing who was responsible for what.
In practice A section’s covers, average order value and comps are attributable to the people who worked it, which is the only fair basis for a conversation about performance.
Work
The day’s fixed tasks are work with an owner, a due time and a state, connected to the service they prepare for.
Why it matters here Restaurant failures are usually a step that did not happen on time rather than a step that went wrong, and a laminated checklist records neither.
In practice Prep for dinner is either marked complete at 16:40 by the person who owns it, or it is visibly not, while there is still time.
Workforce
Assignment, attendance and availability stay connected to the service they covered. Every state is a record rather than a mark on a printed roster.
Why it matters here Labour is the second-largest cost in a restaurant and the one most often planned without evidence. Knowing who was actually on the floor is the beginning of knowing why a service went badly.
In practice Two no-shows in Section 3 on a Friday appear against the same service whose average table time went up. The connection is visible rather than suspected.
Schedule
A timeline of the day’s work with each step’s state and owner, from opening checks through to close.
Why it matters here A restaurant day has a fixed shape — delivery, prep, lunch, changeover, dinner, close — and the failures are almost always a step that did not happen on time.
In practice Prep for dinner service is marked complete at 16:40 or it is not. If it is not, the person who owns it knows before the first table sits.
Relationships
Guests and accounts are records with their visit history, preferences and outstanding balances.
Why it matters here Repeat business is the cheapest revenue a restaurant has, and it is almost never tracked. A corporate account that has stopped booking is a loss nobody notices for a quarter.
In practice The company that used to book a private dining room twice a month has not booked since June. That is a list, not a hunch.
Workflows
Purchases above a threshold, comped meals and stock write-offs move through defined approval steps with a requester and a reason.
Why it matters here The transactions restaurants lose money on are the discretionary ones done at speed during service.
In practice A comped table above the manager’s threshold becomes an approval with a reason attached, not a note in the till.
Reports and analytics
Item performance, revenue by day and section, wastage, labour against covers and supplier price movement come from the operational records.
Why it matters here Restaurant reporting is usually monthly and backwards-looking, which is exactly the wrong shape for a business that resets daily.
In practice Comparing this Friday with the last six Fridays takes a moment, because every Friday is the same records.
Verity AI
Verity AI answers from your own orders, stock and roster records, only shows what the person asking can see, and can turn an answer into assigned follow-ups.
Why it matters here The questions worth asking in a restaurant are asked at eleven at night by someone who is tired, and they need an answer rather than a report to build.
In practice "Which items ran out before nine this week?" returns four, and one instruction raises tomorrow’s purchase against the right supplier.
Locations
Each outlet is a location that rolls into the business, with permissions, reporting and exceptions following the same structure.
Why it matters here A second outlet does not double the complexity of a restaurant group — it multiplies it, because nothing is comparable unless it is recorded the same way.
In practice Three outlets and a cloud kitchen report into one view without anyone reformatting a spreadsheet.
Communication
Comments, notifications and activity attach to the record they concern rather than living in a group chat.
Why it matters here Restaurant context is passed verbally between shifts and lost the moment someone is off for two days.
In practice The note that a supplier substituted an ingredient sits on the delivery record, where the evening chef will actually find it.
Work in motion
These sequences already happen in your restaurant. The difference is that each step becomes a state on a record instead of something someone remembers to mention.
The gap between what was received, what was sold and what was written off is calculated rather than estimated.
The point of the sequence is that it starts from a record rather than from someone opening a fridge.
Staffing stops being a template and becomes a decision informed by the same day last month.
A menu change becomes a documented decision with the numbers that produced it, not an argument between the chef and the owner.
Wastage becomes a number with a trend rather than a bag nobody counted.
The account has a history, so a drop in booking frequency is visible instead of gradual and unnoticed.
Verity AI
Verity AI reads the same orders, stock, roster and supplier records the rest of the system runs on. It answers from your restaurant rather than from general knowledge, and it can turn the answer into work assigned to the person who owns it.
Verity / Ask
Verity AI only returns what the person asking has permission to see.
Without chasing
Each of these runs from the records themselves, at the point the condition is actually met.
When
Stock of an item falls below par
When
An item is marked unavailable during service
When
A rostered staff member does not check in
When
A service closes
When
A comp or discount exceeds the threshold
When
A corporate account goes quiet
What you can understand
Every one of these comes from records the restaurant creates in the ordinary course of service.
None of this requires a separate reporting exercise. It is the same records the restaurant already produces during service.
One system, different ways of seeing it
Everyone works from the same records, and each role opens on the question they actually need answered.
Owner
Did the week make money, and where did it leak?
Revenue against the same period, contribution by item, wastage, labour against covers, outlet comparison.
Restaurant manager
What do I need to fix before service?
Stock against tonight’s covers, roster gaps, prep steps outstanding, items unavailable.
Head chef
What is the kitchen short of, and what is it wasting?
Stock levels, wastage by item, deliveries due, item volumes across recent services.
Purchasing
What has to be ordered and what does it now cost?
Reorder flags, supplier prices and delivery reliability, outstanding payables.
Accounts
What came in and what is owed?
Daily revenue, corporate account balances, supplier payables, approvals awaiting a decision.
Where it is used
Stock recorded with supplier and cost, moving as it is received, prepped, consumed by orders and written off — so the gap between sales and consumption is a number.
Item volume set against current ingredient cost, so menu decisions are made on contribution rather than on which dishes the kitchen enjoys making.
Waste as a recorded movement by item, reason and service, comparable across days and outlets instead of absorbed at close.
Who was actually on the floor, connected to the service they worked and the covers it produced.
Orders, deliveries, price movement, missed dates and outstanding balances against each vendor.
Outlets and cloud kitchens as locations rolling into one view, without anyone reformatting a weekly spreadsheet.
Enquiries, confirmations, staffing and billing against an account with a visible booking history.
The fixed shape of the day — delivery, prep, service, close — as work with owners and states rather than as a laminated sheet.
Plain-language questions answered from the restaurant’s own records, with the follow-up created and assigned in the same step.
Getting there
Your billing or point-of-sale setup does not have to change on day one. Verity maps what you already run — the order records, the stock sheet, the roster, the supplier list — brings across what matters, and introduces the operational layer around it while service continues as normal.
Implementation runs about four weeks: discovery and mapping, configuration, migration, then an ongoing operations partnership.
Questions
Verity AI answers questions from your restaurant’s own order, stock, roster and supplier records. You can ask what sold best this week and what it consumed, which items ran out before nine, how this Friday compared with the last six, or which corporate accounts have gone quiet — and turn the answer into work assigned to the person who owns it.
Yes. Stock is held with its supplier, cost and location, and moves as it is received, prepped, consumed by orders and written off as waste. That makes the gap between what was bought, what was sold and what was wasted a calculated number rather than an estimate.
No. Verity is introduced as an operational layer over what you already run. Your existing order and billing setup is mapped during implementation and continues to work while Verity takes over the operational side — stock, suppliers, rosters, reporting and the questions across all of them.
It shows item volume against the ingredient cost recorded on your purchases, so contribution can be compared across the menu and tracked as supplier prices move. It reports from the records you keep; it does not estimate costs you have not recorded.
Yes. Each outlet or cloud kitchen is a location that rolls into the business, so the group view is the same records rather than a reconciliation of separately formatted reports. Permissions follow the same structure, so an outlet manager sees their site and the owner sees all of them.
Shifts, attendance and availability are records connected to the service they covered, so hours worked can be compared with covers and revenue for the same period. Staffing decisions can then be made against what the equivalent day actually produced.
A single restaurant already runs a kitchen, a floor, a stock room and a supplier list that do not talk to each other. That is the problem Verity solves. Additional outlets use the same structure without additional setup.
Implementation is about four weeks: discovery and mapping of how your service actually runs, configuration to match it, migration of your existing records, and then an ongoing operations partnership rather than a handover and a manual.
Yes. Verity has one permission model across every record, so cost, margin and revenue can be visible to the owner and accounts while kitchen and floor staff see stock levels, prep status and service information.
For most restaurants that is either stock consumption or the gap between rostered and actual labour. Tell us which one and we will show you what it looks like in Verity.