Bakery order confirmations and collection reminders: the last mile

A cake that is made and not collected is worse than an order never taken. The ingredients are spent, the work is done, the space in the day was used, and the item cannot be resold. It is the most expensive single failure in a bakery and it is almost entirely preventable with two messages.

Those two messages — the confirmation when the order is placed and the reminder before collection — carry more operational weight than anything else in this article, and most bakeries send neither reliably.

What we'll cover

• Why an uncollected order costs most
• What the confirmation must contain
• When to remind
• Building it with CodeWords
• Collection windows and the queue
• When nobody arrives
• Delivery, which is a different problem
• The day-of operation
• After the collection
• Making it survive
• Limits worth knowing about
• What to build first
• Frequently asked questions

Why an uncollected order costs most

The ingredients are gone, and for a custom cake they are not cheap.

The labour is spent, frequently hours of it.

It cannot be resold, since it says somebody else's name on it.

It occupied the day that another order could have used.

It takes fridge space you need for tomorrow.

Most are not deliberate. People misremember the day, the time, or who was collecting — which is why two messages fix most of it.

What the confirmation must contain

The date and the collection time, stated plainly rather than implied.

What was ordered, in enough detail that they would notice a mistake.

The allergen answer, restated, since that is the moment to catch a misunderstanding.

The address, which sounds unnecessary and is not for a home bakery or a customer who ordered online.

What is still outstanding — the balance, a design confirmation — with a date.

Sent immediately, since a confirmation days later has lost the purpose of catching errors early.

When to remind

A few days before, which is the one that catches a wrong date while it can still be fixed.

The morning of, which is the practical prompt.

Not more than two, since this is a channel where a third message is noticed.

Include the time and the address again, because that is what people actually need in the moment.

Ask them to confirm for high-value orders, which is proportionate at the top end and excessive generally.

Say who can collect if somebody else is coming, which is the detail that produces a phone call on the day.

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: when the confirmation goes, when the reminders go, and what happens if nobody collects.
3. Authorize the connections to wherever orders are recorded and your WhatsApp Business Platform account.
4. Describe the exceptions: an unpaid balance, a delivery rather than a collection, a changed date, nobody arriving.
5. Run it against a week of orders and check what each customer would have received.

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.

Collection windows and the queue

Give a window rather than a time where you can, since a bakery on a Saturday morning is not a place for precision.

Stagger the windows so that eleven cakes are not all collected at eleven.

Say how long you will hold it, which is the sentence that makes the next section manageable.

Tell them what to expect — parking, whether to come to the counter or the side door, whether the cake is boxed.

Transport advice matters for tiered cakes, and a sentence about keeping it flat prevents a complaint that is not your fault.

Confirm collection when it happens, which closes the order and stops a reminder going out afterwards.

When nobody arrives

Message within the hour, not at the end of the day, since many are a misremembered time.

Then call, because a cake is worth a phone call and a message may not be read.

Say how long you will hold it and in what condition, which is a food safety matter as much as a commercial one.

Have a stated policy on uncollected orders and what happens to the balance, given before the day rather than after.

Do not simply eat the loss silently and say nothing, which teaches nothing and repeats.

Record why, since a pattern in uncollected orders usually points at the confirmation rather than the customer.

Delivery, which is a different problem

A delivery slot is a promise in a way a collection window is not.

Confirm the address the day before, since people move, and a wedding venue is not a home address.

Say who will receive it, which for a venue is frequently not the customer.

Message on the way, which prevents the call asking where it is.

Photograph it on arrival, which resolves the dispute about condition before it starts.

Set a time window rather than a time, and tell them if it moves.

The day-of operation

One list, in collection order, which is what the morning actually runs on.

Everything outstanding visible: unpaid balances, unconfirmed designs, allergen notes.

Not in a chat thread, which is unreadable while decorating.

Printed or on a screen somewhere the kitchen can see.

Mark them off as they go, which is how you know at two o'clock what is still waiting.

This list is the point of everything above, and it is the reason the order record has to live somewhere other than the conversation.

After the collection

The order ends at the counter and the relationship does not, and this is the point at which most bakeries stop entirely.

Ask how it went, once, a few days later — which is when they have eaten it and have a view.

Ask for a photograph, since customers take them anyway and a real cake at a real party is worth more than a studio shot.

Ask permission separately before using it, because sending you a picture is not consent to publish it.

Ask for a review at the same moment, when the feeling is fresh, rather than weeks later.

Note the occasion, since a birthday recurs annually and a customer who liked the cake is the easiest order next year.

Do not do all four in one message, which reads as a demand rather than an interest.

Making it survive

Check the order is still live before every reminder.

Never send a collection reminder for something already collected.

Make confirmations idempotent, since a duplicate confirmation makes customers doubt the order.

Handle the changed collection date, which is common and affects both reminders.

Report the outcome: orders due, reminders sent, collected, uncollected, and balances outstanding on the day.

Limits worth knowing about

Some customers will not read messages, and a phone call is the only route.

Food safety limits how long you can hold an uncollected item, which is not a commercial decision.

Peak periods break the pattern, particularly December and around holidays.

Delivery adds a whole category of failure that collection does not have.

Automation does not bake, and capacity on a Saturday is the real constraint.

What to build first

The collection reminder a few days ahead, with the date, time and address. It catches the misremembered day while it can still be corrected, which is the cause of most uncollected orders — and an uncollected order is the single most expensive thing that happens in a bakery week.

Two habits make the difference. Put the collection time and the address in every reminder, since that is what people actually need and the absence of it generates the calls you are trying to avoid. And message within the hour when somebody has not arrived rather than at the end of the day, because most no-shows are a misremembered time and an hour is still recoverable.

Frequently asked questions

Why is an uncollected order the worst outcome?

The ingredients are spent, the labour is done, the day was used, it takes fridge space, and it cannot be resold because it has somebody's name on it. Most are not deliberate — people misremember the day or the time.

What should the confirmation contain?

Date and collection time stated plainly, what was ordered in enough detail to spot a mistake, the allergen answer restated, the address, and anything still outstanding with a date. Sent immediately, since the purpose is catching errors early.

How many reminders should I send?

Two: a few days before, which catches a wrong date while it can still be fixed, and the morning of as the practical prompt. A third is noticed on this channel.

Should I give a collection time or a window?

A window, staggered so eleven cakes are not all collected at eleven — and say how long you will hold it, which makes the uncollected conversation manageable.

What should I do when nobody arrives?

Message within the hour rather than at the end of the day, then call, since a cake is worth a phone call. Say how long you will hold it and in what condition, which is a food safety matter as well as a commercial one.

How is delivery different?

A delivery slot is a promise rather than a window. Confirm the address the day before since people move and venues are not home addresses, say who will receive it, message on the way, and photograph it on arrival.

What does the kitchen actually need on the day?

One list in collection order with everything outstanding visible — unpaid balances, unconfirmed designs, allergen notes — somewhere readable while decorating, which is not a chat thread.

What does a pattern of uncollected orders tell me?

Usually something about the confirmation rather than the customers. Record the reason each time, and the cause tends to be a time or date that was never stated plainly.

Should I follow up after collection?

Once, a few days later, when they have eaten it and have a view. Ask how it went, and separately ask permission before using any photograph they send — sending you a picture is not consent to publish it.

What is the easiest order next year?

The same occasion for the same customer. Noting that a cake was for a birthday makes an annual reminder possible, and a customer who liked last year's cake is the least effort of any enquiry you will handle.

Related reading

• Collecting bakery deposits and payments
• Taking custom cake orders over WhatsApp
• A baker's guide to WhatsApp automation