Bakery order confirmations and collection reminders: the last mile

Bakeries should send two automated messages for every order: a confirmation when the order is placed and a reminder before collection. These two messages prevent the most expensive failure in a bakery, the uncollected cake. The ingredients are spent, the work is done, the day's capacity was used, and the item cannot be resold. Most bakeries send neither message reliably.

What we'll cover

• Why does an uncollected order cost the most?
• What must the confirmation contain?
• When should you send reminders?
• Building it with CodeWords
• Collection windows and the queue
• What to do when nobody arrives
• How is delivery different from collection?
• The day-of operation
• After the collection
• Making it survive
• Limits worth knowing about
• What to build first
• Frequently asked questions

Key takeaways

• An uncollected order is the most expensive failure in a bakery, and most are not deliberate.
• Send the confirmation immediately, with the date, time, address, allergen answer and anything still owed.
• Send two reminders only: a few days before, and the morning of collection.
• Message within the hour when a customer has not arrived, then phone.
• Build the reminder a few days ahead first, because it catches the misremembered date while it is still fixable.

Why does an uncollected order cost the most?

An uncollected order costs the most because every input is spent and nothing can be recovered. The cake cannot be resold, since it carries somebody else's name.

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

The labour is spent, often hours of it.

The day was used. Another order could have taken that capacity, and the cake 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 cases.

What must the confirmation contain?

The confirmation must contain the date and collection time, what was ordered, the allergen answer, the address and anything still outstanding. Send it immediately, because a confirmation days later no longer catches errors early.

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

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

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

The address. This matters for a home bakery and for a customer who ordered online.

What is still outstanding, such as the balance or a design confirmation, with a date.

When should you send reminders?

Send two reminders: one a few days before collection and one on the morning of collection. The first catches a wrong date while you can still fix it, and the second is the practical prompt.

Send no more than two. A third message is noticed on this channel, and customers who feel over-messaged stop reading the other two.

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

Ask high-value orders to confirm. The request is proportionate at the top end and excessive elsewhere.

Say who can collect if somebody else is coming. Missing this detail produces a phone call on the day.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations (CodeWords pricing page, 2026), and you make each connection once and reuse it.

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 (CodeWords pricing page, 2026). Details are on the pricing page.

Collection windows and the queue

Give customers a collection window rather than an exact time, and stagger the windows. 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 the order. This sentence makes uncollected orders manageable.

Tell customers what to expect: parking, whether to use the counter or the side door, and whether the cake is boxed.

Give transport advice for tiered cakes. One sentence about keeping the cake flat prevents a complaint that is not your fault.

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

What to do when nobody arrives

Message the customer within the hour, then phone. Many no-shows are a misremembered time, and an hour is still recoverable. A message may not be read, and a cake is worth a phone call.

Say how long you will hold the order and in what condition. This is a food safety matter as much as a commercial one.

State a policy on uncollected orders and on what happens to the balance, and give it before the day rather than after.

Do not absorb the loss silently. Silence teaches nothing and the loss repeats.

Record why each order went uncollected. A pattern usually points at the confirmation rather than the customer.

How is delivery different from collection?

A delivery slot is a promise, while a collection window is an arrangement. Delivery adds address, recipient and timing problems that collection does not have.

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

Say who will receive the order. For a venue, the recipient is often not the customer.

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

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

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

The day-of operation

The day-of operation runs on one list, in collection order, with everything outstanding visible. This list is the point of every message above, and the order record must live somewhere other than the conversation for the list to exist.

Show outstanding items: unpaid balances, unconfirmed designs and allergen notes.

Keep the list out of a chat thread, which is unreadable while decorating.

Print it or show it on a screen where the kitchen can see.

Mark orders off as they go, so you know at two o'clock what is still waiting.

After the collection

After collection, ask once how the order went, a few days later. The order ends at the counter but the relationship does not, and most bakeries stop here entirely.

Ask how it went when the customer has eaten the cake and has a view.

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

Ask permission separately before using the photograph. Sending you a picture is not consent to publish it.

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

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

Do not combine all four requests in one message. A single message with four asks reads as a demand rather than interest.

Making it survive

A reminder automation survives when it checks the order is still live before every send.

Check the order is still live before every reminder.

Never send a collection reminder for an order already collected.

Make confirmations idempotent. 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, orders collected, orders uncollected and balances outstanding on the day.

Limits worth knowing about

Automation sends messages; it does not collect orders, bake or hold food safely.

Some customers do not read messages. A phone call is the only route for them.

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

Peak periods break the pattern, particularly December and holidays.

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

Automation does not bake. Capacity on a Saturday is the real constraint.

What to build first

Build the collection reminder a few days ahead, with the date, time and address. The reminder catches the misremembered day while you can still correct it, and that misremembered day causes most uncollected orders.

Two habits make the difference. Put the collection time and the address in every reminder, since the absence of either generates the calls you are trying to avoid. And message within the hour when somebody has not arrived, 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, the cake takes fridge space and it cannot be resold because it carries somebody's name. Most uncollected orders are not deliberate: customers misremember the day or the time.

What should the confirmation contain?

Include the 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. Send it immediately, since the purpose is catching errors early.

How many reminders should I send?

Send two: one a few days before, which catches a wrong date while you can still fix it, and one on the morning of collection as the practical prompt. A third message is noticed on this channel, and customers who feel over-messaged stop reading the other two.

Should I give a collection time or a window?

Give a window, staggered so eleven cakes are not all collected at eleven. Also say how long you will hold the order, which makes the uncollected-order conversation manageable. A staggered window also keeps the counter clear, so each customer gets served without waiting behind others.

What should I do when nobody arrives?

Message within the hour rather than at the end of the day, then phone, since a cake is worth a phone call. Say how long you will hold the order 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 the cake, message on the way and photograph it on arrival.

What does the kitchen need on the day?

The kitchen needs one list in collection order with everything outstanding visible: unpaid balances, unconfirmed designs and allergen notes. Put it where staff can read it while decorating, which is not a chat thread. A printed or screen list for the day lets anyone on the team pick up an order without asking.

What does a pattern of uncollected orders tell me?

A pattern usually points at 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. Fix the wording of the confirmation first, then check whether the pattern continues.

Should I follow up after collection?

Follow up once, a few days later, when the customer has eaten the cake and has a view. Ask how it went, and ask permission separately before using any photograph they send. The follow-up also gives the customer an easy way to raise a problem privately.

What is the easiest order next year?

The easiest order is 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 takes the least effort of any enquiry. Ask permission before storing the date, and send one short message a few weeks ahead.

Related reading

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