Order management for small bakeries: custom orders and lead times
Bakery orders arrive by message, need a deposit, have a lead time and a collection slot, and sometimes carry an allergy. What to automate, and what must stay with a person.
Rebecca Pearson11 min read
On this page
A bakery order is a small project. It has a specification that arrives in pieces over several messages, a lead time measured in days, a deposit, a date that cannot move, a collection slot, and occasionally an allergy that changes everything.
Most small bakeries manage this in a notebook and a phone, which works until it does not, and the failure is expensive in a way few businesses experience: a cake for Saturday that nobody made is not a refund problem, it is somebody's wedding.
What we'll cover
Why bakery orders are harder than they look
Four things distinguish this from ordinary retail.
The specification arrives in fragments. A customer messages about a cake, then sends a photograph two days later, then remembers it needs to be nut-free, then asks whether you can do a different colour. Each fragment lands wherever it was sent, and the complete picture exists only in somebody's head.
The date is immovable. A birthday cannot be rescheduled because a supplier was late. This makes lead time and capacity genuinely constraining rather than merely inconvenient.
Orders arrive across several channels. Instagram, WhatsApp, Facebook, email, the website, and people walking in. A single order can begin on one and continue on another.
Small numbers, high consequence. Ten orders a week, each carrying a meaningful share of revenue and an occasion somebody cares about. The tolerance for losing one is essentially zero.
That combination is why a bakery outgrows a notebook faster than the volume suggests.
Taking the order properly
The single most valuable change is getting the specification captured once, completely, in one place.
Use a structured form for custom orders, even if the conversation starts in a message. Date required, collection or delivery, size or servings, flavour, design, inscription, allergies, budget, and contact number. A form gets all of it; a conversation gets whatever the customer thought to mention.
Send the form as a link from wherever they messaged. Customers will happily fill in a form; they will not happily answer eleven questions across three days of messages.
Bring every channel into one list. Whatever arrives, on whichever platform, should land in one place with the source recorded. The orders that get lost are the ones on the channel nobody checked that day.
Confirm the specification back to them in writing. Everything you have understood, in a single message, before any money changes hands. This is the step that prevents the Saturday morning conversation where the customer expected something different.
Keep the photographs with the order. A reference image somebody sent in a chat two weeks ago needs to be attached to the order, not findable by scrolling.
Deposits and the no-show order
The commercial protection most small bakeries lack and most need.
Take a deposit on confirmation. It filters the enquiries that were never going to become orders, and it covers the ingredients on the ones that evaporate.
Make paying easy from the confirmation message. A payment link attached to the specification confirmation converts far better than an invoice sent separately.
Chase it automatically. An order without a deposit after a set period is not confirmed, and it should either be chased or released. Doing this by memory means holding capacity for orders that will not happen.
Be clear about what happens on cancellation, in the confirmation, before the deposit. That sentence prevents nearly every subsequent dispute.
Release unconfirmed slots on a schedule. Capacity held for an order that never firmed up is capacity you could have sold, particularly in a busy week.
Lead times and capacity
The constraint that makes a bakery different from a shop.
Encode the lead time per product. A celebration cake, a batch of cupcakes and a tiered wedding cake have different minimum notice. A booking form that knows this stops accepting orders you cannot make.
Cap the day, not the week. Saturday is the constraint, not the seven days around it. Capacity should be expressed as how many of each thing you can produce for a given collection date.
Close dates automatically when full. The enquiry you have to decline is worse than the slot the customer never saw, and it happens because the form was still accepting orders after the day was full.
Handle the peaks deliberately. Valentine's, Mother's Day, Christmas and the local school holidays are predictable and they break the ordinary rules. Different lead times, earlier cut-offs, and a decision made in advance rather than during the week itself.
Warn yourself before the week arrives. A summary each Monday of what is due that week, with anything missing a deposit or a specification detail flagged, is five minutes of automation and it is the check that catches the order about to go wrong.
Building that means pulling orders from wherever they arrived, checking them against your rules, and messaging the right people at the right times. On CodeWords you describe it in plain language — which channels, what makes an order complete, when to chase, what to flag — and Cody, the automation builder, builds it, connects it to your systems, and deploys it. Automations connect to more than 3,000 integrations. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.
Collection day
The day everything either works or does not.
Remind the day before, with the collection slot, the address and what they are collecting. Customers forget, particularly for orders placed three weeks earlier.
Remind again on the morning for anything time-sensitive, which for a bakery is most things.
Tell them when it is ready if the slot is flexible. A customer arriving to wait is a customer standing in a small shop while you are busy.
Confirm the balance is paid before they arrive rather than at the counter, which removes the awkward conversation and the queue behind it.
Flag uncollected orders quickly. An order still sitting at the end of the day needs a call, and it is the sort of thing that gets noticed at closing time when it is too late to do anything.
Allergens, which are not an automation problem
Worth a section on its own, because this is the one place where automating too much is dangerous.
Capture the allergy at intake, prominently. A structured form with an explicit allergy field is far better than hoping it comes up in conversation.
Make it visible on every view of the order. On the production sheet, on the label, in the reminder to yourself. Allergy information that lives only in the original message is allergy information that will be missed.
Never let an automation answer an allergy question. A customer asking whether something is safe for their child needs a person who knows your kitchen, your ingredients and your cross-contamination risk. An automated reassurance is a category of mistake with consequences no efficiency gain justifies.
Route those questions to a person immediately and have the automation say that is what it is doing.
Keep the record. What was asked, what was answered, what was made. This matters if anything ever goes wrong.
The rule of thumb: automate the capture and the visibility of allergen information, and never the judgement about it.
The quiet revenue in repeat occasions
The part nearly every small bakery leaves on the table.
A customer who ordered a birthday cake last March has a birthday this March. Nobody in the business knows that, because the order is in a notebook from last year.
Record the occasion with the order. Birthday, anniversary, christening, and whose.
Remind yourself, or them, a few weeks before it comes round. A short message asking whether they would like something again for the same occasion converts remarkably well, because you are the bakery that remembered.
Keep what they ordered. Repeating a previous order is a two-message conversation when you have the details and a fifteen-minute one when you do not.
Ask for the review after collection, and suppress it for anything that went wrong.
A week, ordered properly
What the automations above add up to, across one ordinary week.
Monday morning. A summary of every order due this week, with two flagged: one missing a deposit, one where the inscription was never confirmed. Both are chased before anything is baked. Under the old arrangement, the inscription would have surfaced on Friday afternoon.
Monday through Wednesday. New enquiries arrive across three channels and all land in one list. Each gets the form; each completed form becomes a confirmed specification with a deposit link. Two enquiries never complete the form and quietly drop out, which is information rather than a loss — they were never orders.
Thursday. Saturday's capacity fills and the form stops accepting Saturday collections. Nobody has to remember to close it, and nobody has to decline a customer who had already got their hopes up.
Friday afternoon. Collection reminders go for Saturday, with slot, address and what they are collecting. The balance links go with them.
Saturday. Customers arrive knowing their slot, having paid. Anything uncollected by mid-afternoon is flagged while there is still time to ring.
Sunday. Review requests go to everyone whose collection went smoothly, and to nobody whose did not.
None of that is sophisticated. It is a form, a list, some dates and a few rules. The difference it makes is that the week contains no moment where somebody realises something has been missed.
Frequently asked questions
What should a small bakery automate first?
The structured order form and getting every channel into one list. It takes an afternoon, it prevents the failure that actually hurts, and everything else on this page depends on having the order captured properly in one place.
Do we need dedicated bakery software?
Not necessarily. Plenty of small bakeries run well on a form, a spreadsheet or a simple database, and a messaging channel, connected with automation. Dedicated software is worth it when volume makes production scheduling itself the constraint rather than order capture.
How do we handle orders that arrive on Instagram?
Reply where they messaged and move the specification to a form immediately. Trying to capture a full custom order in social messages is how details get lost, and customers are used to being sent a link.
Should we take deposits?
Almost always, for custom orders. It filters enquiries that were never going to convert and covers ingredients on the ones that fall through. Being clear about the cancellation terms at that moment prevents nearly every subsequent dispute.
Can automation handle allergy questions?
It should capture allergy information and make it visible everywhere, and it must not answer questions about whether something is safe. Those go to a person who knows the kitchen, immediately, and the automated message should say so.
What about wedding cakes specifically?
Longer lead times, more consultation, staged payments and considerably higher stakes. The capture and reminder automation still helps, and the consultation is the product and should stay entirely with a person.
How do we not lose an order during a busy week?
The Monday summary of what is due that week, with anything incomplete flagged. Five minutes to build, and it is the check that catches the order missing a deposit or a specification detail before the week starts rather than on the day.
Is this worth it for ten orders a week?
Yes, and for a different reason than volume. Ten orders a week is low enough that a notebook feels adequate and high enough that losing one is a real problem. The value here is not hours saved but the absence of the Saturday morning where something was missed, and that value does not scale with order count.