Catering & events
Catering and events on a deposit-to-balance rhythm
Book events with deposits, track outstanding balances, and hand the kitchen a locked headcount — on the same platform as daily service.
Catering falls apart in the gaps — a deposit noted in an inbox, a headcount that changed after prep started. Novaryq runs events on a deposit → balance rhythm with outstanding balances tracked automatically, and hands the kitchen a locked headcount so prep is built on a number that can’t silently move.
Event bookings
Book catering and events with menus, dates and headcounts in one flow.
Deposit → balance
Collect a deposit at booking and the balance on schedule — state tracked end to end.
Outstanding balances
Every unpaid balance is visible and tracked — nothing lives in an inbox.
Locked-headcount handoff
The kitchen preps against a locked number, on the same KDS as daily service.
Same menu, same queue, same reports
Catering isn’t a side system: events use the same menu engine, flow through the same order queue and land in the same reporting as daily service. Available on Growth plans and up.
A booking is a state machine
From enquiry to a locked headcount
Catering goes wrong in the gaps: a deposit nobody chased, a headcount that changed after the order was placed, a balance living in somebody’s inbox.
Booked
Menu, date and headcount captured in one flow rather than reconstructed from an email chain.
Deposit taken
A deposit at booking and a balance on schedule, with the state tracked end to end rather than remembered.
Headcount locked
The kitchen preps against a locked number on the same kitchen display as daily service — not a printout that is one revision old.
Balance settled
Outstanding balances are visible as a list, so chasing one is a task rather than an act of memory.
Run events without the inbox ledger
See deposit tracking and kitchen handoff in a demo.