A catering order without a deposit is not a sale. It's a reservation, and reservations get cancelled.
That distinction matters most on the jobs you are gladdest to get. A 200-person order that lands three weeks out looks like a great week until it disappears on the Thursday, after you bought forty pounds of protein you now have to move, and after you scheduled two extra prep hands and told a smaller customer you were full that day. The deposit is not there to make you money. It exists so that a cancellation costs the customer something proportional to what it costs you.
Work out what you actually lose when a job cancels
Before picking a percentage, price the cancellation. There are three real losses and they are not the same size.
The first is product you bought specifically for the job and cannot sell through normal service. Specialty proteins, a case of something you don't otherwise stock, custom cake work, rentals. This is often the largest number and it's the one you can put an exact figure on by looking at the purchase order.
The second is scheduled labor. If you brought in prep hands or held a driver, you either pay them or you burn goodwill sending them home.
The third is the business you turned away, and this one is invisible so operators skip it. If you told two other callers you were booked that Saturday, the cancellation cost you those orders too, and you'll never see them show up on a report.
Add the first two, take a view on the third, and you have the floor your deposit needs to cover. That number, not a percentage you read somewhere, is where the policy starts.
The number most operators land on
In practice, 25 to 50 percent of the estimated total is the common range, with a flat minimum, something like $100, so a small job isn't governed by a percentage of almost nothing.
Toward the low end when the food is standard menu items you could sell anyway, the date is far out, and the customer has ordered before. Toward the high end when the order requires product you don't normally carry, when it's on a date you could otherwise fill easily, or when the customer is new to you.
A corporate account that orders lunch every second Tuesday does not need a 50 percent deposit and will be irritated by one. Keep a card on file for those and skip the ceremony. A first-time caller booking a wedding on a Saturday in June is exactly the case the deposit exists for.
Set a dollar threshold below which no deposit applies at all. Somewhere around $500 is common. Under it, a card on file and a confirmation is enough friction.
One more variable: the date. A Saturday in wedding season is worth more to you than a Wednesday in February, and your deposit can say so. Operators who run a flat percentage year-round are effectively underpricing their scarcest dates, which is why the cancellations that hurt most always seem to land on the days you could most easily have filled.
Write the cancellation deadline as a date, not a duration
This is where the money is actually won or lost, and most policies get it wrong by being vague.
"Cancellations more than 72 hours in advance receive a full refund" sounds precise and isn't. Seventy-two hours before what, the delivery time or the event? Do weekends count? The customer will read it generously and you will read it strictly, and you will both be reading in good faith.
Put an actual timestamp on the confirmation. "This deposit becomes non-refundable at 2pm on Thursday, June 12." Nobody misreads that.
The deadline should sit where your own commitment sits, which is when you place the order with your purveyor. For most kitchens that's two to three days out. If you're ordering specialty product a week ahead, your deadline is a week, and you should say so at the time of booking rather than discovering the mismatch during an argument.
Taking the money during the call, not after it
The common failure is not the policy. It's that the deposit gets taken later. Someone books the job on Tuesday, the deposit is meant to follow by invoice, the invoice gets sent Thursday, and by the following week you have a confirmed catering order on the calendar with no money against it. Now the deadline you wrote down protects nothing.
Take it on the call. That means a card-not-present payment where the number goes straight to your processor and is stored as a token rather than being written on a pad, read into a transcript, or held in someone's memory until they get to a terminal. The mechanics of that are the same as any phone payment and are worth understanding before you set the policy, because the storage question is where the compliance exposure lives. Both collecting payment over the phone safely and phone payment tokenization explained cover what actually happens to the card number.
Then send a written confirmation immediately, by email or text, containing the order, the total estimate, the deposit taken, and the timestamped cancellation deadline. Keep the send record. If a deposit is ever disputed, that message is your entire case.
What to hand to software and what to keep for a manager
A voice agent handles the mechanical half of this well. It can quote your deposit rule, take the payment through the same tokenized path as any other card order, and send the confirmation without anybody remembering to do it. That last part alone closes the most common leak, since the deposit that never gets collected is almost always the one that depended on a busy person following up.
What it should not do is negotiate. A caller asking whether the deposit can be waived, or whether the deadline can move because their event date might shift, is asking a business question with money attached. That's a manager call, and your escalation rules should route it as one.
The larger pattern holds across catering generally: qualify and capture on the call, decide the terms with a person. That split is the same one described in voice AI for large catering orders and in how catering lead qualification works when the inquiry comes in cold.
The version to put on your catering sheet tonight
Three lines. The dollar threshold where a deposit applies. The percentage, with a flat minimum. The rule that the cancellation deadline is written as a specific date and time on every confirmation, tied to the day you place your purveyor order.
Then test it against the last catering job you lost. If your policy as written would have recovered your product cost on that specific cancellation, the numbers are right. If it wouldn't have, raise them until it does.