Event catering

A wedding has four hundred details. You should type none of them twice.

The enquiry becomes an event, the event becomes a quote, and the customer accepts, changes and pays against it themselves. What reaches you is the work — the run sheet, the crew and the number at the end.

What it does

Four things, and they are the whole job

Everything below ships today. Nothing here is a roadmap item.

The dates you can take, and the ones you cannot

One resolver decides what a day is — open, limited, busy, full, blocked — and every surface reads the same answer. A booked wedding publishes as a shape and a time; the couple on it are nobody else's business.

  • Public availability widget
  • Capacity that refuses to over-promise
  • A blocked day carries no reason

A quote your customer can accept and pay

The enquiry email is read into a real event, the reply and the quote are drafted from it, and one link carries the itemised quote, the terms and the deposit. The booking lands on your board and your calendar.

  • Itemised quote with the date priced in
  • Deposit taken on the quote page
  • Google Calendar in step from the moment it is booked

The customer runs their own event

Their portal moves the start time, adds the grazing board, gives you the dietaries and the venue access, and pays the balance. Every one of those lands as a change on the job rather than an email you have to action.

  • Change requests priced before you agree to them
  • Dietaries and access collected from the customer
  • Balance paid without an invoice chase

What the event made, not what it billed

Price per head and food cost per head on the same line, with crew, travel and fuel against it. Where a cost cannot be worked out the event says which input is missing instead of calling it zero.

  • Per-event P&L
  • Food cost from your own supplier prices
  • A gap is named, never rounded to $0

By occasion

The same product, whatever is on the invitation

Weddings

Seated dinners, canapés on arrival, a run sheet the venue can read.

Corporate & conference

Recurring orders, several rooms, one invoice and one contact.

Private parties

Birthdays, anniversaries and family gatherings, quoted in minutes.

Fundraisers

Charity dinners and community events, costed before you commit.

The details, moving

Four hundred details, typed once

One event, one screen. Change the bump-in time and the schedule, the crew and the customer's own copy all move with it — because they are reading the same event, not their own copies of it.

Hartwell Wedding
Confirmed

Hartwell Wedding

Sat 26 September · 80 guests · Stonefields Barn

Value$6,200
Bump in 07:30 Service 12:00 Crew 6
Roadmap
List Schedule People Run sheet
  • 07:00Bump inVan loaded, esky in
  • 09:30SetupTables, grazing board
  • 12:00ServiceFull crew
  • 15:30Pack downStrip and load
07
09
12
15

The same steps on a clock, so overlaps show

Hartwell Wedding — run sheet

The sheet you print, copy or send

Print
Run sheet sent to printer
Team
Jack R Service · 12:00–15:30
Dana M Drop a shift here
Menu
Grazing tableon arrival
Slow lamb shouldershared main
Charred greens, three saladssides
Dessert grazingto finish
Money
Revenue$6,200
Food & goods−$1,240
Crew−$836
Overheads−$540
Fees−$112
TravelNo distance on this event
Net$3,472

Margin withheld — one cost is unknown

Today

Hartwell Wedding

Sat 26 Sept · 80 guests

07:00Bump in
09:30Setup
12:00Service
15:30Pack down

The same event, in your pocket

03In their words

Caterers who love CaterCloud

The moment I realised this was actually working was waking up in the morning and having the leads in my inbox already — without chasing the business. I've gone from one booking a month to three or four.

Michelle

Owner, Michelle's Catering

50–60% of leads converted

Michelle, Michelle's Catering
1 / 5

Start

Free to start, and nothing is feature-locked

Every feature is on every plan. The plans differ on volume, not on capability.

By using CaterCloud, you agree to our use of cookies. See our Cookie Policy.