A Cake Booked Without Money Is an Intention
And intentions cancel the week before — usually the week you turned down two other orders for. Here’s the small set of habits that turns a friendly yes into an actual booking.
There’s a particular kind of loss in custom baking that doesn’t look like a loss at all. Someone books a cake for a date eight weeks out. You block the weekend. You turn away two other enquiries for it, politely, because you’re full. And then, ten days before, they message to say something’s changed. No deposit was taken, so nothing is owed, and you’re left with an empty weekend that had two paying orders in it a month ago. Nobody behaved badly. It just turns out that a booking without money attached isn’t really a booking — it’s an intention. A cake deposit policy is the difference between the two, and it’s one of a small handful of habits that separate a hobby taking orders from a business.
Why deposits matter more in cake than almost anywhere else
Plenty of businesses take deposits. Very few have quite this combination of factors:
The capacity is genuinely scarce. You have around fifty weekends a year, and a booked one has been withdrawn from sale. That’s completely different from a shop holding an item that anyone else could still buy.
The date is fixed and unrepeatable. The wedding is on the 12th. You can’t sell that Saturday afterwards. A late cancellation doesn’t cost you a delayed sale; it costs you the sale entirely.
The costs start early. Toppers ordered, ingredients bought, a bespoke topper commissioned. Some of that money is gone whether or not the cake happens.
And cancelling is emotionally cheap for the customer when nothing has been paid. A deposit doesn’t only compensate you — it changes the psychology of the arrangement, for both sides. People honour bookings they’ve paid toward.
That last point is the real function. Most bakers who introduce deposits report fewer cancellations, not more compensation.
The flag that makes it real
The awkward part isn’t deciding to take deposits — nearly everyone agrees with that. It’s noticing when one hasn’t arrived.
The pattern is familiar: you agree the order, you say you’ll send the deposit details, life happens, and three weeks later the weekend is blocked and no money has moved. Nobody was avoiding it; it just fell through a gap between a friendly conversation and an admin task nobody owns.
A simple flag fixes it: any confirmed order holding less than your minimum deposit gets marked. Then a five-second glance tells you which of your “bookings” are actually secured, and which are still intentions occupying real weekends.
What you do about it is your call — chase it, or move the order back to “quoted” until it’s paid. But you can only make that call if you can see it.
Get Diginesian’s stories in your inbox
Join Medium for free to get updates from this writer.
The same mechanism handles the other quiet leak: balance due. Custom cakes are often paid in two parts, and the final balance is the one that gets forgotten in the rush of delivery week. A running balance per order, and a total, means you’re never doing that arithmetic in the car park.
Rush orders: charge for it, or decide not to
The other habit worth building is around short-notice work — and the framing matters here.
Someone asks for a cake inside your normal lead time. It’s flattering, you probably can squeeze it in, and you say yes in a friendly message. Then on Thursday you remember that “squeezing it in” means reordering your entire week, possibly paying express shipping on a topper, and definitely working an evening you’d planned to have off. And you’re doing it at your standard price, because the moment to mention a rush fee was in the friendly message and it passed.
A rush flag isn’t there to make you refuse. It’s there so the decision happens at the point of quoting rather than in hindsight. Then you have three honest options: charge a rush fee, do it as a favour knowing exactly what you’re giving, or decline. All three are fine. What isn’t fine is discovering on Thursday that you accidentally chose the second one.
The same applies to delivery, setup, and anything else that’s easy to agree to in conversation and expensive to deliver in practice. If it costs you time, it belongs in the quote — and quoting consistently, from a set list of prices and add-ons, is what stops the same cake getting two different prices depending on how the conversation went.
The schedule that survives a change of plan
The last piece is the one that saves your actual week.
Custom cakes are made backwards from a fixed date, in a defined sequence: confirm the details, order anything that needs ordering, shop, bake and freeze the sponges, make the buttercream, fill and crumb coat, final coat, decorate, box, deliver. Each step has to happen a certain number of days before the event, and the sequence is genuinely unforgiving — you can’t decorate a cake you haven’t baked.
Most bakers hold this in their heads or write it on a calendar. Both work perfectly until the first change of plan — and there is always a change of plan. The wedding moves. The party shifts to the Sunday. And a handwritten timeline is now wrong at every single step, with no realistic prospect of anyone re-deriving it in the middle of a busy fortnight.
That’s exactly the sort of thing that should recalculate. Change the event date, and every step moves with it. Which also means that when three orders land in the same week, you can see the collisions — the two Thursdays that both want to be decorating day — while there’s still time to shift one.
An important note
To be clear: this is a general perspective on running an order book. It is not food safety, allergen, legal, tax, accounting, insurance, or business advice, and it guarantees no outcome. Any prices mentioned are placeholders rather than recommendations, and cake prices vary enormously by country, city and skill level. Deposit terms, cancellation rights and consumer-protection rules differ by country — what you may keep from a deposit is a legal question where you live, not a matter of preference, so check before setting your terms. Requirements for selling food — registration, hygiene training, kitchen standards, allergen declaration, labeling, traceability, temperature control and insurance — differ substantially by country and region. Establish and comply with the rules that apply to you before you sell anything, using your own food safety authority as the source. And on allergens specifically: a shared home kitchen cannot guarantee the absence of traces, “may contain” is an honest answer, and nobody should ever guess.
If you want the flags built in
I built deposit and rush flags into my home bakery order tracker in Google Sheets — any confirmed order holding less than your minimum deposit is marked, anything falling inside your lead time is flagged as rush, balances calculate per order and in total, and a twelve-step bake schedule re-dates itself the moment an event date changes:
👉 Cake Order Form & Home Bakery Tracker for Google Sheets & Excel
Whether you use mine or a notebook, take a deposit, flag the rush jobs at quoting time, and keep a schedule that can survive someone moving a wedding. None of it makes you less generous — it just means the generosity is something you chose, rather than something that happened to you on a Thursday. Say yes on purpose. 🧁
This reflects my own perspective and describes a planning tool — NOT food safety, allergen, legal or business advice, and it guarantees no outcome; deposit and cancellation rules differ by country, and food-selling requirements differ by country and region — check with your own food safety authority. Never guess about an allergen. Bakers: what changed for you when you started taking deposits? Tell me in the comments.
