How to handle last-minute order changes with WhatsApp automation

Tuesday morning. You're prepping a fondant-covered three-tier cake for Saturday. A message comes in: "Hi! So sorry to ask — could we change the flavour from vanilla to chocolate? And actually, can we add an extra tier? The family's grown." The cake is two layers in. The chocolate sponge would need a new bake. The extra tier changes the price by £30 and your Saturday production schedule by two hours.

Last-minute order changes are one of the most stressful parts of running a custom cake business. They're also almost inevitable. How you handle them — the speed of your response, the clarity of the amended order, the updated deposit — determines whether the change is a manageable bump or a chaotic scramble.

TL;DR

• Most order change stress comes from unclear communication and missing paper trails, not the change itself.
• WhatsApp automation creates a structured change request process — customers submit changes via Cody, you review with full context.
• Amended orders update your tracker automatically, with deposit adjustments sent as a follow-up.

Why order changes go wrong

An order change that arrives as a casual WhatsApp message ("oh and can we also...") is easy to overlook, misread, or forget. It exists in a chat thread alongside 40 other messages, there's no formal record, and if the deposit amount changes, the follow-up often gets lost in the same thread.

The other failure mode is agreeing to a change verbally without updating the order record. You make the amended cake, deliver a perfect product — then there's a dispute at collection because the customer remembers a different price, or the balance due doesn't match what they were expecting.

Good change management is really a documentation problem. When every change has a written trail, an amended confirmation, and a revised payment request, the chaos disappears.

Setting up a change request flow with Cody

CodeWords can handle order changes through a dedicated flow. Here's how it works:

Trigger: customer initiates a change. When an existing customer sends a message containing words like "change", "update", "amend", "different", or "mistake", Cody recognises the intent and responds with a structured prompt: "I can help with that! To make sure we update your order correctly, could you let me know: what's your order date, and what would you like to change?"

Collection: structured change details. Cody guides the customer through specifying exactly what's changing: flavour, size, date, design, delivery vs collection. Each answer is captured in a structured format rather than buried in free-form chat.

Review: flagged for your attention. The change request arrives in your dashboard (or as a message to you) with all the context: original order details, requested changes, and any pricing implications. You review, decide whether to accept the change, and respond with one click.

Confirmation: amended order sent. Once you approve, Cody sends the customer an updated order confirmation reflecting all changes. If the price has changed, a revised deposit request or balance adjustment follows immediately.

Update: order tracker refreshed. Your Airtable or Notion database row updates automatically with the new details. Your production notes are current.

How to set your change policy before automating it

Before building a change flow, you need a clear policy. Automation makes your policy consistent — but it can't define the policy for you. Consider:

Cutoff windows. When is it too late to change an order? Many cake businesses use 72 hours before pickup as the cutoff. Cody can communicate this automatically: "I'm sorry, we're unable to make changes within 72 hours of collection. For changes before this deadline, I'm happy to help."

See how CodeWords works for bakeries → codewords.ai/whatsapp-agents/bakery

Charges for changes. Does changing from vanilla to chocolate incur a fee? Does adding a tier carry a price difference? Define these clearly, and Cody can apply them automatically: "No problem — adding an extra tier will bring the new total to £X. An additional payment of £Y is required to confirm the change."

What Cody can confirm vs. what needs you. Simple changes (flavour swap, adding a name to piping, changing pickup time) can often be handled and confirmed without your involvement. More complex changes (new design, significant size increase, date change) should route to you. Set this threshold in your flow.

The paper trail that protects you

One underappreciated benefit of structured change management: it protects you when things go wrong. If a customer claims they never asked for chocolate or "didn't know" the size change would cost more, you have a timestamped WhatsApp conversation showing exactly what was requested, confirmed, and charged.

This isn't about being adversarial — most customers are acting in good faith. But having a clear record makes it easy to resolve any confusion without it turning into a dispute.

Handling date changes

Date changes are a specific challenge because they affect your production schedule, not just the order details. A customer wanting to push a Saturday order to the following Saturday might seem simple — but if you have a full Saturday already, it's not.

Cody can check availability before confirming a date change. If your Airtable calendar shows the new date is free, Cody confirms and updates. If it's full, Cody responds: "The new date you've requested is already fully booked. Could I suggest [alternative date]?" You don't have to be present for any of this.

Preventing changes before they happen

The best change management is reducing unnecessary changes in the first place. Many last-minute change requests happen because the original order wasn't specific enough — the customer said "chocolate cake" but didn't think about filling until later, or forgot to mention the dietary requirement until the week of the order.

A thorough upfront intake flow (see how to take custom cake orders via WhatsApp without the back-and-forth) collects all the relevant details at booking time. When customers have to answer every question specifically — flavour, filling, dietary needs, design, personalisation — they think more carefully at the start. The result is fewer surprises later.

Also relevant: automated order confirmations and pickup reminders for bakeries — a detailed confirmation at order time gives the customer a chance to spot errors before it's too late to fix them easily.

For the complete automation picture for bakeries, the WhatsApp agents for bakeries page is a good starting point.

Start with the most common change type

If you're setting up change management automation for the first time, start with the single most common change request you get. For most cake businesses, that's a date change or a flavour change. Build a flow specifically for that, test it for a month, then expand to cover other change types.

Try CodeWords free and build your first change request flow without writing a line of code.