Add-ons you sell
- Keep a catalogue of add-ons, such as platters, a cake, a table upgrade or parking.
- Each add-on has a price and a tax rate.
- On ticketed events, alcohol cannot be sold as an add-on.
Banquet and event booking software takes a function from enquiry to the day itself. Zentaro Serve builds a proposal from your packages and lets the client approve it. It collects advances by payment link and handles party bookings. Task reminders go to your teams, so the kitchen is never told late.
The enquiry becomes a priced proposal from your buffet packages, with course groups.
Approval is verified by OTP on the customer's own phone. Nobody on your staff marks it accepted for them.
The advance is tracked against the event and settles to your own account.
The customer, your manager and the teams you assign are reminded as the date approaches.
A booking can ask for an advance, under a cancellation policy you set.
Take a party's order days ahead, with the advance collected and the balance tracked.
A diary remembers the event. Zentaro Serve runs it.
Watch the chain. Green means the platform did it; blue means your customer did it themselves.
Date, covers, budget and requirements go in once — "Mehta reception, 120 covers, 14 December".
Pick the package, set the covers — the proposal prices itself. No spreadsheet, no re-typing the menu.
The customer gets a link to a proposal page of their own — no app to install, nothing to print.
The yes is OTP-verified on the customer's own phone. Nobody on your staff "marks it accepted" on their behalf — it is genuinely theirs, with a record.
The advance is requested the moment they approve. Paid, tracked and receipted against the event — UPI or card, settled to your own account.
Your customer is reminded before every due date — balance, confirmation cut-offs. Your manager sees exactly what's pending. The teams you've assigned — kitchen included — get their preparation task reminders as the date approaches. Nobody keeps a call-back list.
Everyone knows what they own and when. The function you quoted three weeks ago executes without anyone re-reading an email thread.
You quoted once. The platform chased everything else.
The same discipline, table-sized: a booking that hasn't paid isn't allowed to quietly block your Saturday night.
Party size, table, time — and the advance the booking is worth.
The guest pays from their phone. No card machine over the phone, no "transfer to this number".
A paid advance holds the table. Your cancellation policy decides what happens to the advance if the guest does not come.
The advance is sitting against the reservation and settles into the final bill — no arithmetic at the table.
Big orders placed days ahead — pickup or delivery — run on the same rails: paid in advance, on record for the kitchen, nobody surprised.
Items, quantity, pickup or delivery, date and time — with special instructions attached to the order, not to somebody's memory.
Your advance percentage is applied and collected by payment link; the balance is tracked against the order until it's settled.
The order sits in Zentaro Serve with its date, time and instructions, so the kitchen can plan for it. Saturday's order is not on a sticky note.
Balance settles on handover and the order closes with its whole trail: who ordered, what was paid, when it was ready, when it left.
You set the rules once in Payment rules and Reminders. Then Zentaro Serve does these jobs on its own.
When you approve a proposal, the guest gets a secure link for the advance. Once per proposal.
The event moves to Confirmed as soon as the advance arrives. You can switch this off.
Reminders before the due date, on the day and after it, up to a limit you set. Each one carries the payment link.
After the due date the guest is reminded at the spacing you set, up to a cap, and the booking is marked overdue.
An unpaid link expires after the days you set, so an old link cannot be paid.
If a payment confirmation never arrives, Zentaro Serve checks with the payment provider and records the payment once.
An approved proposal that is not paid is released after a warning to the guest.
The day before a confirmed event, the guest gets a "see you tomorrow" message. Your managers are told about money still due. You can set more reminder days.
A part-paid event gets one balance reminder three days before.
Guests of yesterday's events get a thank-you message.
Confirmed events turn Completed once their date has passed, so your counts stay right.
Decor, DJ, photography and other tasks get reminders as the date comes closer.
What an event needs goes into the vendor's draft order on its order date.
Managers get one alert for each new request from a guest. Built, off by default. Ask us to switch it on for you.
Temporary holds on party areas and ticket seats are freed when they expire. Built, off by default. Ask us to switch it on for you.
Automation here follows your settings. See how automation works →
Build your packages the way you actually sell them: courses and sections with choice rules — "any two starters, one main per cover, dessert counter included". Set the per-cover price, a minimum and a guaranteed cover count, even different variants of the same package. When the next enquiry comes, the quote is a selection, not an evening with a calculator.
The problem you know
What it is not
Who it is for
Talk to us. Talk to us
It becomes a proposal. The guest approves it with an OTP. An advance is paid and a task list is made for the day.
Yes. Reservations can chase their own advance.
Yes. Party orders are supported, ordered ahead and ready on time.
It runs a function from enquiry to the day itself: proposal, approval, advance, tasks and readiness.
The advance is requested by a payment link when the client approves. It is tracked against the event and settles to your own account.
Yes. The customer gets a page of their own, can negotiate, and approves with an OTP.
Link the days into one event group, so you plan and track them together.
Yes. Table booking is part of the product. It has advance payment, packages, add-ons and a cancellation policy.
Build one real proposal and let a client approve it from their own phone. That moment sells it better than this page can.
Last updated: