A baker's guide to WhatsApp automation: the order lifecycle

A cake order is not an event, it is a sequence that runs for weeks: somebody enquires, a brief is agreed, a price is quoted, a deposit holds the date, a balance is paid, and eventually it is collected. Each stage can stall, and a stalled order looks exactly like a progressing one in a message thread.

Seeing the whole lifecycle at once is what makes the individual automations make sense. Built stage by stage without that view, you end up with reminders for a process nobody can see the state of.

What we'll cover

• The six stages
• What stalls at each one
• What must reach you
• Building it with CodeWords
• The order record
• The weekly view
• What never gets automated
• Starting without rebuilding everything
• Peak season, which breaks the normal shape
• Making it survive
• Limits worth knowing about
• What to build first
• Frequently asked questions

The six stages

Enquiry, which is somebody asking whether you can do something.

Brief, where the date, size, flavour, allergens and design are established.

Quote, a price for that brief with what it includes.

Deposit, which holds the date and converts an intention into an order.

Production, where the order is a job rather than a conversation.

Collection, which is the end and the beginning of the next one.

Name them, because the value of this whole article is being able to say which stage an order is at.

What stalls at each one

Enquiry: no reply, or a reply too late to matter.

Brief: a question asked and never answered, usually the date or the allergens.

Quote: sent and never followed up.

Deposit: requested and never chased, holding a date for nobody.

Production: nothing stalls here, which is why it needs no automation.

Collection: a wrong time, a balance unpaid, nobody arriving.

Five of six stall in a conversation, which is the argument for state living somewhere else.

What must reach you

Anything about allergens, immediately, without interpretation.

A design question, which is the part customers are paying you for.

A complaint, in any form.

A date change, since it affects capacity and everything downstream.

A cancellation, which needs a decision rather than a rule.

Anybody upset, which a message can detect and should never try to resolve.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations, and the connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: the stages, what moves an order between them, and what reaches you.
3. Authorize the connections to wherever orders are recorded, your payment provider, and your WhatsApp Business Platform account.
4. Describe the exceptions: a date at capacity, an allergen you cannot accommodate, an unpaid deposit, a design question, a complaint.
5. Run it alongside how you work now for a fortnight rather than switching.

You describe the outcome; Cody builds it, connects it, and deploys it. 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.

The order record

One per order, holding everything the lifecycle needs.

The brief: date, size, flavour, allergens, design, collection or delivery.

The images, attached rather than in a thread.

The money: quoted, deposit, balance, what is outstanding.

The stage, which is the field that makes everything else work.

Not in the conversation, which is the single structural decision this guide rests on.

The weekly view

What is being made this week, in collection order.

What is outstanding on those orders — balances, unconfirmed designs.

What has stalled: quotes unanswered, deposits unpaid, briefs incomplete.

Next week's capacity against what is booked.

Fifteen minutes on a Sunday covers all of it once the record exists.

This view is the point of the automation, more than any individual message.

What never gets automated

The design conversation, which is the craft and the reason they chose you.

Saying yes or no to an order, which is a capacity and a judgement call.

Anything about allergens beyond asking the question and recording the answer.

A complaint or a mistake, which is a person's job and frequently a phone call.

The relationship, which in this trade is most of why people return.

Pricing a bespoke piece, which depends on things only you can see.

Starting without rebuilding everything

One stage at a time, with a fortnight between.

Start where you lose most, which for most bakers is the enquiry reply or the unchased deposit.

Keep your spreadsheet if it works; add the flow into it rather than replacing it.

Do not announce a system, since customers care that you reply and remember.

Run both ways in parallel at first, which is how you find the case you did not think of.

Stop when it is enough. A solo baker does not need what a shop with three staff needs.

Peak season, which breaks the normal shape

December, wedding season and the fortnight before Mother's Day do not behave like the rest of the year, and a process tuned for a quiet March fails in them.

Capacity fills months ahead, so the enquiry that arrives in November for December is frequently already too late.

Say when you are full, publicly and early, which prevents enquiries you cannot fulfil and reads as success rather than refusal.

Open a cut-off date for orders and state it, since the alternative is declining individually for weeks.

Simplify the offer for peak periods — a shorter menu of things you can produce at volume — which is how most bakeries survive December.

Deposits matter more when the diary is full, because a cancellation at peak is a slot you could have sold ten times.

Plan the collection days deliberately, since twenty cakes leaving on one morning is a logistics problem rather than a baking one.

Making it survive

The order record is the source of truth, never the thread.

Check the stage before any automated message, since the customer may have paid or cancelled.

Have a manual route for anything unusual, which there will be.

Keep your allergen and ingredient records in a form you could show somebody.

Report the outcome: orders by stage, stalled by age, capacity used, and collections due.

Limits worth knowing about

Capacity is the ceiling, and no automation adds oven hours.

Food safety and registration duties apply regardless of how orders are taken.

Seasonal peaks change everything, particularly December and wedding season.

Some customers only use the phone, and that is the business you have.

Automation does not improve a cake, it removes the reasons an order goes wrong around it.

What to build first

Stage, as a single field on each order. Not a system, not software necessarily — just knowing whether each live order is at enquiry, brief, quote, deposit, production or collection. Everything else in this guide becomes obvious once you can see that, and almost nothing works without it.

Two habits make the difference. Keep the order record outside the conversation, since five of the six stages stall inside a thread and none of that is visible while it is happening. And look at the stalled list once a week, because a quote nobody followed up and a deposit nobody chased are the two most common lost orders in this trade and both are recoverable for the cost of one message.

Frequently asked questions

What are the stages of a cake order?

Enquiry, brief, quote, deposit, production and collection. Naming them is most of the value, because it lets you say which stage an order is at — which a message thread cannot.

Where do orders stall?

Five of the six stages: no reply to an enquiry, an unanswered question in the brief, a quote never followed up, a deposit never chased, and a collection that goes wrong. Production is the one stage that does not stall.

What must always reach me?

Allergens, design questions, complaints, date changes, cancellations, and anybody upset. Those need a person, and an automation should route rather than answer.

What should the order record hold?

The brief with date, size, flavour, allergens and design; the images attached rather than in a thread; the money quoted, deposited and outstanding; and the stage — which is the field that makes the rest work.

What does the weekly view need to show?

What is being made this week in collection order, what is outstanding on those orders, what has stalled, and next week's capacity against what is booked. Fifteen minutes covers it once the record exists.

Do I need to replace my spreadsheet?

Not necessarily. Add the flow into it rather than replacing it, and stop when it is enough — a solo baker does not need what a shop with staff needs.

What should never be automated?

The design conversation, deciding whether to accept an order, anything about allergens beyond asking and recording, complaints and mistakes, pricing a bespoke piece, and the relationship itself.

Where should I start?

Where you lose most, which for most bakers is the enquiry reply or the unchased deposit. One stage at a time with a fortnight between, running both ways in parallel at first.

How does peak season change things?

Capacity fills months ahead, so publishing a cut-off date and saying publicly when you are full prevents weeks of individual declines. Most bakeries also simplify the offer for peak — a shorter menu producible at volume.

Why do deposits matter more at peak?

Because a cancellation when the diary is full is a slot you could have sold ten times over, and it is the only period where the deposit is genuinely protecting scarce capacity rather than covering ingredients.

Related reading

• Taking custom cake orders over WhatsApp
• Where cake enquiries die
• Home bakers and the spreadsheet