Everything in one app
Four invoices, and everything underneath them
Each of these is a product somebody else sells on its own. The reason to have them in one place is not the bill — it is that the rota knows what the clock-in recorded, and the stock count knows what the recipe sold.
Rotas and clock-in
instead of PlandayBuild the week, publish it, and let people clock in from their own phone.
Stock and ordering
instead of SupyCount as a round, see what the variance cost, and send the supplier order.
Daily checks
instead of Check65Opening, closing and temperatures — with photos and readings where a tick is not enough.
Team and training
instead of All GravyChat, announcements, handbooks and training, in the app everyone already has open.
Also included
No page of their own yet. They are in the product all the same.
Bookings
A diary, a table plan, pacing, and a booking page for guests.
Payroll and bookkeeping
Hours to gross pay and tronc, suppliers to P&L, per site.
Roles you design
Start blank. Choose, per feature, what each role can see and change.
Guest and staff feedback
What guests say and what the team raises, in one place.
And what it doesn’t do
The fastest way to find out this is not for you.
Take the payment
your EPOS staysZudaya is not a till. Keep the one on your counter and the card machine beside it. What matters here is what comes out of it at the end of the night.
File with HMRC
payroll stops at grossHours become gross pay and a tronc split per person. PAYE, National Insurance and RTI filing need HMRC-recognised software, and that is not us.
Work for any business
restaurants onlyNo salons, no retail, no "any industry". Every screen assumes a kitchen, a service, and a rota that changes on a Thursday.
See it on your own numbers
Tell us how many sites you run and what you use now. We set the demo up around that and walk you through the parts that apply.