Venue Availability Calendar
Venues in day, week and month views; option and confirmed blocks are shown separately, and a second block cannot be saved for the same venue at the same time.
Venue availability calendar, proposals with online acceptance, BEOs, operations and payments in one banquet software. Weddings, meetings, conferences and trainings move from inquiry to invoice on the same record.
Venues, events, CRM, proposals, BEOs, menus and packages, operations and finance in the same banquet management software; each screen opens according to the user's role.
Venues in day, week and month views; option and confirmed blocks are shown separately, and a second block cannot be saved for the same venue at the same time.
Each event moves through inquiry, proposal, option, confirmed and completed; venue blocks and the attendee list live on the event.
Companies & Clients, Contacts and Follow-ups & Activities; the company card shows event count, won value and open pipeline together.
The proposal goes out by email with a PDF; the client reviews it via a link, accepts the terms and signs to accept it.
BEO lines are created from the accepted proposal; department notes, programme and staff sit in one document, and every publish is a new revision.
Banquet menus link to POS products and per-person cost comes from the recipe; packages and equipment & extras are added to proposals.
Daily Plan, Department Checklist and Kitchen Production & Requirements; portions are converted into a raw-material list from recipes.
Payment schedule, deposits, payments, extra charges and invoicing; reports by monthly revenue, event type, sales rep, source and lost reason.
Proposals are prepared in Turkish, English, German or Russian, and whether prices include VAT is chosen per event. A sent proposal goes out by email with a PDF attachment and is locked; changes open as a new version. The client opens the link in the email, reviews the proposal without logging in, accepts the terms and signs; once accepted, the event is confirmed.
The BEO brings food, technical, décor and accommodation lines, department notes, the programme and assigned staff into one document. Every publish is a new revision, and changed sections are marked in the document. If the Tasks module is enabled, tasks are opened only for the departments affected by the change.
Each event gets a payment schedule of deposit, interim payment and balance, and overdue instalments are flagged. If you also use the hotel software, payments are posted to the hotel cash desk and the company's account card, the invoice is written as a draft to hotel invoices and the Turkish e-invoice is sent from there.
Room blocks show from group reservations; payments flow to the cash desk and accounts, invoices to e-invoicing. With the related modules enabled, BEO products are deducted from stock and requirements become purchase requests.
Explore the Hotel Management SoftwareA wedding venue, congress centre or event space can run on the Banquet licence alone; users land directly in the banquet panel at login.
The event form on your site sends inquiries straight to the panel via the Banquet API; showing venues and availability on the site is optional.
Expired options, upcoming events and follow-ups are on the Dashboard; the team receives reminders as notifications.
Yes. Banquets & Events (BEO) is a Chexta module enabled with its own licence. In a business with only the Banquet licence, users go straight to the banquet panel at login; if you use the hotel software, the module opens from the top menu. Screens open with five role-based permissions: view, sales, manage, finance and settings.
A BEO (Banquet Event Order) is the work order that brings together an event's menu, room setup, technical and décor needs, programme and department notes. In Chexta each event has a single BEO; every publish is stored as a new revision and changed sections are marked in the document.
The proposal is emailed with a PDF attachment, and the link in the email opens the proposal page. Without logging in, the client reviews the proposal, accepts the terms and signs on screen to accept it, or rejects it. Accepting confirms the event, and the sales rep is notified by email.
No. A second block cannot be saved for a venue in the same time range; even if two users save at the same moment, the checks run one after the other. Option blocks hold the venue too, and expired options are listed on the Dashboard.
Theatre, classroom, U-shape, boardroom, banquet (round tables) and cocktail (standing). Capacity is entered per setup for each venue; a warning appears if the expected guest count exceeds the chosen setup's capacity.
Proposal and BEO documents are prepared in Turkish, English, German and Russian, and the proposal email text follows the chosen language. The banquet screens are in Turkish.
If you also use the hotel software, payments are posted to the hotel cash desk and the company's account card, the invoice is written as a draft to hotel invoices and the e-invoice is sent from there; room blocks show from group reservations. With the Tasks module, BEO tasks go to departments; with HR, staff are assigned to events; stock and purchasing connect depending on your licences.
Yes. With the Banquet API, the event form on your website sends the inquiry straight to Banquet; it appears in the event list and the team is notified. You decide on the API & Integration screen which venues and availability information appear on the site.
Define your venues and capacities, add your menus and packages, and send your first proposal. Fill in the form for a demo or write to us.