Order management for small bakeries: custom orders and lead times

A small bakery needs order management that captures every custom order once, in one list, with a deposit, a lead time check, a collection slot and a visible allergy field. Without that, a notebook and a phone eventually lose an order, and a lost Saturday cake is not a refund problem, it is somebody's wedding.

A bakery order is a small project. The specification arrives in pieces over several messages, the lead time is measured in days, and the date cannot move. This page covers what a small bakery can automate and what needs a person.

What we'll cover

• Why bakery orders are harder than they look
• Taking the order properly
• Deposits and the no-show order
• Lead times and capacity
• Collection day
• Allergens, which are not an automation problem
• The quiet revenue in repeat occasions
• A week, ordered properly
• Frequently asked questions

Key takeaways

• A structured order form that captures the full specification once is the most valuable change for a small bakery.
• A deposit on confirmation filters out enquiries that were never going to become orders.
• Capacity should be capped per collection day, and the form should close a date automatically when it is full.
• Automation should capture and display allergy information, and a person should answer every allergy question.
• Recording the occasion with each order lets the bakery contact the customer before the next birthday or anniversary.

Why bakery orders are harder than they look

Bakery orders are harder than ordinary retail orders for four reasons: the specification arrives in fragments, the date is immovable, orders arrive across several channels, and each order carries high consequences.

• The specification arrives in fragments. A customer messages about a cake, sends a photograph two days later, remembers it must be nut-free, then asks about a different colour. The complete picture exists only in someone's head.
• The date is immovable. A birthday cannot move because a supplier was late, so lead time and capacity are real constraints.
• Orders arrive across channels: Instagram, WhatsApp, Facebook, email, the website and walk-ins. One order can begin on one channel and continue on another.
• Volumes are small and stakes are high. A bakery with ten orders a week cannot tolerate losing one, since each order carries a meaningful share of revenue and an occasion the customer cares about.

For these reasons a bakery outgrows a notebook faster than its volume suggests.

Taking the order properly

To take an order properly, capture the full specification once, completely, in one place. This is the single most valuable change.

• Use a structured form for custom orders, even when the conversation starts in a message. Ask for the date, collection or delivery, size or servings, flavour, design, inscription, allergies, budget and contact number. A form collects all of it, while a conversation collects what the customer thought to mention.
• Send the form as a link from the channel where they messaged. Customers fill in a form more readily than they answer eleven questions across three days.
• Bring every channel into one list and record the source. The orders that get lost sit on the channel nobody checked that day.
• Confirm the specification in writing, in a single message, before any money changes hands. This prevents the Saturday morning conversation where the customer expected something different.
• Keep the photographs with the order. A reference image sent in a chat two weeks ago must be attached to the order, not found by scrolling.

Deposits and the no-show order

A deposit on confirmation is the commercial protection most small bakeries lack. It filters out enquiries that were never going to become orders, and it covers ingredients on orders that fall through.

• Make paying easy. Attach a payment link to the specification confirmation instead of sending a separate invoice.
• Chase the deposit automatically. An order without a deposit after a set period is not confirmed, so chase it or release it. Doing this by memory holds capacity for orders that will not happen.
• State the cancellation terms in the confirmation, before the deposit. That one sentence prevents nearly every later 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

Lead times and capacity are the constraints that make a bakery different from a shop. Set a minimum notice per product and a production cap per collection day, and let the order form enforce both.

• Encode the lead time per product. A celebration cake, a batch of cupcakes and a tiered wedding cake need different minimum notice. A form that knows this stops accepting orders you cannot make.
• Cap the day, not the week. Saturday is the constraint, so express capacity as how many of each item you can produce for a given collection date.
• Close dates automatically when full. Declining an enquiry is worse than the customer never seeing the slot, and it happens when the form keeps accepting orders after the day is full.
• Plan the peaks in advance. Valentine's Day, Mother's Day, Christmas and local school holidays are predictable and break the ordinary rules. Set different lead times and earlier cut-offs before the week arrives.
• Send yourself a Monday summary of what is due that week, with missing deposits and missing specification details flagged. It takes five minutes to set up and catches the order about to go wrong.

To build this, pull orders from every channel, check them against your rules, and message 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 3,000+ integrations (CodeWords integrations page, 2026). The Free plan covers light use. Pro costs $39 per month and Business costs $100 per month (CodeWords pricing page, 2026). Details are on the pricing page.

Collection day

On collection day, send a reminder the day before, a second reminder that morning, a ready message and a balance link. Collection day is when everything either works or does not.

• Remind the day before, with the slot, the address and what the customer is collecting. Customers forget orders placed three weeks earlier.
• Remind again on the morning for anything time-sensitive, which covers most bakery items.
• Tell the customer when the order is ready if the slot is flexible, so nobody waits in a small shop while you are busy.
• Confirm the balance is paid before arrival, which removes the awkward counter conversation and the queue behind it.
• Flag uncollected orders quickly. An order still on the shelf at closing time is too late to chase, so ring earlier in the afternoon.

Allergens, which are not an automation problem

Allergen decisions must stay with a person, because automating them is dangerous. Automate the capture and the visibility of allergy information, and never the judgement about it.

• Capture the allergy at intake, in a prominent field on a structured form, instead of hoping it comes up in conversation.
• Show it on every view of the order: the production sheet, the label and your own reminders. Allergy information that lives only in the original message gets missed.
• Never let an automation answer an allergy question. A customer asking whether a cake is safe for their child needs a person who knows your kitchen, your ingredients and your cross-contamination risk.
• Route those questions to a person immediately, and have the automation say that this is what it is doing.
• Keep the record of what was asked, what was answered and what was made.

The quiet revenue in repeat occasions

Repeat occasions are revenue that nearly every small bakery leaves unclaimed. A customer who ordered a birthday cake last March has a birthday this March, and nobody in the business knows, because the order is in last year's notebook.

• Record the occasion with the order: birthday, anniversary, christening, and whose.
• Message the customer a few weeks before the date comes round, asking whether they would like something again. You are the bakery that remembered.
• Keep what they ordered. Repeating a previous order takes two messages when you have the details.
• Ask for a review after collection, and skip the request for any order that went wrong.

A week, ordered properly

A week with these automations runs in a fixed order, and no moment arrives where someone realises something was missed. This is one ordinary week:

• Monday morning: a summary of every order due this week, with two flagged, one missing a deposit and one with an unconfirmed inscription. Both are chased before baking starts.
• Monday to Wednesday: new enquiries from three channels land in one list. Each gets the form, and each completed form becomes a confirmed specification with a deposit link. Enquiries that never complete the form drop out, and they were never orders.
• Thursday: Saturday's capacity fills, and the form stops accepting Saturday collections without anyone remembering to close it.
• Friday afternoon: collection reminders and balance links go out for Saturday.
• Saturday: customers arrive knowing their slot and having paid. Anything uncollected by mid-afternoon is flagged while there is time to ring.
• Sunday: review requests go to every customer whose collection went smoothly, and to nobody else.

The setup is a form, a list, some dates and a few rules.

Frequently asked questions

What should a small bakery automate first?

Automate the structured order form and one shared list for every channel first. It takes an afternoon, it prevents the failure that hurts most, and everything else on this page depends on capturing the order properly in one place.

Do we need dedicated bakery software?

No, not necessarily. Many small bakeries run well on a form, a spreadsheet or a simple database, and a messaging channel, connected with automation. Dedicated software pays off when production scheduling becomes the constraint instead of order capture.

How do we handle orders that arrive on Instagram?

Reply where the customer messaged and move the specification to a form immediately. Capturing a full custom order in social messages is how details get lost, and customers are used to receiving a link.

Should we take deposits?

Yes, for custom orders. A deposit filters out enquiries that were never going to convert and covers ingredients on orders that fall through. State the cancellation terms at that moment to prevent later disputes.

Can automation handle allergy questions?

No. Automation should capture allergy information and show it everywhere, but a person must answer whether something is safe. Route those questions to someone who knows the kitchen immediately, and have the automated message say so.

What about wedding cakes specifically?

Wedding cakes need longer lead times, more consultation, staged payments and higher stakes. Capture and reminder automation still helps, but the consultation is the product and should stay with a person.

How do we not lose an order during a busy week?

Send a Monday summary of what is due that week, with incomplete orders flagged. It takes five minutes to build and catches an order missing a deposit or a specification detail before the day itself.

Is this worth it for ten orders a week?

Yes, though the reason is not volume. Ten orders a week feels manageable in a notebook, yet losing one is a real problem. The value is the absence of the Saturday morning when something was missed, and that value does not depend on order count.

Related reading

• Automated order confirmations and pickup reminders for bakeries
• Baker's guide to WhatsApp Business automation
• Automation tools for small business: the processes worth the effort
• CodeWords integrations and templates