Verity for cafés
A café lives on throughput per hour, wastage at close and the cost of a cup. None of the three are visible in a daily total. Verity records them where they happen.
Runs alongside your existing billing setup.
Verity / Café
LiveTakings today
₹52,400
Average ticket
₹125
Close wastage
₹3,100
Peak cover
2 of 3
Needs attention
Illustrative figures. Verity shows your own café in this shape.
How the business runs
A café does four hundred transactions a day at a small average ticket. Nothing about that business is decided by a single event. It is decided by whether the morning peak was staffed to meet it, by how much prepared food went in the bin at close, by whether the cost of milk moved without the menu moving, and by whether the regulars who come four times a week are still coming.
All four are invisible in a daily takings figure, which is what most cafés actually manage against. The day made money or it did not, and the reasons are inferred afterwards.
Throughput is the first. A café’s revenue is concentrated in a small number of hours, and being one person short during those hours does not just slow service — it loses the customers at the back of the queue, who do not appear in any report because they never transacted.
Prepared-item wastage is the second, and it is uniquely a café problem: sandwiches, pastries and cut fruit are made ahead against a forecast, and everything unsold at close is a total loss. The forecast is usually a habit rather than a calculation from what the same weekday actually sold.
Verity records the transaction with its hour, staff and items, the stock those items consumed, the wastage at close and the regular who bought it, so the four things that decide the year become measurable rather than felt.
What Verity calls these things
What gets in the way
Café problems are all about timing — which hour, which day, which prep decision — and daily totals average every one of them away.
The peak is understaffed and nobody sees the cost
Being one short between half past eight and ten does not show up as a loss. The customers who left the queue never transacted.
In Verity Transactions carry their hour and the roster carries who was on, so throughput per staffed hour is comparable across days.
Prepared items are made on habit
The same quantity is prepped every day regardless of what the equivalent weekday actually sold, and the difference goes in the bin.
In Verity Wastage is recorded by item at close against what sold, so prep quantities can be set from the same weekday’s history.
Ingredient cost moves and the menu does not
Milk, beans and packaging costs move several times a year on a menu price that moves once, and on café margins that is the whole difference.
In Verity Purchase cost sits on the ingredient, so cost movement against the drinks it feeds is visible per item.
Regulars leave quietly
A café’s revenue is built on customers who come several times a week, and one who stops is worth more than a dozen one-off visits — but nothing counts them.
In Verity Repeat customers are records with visit frequency, so a drop in the regular base surfaces as a number.
Part-time rosters are a scheduling puzzle nobody has data for
Availability, shift swaps and no-shows are managed by message, and the roster is built without reference to what each hour actually needs.
In Verity Attendance and shifts are records connected to the hours they covered, so staffing follows demand rather than a template.
A second outlet is not comparable
Two cafés with two prep habits and two rosters produce two sets of numbers that cannot be set against each other.
In Verity Outlets are locations rolling into the business, so throughput, wastage and ticket are directly comparable.
The complete system
One system across transactions, stock, prep and staffing. These are the parts a café works with.
Orders
Every transaction records its items, its hour, the staff member and the stock it consumed.
Why it matters here A café’s only meaningful revenue analysis is by hour and by item. A daily total cannot tell you the morning peak failed.
In practice Four hundred and eighteen transactions concentrated in three hours, against a roster that treated the day as flat.
Inventory
Stock is held with supplier, cost and reorder point, and moves as it is received, consumed by drinks and items, or written off at close.
Why it matters here Consumption per drink is the entire cost side of a café, and a cost movement in milk affects most of the menu at once.
In practice An eleven percent rise in milk cost, mapped to the sixty percent of drinks that use it.
Work
The day’s fixed tasks are work with an owner, a due time and a state, including the prep quantities set for the day.
Why it matters here A café day is a sequence of timed tasks, and the failures are tasks that did not happen before the peak arrived.
In practice Prep completed and recorded at 07:40 with the quantities used, which is what makes tomorrow’s forecast better than today’s.
Workforce
Assignment, availability and attendance stay connected to the hours they covered.
Why it matters here Part-time rostering is a café’s hardest recurring administrative job and its biggest controllable cost.
In practice Two staff on at nine when the same weekday historically needs three, flagged the day before rather than during the queue.
People
Staff are modelled once, and every transaction, prep task, wastage record and refund carries who handled it.
Why it matters here Throughput per person during peak, and attachment of food to drinks, both vary by individual.
In practice Transactions per staffed hour by person, from the transactions themselves.
Relationships
Repeat customers and corporate accounts are records with their visit frequency, spend and any credit position.
Why it matters here A café’s economics rest on frequency rather than on ticket size, and frequency is only measurable if the customer is identified.
In practice Thirty-eight regulars who visited four times a week until this month and have not returned.
Suppliers
Suppliers are relationships with their orders, delivery reliability, price movement and balances.
Why it matters here Café purchasing is frequent, small and unexamined, and price creep passes straight through a thin margin.
In practice Three price movements from one supplier this year against one menu change on the café’s side.
Reports and analytics
Throughput per staffed hour, item mix, wastage, cost movement, regular retention and outlet comparison come from the transactions.
Why it matters here Daily totals hide every café-relevant variable. Hourly and item-level records are the only useful resolution.
In practice This Tuesday’s morning peak set against the last six Tuesdays, in the same shape.
Workflows
Refunds, comped items, wastage write-offs and price overrides move through defined steps with a recorded reason.
Why it matters here At a hundred-and-twenty-rupee ticket, a handful of unrecorded comps a day is a real number by month end.
In practice A comp above the shift lead’s threshold becomes an approval rather than a decision at the counter.
Verity AI
Verity AI answers from your own transaction, stock, roster and customer records, respects permissions, and can create assigned follow-ups.
Why it matters here The owner’s questions are about hours and items and need answering at close, not at month end.
In practice "Which hours were understaffed against their usual throughput this week?" returns the pattern with the roster task raised.
Records
Drinks and prepared items are records with their components and standard quantities.
Why it matters here Consumption per item is what turns a milk price rise into a specific margin number rather than a general worry.
In practice A drink’s recorded components make the effect of a supplier increase calculable rather than estimated.
Locations
Locations roll into the business, with stock, staffing and reporting following the same structure.
Why it matters here Two cafés only teach you anything if they are recorded identically.
In practice Throughput per staffed hour and wastage rate, comparable across outlets.
Communication
Notes, notifications and activity attach to the record they concern.
Why it matters here Café knowledge is handed over verbally between part-time shifts and is lost within a day.
In practice The note that a supplier substituted a product sits on the delivery, where the closing shift will see it.
Work in motion
These are what a café already does. Recorded with their hour, they become the numbers that set tomorrow.
This single loop is the difference between prepping on habit and prepping on evidence.
The cost of a short peak is invisible in takings, which is why it repeats.
On café margins an ingredient move that goes unnoticed for a quarter is a meaningful loss.
A café regular is worth many times a one-off visit and is the least tracked customer in hospitality.
Recording wastage at close is what makes the next forecast possible.
Verity AI
Verity AI reads the same transaction, stock, roster and customer records the café creates as it trades. It answers from your own café, only shows what the person asking can see, and can turn the answer into work assigned to a shift lead.
Verity / Ask
Verity AI only returns what the person asking has permission to see.
Without chasing
Each runs from the café’s own records at the point the condition is met.
When
Wastage on an item exceeds tolerance
When
A shift is short against the hourly pattern
When
An ingredient cost rises
When
Stock falls below reorder before a delivery day
When
A regular’s visit frequency drops
When
A comp or refund exceeds the threshold
What you can understand
Throughput, wastage and cost from the transactions themselves.
All of this follows from recording the transaction with its hour and the wastage at close, which takes no additional effort during service.
One system, different ways of seeing it
Everyone works from the same records, and each opens on what they need.
Owner
Where is the margin going?
Throughput per staffed hour, wastage cost, ingredient cost movement, regular retention, outlet comparison.
Café manager
Is tomorrow set up properly?
Roster against the hourly pattern, prep quantities, stock before delivery day, approvals pending.
Shift lead
What has to happen this shift?
Opening and prep tasks, stock on hand, staff on, wastage to record at close.
Where it is used
Transactions recorded with their hour against who was rostered, so a short peak becomes a measured cost rather than an invisible one.
Wastage at close recorded by item against what sold, so prep quantities are set from the same weekday’s history rather than from habit.
Cost movement mapped through recorded components to the drinks and items it affects, so a milk rise is a per-item margin number.
Visit frequency on the customer record, so the four-times-a-week regulars who stop are visible as a number.
Availability, swaps and attendance as records connected to the hours covered, so the roster follows demand.
Stock consumed reconciled against sales with wastage recorded separately, so the unexplained gap is isolated.
Discretionary counter decisions as approvals with reasons, which matter at a small average ticket.
Throughput, wastage and ticket comparable across cafés because every outlet records the same things the same way.
Getting there
Your billing setup and supplier arrangements are mapped during implementation and continue to run. Stock, suppliers, recipes and customers are brought across, and Verity is configured around the way the café already works its day.
Implementation runs about four weeks: discovery and mapping, configuration, migration, then an ongoing operations partnership.
Questions
Verity AI answers questions from your own transaction, stock, roster and customer records: which hours were understaffed against their usual throughput, what was wasted at close and which items repeat, which ingredient costs moved without a menu change, which regulars have stopped visiting. Each answer can become a roster or prep task assigned to a shift lead.
No. Billing continues and is mapped during implementation. Verity is the operational layer over it — stock, prep, wastage, rostering, suppliers and the reporting across them.
Wastage is recorded by item at close against what actually sold, so prep quantities can be set from the same weekday’s history. That loop is the main difference between prepping on habit and prepping on evidence.
Transactions carry their hour and the roster records who was on, so throughput per staffed hour is comparable across days and a shift that will be short can be flagged the day before rather than discovered during the queue.
Drinks and prepared items are records with their components, so a cost movement in milk or beans is mapped to every item that uses them and margin is recalculated per item rather than estimated.
Repeat customers and office accounts are records with visit frequency and spend, so a drop in the regular base — which is where a café’s revenue actually comes from — is a number rather than a feeling.
Yes. Throughput, wastage, cost movement and regular retention are all single-site problems. Additional outlets simply make them comparable.
About four weeks: discovery and mapping of how the café runs its day, configuration, migration of stock, recipes and suppliers, then an ongoing operations partnership.
Those two decide most of a café’s year and neither shows up in a daily total. Tell us which one worries you more.