Catering orders without the notebook: from booking to final invoice
Where caterers lose money between the first phone call and the final invoice, a booking checklist, an illustrative event costing, and how to run the whole chain in one place.
- Playbooks
- 9 min read
- By Team Bhookly
Catering order management means keeping one record of each event from the first enquiry to the final invoice: who booked, what they ordered and at what price, what has been paid, what the kitchen must cook, what went out to the venue and what the event really cost. Most caterers keep those six things in six places, usually a notebook, a WhatsApp thread, the cashier's memory and the chef's head. Money is lost in the gaps between them. Putting the record in one place, and making the kitchen cook from that record and nothing else, fixes most of it.
Key takeaways
- Caterers lose money in five predictable places: deposits mixed into the till, the kitchen cooking from an old version of the order, quantities guessed, equipment left at venues, and no figure for what the event cost.
- Take every booking against the same checklist, and write down the price and the guest count the customer agreed to, with the date they agreed.
- Keep event money apart from the day's sales. A deposit taken today for an event next month is not today's revenue.
- Cost every event afterwards. Quoted price minus recipe cost is a forecast. What was actually used, wasted and left behind is the result.
- Bhookly carries a booking from Enquiry to Closed, with deposits, a kitchen plan in one tap, recipes scaled to the guest count, returnable equipment and an after-event wrap-up.
Where do caterers lose money?
Deposits mixed into the till
A customer pays a deposit at the counter and the cashier puts it in the drawer. That night the till is over by exactly that amount, or the deposit is rung up as a sale and the day's revenue is overstated. A month later nobody is sure how much was paid. Event money needs its own ledger: deposits, further payments and refunds per booking, with the balance always visible.
The kitchen cooking from an old version of the order
The customer rings on Tuesday to raise the count from 100 to 120 and swap one dish. The owner updates the notebook. The chef's printed sheet still says 100, with the old dish. The mistake is discovered at the venue, where it cannot be fixed. The rule: there is one order, and the kitchen's plan is produced from it every time it changes.
Quantities guessed
A chef who cooks a dish for six every day does not automatically know what 120 portions needs. The result is either a second trip to the market on the morning of the event, at whatever price the market asks, or trays of leftovers that were paid for and thrown away. Written recipes, scaled by arithmetic and checked against what the store already holds, remove the guess.
Equipment left at venues
Chafing dishes, serving spoons, crates, urns and tablecloths go out on the van. Some come back. A missing dish is noticed weeks later when the next event needs it, and by then nobody knows which venue has it. Every returnable item should be listed against the event when it leaves and ticked when it returns.
No idea what the event really cost
Most caterers know what they charged. Few know what the event cost, because the ingredients came out of the same store as the restaurant's daily stock and the leftovers went back into the same fridge or into the bin. Without a wrap-up, next year's quote is based on last year's guess.
What should a catering booking record?
- Customer name, phone number and who to call on the day if it is someone different.
- Event date, serving time and the time the food must leave the kitchen.
- Venue, with an address or a map pin, and any access notes such as stairs, a lift or a loading time.
- Guest count, and the date by which the customer can still change it.
- Dishes and quantities, with any price agreed specially for this event.
- Dietary notes and special requests, written in the customer's own words.
- Deposit taken, the method, the date and who received it.
- Balance due and when it is to be paid.
- Equipment going out that has to come back.
- A stage for the booking, so anyone can see whether it is an enquiry, confirmed, delivered or closed.
The stage matters: an enquiry that was never confirmed should not reach the kitchen, and a delivered event with a balance owing should not be forgotten.
How do you work out what an event really cost?
Start from what the recipes say the menu should have used at the guest count, then add what happened in reality. The table below is an illustrative example for a 120-guest buffet. The figures are made up to show the method, and they are not benchmarks.
| Line | Amount (illustrative) | Where the number comes from |
|---|---|---|
| Price agreed with the customer | Rs 288,000 | The booking: 120 guests at Rs 2,400 a head |
| Ingredients the recipes called for | Rs 96,000 | Each dish's recipe scaled to 120 |
| Ingredients used beyond the recipes | Rs 7,500 | What left the store, less what the recipes called for |
| Packaging and disposables | Rs 11,000 | Boxes, foil and trays listed on the plan |
| Extra staff for the day | Rs 18,000 | Wages paid for the event |
| Transport | Rs 6,000 | Van hire and fuel |
| Equipment that did not come back | Rs 8,500 | One chafing dish still out at the venue |
| Total event cost | Rs 147,000 | Sum of the cost lines |
| Left over towards rent, salaries and profit | Rs 141,000 | Price less total event cost |
Illustrative figures only, for a made-up 120-guest event. Replace every line with your own numbers.
Two lines in that table are invisible to a caterer who works from a notebook: the ingredients used beyond the recipes and the equipment that did not come back. In this example they come to Rs 16,000, which is more than one in every ten rupees of the event's cost. The wrap-up should also record the leftovers: food sent back to the store reduces the cost of the event, and food thrown away does not.
How does Bhookly handle a catering order from booking to invoice?
Bhookly keeps the whole chain on one booking, from the first enquiry to the wrap-up after the event.
Booking stages
A catering booking holds the customer, date, venue, guest count, dishes, special prices and notes. It moves from Enquiry to Confirmed to Delivered to Closed, and keeps a history of every change, so the question “who changed the count, and when?” has an answer.
Deposits, balance and PDFs
Deposits, further payments and refunds are recorded against the booking, and the balance due is always shown. An invoice and a receipt print as PDFs. Catering money is kept apart from the till, so a deposit taken at the counter never distorts the day's cash-up.
Send to kitchen
One tap on “Send to kitchen” turns the booking into a production plan. If the booking changes later, the plan updates, so the kitchen never works from an old version of the order. Event dishes also appear in a catering lane on the kitchen display days ahead, with a countdown and the recipe at the event's quantity, so event cooking and walk-in service share one screen.
Plan cooking with scaled recipes
The plan lists what will be cooked for the date. Bhookly works out every ingredient and every prep item, such as a gravy or a dough made in-house, and compares the total with what the kitchen and the store already hold. The recipe card on the kitchen screen opens at the event's quantity and shows amounts the way a kitchen scale reads them, such as 1.5 kg or 250 g, so nobody does the arithmetic for 120 in their head. The plan can also be printed as a production sheet for the wall.
Packaging and returnable equipment
Boxes, foil and chafing dishes are added to the same plan. Returnable items are tracked as sent, back or still out, which is how the missing dish is noticed the day after the event and not the week before the next one.
Change a plan
When the guest count changes, the new numbers show what is needed more or less than before, and a top-up request goes to the store. A last-minute change is absorbed without a round of phone calls.
After-event wrap-up
After the event, the wrap-up compares what the recipes said with what was actually used, and splits the leftovers into keep, send back or throw away. That gives the true cost of the event, ready to set against the price on the booking. The Catering and Production Planning module pages cover each screen.
Frequently asked questions
What is catering order management?
Catering order management is the practice of keeping one record of each event from enquiry to final invoice. It covers the booking details, the price agreed, deposits and balance, the kitchen's cooking plan, the packaging and equipment that go out, and a costing after the event.
Should a catering deposit go through the till?
No. A deposit for a future event is not that day's sale, and putting it in the till makes the drawer over and the day's revenue wrong. Record it against the booking in a separate ledger. Bhookly keeps catering deposits, payments and refunds apart from the till and shows the balance due on each booking.
How do I scale a recipe for a large event?
Write the recipe per portion or per batch, multiply every ingredient by the number needed, then check the total against what is already in stock before buying. Bhookly does this from the production plan: recipes are scaled to the event's quantity, prep items are included, and the totals are compared with what the kitchen and the store hold.
How does Bhookly keep the kitchen on the latest version of a catering order?
Bhookly builds the kitchen's production plan from the booking itself. “Send to kitchen” creates the plan in one tap, and later changes to the booking update the plan and show what is needed more or less, with a top-up request sent to the store.
How do I stop losing catering equipment at venues?
List every returnable item against the event when it leaves and tick it off when it comes back, the same day. Bhookly adds packaging and equipment to the production plan and tracks returnable items as sent, back or still out.
How do I know if a catering event made money?
Compare the price with what the event really used, including the extras the recipes did not predict. Bhookly's after-event wrap-up sets what the recipes said against what was used and splits leftovers into keep, send back or throw away, which gives the true cost of each event.
The bottom line
Catering goes wrong in the hand-offs: from the customer to the notebook, from the notebook to the kitchen, from the kitchen to the van, and from the van back to the store. Keep one record per event, separate event money from the till, cook only from the current order and cost every event afterwards. Bhookly holds that record from the first enquiry to the wrap-up, so the booking, the deposit, the cooking plan and the final invoice always agree.